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

Re: Organizing the issues - GitHub Projects?

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Wed, 25 Apr 2018 11:35:57 +0200
To: <public-dxwg-wg@w3.org>
Message-ID: <0c7a655e-8c3c-d507-692d-29698173a055@few.vu.nl>
Hi Simon, all,

In principle using projects could be a good idea but I'm a bit worried that we would have some issues that span across deliverables, and I'm not sure that gihub handles this well.

In fact as for the other github features, I believe it's more a matter of everyone (including me) really investing in learning github.
Github allows to split quite easily a project space, for example here are all the profile requirements:

I believe that milestones could be a more efficient solution in fact, and you should be praised for having started it at [2]. Perhaps it needs to be more promoted. I don't see an announcement that you did this work on our mailing list, am I missing anything?
Perhaps also the milestones should be discussed more and agreed upon. The ones that are at [2] don't intuitively align with our deliverables (do we have a deliverable on 'profile formalization'?). Also they seem to be at different levels: I believe some DCAT-related milestones can be deliverables, others not.
In any case I think we shouldn't dismiss the milestone option at this stage.



On 25/04/18 11:03, Svensson, Lars wrote:
> Good morning Simon,
> On Wednesday, April 25, 2018 4:44 AM, Simon.Cox@csiro.au [mailto: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?
> Seems worth a try! (I have absolutely no experience with GitHub Projects but anything that can help us keep organised is worth to be looked at). Do you know if it's possible to have milestones within a project? I couldn't find anything on that in the documentation.
> Best,
> Lars
Received on Wednesday, 25 April 2018 09:36:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:02 UTC