Re: Additional admin feature: action management

Oops, sorry, wrong group!!! This is old news for this group, just setting it up in another one…

Doh.

Sorry…

Ivan

> On 25 Apr 2019, at 13:40, Ivan Herman <ivan@w3.org <mailto:ivan@w3.org>> wrote:
> 
> Dear all,
> 
> lately I did some additional work (with the help of Benjamin) on the scribe management script to allow for a somewhat better management of actions assigned to group participants. The short summary is that the scribe can (following a syntax, see below) assign an action to a participant; this action will be recorded as a github issue with special label and assigned to that person. This setup has been operational in the JSON-LD WG since a few weeks. The reason I thought it is worthwhile setting it ip for this Working Group is that if we get closer to the slightly more administrative person of Candidate Recommendation, this a better control over the open actions may become helpful.
> 
> A more detailed view is:
> 
> - Actions are to be added on IRC by the scribe following the syntax "action: XYZ to (the text describing the action comes here)". XYZ is, as usual, the person's IRC handle.
> 
> - The minute generator (ie, scribejs) picks up those actions and raises an issue for each of those in the "github.com/w3c/publ-wg' <http://github.com/w3c/publ-wg'> repository. Each issue:
>  - includes a unique ID as part of the title (which helps avoiding that the same action is raised twice in case the minutes are re-generated for whatever purpose)
>  - the issue is assigned to the person in github (in case we have that person's github id in our admin…)
>  - the issue text itself has a link to the relevant portion of the minutes.
>  - the issue is labeled 'action'
> 
> - Examples of a specific test repo for another WG can be seen in, e.g., [1]. For our WG, the relevant URL will be [2].
> 
> - From that point on, actions can be handled as issues: when an action is completed, the relevant issue can be closed. It is up to the chairs to chase people for their open actions...
> 
> I hope there won't be any hiccups, although it has been already operational for some times in the JSON-LD Working Group.
> 
> Cheers
> 
> Ivan
> 
> [1] https://github.com/w3c/json-ld-wg/issues?q=is%3Aissue+is%3Aopen+label%3Aaction <https://github.com/w3c/json-ld-wg/issues?q=is%3Aissue+is%3Aopen+label%3Aaction>
> [2] https://github.com/w3c/publ-wg/issues?q=is%3Aopen+is%3Aissue+label%3Aaction <https://github.com/w3c/publ-wg/issues?q=is%3Aopen+is%3Aissue+label%3Aaction>
> 
> 
> 
> 
> ----
> Ivan Herman, W3C 
> Publishing@W3C Technical Lead
> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
> mobile: +31-641044153
> ORCID ID: https://orcid.org/0000-0003-0782-2704 <https://orcid.org/0000-0003-0782-2704>
> 


----
Ivan Herman, W3C 
Publishing@W3C Technical Lead
Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
mobile: +31-641044153
ORCID ID: https://orcid.org/0000-0003-0782-2704 <https://orcid.org/0000-0003-0782-2704>