W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > April 2018

RE: Organizing the issues - GitHub Projects?

From: <Simon.Cox@csiro.au>
Date: Thu, 26 Apr 2018 22:52:57 +0000
To: <kcoyle@kcoyle.net>, <public-dxwg-wg@w3.org>
Message-ID: <cf700f0e4ae441e98b850c89240103a2@exch1-mel.nexus.csiro.au>
I fear the labels' horse has bolted. 
Earlier this week I deleted all the unused labels (about 10) but there are still a lot. Labels, like tags, are primarily for recall. 

Perhaps use of milestones for precise grouping? I made up a few, but so far they mostly reflect my biases, plus observations of some hot topics. 

-----Original Message-----
From: Karen Coyle [mailto:kcoyle@kcoyle.net] 
Sent: Thursday, 26 April, 2018 01:55
To: public-dxwg-wg@w3.org
Subject: Re: Organizing the issues - GitHub Projects?

Regardless of whether we opt to use projects, would there be an advantage to making stricter use of the labels? Or creating labels that are only used to identify deliverables? It seems to me that the labels we have are being used pretty loosely, which is good for recall but less so for precision. A few precise labels might help with the organizing?

kc

On 4/24/18 7:43 PM, Simon.Cox@csiro.au wrote:
> The list of issues on our GitHub is getting quite overwhelming [1].
> 
> A few weeks ago I proposed that we make some groupings using GitHub's 
> Milestones and set up a few [2] but this doesn't appear to have helped 
> much.
> 
> Effectively the Milestones are just a kind of glorified tag (label).
> 
> And we definitely have too many tags (labels) [3].
> 
>  
> 
> So, here's another suggestion: create a GitHub Project for each 
> deliverable [4].
> 
> GitHub "Projects" provides a rudimentary Kanban board for each 
> project, allowing issues to be sorted in status ("todo", "in progress", "done") [5].
> 
> It seems to correspond pretty well with deliverables, and at least 
> will allow us to look at the issues associated with the separate 
> deliverables more cleanly.
> 
>  
> 
> Any comments?
> 
>  
> 
> [1] https://github.com/w3c/dxwg/issues
> 
> [2] https://github.com/w3c/dxwg/milestones
> 
> [3] https://github.com/w3c/dxwg/labels
> 
> [4] https://github.com/w3c/dxwg/projects
> 
> [5] https://help.github.com/articles/about-project-boards/
> 
>  
> 
> *Simon J D Cox *
> 
> Research Scientist - Environmental Informatics
> 
> Team Leader - Environmental Information Infrastructure
> 
> CSIRO Land and Water <http://www.csiro.au/Research/LWF>
> 
>  
> 
> *E*simon.cox@csiro.au <mailto:simon.cox@csiro.au>*T*+61 3 9545 2365
> *M*+61 403 302 672
> 
>    /Mail:/Private Bag 10, Clayton South, Vic 3169
> 
> /   Visit: /Central Reception,//Research Way, Clayton, Vic 3168
> 
> /   Deliver: /Gate 3, Normanby Road, Clayton, Vic 3168
> 
> people.csiro.au/Simon-Cox <http://people.csiro.au/Simon-Cox>
> 
> orcid.org/0000-0002-3884-3420 <http://orcid.org/0000-0002-3884-3420>
> 
> researchgate.net/profile/Simon_Cox3
> <https://www.researchgate.net/profile/Simon_Cox3>
> 
> github.com/dr-shorthair <https://github.com/dr-shorthair>
> 
> lov.okfn.org/dataset/lov/agents/Simon%20Cox
> <http://lov.okfn.org/dataset/lov/agents/Simon%20Cox>
> 
> Twitter @dr_shorthair <https://twitter.com/dr_shorthair>
> 
> Skype dr_shorthair <skype:dr_shorthair>
> 
> https://xkcd.com/1810/
> 
>  
> 
> *PLEASE NOTE*
> 
> The information contained in this email may be confidential or 
> privileged. Any unauthorised use or disclosure is prohibited. If you 
> have received this email in error, please delete it immediately and 
> notify the sender by return email. Thank you. To the extent permitted 
> by law, CSIRO does not represent, warrant and/or guarantee that the 
> integrity of this communication has been maintained or that the 
> communication is free of errors, virus, interception or interference.
> 
>  
> 
> /Please consider the environment before printing this email./
> 
>  
> 
>  
> 

--
Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
m: 1-510-435-8234 (Signal)
skype: kcoylenet/+1-510-984-3600
Received on Thursday, 26 April 2018 22:54:18 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 April 2019 13:44:58 UTC