...
- The model proposer shall create modeling requirements in the 'High Level Requirements' page, and create corresponding JIRAs. The requirements and JIRAs will be reviewed in the modeling subcommittee call and need to be agreed by the teambe modified if any changes are needed.
- The model proposer shall create the wiki page (contribution) under the 'discussion' category of the modeling workspace
- After the first presentation in the modeling subcommittee call, the model proposer MUST also “call for an official review” participation” of the page (contribution) via via an email to : the mailing list
- Reviews & Comments:
- The proposal shall be presented and discussed in the weekly modeling subcommittee call.
- Comments should be captured directly on the wiki page (either at the bottom or preferably “in line”), or by emails to the modeling subcommittee's mailing list. , see clause 3 below for the instructions)
- Responses must be made to EACH comment with heading:
- <AGREE> agree with the comment and provide description of action,
- <DISCUSS> no action will be taken until discussed by the team,
- <INFORMATION> additional information provided,
- <DEFER> no action until some later time.
- Review decisions are captured on the wiki, and in meeting minutes.
...
- There is general consensus within the modeling team for the proposal. General consensus includes:
- All WIKI comments addressed (nothing left in discussion).wiki comments are discussed, and further actions decided
- Call for team agreement in meeting for the email poll, and captured in meeting minutes.
- The Modeling Chair does a “call for approval” of the wiki discussion page to onap-modelingsub@lists.onap.org, providing a 2-week time period for approval of the page. People respond “Yes”, "No" (with reasons) or “Abstain” (may with reasons). The goal of the poll is to gather opinions from the committee members.
- In the following modeling subcommittee call after the end of the email poll, the Modeling Chair will address rough consensus of the poll:
- If there's no objection received in the email poll and the modeling call, the contribution is approved.
- If there are objections raised, the objectors shall describe their comments, and the team will see if the comments can be addressed and agreed. If so, the updated proposals will be reviewed and approved by email or in chair(s) will try to get rough consensus (based on reference: https://datatracker.ietf.org/doc/html/rfc7282). If a consensus/rough consensus can be reached, the proposal will either be approved, or will be revised for further review in the following modeling calls.
- If the objections cannot be addressed :Option 1:a in the end, a formal vote is conducted during the call. Approval requires 2/3 of the votes approving the contribution, and the vote requires at least 3 committee members to attend.
- Note 1: the previous if the quorum is not met, another email vote will be triggered on the mailing list for final decision
- Note 2: if a member has given a response in the poll, but not join the modeling call, the response of the poll will be considered as votes from responding companiestheir opinion (vote) in this formal vote, unless they change their mind; and participants of the call can also attend the voteOption 2:the chair will try to get rough consensus (reference: https://datatracker.ietf.org/doc/html/rfc7282), and the Modeling Chair will decide whether the contribution is approved based on the rough consensus
- The Modeling Chair publishes the results to the mailing list, and record in meeting minutes.
- If approved, the DISCUSSION wiki goes to CLEAN. If not approved, there is no transition
- If the subcommittee is unable to reach consensus (e.g., members have strong objections against the decisions), the subcommittee will escalate those members may escalate the matter to the TSC and seek guidance or decisions.
- There is general consensus within the modeling team for the proposal. General consensus includes:
...