(OLD) HowTo guide for developers: Difference between revisions
From OSM Public Wiki
Garciadeblas (talk | contribs) (Created page with "This section provides developer guidelines across modules. For module specific guidelines refer to module specific links indicated above. * Please make sure that no one else i...") |
Garciadeblas (talk | contribs) m (Garciadeblas moved page HowTo guide for developers to (OLD) HowTo guide for developers: Obsolete) |
(No difference)
|
Latest revision as of 11:26, 22 October 2018
This section provides developer guidelines across modules. For module specific guidelines refer to module specific links indicated above.
- Please make sure that no one else is already working on an item in bugzilla before making changes. If someone is already working it, please check with the person first.
- Similar rules applies when addressing a new feature/blueprint
- Use meaningful comments when checking in the code
- Use consistent conventions/style for changes to an existing module
When doing changes, be sure that you are situated in the master branch, or in the assigned branch for your change:
git checkout master
HowTo per module
- UI: Developer HowTo for UI Module
- SO: Developer HowTo for SO Module
- RO: Developer HowTo for RO Module
OSM relies on Juju for the VNF Configuration and Abstraction (VCA). For more information on Juju, the project is hosted on github: Juju development site. A guide for VNFs developers on how to develop Juju charms (language independent) can be found here.
References
Your feedback is most welcome! You can send us your comments and questions to OSM_TECH@list.etsi.org Or join the OpenSourceMANO Slack Workplace See hereafter some best practices to report issues on OSM