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

From WHATWG Wiki
Jump to navigation Jump to search
(note that GH issues are spammable & forgeable.)
(Replaced content with "{{moved|[https://github.com/whatwg WHATWG on GitHub].}}")
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
Most WHATWG standards are [https://github.com/whatwg hosted on GitHub].
{{moved|[https://github.com/whatwg WHATWG on GitHub].}}
 
== Makefile ==
 
To run the standard's Makefile (i.e. to run "make" in your terminal) you need to have [https://github.com/whatwg/xref whatwg/xref] in the same parent directory as the repository of your standard (e.g. [https://github.com/whatwg/dom 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 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.
 
[[Category:Spec coordination]]

Latest revision as of 17:44, 24 January 2018

This page has moved to WHATWG on GitHub.