|
 |
61a679 |
Permissively licensed components of the midipix project currently
|
|
|
61a679 |
accept contributions in the form of gpg-signed patches. The requirement
|
|
|
61a679 |
that all contributions be gpg-signed helps to ensure a repository's
|
|
|
61a679 |
reliability and license integrity, and is thus considered worth of
|
|
|
61a679 |
the (small) trouble that it might entail.
|
|
|
61a679 |
|
|
|
61a679 |
Please note that patch submission is only one of the many ways to
|
|
|
61a679 |
advance the development of a software component, and that assistance
|
|
|
61a679 |
in the following areas is always needed, and greatly appreciated:
|
|
|
61a679 |
|
|
|
61a679 |
* brainstorming.
|
|
|
61a679 |
* expressing needs, requesting features.
|
|
|
61a679 |
* sharing knowledge about your favorite system.
|
|
|
61a679 |
* lurking on irc, reviewing commits and patches.
|
|
|
eef5ed |
* testing release candidates on different systems.
|
|
|
61a679 |
* building from source, testing bleeding-edge versions.
|
|
|
61a679 |
|
|
|
61a679 |
|
|
|
61a679 |
If you would like to submit code, then the following how-to is for you.
|
|
|
61a679 |
|
|
|
61a679 |
1. discuss your proposed changes on the project's freenode irc channel.
|
|
|
61a679 |
2. if the changes you propose are not trivial to accept, start a discussion
|
|
|
61a679 |
on the project's mailing list.
|
|
|
61a679 |
3. obtain as much help as needed on irc; post early versions of your work.
|
|
|
61a679 |
4. finalize your patch together with the project maintainer.
|
|
|
61a679 |
5. commit the patch to your local repository.
|
|
|
61a679 |
6. verify that everything builds, and that nothing breaks.
|
|
|
61a679 |
7 run contrib.sh, then sign and submit your patch.
|