Contributing to Mainzelliste
We would love to include your useful changes to the Mainzelliste code in a future official release. In order to contribute code, we ask you to do the following:
- Fork the repository (you probably have done so already if you read this).
- Commit your changes to a branch different than master. If the commits already exist in the master branch, create a new branch from there. If possible, sign off the commits (see the notes on the developer certificate of origin below). Choose a meaningful name for the branch, preferably using a prefix like
bugfix/to denote the type of changes.
- Create a pull request from this branch to a new branch of the same name in our repository. We usually give short feedback on a pull request within a couple of days. The time it takes us to review the request will of course depend on the amount of code provided.
Every contribution must be under a license compatible to the GNU Affero General Public License, version 3 (AGPL), preferably the AGPL itself. See https://www.gnu.org/licenses/license-list.html#SoftwareLicenses for a list of common software licenses and information about their compatibility to the AGPL. Please include a license header in every new file that is part of your contribution.
Developer certificate of origin
In order to make sure that we can legally distribute your code, we ask you to certify that your contribution meets the requirement stated by the Developer Certificate of Origin (http://developercertificate.org/):
Developer Certificate of Origin Version 1.1 Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 1 Letterman Drive Suite D4700 San Francisco, CA, 94129 Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
In order to accept these conditions, add the following message to your commits with your full name and email address filled in (with the –s option, git commit does this for you):
Signed-off-by: Jane Example email@example.com
If signing off commits is not possible, (e.g. the commits already exist and cannot be safely rewritten because other people depend on their commit hashes), add the sign-off message as a comment to the pull request.