RE: Process for github issue management

Thanks marcos for that link that I completely missed. 
The grey zone stays on the way issues are treated, once provisioned : who assigns labels (bug/enhancement/...) to issues, how do they come into the wg agenda and by which priority, is there any mean to allocate deadline for issues (like tracker does for actions). 
I am not requesting here everything to be written, but few guidance to have new delegates knowing how to deal with the wg habits and best practices. 

Regards,
Virginie


-----Original Message-----
From: Marcos Caceres [mailto:w3c@marcosc.com] 
Sent: jeudi 22 août 2013 20:06
To: GALINDO Virginie
Cc: Mounir Lamouri; wonsuk11.lee@samsung.com; sysapps
Subject: Re: Process for github issue management

Hi Virginie,  

On Monday, August 19, 2013 at 10:42 PM, GALINDO Virginie wrote:

> Hi chairs,  
>  
> Is there any documentation about the way the github sysapps issues are treated by the team of chair and editors ? (e.g. how to you assign a bug to someone, who is provisioning its label, how is it addressed in the agenda…) Any guidance to better understand the working group habits and thus use properly issues ?

This might help a bit:  

http://www.w3.org/wiki/System_Applications#Editorial_process


If not, we should document answers to your questions in the Wiki. Please let me know if that helps - and if not, then it might be something to quickly put together next week during the F2F.

Received on Friday, 23 August 2013 15:23:41 UTC