Differences

This shows you the differences between two versions of the page.

--- tools [2023/07/07 09:51] – [Meeting Tools] tabatkins
+++ tools [2024/03/26 11:36] (current) – [Meeting Tools] fantasai
@@ Line 14: / Line 14: @@
     * [[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://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.)  This is perhaps semi-obsolete since the chairs now have the ability to add events to [[https://www.w3.org/users/myprofile/calendar/|your W3C Calendar]], but it's still somewhat maintained.
   * [[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]].)  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.
-    * in your [[https://www.w3.org/users/myprofile|w3c account]] go to “Connected accounts”, make sure your github account is linked
+    * 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]].)
-    * 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?)
+    * 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]]
-  * [[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.)
+    * See also [[https://speced.github.io/spec-maintenance/w3c/csswg-drafts/|Spec Maintenance Tracker]].
+  * 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
+    * 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]].
   * [[http://www.w3.org/Mail/|W3C Mailing Lists]]: specifically
-    * [[tools:www-style|www-style]] for **all** CSS spec-related discussion,
+    * [[tools:www-style|www-style]] used to be used for for **all** CSS spec-related discussion, now moved to GitHub issues,
-    * [[http://lists.w3.org/Archives/Public/public-fx/|public-fx]] for specs we co-edit with the [[http://www.w3.org/Graphics/SVG/|SVGWG]].
+    * [[https://lists.w3.org/Archives/Public/public-fx/|public-fx]] for specs we co-edit with the [[http://www.w3.org/Graphics/SVG/|SVGWG]].
+    * [[https://lists.w3.org/Archives/Public/public-houdini/|public-houdini]] for the Houdini Task Force spec (joint with the TAG)
     * The [[http://lists.w3.org/Archives/Member/w3c-css-wg/|CSSWG private list]] for administrivia **only**, no spec discussions occur here.
@@ Line 42: / Line 47: @@
   * [[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