Pull Request Review and GitHub Members¶
This document describes the procedure that the people in the “sunpy-maintainers” group must follow when merging a pull request. If in any doubt about merging a pull request, the correct course of action is to contact the Lead Developer and ask.
Each pull request must meet the following criteria before it is considered for merge:
The code must be PEP 8 compliant and meet the ill-defined SunPy quality standards. We have these in the Coding Standards page.
The PR must contain a CHANGELOG entry if it changes the behavior of any code.
The test coverage should not decrease, and for new features should be at or very close to 100%.
All code must be properly documented. Each function and each class must have an associated documentation string in the correct format.
Before the “merge” button is clicked the following criteria must be met:
All the continuous integration must pass unless there is a known issue.
At least two members (not the author of the PR) of the “sunpy-developers” group must have approved the PR, one should be a relevant subpackage maintainer.
All comments posted on the thread must be resolved.
It is important that approval for merging the PR is done on the comment thread, as this becomes part of the “permanent record”, this includes in during community meetings or in chat.
Currently we have a variety of services that respond or activate on an opened pull request:
pep8speaks: Performs a PEP8 check on any submitted code.
CircleCi: Tests to see if sunpy installs, builds the documentation and runs the figure tests.
Giles: Returns a link if the documentation builds successfully.
Azure Pipelines: Runs our test suite on all three operating systems.
CodeCov: Checks how many lines of the code lack test coverage.
SunPy GitHub Groups¶
This document has already referred to two SunPy groups, namely “developers” and “maintainers” there is also a third primary SunPy group “owners”. These owners’ have control over the means of production.
The SunPy owners group is the group of people who have total control over the SunPy GitHub organization. The SunPy board have control over who is in this group, it has been decided that generally it will be the Lead Developer and the SunPy board chair and vice-chair.
This is the group of people who have push access to the main SunPy repository. The membership of this group is at the discretion of the Lead Developer, but shall generally be made up of people who have demonstrated themselves to be trust worthy and active contributors to the project.
The members of this group have “read” access to the SunPy repository. As all these repository are open anyway, what this effectively means is that these people can be assigned to issues. The members of this group are people who are involved in the development of SunPy at a good frequency, they are people who’s opinions have been demonstrated to be constructive and informative.