Re: [admin] Tool choices for the Annotation WG

yes, we need email to go to the entire public list when issues are raised and updated (I believe)

also the previous edit from Maxence already demonstrates a benefit over raising issues in email :)

regards, Frederick

Frederick Hirsch, Nokia
@fjhirsch



On Sep 29, 2014, at 8:01 AM, Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk> wrote:

> I would also be a strong supporter of Github for document versioning and tracker, so same +1 as Robert here. We have used this in HCLS WG, and it is also a nice way to be more open and inclusive. I have for instance participated in a couple of bugs from other WGs which I would never bother with on the Tracker.
> 
> The technical examples you laid out are almost impossible to express in the W3C tracker without also making wiki pages and keeping those in sync. With Github we get links from commits to the issue (just say Issue #2 in the commit message), pull requests for experimental changes, etc.
> 
> I would however be slightly concerned about not including the whole WG mailing list if one starts using the email/discussion feature of the Github Issues, as was mentioned, can we be sure that every participant is a member? There is also the question of archiving those discussions for future generations. Perhaps this can be solved by simply having the list address "watch" the repository?
> 
> On 26 Sep 2014 21:52, "Robert Sanderson" <azaroth42@gmail.com> wrote:
> 
> 
> On Fri, Sep 26, 2014 at 9:26 AM, Robert Sanderson <azaroth42@gmail.com> wrote: 
> (3) Issue Tracking
> There are a number of ways to manage issues, and the WG needs to decide [5]. 
> 
> 3. Git issue management 
> +1 to using Github issues, and especially when there's an IRC bot.  Keeping the issues with the documents, and in a very public venue I think has advantages.  The web UI is clear, and there's a zillion apps and other integrated solutions available.
> 
> As a strawperson example of how github issues could be used, I created two interdependent ones and a set of tags for the deliverables that they would impact.
> 
> * https://github.com/w3c/web-annotation/issues/1
> * https://github.com/w3c/web-annotation/issues/2
>  
> As Randall replied to one before I could clarify that they were examples to demonstrate the use, there's also an example of the discussion stream in /1
> 
> Discussion on whether this would be a good platform or not is encouraged :)
> 
> Rob
>