-
-
Notifications
You must be signed in to change notification settings - Fork 128
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
16 additions
and
24 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,9 +20,10 @@ To become a maintainer of PyPOTS, you should | |
2. watch the repository to receive latest news from it; | ||
3. be familiar with the PyPOTS codebase; | ||
4. and have made at least one pull request merged into branch ``main`` of PyPOTS, | ||
which is not for fixing typos or improving the docs. | ||
5. join the PyPOTS community on Slack and become a member of the channel ``#dev-team``. | ||
``#dev-team`` currently is a public channel, and you don't need an invitation to join it. | ||
which is not for fixing typos or improving the docs; | ||
5. join the `PyPOTS community on Slack <https://join.slack.com/t/pypots-org/shared_invite/zt-1gq6ufwsi-p0OZdW~e9UW_IA4_f1OfxA>`_ | ||
and become a member of the channel ``#dev-team``. ``#dev-team`` currently is a public channel, and you don't need an invitation to join it. | ||
6. commit to obey our development principles; | ||
|
||
After meeting up with the above conditions, | ||
you can propose to get a maintainer role by dropping an email to `[email protected] <mailto:[email protected]>`_. | ||
|
@@ -31,3 +32,14 @@ Once you obtain the role, you'll be listed as a member on the ``About Us`` pages | |
`PyPOTS main site <https://pypots.com/about/>`_ | ||
and | ||
`PyPOTS docs site <https://docs.pypots.com/en/latest/about_us.html>`_. | ||
|
||
|
||
Our Development Principles | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
1. `Do one thing and do it well (Unix philosophy) <https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_and_Do_It_Well>`_. | ||
We're PyPOTS: we don't build everything related to time series and we don't have to, but only things related to partially-observed time series. | ||
And when we build something in PyPOTS, we're responsible and trying our best to do it well; | ||
2. `Eat our own dog food <https://en.wikipedia.org/wiki/Eating_your_own_dog_food>`_. | ||
We develop PyPOTS and we should try the best to use it in any scenarios related to POTS data. | ||
Only in this way, we can figure out how it tastes like, if it is a good toolset for users, and what other features and models should be included into PyPOTS; | ||
3. `` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters