Contributor Guide Summary


This document is intended to describe general development practices within the MPAS project. The information contained should be read prior to starting a project within the MPAS framework. Instructions can be used by MPAS core developers, or external developers. Notes specific to external developers are made where relevant.



Becoming an MPAS Developer

The preferred approach to contributing source code to the MPAS-Dev repositories is via a fork of the release repository. If the preferred approach is not workable, developer access to the MPAS-Dev GitHub project must be approved by core maintainers. Prospective developers should send the following information to the relevant core maintainers.

  • GitHub user name (can be acquired at GitHub)

  • Can your work be completed in a fork of the release repository?

  • If no, please explain the reason.

  • What core do you intend to develop?

  • What work do you intend to contribute to MPAS?