we had our third bi-weekly doc meeting. Sorry for the delay, but after 4 years, my OS needed a re-install and restore ;)
Current status quo
- We have started introducing two new boards in JIRA to get a better idea about what’s going on
|—> First an agile board  which is focused on the current work package for documenting just the monitors
|—> Second a kanban board  which has an overall overview about all issues in component "Documentation" and "Documentation-Wiki”
- Since the last meeting we were able increase from 17 to 27 documented monitors + additional 4 in review state and 1 unfortunately incomplete but started *JAY*
- The DHCP monitor (the one which is incomplete) is harder than expected ;) He depends on the DHCP daemon and turns out the documentation for this one is more complex but doable ;)
This is also the reason the status is set to "In progress" instead of “Resolved". If somebody wants to help here to make this part complete, send you comments or pull requests to Marcel Fuhrmanns working branch here:
- In general we have some outstanding review work in the pipeline
- We have added some help and hints for reviewers which has to be reviewed :D
This is our ready-for-review pipeline (See also the Agile board in ):
So if you feel comfortable feel free and give it a try.
What is in progress:
- DHCPMonitor: The part of the OpenNMS DHCP daemon is missing and how the monitor and the daemon work together.
Ideas from the meeting
- We got input using the new documentation in the release of OpenNMS
|—> Idea to add link in the OpenNMS WebUI to local and/or remote web based documentation
|—> Idea to add links in service monitors to the monitor documentation which describes the functionality
- We decided to aim for the next 1.13.5 release to deploy the documentation with it, the release contains everything which is reviewed, merged in development/docs and closed in JIRA. So basically what's done is done.
- Evaluated mail2Jira tool to simplify the workflow which seems to end up in a little bit more work. Issues coming from mail have to be qualified and add probably more work then it helps and could add also some SPAM issues.
- A quick web form to open a JIRA issue isn't evaluated yet. Is still worth to evaluate it if the web form is placed in the right context.
- It is not possible for default users in JIRA to take an issue.
We try to get in contact with Atlassian to figure out what possibility we have for this granular permission in components.
In the meantime Ronny is taking care about JIRA housekeeping in the Documentation and Documentation-Wiki component.