From Fedora Project Wiki
mNo edit summary |
|||
| Line 18: | Line 18: | ||
* [[Modularity/Development/Getting Fedora Packages for Testing|Getting Fedora Packages for Testing]] | * [[Modularity/Development/Getting Fedora Packages for Testing|Getting Fedora Packages for Testing]] | ||
* [https://fedoraproject.org/wiki/Fedora_Packaging_Guidelines_for_Modules Fedora Packaging Guidelines for Modules] | |||
* [[Modularity/Development/Getting Pungi (Modularity Style)|Getting Pungi (Modularity Style)]] | * [[Modularity/Development/Getting Pungi (Modularity Style)|Getting Pungi (Modularity Style)]] | ||
* [[Modularity/Development/Composing Modules with Pungi|Composing Modules with Pungi]] | * [[Modularity/Development/Composing Modules with Pungi|Composing Modules with Pungi]] | ||
Revision as of 16:31, 14 September 2016
Resources for developing for a modular Fedora
Getting your changes accepted
In order so that our code base is always clean and maintainable, we have to enforce certain rules on how code is written or formatted, how changes are broken up into commits and how pull requests are handled.