| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| tools [2023/07/06 10:48] – [Meeting Tools] reorganize section a bit with some inspiration from https://w3ctag.github.io/process/guide-for-tag-members#access-to-systems , add some more detail about IRC, and link to fxtf and houdini more reliably where needed dbaron | tools [2023/07/06 10:52] – [Meeting Tools] add github details from https://w3ctag.github.io/process/guide-for-tag-members#access-to-systems dbaron |
|---|
| |
| * [[https://drafts.csswg.org/|CSS Editor's Drafts]], [[https://drafts.fxtf.org/|FXTF Editor's Drafts]], and [[https://drafts.css-houdini.org/|Houdini Editor's Drafts]] are automatically generated and available with publishing history. | * [[https://drafts.csswg.org/|CSS Editor's Drafts]], [[https://drafts.fxtf.org/|FXTF Editor's Drafts]], and [[https://drafts.css-houdini.org/|Houdini Editor's Drafts]] are automatically generated and available with publishing history. |
| * GitHub issues in [[https://github.com/w3c/csswg-drafts/issues|csswg-drafts]], [[https://github.com/w3c/fxtf-drafts/issues|fxtf-drafts]], and [[https://github.com/w3c/css-houdini-drafts/issues|css-houdini-drafts]] are used to track spec issues. (Older spec issues are found in the mail archives, and might be additionally tracked in [[https://www.w3.org/Style/CSS/Tracker/|CSS Tracker]], [[https://www.w3.org/Graphics/fx/track/|FXTF Tracker]], [[https://www.w3.org/Bugs/Public/|Bugzilla]], and [[spec|this wiki]].) | * GitHub issues in [[https://github.com/w3c/csswg-drafts/issues|csswg-drafts]], [[https://github.com/w3c/fxtf-drafts/issues|fxtf-drafts]], and [[https://github.com/w3c/css-houdini-drafts/issues|css-houdini-drafts]] are used to track spec issues. (Older spec issues are found in the mail archives, and might be additionally tracked in [[https://www.w3.org/Style/CSS/Tracker/|CSS Tracker]], [[https://www.w3.org/Graphics/fx/track/|FXTF Tracker]], [[https://www.w3.org/Bugs/Public/|Bugzilla]], and [[spec|this wiki]].) To use GitHub effectively: |
| | * in your [[https://www.w3.org/users/myprofile|w3c account]] go to “Connected accounts”, make sure your github account is linked |
| | * Get yourself invited to the w3c GitHub organization, and accept the invite. You can make your membership public if you want. This (plus the account linking above) should mean you’re automatically added to https://github.com/orgs/w3c/teams/w3c-group-100-members/members . The invite should be doable by any W3C staff. (TODO: Is this step still needed?) |
| * [[tools:git|Git/GitHub]] or [[tools:hg|Mercurial]] can be used to access the version control system for our [[spec|specs]] and our [[test|tests]]. (Mercurial access is deprecated; the bidirectional mirroring may no longer be running.) | * [[tools:git|Git/GitHub]] or [[tools:hg|Mercurial]] can be used to access the version control system for our [[spec|specs]] and our [[test|tests]]. (Mercurial access is deprecated; the bidirectional mirroring may no longer be running.) |
| * [[http://www.w3.org/Mail/|W3C Mailing Lists]]: specifically | * [[http://www.w3.org/Mail/|W3C Mailing Lists]]: specifically |
