From Fedora Project Wiki
No edit summary |
|||
| Line 28: | Line 28: | ||
* [[Modularity/Development/Setting up PDC locally|Setting up PDC locally]] | * [[Modularity/Development/Setting up PDC locally|Setting up PDC locally]] | ||
* [[Modularity/Development/Developer_Notes|Developer Notes]] | * [[Modularity/Development/Developer_Notes|Developer Notes]] | ||
* [[Modularity/Development/Container_OpenShift_with_ease|How to deploy container into OpenShift with ease] | |||
[[Category:Modularity]] | [[Category:Modularity]] | ||
Revision as of 09:31, 24 January 2017
Resources for developing for a modular Fedora
Integration of changes
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.
Local Development
Getting started with the Prototype
- Getting Fedora Packages for Testing
- Fedora Packaging Guidelines for Modules
- Getting Pungi (Modularity Style)
- Composing Modules with Pungi
- Setting up PDC locally
- Developer Notes
- [[Modularity/Development/Container_OpenShift_with_ease|How to deploy container into OpenShift with ease]