W3C home > Mailing lists > Public > public-sysapps@w3.org > August 2013

RE: Process for github issue management

From: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
Date: Fri, 23 Aug 2013 17:23:10 +0200
To: Marcos Caceres <w3c@marcosc.com>
CC: POTONNIEE Olivier <Olivier.POTONNIEE@gemalto.com>, SUWIRYA Darmawan <Darmawan.SUWIRYA@gemalto.com>, "wonsuk11.lee@samsung.com" <wonsuk11.lee@samsung.com>, sysapps <public-sysapps@w3.org>
Message-ID: <239D7A53E5B17B4BB20795A7977613A40129B2FB3335@CROEXCFWP04.gemalto.com>
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. 


-----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:  


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

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:14 UTC