| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| tools [2022/06/02 10:53] – [Meeting Tools] add excalidraw fantasai | tools [2023/07/06 11:32] – [Editing Publishing Testing] tabatkins |
|---|
| Tools particularly useful during (f2f or telcon) meetings: | Tools particularly useful during (f2f or telcon) meetings: |
| * This DokuWiki (obviously) | * This DokuWiki (obviously) |
| * [[irc://irc.w3.org:6665/#css|IRC]] is the real-time chat system we use for backchannel communication during meetings. | * To create an account, do (TO BE WRITTEN) |
| * [[https://excalidraw.com/|Excalidraw]] in case you need a virtual whiteboard. | * To get that account permission to edit group pages, do (TO BE WRITTEN) |
| * [[http://www.w3.org/2001/12/zakim-irc-bot|Zakim]] is <del> a conference bridge with</del> an IRC bot that helps us manage our telecons. | * We use [[https://www.w3.org/Project/IRC/|the W3C's IRC server]] for backchannel communication and for minuting during meetings |
| * A [[https://bocoup.com/blog/how-to-scribe-at-tpac|blog post]] on some of the conventions we use on IRC, with a scribing focus | * We use multiple IRC bots: [[http://www.w3.org/2001/12/zakim-irc-bot|Zakim]], [[https://www.w3.org/2002/03/RRSAgent|RRSAgent]], [[https://github.com/dbaron/wgmeeting-github-ircbot/|github-bot]] |
| * [[https://log.csswg.org/irc.w3.org/css/today|IRC Logs]] are available for our IRC channels | * A [[https://bocoup.com/blog/how-to-scribe-at-tpac|blog post]] on some of the conventions we use on IRC, with a scribing focus |
| * [[https://cal.csswg.org/public.php/csswg/calendar.ics|iCal Feed]] contains our meeting times. | * [[https://log.csswg.org/irc.w3.org/css/today|IRC Logs]] are available for our IRC channels |
| | * [[https://excalidraw.com/|Excalidraw]] and [[https://pad.w3.org/|W3C Etherpad]] in case you need a virtual whiteboard during a meeting. |
| | * [[https://cal.csswg.org/public.php/csswg/calendar.ics|iCal Feed]] contains our meeting times. (Ask Peter Linss if you need permissions to edit this calendar.) |
| * [[https://data.microsoftedge.com|Interop Browser Data]] Provides crawler data from Chrome/Microsoft Edge about CSS properties, values and top sites utilized | * [[https://data.microsoftedge.com|Interop Browser Data]] Provides crawler data from Chrome/Microsoft Edge about CSS properties, values and top sites utilized |
| |
| * [[https://drafts.csswg.org/|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. |
| * [[https://github.com/w3c/csswg-drafts/issues|GitHub issues]] are used to track spec issues. (Older spec issues are found in the mail archives, and might be additionally tracked in | * 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: |
| * [[https://www.w3.org/Style/CSS/Tracker/|CSS Tracker]], | * in your [[https://www.w3.org/users/myprofile|w3c account]] go to “Connected accounts”, make sure your github account is linked |
| * [[https://www.w3.org/Graphics/fx/track/|FXTF Tracker]], | * 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?) |
| * [[https://www.w3.org/Bugs/Public/|Bugzilla]], and | * [[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.) |
| * [[spec|this wiki]].) | |
| * [[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]]. | |
| * [[http://www.w3.org/Mail/|W3C Mailing Lists]]: specifically | * [[http://www.w3.org/Mail/|W3C Mailing Lists]]: specifically |
| * [[tools:www-style|www-style]] for our specs, | * [[tools:www-style|www-style]] for our specs, |
| |
| ===== Editing Publishing Testing ===== | ===== Editing Publishing Testing ===== |
| * The CSS [[https://drafts.csswg.org/css-module-bikeshed/Overview.bs|module template]], [[https://github.com/tabatkins/bikeshed|the Bikeshed spec preprocessor]], and the [[https://drafts.csswg.org/biblio.ref|bibliographic data file]] are used to generate our specs. A more comprehensive set of bibliographic data can be found at [[https://www.specref.org/|SpecRef]], which is automatically loaded into Bikeshed. See [[tools:spec-processor]] for tips. | * Specs are written in [[https://speced.github.io/bikeshed|Bikeshed]] ([[https://speced.github.io/bikeshed/#install-normal|install instructions]], or use [[https://speced.github.io/bikeshed/#remote|curl or the web form]]. |
| * Note: Some specs still use | * A fresh spec should be started from the [[https://drafts.csswg.org/css-module-bikeshed/Overview.bs|module template]]. |
| | * Bibliographic data is sourced from [[https://www.specref.org/|SpecRef]], which is automatically loaded into Bikeshed. See [[tools:spec-processor]] for tips. |
| | * Note: A few very old specs specs still use |
| * [[https://www.w3.org/Style/Group/css3-src/bin/postprocess|Bert's post-processor]] | * [[https://www.w3.org/Style/Group/css3-src/bin/postprocess|Bert's post-processor]] |
| * the older [[http://dev.w3.org/csswg/css-module/Overview.src.html|module template]] | * the older [[http://dev.w3.org/csswg/css-module/Overview.src.html|module template]] |
| | * Ask Tab, fantasai, or ChrisL for help if you need to edit these. |
| * [[https://www.w3.org/blog/CSS/wp-admin/|WordPress login]] for our [[http://www.w3.org/blog/CSS/|official blog]] | * [[https://www.w3.org/blog/CSS/wp-admin/|WordPress login]] for our [[http://www.w3.org/blog/CSS/|official blog]] |
| * [[http://test.csswg.org/shepherd/|Shepherd]] is used to track test suite bugs. | * [[https://github.com/web-platform-tests/wpt#readme|Web Platform Tests]] is used to store and run test suites. |
| * [[http://test.csswg.org/harness/|Test Harness]] is used for running test suites and generating implementation reports. | * [[https://wpt.fyi/]] shows current testsuite results and links to sources. |
| | * [[https://wpt.live/]] is a runner for all the WPT tests. |
| * [[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. |
| |
