A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
GitHub: Difference between revisions
Jump to navigation
Jump to search
(→"forked from": we fixed this) |
(note that GH issues are spammable & forgeable.) |
||
| Line 13: | Line 13: | ||
* Lack of mailing list integration. | * Lack of mailing list integration. | ||
* Lack of sophisticated query mechanism found in Bugzilla. | * Lack of sophisticated query mechanism found in Bugzilla. | ||
* Spammable with forgeable/spoofable attribution. Example: [https://github.com/WebAudio/web-audio-api/issues/104#issuecomment-27174608 https://github.com/WebAudio/web-audio-api/issues/104#issuecomment-27174608]. | |||
And with GitHub in general: | And with GitHub in general: | ||
Revision as of 18:07, 29 October 2013
Most WHATWG standards are hosted on GitHub.
Makefile
To run the standard's Makefile (i.e. to run "make" in your terminal) you need to have whatwg/xref in the same parent directory as the repository of your standard (e.g. whatwg/dom). In addition you need to have installed Anolis (ms2ger/anolis).
On using GitHub Issues
Most WHATWG standards are not using GitHub Issues.
Issues some WHATWG contributors have with GitHub Issues:
- Lack of mailing list integration.
- Lack of sophisticated query mechanism found in Bugzilla.
- Spammable with forgeable/spoofable attribution. Example: https://github.com/WebAudio/web-audio-api/issues/104#issuecomment-27174608.
And with GitHub in general:
- As the new Google Code it too might disappear.
- Hard to find new standards-related activities as people tend to put them in private and/or personal repositories.
- Notification system is unclear.