forked from w3c/csswg-wiki
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
159 lines (157 loc) · 14 KB
/
Copy pathindex.html
File metadata and controls
159 lines (157 loc) · 14 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>CSSWG Tools - CSS Working Group Wiki (Archive)</title>
<style>
*, *::before, *::after { box-sizing: border-box; }
body {
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;
max-width: 900px; margin: 0 auto; padding: 1.5em 1em; line-height: 1.6;
color: #1f2328; background: #fff;
}
.archive-banner {
background: #fff8c5; border: 1px solid #d4a72c; border-radius: 6px;
padding: 0.75em 1em; margin-bottom: 1.5em; font-size: 0.9em;
}
.archive-banner strong { color: #6e5600; }
header { border-bottom: 1px solid #d1d5db; padding-bottom: 1em; margin-bottom: 1.5em; }
header h1 { margin: 0; font-size: 1.25em; }
header h1 a { color: #0366d6; text-decoration: none; }
header h1 a:hover { text-decoration: underline; }
nav { margin-top: 0.5em; font-size: 0.9em; }
nav a { color: #656d76; text-decoration: none; margin-right: 1em; }
nav a:hover { color: #0366d6; }
h1, h2, h3, h4 { color: #1f2328; margin-top: 1.5em; }
h1:first-child { margin-top: 0; }
a { color: #0366d6; }
code { background: #f6f8fa; padding: 0.15em 0.3em; border-radius: 3px; font-size: 0.9em; }
pre { background: #f6f8fa; padding: 1em; overflow: auto; border-radius: 6px; }
pre code { background: none; padding: 0; }
table { border-collapse: collapse; margin: 1em 0; }
th, td { border: 1px solid #d1d5db; padding: 0.4em 0.8em; }
th { background: #f6f8fa; }
img { max-width: 100%; }
.breadcrumb { font-size: 0.85em; color: #656d76; margin-bottom: 1em; }
.breadcrumb a { color: #656d76; }
ul, ol { padding-left: 1.5em; }
li { margin: 0.25em 0; }
.plugin_note { background: #f0f4f8; border-left: 4px solid #0366d6; padding: 0.75em 1em; margin: 1em 0; border-radius: 3px; }
abbr { text-decoration: underline dotted; cursor: help; }
@media (prefers-color-scheme: dark) {
body { background: #0d1117; color: #e6edf3; }
.archive-banner { background: #3d2e00; border-color: #6e5600; }
.archive-banner strong { color: #f0c000; }
header { border-bottom-color: #30363d; }
header h1 a { color: #58a6ff; }
nav a { color: #8b949e; }
nav a:hover { color: #58a6ff; }
h1, h2, h3, h4 { color: #e6edf3; }
a { color: #58a6ff; }
code, pre { background: #161b22; }
th, td { border-color: #30363d; }
th { background: #161b22; }
.breadcrumb, .breadcrumb a { color: #8b949e; }
.plugin_note { background: #161b22; border-color: #58a6ff; }
}
</style>
</head>
<body>
<div class="archive-banner">
<strong>Archive Notice:</strong> This is a read-only archive of the CSS Working Group Wiki.
The original wiki was hosted at wiki.csswg.org.
</div>
<header>
<h1><a href="/">CSS Working Group Wiki</a></h1>
<nav>
<a href="/">Home</a>
<a href="/spec/">Specs</a>
<a href="/ideas/">Ideas</a>
<a href="/test/">Testing</a>
<a href="/wiki/">About</a>
</nav>
</header>
<div class="breadcrumb"><a href="/">Home</a> / tools</div>
<main>
<!-- TOC START -->
<div id="dw__toc" class="dw__toc">
<h3 class="toggle">Table of Contents</h3>
<div>
<ul class="toc">
<li class="level1"><a href="#csswg-tools">CSSWG Tools</a><ul class="toc">
<li class="level2"><a href="#meeting-tools">Meeting Tools</a></li>
<li class="level2"><a href="#editing-publishing-testing">Editing Publishing Testing</a></li>
</ul></li>
</ul>
</div>
</div>
<!-- TOC END -->
<h1 id="csswg-tools">CSSWG Tools</h1>
<p>
The CSSWG uses some tools to make our jobs easier. Here they are!
</p><h2 id="meeting-tools">Meeting Tools</h2>
<p>
Tools particularly useful during (f2f or telcon) meetings:
</p>
<ul>
<li class="level1 node">This DokuWiki (obviously)<ul>
<li class="level2">To create an account, <a href="https://test.csswg.org/shepherd/register/" title="https://test.csswg.org/shepherd/register/" rel="noopener">register on Shepherd</a>.</li>
<li class="level2">To get that account permission to edit group pages, email plinss and/or fantasai</li>
</ul>
</li>
<li class="level1 node">We use <a href="https://www.w3.org/Project/IRC/" title="https://www.w3.org/Project/IRC/" rel="noopener">the W3C's IRC server</a> for backchannel communication and for minuting during meetings<ul>
<li class="level2 node">We use multiple <abbr title="Internet Relay Chat">IRC</abbr> bots: <a href="http://www.w3.org/2001/12/zakim-irc-bot" title="http://www.w3.org/2001/12/zakim-irc-bot" rel="noopener">Zakim</a>, <a href="https://www.w3.org/2002/03/RRSAgent" title="https://www.w3.org/2002/03/RRSAgent" rel="noopener">RRSAgent</a>, <a href="https://github.com/dbaron/wgmeeting-github-ircbot/" title="https://github.com/dbaron/wgmeeting-github-ircbot/" rel="noopener">github-bot</a><ul>
<li class="level3"><a href="/tools/scribing-conventions/" title="tools:scribing-conventions">General IRC conventions</a></li>
<li class="level3">A <a href="https://bocoup.com/blog/how-to-scribe-at-tpac" title="https://bocoup.com/blog/how-to-scribe-at-tpac" rel="noopener">blog post</a> on some of the conventions we use on <abbr title="Internet Relay Chat">IRC</abbr>, with a scribing focus</li>
</ul>
</li>
<li class="level2"><a href="https://log.csswg.org/irc.w3.org/css/today" title="https://log.csswg.org/irc.w3.org/css/today" rel="noopener">IRC Logs</a> are available for our <abbr title="Internet Relay Chat">IRC</abbr> channels</li>
</ul>
</li>
<li class="level1"><a href="https://excalidraw.com/" title="https://excalidraw.com/" rel="noopener">Excalidraw</a> and <a href="https://pad.w3.org/" title="https://pad.w3.org/" rel="noopener">W3C Etherpad</a> in case you need a virtual whiteboard during a meeting.</li>
<li class="level1"><a href="https://cal.csswg.org/public.php/csswg/calendar.ics" title="https://cal.csswg.org/public.php/csswg/calendar.ics" rel="noopener">iCal Feed</a> 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 <a href="https://www.w3.org/users/myprofile/calendar/" title="https://www.w3.org/users/myprofile/calendar/" rel="noopener">your W3C Calendar</a>, but it's still somewhat maintained.</li>
<li class="level1"><a href="https://data.microsoftedge.com" title="https://data.microsoftedge.com" rel="noopener">Interop Browser Data</a> Provides crawler data from Chrome/Microsoft Edge about <abbr title="Cascading Style Sheets">CSS</abbr> properties, values and top sites utilized</li>
</ul>
<ul>
<li class="level1"><a href="https://drafts.csswg.org/index.html" title="https://drafts.csswg.org/index.html" rel="noopener">CSS Editor's Drafts</a>, <a href="https://drafts.fxtf.org/" title="https://drafts.fxtf.org/" rel="noopener">FXTF Editor's Drafts</a>, and <a href="https://drafts.css-houdini.org/" title="https://drafts.css-houdini.org/" rel="noopener">Houdini Editor's Drafts</a> are automatically generated and available with publishing history.</li>
<li class="level1 node">GitHub issues in <a href="https://github.com/w3c/csswg-drafts/issues" title="https://github.com/w3c/csswg-drafts/issues" rel="noopener">csswg-drafts</a>, <a href="https://github.com/w3c/fxtf-drafts/issues" title="https://github.com/w3c/fxtf-drafts/issues" rel="noopener">fxtf-drafts</a>, and <a href="https://github.com/w3c/css-houdini-drafts/issues" title="https://github.com/w3c/css-houdini-drafts/issues" rel="noopener">css-houdini-drafts</a> are used to track <abbr title="specification">spec</abbr> issues.<ul>
<li class="level2">Older <abbr title="specification">spec</abbr> issues are found in the mail archives, and might be additionally tracked in <a href="https://www.w3.org/Style/CSS/Tracker/" title="https://www.w3.org/Style/CSS/Tracker/" rel="noopener">CSS Tracker</a>, <a href="https://www.w3.org/Graphics/fx/track/" title="https://www.w3.org/Graphics/fx/track/" rel="noopener">FXTF Tracker</a>, <a href="https://www.w3.org/Bugs/Public/" title="https://www.w3.org/Bugs/Public/" rel="noopener">Bugzilla</a>, and <a href="/spec/" title="spec">this wiki</a>.)</li>
<li class="level2">Issues in these github repositories are permanently archived in <a href="https://lists.w3.org/Archives/Public/public-css-archive/" title="https://lists.w3.org/Archives/Public/public-css-archive/" rel="noopener">public-css-archive</a>, <a href="https://lists.w3.org/Archives/Public/public-fxtf-archive/" title="https://lists.w3.org/Archives/Public/public-fxtf-archive/" rel="noopener">public-fxtf-archive</a>, and <a href="https://lists.w3.org/Archives/Public/public-houdini-archive/" title="https://lists.w3.org/Archives/Public/public-houdini-archive/" rel="noopener">public-houdini-archive</a></li>
<li class="level2">See also <a href="https://speced.github.io/spec-maintenance/w3c/csswg-drafts/" title="https://speced.github.io/spec-maintenance/w3c/csswg-drafts/" rel="noopener">Spec Maintenance Tracker</a>.</li>
</ul>
</li>
<li class="level1 node">To use GitHub effectively:<ul>
<li class="level2">in your <a href="https://www.w3.org/users/myprofile" title="https://www.w3.org/users/myprofile" rel="noopener">w3c account</a> go to “Connected accounts”, make sure your github account is linked otherwise it will not show up on the <a href="https://www.w3.org/groups/wg/css/participants/" title="https://www.w3.org/groups/wg/css/participants/" rel="noopener">CSSWG participant list</a> and a bot will flag your pull requests</li>
<li class="level2">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 <a href="https://github.com/orgs/w3c/teams/w3c-group-32061-members" title="https://github.com/orgs/w3c/teams/w3c-group-32061-members" rel="noopener">https://github.com/orgs/w3c/teams/w3c-group-32061-members</a> (where you can check whether you're in the groups). The invite should be doable by any <abbr title="World Wide Web Consortium">W3C</abbr> staff. (TODO: Is this step still needed?)</li>
</ul>
</li>
<li class="level1">Spec sources are maintained on <a href="/tools/git/" title="tools:git">Git/GitHub</a> and are written in <a href="https://speced.github.io/bikeshed/" title="https://speced.github.io/bikeshed/" rel="noopener">Bikeshed</a>.</li>
<li class="level1 node"><a href="http://www.w3.org/Mail/" title="http://www.w3.org/Mail/" rel="noopener">W3C Mailing Lists</a>: specifically<ul>
<li class="level2"><a href="/tools/www-style/" title="tools:www-style">www-style</a> used to be used for for <strong>all</strong> <abbr title="Cascading Style Sheets">CSS</abbr> <abbr title="specification">spec</abbr>-related discussion, now moved to GitHub issues,</li>
<li class="level2"><a href="https://lists.w3.org/Archives/Public/public-fx/" title="https://lists.w3.org/Archives/Public/public-fx/" rel="noopener">public-fx</a> for specs we co-edit with the <a href="http://www.w3.org/Graphics/SVG/" title="http://www.w3.org/Graphics/SVG/" rel="noopener">SVGWG</a>.</li>
<li class="level2"><a href="https://lists.w3.org/Archives/Public/public-houdini/" title="https://lists.w3.org/Archives/Public/public-houdini/" rel="noopener">public-houdini</a> for the Houdini Task Force <abbr title="specification">spec</abbr> (joint with the TAG)</li>
<li class="level2">The <a href="http://lists.w3.org/Archives/Member/w3c-css-wg/" title="http://lists.w3.org/Archives/Member/w3c-css-wg/" rel="noopener">CSSWG private list</a> for administrivia <strong>only</strong>, no <abbr title="specification">spec</abbr> discussions occur here.</li>
</ul>
</li>
</ul><h2 id="editing-publishing-testing">Editing Publishing Testing</h2>
<ul>
<li class="level1">Specs are written in <a href="https://speced.github.io/bikeshed" title="https://speced.github.io/bikeshed" rel="noopener">Bikeshed</a> (<a href="https://speced.github.io/bikeshed/#install-normal" title="https://speced.github.io/bikeshed/#install-normal" rel="noopener">install instructions</a>, or use <a href="https://speced.github.io/bikeshed/#remote" title="https://speced.github.io/bikeshed/#remote" rel="noopener">curl or the web form</a>)</li>
<li class="level1">A fresh <abbr title="specification">spec</abbr> should be started from the <a href="https://drafts.csswg.org/css-module-bikeshed/Overview.bs" title="https://drafts.csswg.org/css-module-bikeshed/Overview.bs" rel="noopener">module template</a>.</li>
<li class="level1">Bibliographic data is sourced from <a href="https://www.specref.org/" title="https://www.specref.org/" rel="noopener">SpecRef</a>, which is automatically loaded into Bikeshed.</li>
<li class="level1 node">Note: A few very old specs specs still use<ul>
<li class="level2"><a href="https://www.w3.org/Style/Group/css3-src/bin/postprocess" title="https://www.w3.org/Style/Group/css3-src/bin/postprocess" rel="noopener">Bert's post-processor</a></li>
<li class="level2">the older <a href="http://dev.w3.org/csswg/css-module/Overview.src.html" title="http://dev.w3.org/csswg/css-module/Overview.src.html" rel="noopener">module template</a></li>
<li class="level2">See <a href="/tools/spec-processor/" title="tools:spec-processor">CSSWG and other post processing</a> for tips.</li>
<li class="level2">Ask Tab, fantasai, or ChrisL for help if you need to edit these.</li>
</ul>
</li>
<li class="level1"><a href="https://www.w3.org/blog/CSS/wp-admin/" title="https://www.w3.org/blog/CSS/wp-admin/" rel="noopener">WordPress login</a> for our <a href="http://www.w3.org/blog/CSS/" title="http://www.w3.org/blog/CSS/" rel="noopener">official blog</a></li>
<li class="level1"><a href="https://github.com/web-platform-tests/wpt#readme" title="https://github.com/web-platform-tests/wpt#readme" rel="noopener">Web Platform Tests</a> is used to store and run test suites.</li>
<li class="level1"><a href="https://wpt.fyi/" title="https://wpt.fyi/" rel="noopener">https://wpt.fyi/</a> shows current testsuite results and links to sources.</li>
<li class="level1"><a href="https://wpt.live/" title="https://wpt.live/" rel="noopener">https://wpt.live/</a> is a runner for all the WPT tests.</li>
<li class="level1"><a href="https://wiki.csswg.org/tools/doc" title="https://wiki.csswg.org/tools/doc" rel="noopener">Disposition of Comments tool</a> Provides a <abbr title="Graphical User Interface">GUI</abbr> for easy editing and exploring DoCs.</li>
</ul>
</main>
</body>
</html>