W3C home > Mailing lists > Public > public-csv-wg@w3.org > January 2016

Re: Planning for post-WG life: what do we do with CSVW Github esp issue tracker?

From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Fri, 8 Jan 2016 07:53:08 -0800
Cc: Dan Brickley <danbri@google.com>, W3C CSV on the Web Working Group <public-csv-wg@w3.org>
Message-Id: <7F61D334-67E5-4C32-85F9-B974F1543499@greggkellogg.net>
To: Ivan Herman <ivan@w3.org>
On Jan 8, 2016, at 7:43 AM, Ivan Herman <ivan@w3.org> wrote:
> 
> 
>> On 8 Jan 2016, at 16:37, Dan Brickley <danbri@google.com> wrote:
>> 
>> 
>> Ivan,
>> 
>> Are there any conventions for life-after-WG regarding Github presence, e.g. issue trackers or test case repositories? I am wondering what we can do for issue tracking in the new Community Group(*). Should it have its own Github repo (maybe with a fork of the final state of the WG at closure) so that its issues can be kept separate? That way any issues branches made informally within the CG could eventually give rise to pull requests (in 2-3 years time or whatever) should a full WG ever be reactivated. Just thinking out loud, and glad to hear of any useful precedents we can follow…
> 
> There are no real conventions, so we are inventing things as we go…
> 
> My initial reaction is that we should keep the github repo for the CG separate. There may be many discussions on the CG that end up in issues that are not necessarily WG specific. Also, a possible future reincarnation of the WG would have to pick up the WG's repo, including the errata; it may make their life more difficult to separate the CG specific and WG specific problems, issues, documents, etc.

IMO, this Leeds to needless fragmentation. Th json-ld group continues to use the same repo, which is effective for gathering issues to be considered by the next WG and for curating tests ad implementation reports. Of course, they started out as a CG, and the work continued there during the RDF WG phase.

I think with judicious use of issue tags, and being careful not to mess up the existing state of the repo needlessly, CG can safely operate in the same repo. Also, the repo is freer ended fro the specs, and is the natural place people will go with new questions and issues.

Gregg

> My 2 cents...
> 
> Ivan
> 
>> 
>> Dan
>> 
>> 
>> * http://www.w3.org/community/csvw/
> 
> 
> ----
> Ivan Herman, W3C 
> Digital Publishing Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704
> 
> 
> 
> 
Received on Friday, 8 January 2016 15:53:41 UTC

This archive was generated by hypermail 2.3.1 : Friday, 8 January 2016 15:53:42 UTC