| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| tools [2023/07/12 09:09] – [Meeting Tools] use shorter url dbaron | tools [2023/07/18 08:07] – [Experiments] plinss |
|---|
| * 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]].) 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-100-members and 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?) |
| * Spec sources are maintained on [[tools:git|Git/GitHub]] and are written in [[https://speced.github.io/bikeshed/|Bikeshed]]. | * Spec sources are maintained on [[tools:git|Git/GitHub]] and are written in [[https://speced.github.io/bikeshed/|Bikeshed]]. |
| * [[http://www.w3.org/Mail/|W3C Mailing Lists]]: specifically | * [[http://www.w3.org/Mail/|W3C Mailing Lists]]: specifically |
| * [[https://wiki.csswg.org/tools/doc|Disposition of Comments tool]] Provides a GUI for easy editing and exploring DoCs. | * [[https://wiki.csswg.org/tools/doc|Disposition of Comments tool]] Provides a GUI for easy editing and exploring DoCs. |
| |
| ===== Experiments ===== | |
| Tools setup for trying out, or otherwise playing with. Could change / break at any time. | |
| * https://social.csswg.org/ - Mastodon instance | |
| * See http://www.unmung.com/mastoview?url=social.csswg.org&view=local for recent public posts | |
