- From: bergi <bergi@axolotlfarm.org>
- Date: Fri, 24 Jun 2016 00:05:13 +0200
- To: Ruben Verborgh <ruben.verborgh@ugent.be>, Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: Hydra <public-hydra@w3.org>
Hi all, Am 18.06.2016 um 20:16 schrieb Ruben Verborgh: >> - Where should the development happen? Do we want to get a repository >> under the HydraCG organization on GitHub? > > For _the_ Hydra client, it should be HydraCG for me. +1 >> - How should we structure the group? Should assign different roles >> to people? > > Different roles seem good, yes. +1 >> - Should there be 1-2 persons that are responsible to lead the group >> and drive the effort? Who should that be? > > Yes. I'm volunteering (but not yet sure about agenda). I can help, but it's very important for me that we support different formats via the RDFJS spec. And it should be modular (support of high level libraries like SimplRDF). If it's tied to much to JSON-LD I will continue my work on hydra-fetch. >> - What will be our primary communication medium? How do we ensure it >> is properly archived? > > GitHub issues. Calls. Occasional e-mails. +1 Gitter could be also useful, but issues and comments should be create for summaries of discussions. >> - How do we make decisions as a group? > > Some people have to drive the decision process, > depending on the amount of effort they put in. > Contributions by anyone are welcome. +1 Depending on the number of people that contribute, we could say x +1 are required to merge a PR. >> - How do we plan the development? How do we track progress? > > Feature-based planning with milestones. > Tracking through GitHub issues and milestones. +1 >> - How and how often do we report back to the Hydra W3C Community Group >> in case most of our communication/collaborations happens off the Hydra >> mailing list? > > At every milestone. +1 bergi
Received on Thursday, 23 June 2016 22:05:34 UTC