File: CONTRIBUTING

package info (click to toggle)
mpich 3.3-3
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid
  • size: 131,836 kB
  • sloc: ansic: 975,868; cpp: 57,437; f90: 53,762; perl: 19,562; xml: 12,464; sh: 12,303; fortran: 7,875; makefile: 7,078; ruby: 126; java: 100; python: 98; lisp: 19; php: 8; sed: 4
file content (13 lines) | stat: -rw-r--r-- 1,041 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
How to contribute to MPICH

1. Sign and submit a contributors' agreement. http://www.mpich.org/documentation/contributor-docs/

2. Format your patches according to the MPICH coding standards. https://wiki.mpich.org/mpich/index.php/Coding_Standards

3. Use the git pre-commit hook included with MPICH (https://github.com/pmodels/mpich/blob/master/maint/hooks/pre-commit) to catch whitespace violations in new code. Patches with improper whitespace may be automatically rejected for inclusion in MPICH. To activate the pre-commit hook (from the top-level of your working copy):

  ln -s ../../maint/hooks/pre-commit .git/hooks/pre-commit

4. Open a Pull Request on Github (https://github.com/pmodels/mpich/pulls). Your pull request will be tested and reviewed by an MPICH maintainer. Be sure to pay attention to review comments, as they may request changes to the PR before it can be merged.

More info on contributing to MPICH, including tips on how to use git, can be found here: https://wiki.mpich.org/mpich/index.php/Contributing_to_MPICH