Hi Pierre, thank you this sounds great. It is required to sign an OpenNMS Contribution Agreement [1]. You will be added with a contact on our Executed Contributor Agreements page [2].
For the code contribution itself I would recommend the following workflow: - Creating a JIRA [3] issue with a short description of your enhancement, The issue can be tracked and planned for the release in upcoming OpenNMS releases. We can also make sure the changes is reflected in release notes, when it is released. - Fork OpenNMS and create a feature branch with your changes. You can send a Pull Request against the OpenNMS development branch [4].It allows us to set our Bamboo build system against your changes to see if all tests went green and nothing else got broken. The pull request is also helpful for reviewing the code change. Ben wrote a quite detailed document how to contribute code [5]. It contains also a section contributing with GitHub pull requests. In hope this helps and thank you for your contribution Ronny [1] http://www.opennms.org/wiki/Contributor_Agreement [2] http://www.opennms.org/wiki/Executed_contributor_agreements [3] http://issues.opennms.org [4] https://github.com/OpenNMS/opennms [5] http://www.opennms.org/wiki/Developing_with_Git#Option_1:_No_Commit_Access.2C_using_a_GitHub_pull_request On Apr 8, 2015, at 5:24 PM, SCHILTZ, Pierre <pierre.schi...@capgemini.com> wrote: > Hi everyone, > > I’m a French developer of Capgemini. > For one of our project we use OpenNMS and have added 2 functionalities. > > As OpenNMS is open source we would like sharing our modifications. > > The 2 functionalities were developed for OpenNMS version 14.0.3: > · From collected SNMP MIB values, calculate simple KPI expression and > persist the results > o Calculated expression are in xml configuration files and evaluated by a > script engine: JavaScript by default > · Collect of CSV files > o Extending XML collect handler and modifying XML configuration > > Best regards, > > Pierre SCHILTZ > This message contains information that may be privileged or confidential and > is the property of the Capgemini Group. It is intended only for the person to > whom it is addressed. If you are not the intended recipient, you are not > authorized to read, print, retain, copy, disseminate, distribute, or use this > message or any part thereof. If you receive this message in error, please > notify the sender immediately and delete all copies of this message. > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________ > Please read the OpenNMS Mailing List FAQ: > http://www.opennms.org/index.php/Mailing_List_FAQ > > opennms-devel mailing list > > To *unsubscribe* or change your subscription options, see the bottom of this > page: > https://lists.sourceforge.net/lists/listinfo/opennms-devel
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
