Core Developer Guide¶
As a core developer, you should continue making pull requests in accordance with the Contributor Guide. You are responsible for shepherding other contributors through the review process. You should be familiar with our Mission and Values. You also have the ability to merge or approve other contributors’ pull requests. Much like nuclear launch keys, it is a shared power: you must merge only after another core developer has approved the pull request, and after you yourself have carefully reviewed it. (See Reviewing and especially Merge Only Changes You Understand below.) To ensure a clean git history, use GitHub’s Squash and Merge feature to merge, unless you have a good reason not to do so.
How to Conduct A Good Review¶
Always be kind to contributors. Nearly all of NetworkX is volunteer work, for which we are tremendously grateful. Provide constructive criticism on ideas and implementations, and remind yourself of how it felt when your own work was being evaluated as a novice.
NetworkX strongly values mentorship in code review. New users often need more handholding, having little to no git experience. Repeat yourself liberally, and, if you don’t recognize a contributor, point them to our development guide, or other GitHub workflow tutorials around the web. Do not assume that they know how GitHub works (e.g., many don’t realize that adding a commit automatically updates a pull request). Gentle, polite, kind encouragement can make the difference between a new core developer and an abandoned pull request.
When reviewing, focus on the following:
API: The API is what users see when they first use NetworkX. APIs are difficult to change once released, so should be simple, functional (i.e. not carry state), consistent with other parts of the library, and should avoid modifying input variables. Please familiarize yourself with the project’s Policy.
Documentation: Any new feature should have a gallery example that not only illustrates but explains it.
The algorithm: You should understand the code being modified or added before approving it. (See Merge Only Changes You Understand below.) Implementations should do what they claim, and be simple, readable, and efficient.
Tests: All contributions to the library must be tested, and each added line of code should be covered by at least one test. Good tests not only execute the code, but explores corner cases. It is tempting not to review tests, but please do so.
Other changes may be nitpicky: spelling mistakes, formatting, etc. Do not ask contributors to make these changes, and instead make the changes by pushing to their branch, or using GitHub’s suggestion feature. (The latter is preferred because it gives the contributor a choice in whether to accept the changes.)
Our default merge policy is to squash all PR commits into a single
commit. Users who wish to bring the latest changes from
into their branch should be advised to merge, not to rebase. Even
when merge conflicts arise, don’t ask for a rebase unless you know
that a contributor is experienced with git. Instead, rebase the branch
yourself, force-push to their branch, and advise the contributor on
how to force-pull. If the contributor is no longer active, you may
take over their branch by submitting a new pull request and closing
the original. In doing so, ensure you communicate that you are not
throwing the contributor’s work away! You should use GitHub’s
Co-authored-by: keyword for commit messages to credit the
Please add a note to a pull request after you push new changes; GitHub may not send out notifications for these.
Merge Only Changes You Understand¶
Long-term maintainability is an important concern. Code doesn’t merely have to work, but should be understood by multiple core developers. Changes will have to be made in the future, and the original contributor may have moved on.
Therefore, do not merge a code change unless you understand it. Ask for help freely: we have a long history of consulting community members, or even external developers, for added insight where needed, and see this as a great learning opportunity.
While we collectively “own” any patches (and bugs!) that become part of the code base, you are vouching for changes you merge. Please take that responsibility seriously.
Closing issues and pull requests¶
Sometimes, an issue must be closed that was not fully resolved. This can be for a number of reasons:
the person behind the original post has not responded to calls for clarification, and none of the core developers have been able to reproduce their issue;
fixing the issue is difficult, and it is deemed too niche a use case to devote sustained effort or prioritize over other issues; or
the use case or feature request is something that core developers feel does not belong in NetworkX,
among others. Similarly, pull requests sometimes need to be closed without merging, because:
the pull request implements a niche feature that we consider not worth the added maintenance burden;
the pull request implements a useful feature, but requires significant effort to bring up to NetworkX’s standards, and the original contributor has moved on, and no other developer can be found to make the necessary changes; or
the pull request makes changes that do not align with our values, such as increasing the code complexity of a function significantly to implement a marginal speedup,
All these may be valid reasons for closing, but we must be wary not to alienate contributors by closing an issue or pull request without an explanation. When closing, your message should:
explain clearly how the decision was made to close. This is particularly important when the decision was made in a community meeting, which does not have as visible a record as the comments thread on the issue itself;
thank the contributor(s) for their work; and
provide a clear path for the contributor or anyone else to appeal the decision.
These points help ensure that all contributors feel welcome and empowered to keep contributing, regardless of the outcome of past contributions.
As a core member, you should be familiar with community and developer resources such as:
Our Code of Conduct
PEP8 for Python style
PEP257 and the NumPy documentation guide for docstrings. (NumPy docstrings are a superset of PEP257. You should read both.)
The NetworkX tag on StackOverflow
Our mailing list
You are not required to monitor all of the social resources.