Clarify how documentation on the software can be contributed
Software is contributed through merge requests, but how can text can be contributed so that it can go in the deliverable?
A couple of solutions were discussed in ETSI NFV meeting 28, SOL-TST joint WG. Solutions:
-
Embed documentation in the software, so that it can be "exported" or post-processed to appear in the doc (as in forge.etsi.org/rep/nfv/api-tests)
-
Add any changes to the text in the Mirror Contribution filed to approve the software MR