This article is a stub. You can help the W3C wiki by expanding it.
What are best practices for use of Github in W3C efforts?
1. We should find a mechanism to remind all people who show up at the Github repository for a W3C WG Spec that we want contributions from Members or Invited Experts. Participants who are not IEs or from Member organizations who would like to make contributions should explore joining or becoming an IE.
- Is there a policy document (or similar) covering the use of Github versus W3C-hosted version control? (and presumably technology preference is a factor in that, but not the only factor)
... add your question/issue here
- people involved in W3C Working Groups have W3C Account; having them using github require a separate GitHub account?
- A: Yes
- If a W3C group uses github as its basis of collaboration, participation in the group is subject to github's privacy policies etc. When is that a reasonable trade-off?
- Use of git itself is decentralized so participants can collaborate directly with peers as alternative to going through github. But facilities such as issue tracking and pull requests are not; they necessarily involve use of github's web site.
- we need infrastructure to use github to develop content, but have it published on a W3.org URI
- how do we ensure that we keep a log of the interactions that happen on github? (if only for historical purposes)
- A: a git repository would seem to suffice as its own log; for issues, there's an API. Presumably the API suffices for pull requests etc. as well.
- centralized interactions on w3.org services made it (somewhat) easier to search for particular items and topics; having these interactions spread across multiple uncoordinated github repositories makes it harder
- Is there a w3C tutorial page or guide to use Github
- on deploying specs using GH: http://tobie.github.io/specs-on-github/
- https://www.w3.org/wiki/Guide/GitHub gives some good practice
- https://github.com/w3c/csvw/blob/gh-pages/publishing_process.md gives a possible approach to combine github, respec, the W3C publishing process, with a reasonable trace of past versions all at the same place