- From: Shane McCarron <shane@halindrome.com>
- Date: Thu, 21 Jan 2016 11:42:31 -0600
- To: Gregg Kellogg <gregg@greggkellogg.net>
- Cc: Daniel Burnett <danielcburnett@gmail.com>, Ian Jacobs <ij@w3.org>, "public-webpayments-ig@w3.org" <public-webpayments-ig@w3.org>, Credentials Community Group <public-credentials@w3.org>
- Message-ID: <CAJdbnOCaObT2yMBOWnoPCDvFuEeOh8N5x-ygU5OJ2h-iH9WK1Q@mail.gmail.com>
The PFWG also does many documents at the same time in the same repo without too much trouble. But there are issues with branching and merging from time to time. On Thu, Jan 21, 2016 at 11:08 AM, Gregg Kellogg <gregg@greggkellogg.net> wrote: > On Jan 21, 2016, at 3:41 AM, Daniel Burnett <danielcburnett@gmail.com> > wrote: > > Guys, I'm checking into the possibility of duplicating the WebRTC github > setup for our work. Dominique Hazaël-Massieux, developer of many of the > tools editors have been using, including the PubRules checker, has been > building up tooling for us in WebRTC, including Travis scripts. I think we > could benefit from borrowing what he's set up. > > I will ask the WebRTC Chairs in today's WebRTC editors' call if they have > any problems with it, and if not I'll talk with Dom to see what would be > needed. We have a few publication oddities that would need to be adjusted. > > Regarding repositories, many groups differ in opinion on how separated the > different specs in their groupls should be. Having started with the two > primary WebRTC specs being together but eventually separating them because > they progressed independently, I would highly recommend a separate > repository for each but with a common initial name, e.g., vctf-use-cases > for this document. > > > I’d like to better understand the reasoning and experience behind using > separate repositories for different specs. The CSV on the Web group ( > http://github.com/w3c/csvw) had four specs and three notes under way on > different timelines with no real problems from using a single repository, > and there were advantages from being able to share common examples, > bibliographies, and other tools for synchronizing shared components among > the specs. > > Gregg > > -- dan > > On Tue, Jan 19, 2016 at 3:11 PM, Shane McCarron <shane@halindrome.com> > wrote: > >> No - I don't think they have been published yet. >> >> On Tue, Jan 19, 2016 at 2:08 PM, Ian Jacobs <ij@w3.org> wrote: >> >>> >>> > On Jan 19, 2016, at 1:43 PM, Shane McCarron <shane@halindrome.com> >>> wrote: >>> > >>> > Today in the VCTF call I and a few others offered to get the use cases >>> into W3C form and cleaned up. I would like to get started on this straight >>> away. >>> >>> Hi Shane, >>> >>> Do you have a link to the minutes of the meeting? Thanks, >>> >>> Ian >>> >>> > >>> > I know that we are working on github [1]. Is there any reason not to >>> put the documents in that tree? And if they are in that tree, does it make >>> sense to put then under some top level folder (documents?) or should each >>> document be in its own top level folder (usecases)? >>> > >>> > [1] https://github.com/w3c/vctf >>> > >>> > >>> > -- >>> > -Shane >>> >>> -- >>> Ian Jacobs <ij@w3.org> http://www.w3.org/People/Jacobs >>> Tel: +1 718 260 9447 >>> >>> >>> >>> >> >> >> -- >> -Shane >> > > > -- -Shane
Received on Thursday, 21 January 2016 17:42:59 UTC