...
- It is the responsibility of the Editors to update working text and , PS Leads and Work Area Directors to reflect the current state of contributions submitted via Jira.
- Jira updates should occur no later than 1 week after the contribution is discussed at an Access meeting.
CONTRIB, DTP contributions
| Scenario | Contributor | Editor | PS Leads | Work Area Directors | Contribution State |
|---|
Transition| Transition |
|---|
| Normative Contributions |
|
|
|
|
|
| Contribution gets accepted to be incorporated into a working text |
Copy
| - Editor copies the Meeting report notes showing acceptance as Jira comment.
- Set the Jira state of the contribution to "In-progress"
|
and assign - Assign the ticket to the editor.
|
Move
|
| Ticket goes from "For Review" to "In-Progress" |
| Accepted Contribution gets integrated into working text |
Update the working text and inform
| - Editor updates the working text
- Editor adds a comment to Jira ticket that it has been integrated into working text.
- Editor informs the PS leads of the updated text.
| |
will - cross-check the updates and move the ticket from "In-progress to completed stats
|
| Tickets goes from "In-Progress" to "Completed" status |
. |
| Contribution is agreed that it needs work. |
Copy
| - Editor copies the meeting report
|
note comment and assign - Jira comment.
- Editor assigns the ticket to the contribution originator
- Editor moves the ticket to "Needs Work"
|
|
| Ticket goes from "For Review" to "Needs Work" |
| Contribution is presented but not accepted |
| - Editor copies Meeting report notes as a Jira comment.
|
Editor -
- Editor moves the contribution to "Wont Do" state
|
Move
|
| Ticket goes from "For Review" to "Won't Do" |
| Contribution in Needs Work state gets updated | - Contributor updates the contribution
- Contributor moves the Jira ticket from "Needs Work" to "For Review"
|
|
|
| Ticket goes from "Needs Work" to "For Review" |
| Informative Contributions (no target working text) |
|
|
|
|
|
| Work Area Director puts together an informative contribution (e.g., brainstorming, overview of work area, etc) |
|
|
| After presenting such contribution (where no action is expected), the work area director moves the ticket to completed state | Ticket goes from "For Review" to "Completed state" |
YANG contributions (CONTRIB, YMONU, YMOLT, etc)
| Scenario | Contributor | Editor | PS Leads | Contribution State Transition |
|---|
Normative Contributions | |
|---|
| New CONTRIB/YM* Contribution (without Pull Request) | Creates contribution and sets the state to Open |
|
| Ticket goes from "New" to "Open" status |
| CONTRIB/YM* contribution is accepted and has a pull request associated with it |
Contribution gets accepted to be incorporated into a working text |
| - Copy the Meeting report notes showing acceptance as Jira comment.
| PS |
leads when merging pull requests will handle the Jira transitions (no manual intervention is needed)Leads moves ticket to "For Review" state | Ticket goes from "Open" to "Review" status |
| CONTRIB/YM* contribution gets accepted but there is no pull request |
| - Copy the Meeting report notes showing acceptance as Jira comment.
- Assign the ticket to the Contributor (to put together a pull request)
- Note: it is possible that no one person gets assigned the ticket (but is left open for others to write the YANG code)
|
| Ticket goes from "Open" to "Assigned" status |
| Contribution is agreed that it needs work. |
Copy the meeting report note as a comment and assign the ticket to the originator |
|
|
|
|
| Contribution is presented but not accepted |
|
|
|
|