How to contribute to NWB:N software and documents¶
Code of Conduct¶
This project and everyone participating in it is governed by our code of conduct guidelines. By participating, you are expected to uphold this code. Please report unacceptable behavior.
Types of Contributions¶
Did you find a bug? or Do you intend to add a new feature or change an existing one?¶
Identify the appropriate repository for the change you are suggesting:
If you are unable to find an open issue addressing the problem then open a new issue on the respective repository. Be sure to include:
- brief and descriptive title
- clear description of the problem you are trying to solve*. Describing the use case is often more important than proposing a specific solution. By describing the use case and problem you are trying to solve gives the development team and ultimately the NWB:N community a better understanding for the reasons of changes and enables others to suggest solutions.
- context providing as much relevant information as possible and if available a code sample or an executable test case demonstrating the expected behavior and/or problem.
Be sure to select the appropriate labels (see Issue Labels, Projects, and Milestones) for your tickets so that they can be processed accordingly.
NWB:N is currently being developed primarily by staff at scientific research institutions and industry, most of which work on many different research projects. Please be patient, if our development team is not able to respond immediately to your issues. In particular issues that belong to later project milestones may not be reviewed or processed until work on that milestone begins.
Did you write a patch that fixes a bug or implements a new feature?¶
Contributing Patches and Changes section below for details.
Did you fix whitespace, format code, or make a purely cosmetic patch in source code?¶
Source code changes that are purely cosmetic in nature and do not add anything substantial to the stability, functionality, or testability will generally not be accepted unless they have been approved beforehand. One of the main reasons is that there are a lot of hidden costs in addition to writing the code itself, and with the limited resources of the project, we need to optimize developer time. E.g,. someone needs to test and review PRs, backporting of bug fixes gets harder, it creates noise and pollutes the git repo and many other cost factors.
Do you have questions about NWB:N?¶
Contributing Patches and Changes¶
From your local copy directory, use the following commands.
- First create a new branch to work on
$ git checkout -b <new_branch>
- Make your changes.
- Push your feature branch to origin (i.e. github)
$ git push origin <new_branch>
Once you have tested and finalized your changes, create a pull request targeting
devas the base branch:
- Ensure the PR description clearly describes the problem and solution.
- Include the relevant issue number if applicable.
- Before submitting, please ensure that the code follows the standard coding style of the repsective repository.
- NOTE: Contributed branches will be removed by the development team after the merge is complete and should, hence, not be used after the pull request is complete.
Issue Labels, Projects, and Milestones¶
Labels are used to describe the general scope of an issue, e.g., whether it describes a bug or feature request etc. Please review and select the appropriate labels for the respective Git repository:
Milestones are used to define the scope and general timeline for issues. Please review and select the appropriate milestones for the respective Git repository:
Projects are currently used mainly on the NeurodataWithoutBorders organization level and are only accessible to members of the organization. Projects are used to plan and organize developments across repositories. We currently do not use projects on the individual repository level, although that might change in the future.
Git Commit Message Styleguide¶
- Use the present tense (“Add feature” not “Added feature”)
- The first should be short and descriptive.
- Additional details may be included in further paragraphs.
- If a commit fixes an issues, then include “Fix #X” where X is the number of the issue.
- Reference relevant issues and pull requests liberally after the first line.
All documentations is written in reStrcuturedText (RST) using Sphinx.
Format Specification Styleguide¶
Python Code Styleguide¶
Python coding style is checked via
flake8 for automatic checking of PEP8 style during pull requets.
Please don’t take the fact that working with an organization (e.g., during a hackathon or via GitHub) as an endorsement of your work or your organization. It’s okay to say e.g., “We worked with XXXXX to advance science” but not e.g., “XXXXX supports our work on NWB”.”
Licence and Copyright¶
As indicated in the PyNWB license: “You are under no obligation whatsoever to provide any bug fixes, patches, or upgrades to the features, functionality or performance of the source code (“Enhancements”) to anyone; however, if you choose to make your Enhancements available either publicly, or directly to Lawrence Berkeley National Laboratory, without imposing a separate written license agreement for such Enhancements, then you hereby grant the following license: a non-exclusive, royalty-free perpetual license to install, use, modify, prepare derivative works, incorporate into other computer software, distribute, and sublicense such enhancements or derivative works thereof, in binary and source code form.”
Contributors to the NWB code base are expected to use a permissive, non-copyleft open source license. Typically 3-clause BSD i used, but any compatible license is allowed, the MIT and Apache 2.0 licenses being good alternative choices. The GPL and other copyleft licenses are not allowed due to the consternation it generates across many organizations.
Also, make sure that you are permitted to contribute code. Some organizations, even academic organizations, have agreements in place that discuss IP ownership in detail (i.e., address IP rights and ownership that you create while under the employ of the organization). These are typically signed documents that you looked at on your first day of work and then promptly forgot. We don’t want contributed code to be yanked later due to IP issues.