| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| tools [2023/07/18 08:07] – [Experiments] plinss | tools [2023/07/21 14:32] – [Meeting Tools] mention github archives, and restructure lists to accomodate 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]].) To use GitHub effectively: | * 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]].) |
| | * Issues in these github repositories are permanently archived in [[https://lists.w3.org/Archives/Public/public-css-archive/|public-css-archive]], [[https://lists.w3.org/Archives/Public/public-fxtf-archive/|public-fxtf-archive]], and [[https://lists.w3.org/Archives/Public/public-houdini-archive/|public-houdini-archive]] |
| | * 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 otherwise it will not show up on the [[https://www.w3.org/groups/wg/css/participants/|CSSWG participant list]] and a bot will flag your pull requests | * in your [[https://www.w3.org/users/myprofile|w3c account]] go to “Connected accounts”, make sure your github account is linked otherwise it will not show up on the [[https://www.w3.org/groups/wg/css/participants/|CSSWG participant list]] and a bot will flag your pull requests |
| * 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-32061-members (where you can check whether you're in the groups). The invite should be doable by any W3C staff. (TODO: Is this step still needed?) | * 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-32061-members (where you can check whether you're in the groups). The invite should be doable by any W3C staff. (TODO: Is this step still needed?) |
