You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the W3C JSON-LD WG, we have found a GH Project to be useful in managing the workflow across multiple repos without going out to external similar kanban boards like waffle or trello.
I propose a similar pattern for managing the TRC workflow. The chairs and editors can keep the on-deck issues up to date and ordered, and then move them to other columns such as accepted / rejected / sent-back-for-further-work once consensus in the TRC is arrived at.
The text was updated successfully, but these errors were encountered:
In the W3C JSON-LD WG, we have found a GH Project to be useful in managing the workflow across multiple repos without going out to external similar kanban boards like waffle or trello.
I propose a similar pattern for managing the TRC workflow. The chairs and editors can keep the on-deck issues up to date and ordered, and then move them to other columns such as accepted / rejected / sent-back-for-further-work once consensus in the TRC is arrived at.
The text was updated successfully, but these errors were encountered: