Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
tools [2017/01/13 17:31] – Added public Microsoft Edge data site for CSSWG to reference gregwhitworth | 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 |
---|
====== CSSWG Tools ====== | ====== CSSWG Tools ====== |
| |
The CSSWG uses some tools to make our jobs easier. Here they are! | The CSSWG uses some tools to make our jobs easier. Here they are! |
| |
| |
| ===== Meeting Tools ===== |
| Tools particularly useful during (f2f or telcon) meetings: |
* This DokuWiki (obviously) | * This DokuWiki (obviously) |
* [[http://www.w3.org/Mail/|W3C Mailing Lists]]: specifically [[tools:www-style|www-style]] for our specs, [[http://lists.w3.org/Archives/Public/public-css-testsuite/|public-css-testsuite]] for testing, and [[http://lists.w3.org/Archives/Public/public-fx/|public-fx]] for specs we co-edit with the [[http://www.w3.org/Graphics/SVG/|SVGWG]]. We also have an [[http://lists.w3.org/Archives/Member/w3c-css-wg/|internal list]] for administrivia. | * To create an account, do (TO BE WRITTEN) |
* [[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]]. | * To get that account permission to edit group pages, do (TO BE WRITTEN) |
* [[https://www.w3.org/blog/CSS/wp-admin/|WordPress]] runs our [[http://www.w3.org/blog/CSS/|official blog]] | * We use [[https://www.w3.org/Project/IRC/|the W3C's IRC server]] for backchannel communication and for minuting during meetings |
* [[https://github.com/w3c/csswg-drafts/issues|GitHub issues]] are used to track spec issues. (Older spec issues might be found 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]].) | * 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]] |
* [[http://test.csswg.org/shepherd/|Shepherd]] is used to track test suite bugs. | * 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 |
* The CSS [[http://dev.w3.org/csswg/css-module-bikeshed/Overview.bs|module template]], [[https://github.com/tabatkins/bikeshed|the Bikeshed spec preprocessor]], and the [[http://dev.w3.org/csswg/biblio.ref|bibliographic data file]] are used to generate our specs. See [[tools:spec-processor]] for tips. (Some specs still use [[https://www.w3.org/Style/Group/css3-src/bin/postprocess|Bert's post-processor]] and the older [[http://dev.w3.org/csswg/css-module/Overview.src.html|module template]].) | * [[https://log.csswg.org/irc.w3.org/css/today|IRC Logs]] are available for our IRC channels |
* [[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. | * [[https://excalidraw.com/|Excalidraw]] and [[https://pad.w3.org/|W3C Etherpad]] in case you need a virtual whiteboard during a meeting. |
* [[irc://irc.w3.org:6665/#css|IRC]] is the real-time chat system we use for backchannel communication during meetings. | * [[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/|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]].) |
| * [[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 |
| * [[tools:www-style|www-style]] for our specs, |
| * [[http://lists.w3.org/Archives/Public/public-css-testsuite/|public-css-testsuite]] for testing, and |
| * [[http://lists.w3.org/Archives/Public/public-fx/|public-fx]] for specs we co-edit with the [[http://www.w3.org/Graphics/SVG/|SVGWG]]. |
| * We also have an [[http://lists.w3.org/Archives/Member/w3c-css-wg/|internal list]] for administrivia. |
| |
| ===== 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. |
| * Note: Some specs still use |
| * [[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]] |
| * [[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. |
| * [[http://test.csswg.org/harness/|Test Harness]] is used for running test suites and generating implementation reports. |
| * [[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 |