mirror of https://github.com/ZDoom/fluidsynth.git
28 lines
960 B
Markdown
28 lines
960 B
Markdown
|
# Contributing
|
||
|
|
|
||
|
|
Thanks for considering to contribute to FluidSynth. Before implementing
|
||
|
|
any huge new feature, consider bringing up your ideas on our mailing list:
|
||
|
|
https://lists.nongnu.org/mailman/listinfo/fluid-dev
|
||
|
|
|
||
|
|
Contributing can be done by submitting pull requests on Github:
|
||
|
|
https://help.github.com/articles/proposing-changes-to-your-work-with-pull-requests/
|
||
|
|
|
||
|
|
Or by submitting patches to the mailing list. Patches should be created with
|
||
|
|
|
||
|
|
```
|
||
|
|
git format-patch
|
||
|
|
```
|
||
|
|
|
||
|
|
So in every case you should be familiar with the basics of git.
|
||
|
|
|
||
|
|
We'll try comment on our changes within three business days
|
||
|
|
(and typically, one business day). We may suggest
|
||
|
|
changes, improvements or alternatives.
|
||
|
|
|
||
|
|
Some things that will increase the chance that your pull request or patch is accepted:
|
||
|
|
|
||
|
|
* Unless reporting bugs, give a reasoning / motivation for any changes or proposals you make.
|
||
|
|
* Follow our style guide.
|
||
|
|
* Keep your commits "atomic".
|
||
|
|
* Write a meaningful commit messages.
|