1. SARIF Issue Tracking Process
All activity that may impact spec content will be tracked as issues, e.g.,
We encourage discussion on the public issues. Editors will ‘curate’ by applying specific tags, ensuring content from other sources ( ) is recorded, etc.
Editors will prepare proposed changes in separate repository branches. A clean document with revisions tracking enabled will be used for driving specific textual proposals.
Any issues that require time-sensitive discussion will be driven through the mailing list (this should be rate)
Issues that are ready for final approval or which warrant discussion on the telecon will be tagged in advance of each meeting.
After telecon approval/rejection, PRs will be merged or closed unmerged as appropriate.
This process (with additional details) will be driven by an open issue and documented in a file persisted to the repository (and will be approved next TC)