@@ -17,21 +17,21 @@ understand parts of it.
1717Core principles
1818~~~~~~~~~~~~~~~
1919Some core guidelines on the package, requirements for contributors, and the
20- practices and management of contributions.
20+ management of contributions are as follows:
2121
2222* pvlib-python is an advanced scientific modeling toolbox.
2323* Every pull request (PR) should address one or more open issues. The PR should
2424 be outlined in the issue discussion.
25- * Maintainers reserve the right to close PRs that do not comply with the
26- contributing guidelines.
2725* GSoC: For Google Summer of Code, we invite applications only from those with
2826 significnat PV modeling experience and who are motivated to join the pvlib
2927 maintainance teams
30- * A background in solar energy and/or experience in pvlib python
31- is required to effectively address some issues due to subtleties that are hard
32- to appreciate until struggling with an implementation. It is not always clear
33- which issues fall into this bucket. Don't be offended if maintainers close your
34- PR for this reason.
28+ * A background in solar energy and/or experience in pvlib python is required to
29+ effectively address some issues due to subtleties that are hard to appreciate
30+ until struggling with an implementation. It is not always clear which issues
31+ fall into this bucket. Don't be offended if maintainers close your PR for
32+ this reason.
33+ * Maintainers reserve the right to close PRs that do not comply with the
34+ contributing guidelines.
3535
3636While we welcome new contributors, reviewer capacity is limited. Therefore,
3737following the guidelines above throughout in the contributing process is
0 commit comments