W3C home > Mailing lists > Public > spec-prod@w3.org > October to December 2011

Re: Using GitHub for specification development

From: Robin Berjon <robin@berjon.com>
Date: Wed, 9 Nov 2011 17:25:58 +0100
Cc: "spec-prod@w3.org Prod" <spec-prod@w3.org>
Message-Id: <E04020A6-BACC-46E9-BEEB-BA10B19D0BC4@berjon.com>
To: Gregg Kellogg <gregg@kellogg-assoc.com>
On Nov 9, 2011, at 17:02 , Gregg Kellogg wrote:
> We've been using GitHub to generate the JSON-LD specs [1] [2]. It has, indeed, been useful for people to enter comments in-line, and we use the GitHub issue tracker instead of the W3C tracker. What this misses is automatically updating issues based on email threads referencing the issues; but this could probably to added with a fairly simple robot.
> 
> Changes are automatically checked out to http://json-ld.org, and commits are broadcast on IRC (#json-ld on irc.freenode.net).

Sexy!

So it seems there's precedent  clearly I should've moved first and asked later ;-)

How do you handle contributions? I know you're a CG but it still matters. If I, who isn't on the CG, make a pull request including a substantive change, what happens? Do you ask me to join? Or to sign an RF commitment? Has it simply not happened?

Concerning the issue tracker, I think that syncing to W3C (or using only W3C) is a hard requirement. GitHub could be taken over by $evil, or could simply go belly up overnight, and we really shouldn't lose WG work over that. That said, they have an API for almost everything, including issues, so it should be very much doable to sync.

What do you use for your bot notifications, hooks?

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Wednesday, 9 November 2011 16:26:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:19:18 GMT