[Continue with no hats] The second question I tried to answer in the VELOCE presentation was how the WG stays engaged in the new process being envisioned.
I said in the other thread that we continue to use I-D to identify new YANG modules. This experiment will cover new YANG modules. Although the discussion of existing RFCs with YANG modules is interesting, it will defer that discussion for a later time. Hopefully, it is a subset of the work done for a new YANG module. If somebody wants to propose new work that includes a new YANG module, they write up an individual draft, but do not include the YANG module. The YANG module can exist in a private repository till the work gets adopted by the WG. The individual I-D gets updated and posted to the datatracker, much like it happens today. The WG reviews the draft and follows the link in the draft to the private repo to review and provide comments on the module. Comments provided in the repo need to be reflected back to the WG mailing list. Once the draft is adopted as a WG item, the individual I-D gets renamed, and the private repo moves to the WG repo, where the chairs hold admin privileges. The chairs determine rough consensus on the changes being suggested in the WG repo, and decide what should be merged (through the suggested Pull Requests). All this work can continue in a separate branch. When the WG believes the module is ready to be published, the branch gets merged into the master/main branch. An open question would be - how is the community informed about the availability of a new version of the module? Mahesh Jethanandani [email protected]
_______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
