Contributor Requirements ¶

Requirements for new contributors ¶

We welcome new contributors to our community - we want you to use QGIS as a platform for doing your work - and we believe that QGIS is a great platform for that. In order to contribute code, patches, or documentation to the QGIS project, all developers/team members must:

• Abide by the Social Contract.

• Be familiar with the development process and the reference material available in the Developers Guide for QGIS, and the CODING document in the root of the QGIS Sources.

• Ensure that all code committed to the repository is unencumbered and compatible with the QGIS license, GNU Public License (GPL) Version 2 or any later version.

• Not use or include any code that will cause a trademark or patent infringement. If you are unsure, ask on the developer mailing list or contact a Project Steering Committee member.

• Join the qgis-developer mailing list and contribute to discussions

• These requirements apply to both developers desiring commit privileges and those that submit patches.

• Read and agree to the Code of Conduct.

• Read and agree to the Coding Standards.

• Read and agree to the Diversity statement.

• Agree to these requirements by sending an email to the qgis-developer mailing list stating agreement.

Social Contract ¶

QGIS is a collaborative project. As an open source project we hope for and encourage participation and code contributions from interested parties. However in order to maintain high standards we encourage you to participate in the project according to the following social contract:

• To be polite to all members of the project

• To ensure any code you submit via a patch or commit to source control is properly documented

• To ensure any code you submit via a patch or commit to source control is compliant with our CodingStandards

• Not to submit any code without having permission to submit that code

• Not to submit any code that violates the GNU Public License

• To follow the Contributor Requirements mentioned above

• To ensure (to the best of your ability) that any commits you make to git leave the repository in a compilable state

• To ensure that any new class added to the source is accompanied by a test unit

• To carry out appropriate tests before committing new code to the repository

• To smile, laugh and crack a joke once in a while - we are all here to have fun!