-
Notifications
You must be signed in to change notification settings - Fork 39
/
index.html
122 lines (120 loc) · 5.47 KB
/
index.html
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
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<title>W3C on GitHub</title>
<link rel="stylesheet" href="css/wgio.css">
<link rel="icon" type="image/x-icon" href="//labs.w3.org/favicon.ico">
</head>
<body>
<header>
<h1>W3C on GitHub</h1>
</header>
<nav>
<a href="/">Home</a>
•
<a href="https://github.com/w3c/">Repositories</a>
•
<a href="https://help.github.com/">GitHub Help</a>
</nav>
<main>
<p>
Many W3C work groups conduct their work in Github, but not all. Please, explore our repos, watch, star, contribute.
</p>
<p>
The purpose of this page is to progressively list the resources useful when working on
W3C projects using GitHub.
The following links should help you find your way.
Refer to the <a href="faq.html">FAQ</a> for details about the breadth and scope of W3C projects.
</p>
<dl>
<dt><a href="https://github.com/w3c/">Repositories</a></dt>
<dd>
If you are looking for a specific project that we maintain on GitHub, the best is to go
straight to the list of repositories, which is searchable.<br>
Repositories under the W3C organization may represent the work of Working Groups, Interest Groups,
Community Groups, or Team projects, with varied status and formality. Documents and repositories should
maintain their own status indicators.
</dd>
<dt><a href="best-practices.html">Best practices and recommended tools</a></dt>
<dd>
General guidelines, useful tools, tips.
</dd>
<dt><a href="git.html">Git recipes & tricks</a></dt>
<dd>
Configuration, useful aliases and advice — specific for command-line Git.
</dd>
<dt><a href="https://help.github.com/">GitHub Help</a></dt>
<dd>
Most of the issues people have using GitHub are in fact due to <code>git</code>. General
<code>git</code> and GitHub questions will not be addressed here.
GitHub's own help site linked above is a very helpful resource.
You can also usually just cut and paste from
<a href="http://stackoverflow.com/questions/tagged/git">Stack Overflow's git questions</a>.
Eric Eggert conducted a <a href="http://w3c.github.io/wai-gh-training-2015-06-29/">training
session about Git and GitHub (1h40′ video + slides)</a>.
</dd>
<dt><a href="faq.html">FAQ</a></dt>
<dd>
Introductory-level questions that are commonly asked about using GitHub specifically in a W3C
context.
</dd>
<dt><a href="specs.html">Using GitHub for Spec Work</a></dt>
<dd>
A step-by-step guide to get up and running with a specification on GitHub, from Tobie.
</dd>
<dt><a href="repo-transfer.html">Transfer a repository to the W3C GitHub organization</a></dt>
<dd>
A guide to transfer a GitHub repository to the W3C organization.
</dd>
<dt><a href="workflow.html">Workflow for editors and other contributors</a></dt>
<dd>
A guide for a clean and sane workflow for editors.
</dd>
<dt><a href="repo-management.html">Contributor Management</a></dt>
<dd>
If your group accepts contributions from a broad set of people through pull requests, this
tool can help you make sure that the contributors have signed the requisite IPR agreements.
</dd>
<dt>
<a href="https://github.com/w3c/echidna/wiki/Setting-up-Echidna-as-a-GitHub-hook">Automatic
Publication from GitHub</a>
</dt>
<dd>
In general, it is strongly recommended to use <a
href="https://github.com/w3c/echidna/wiki">Echidna</a> to publish TR documents rather than the
manual path that goes through the Webmaster (assuming of course that your document is of a
supported type). This document explains how to set up your repository using Travis CI in order
to automatically publish on every commit (to a given branch) and never again have to worry
about what people used to call “heartbeat” publications. With this, you can even get rid of
the notion of Editor's Draft altogether.
</dd>
<dt><a href="https://labs.w3.org/midgard/">Keeping Track with Midgard</a></dt>
<dd>
Because work that happens on GitHub is spread out across many repositories, it can be challenging
to remain informed about what's going on. Midgard helps there by
filtering the data into mailboxes so that you can for instance get all the events for
WebRTC repositories. Log in there with your W3C credentials, and just start using it. Note:
it does not at this time have many filters and it is likely that your area of interest may not
yet have one. If you wish to add one (which is easy) you should read
<a href="https://github.com/w3c/midgard/blob/master/DEVELOPMENT.md#libfilterseventsjs">the
documentation on Pheme filters</a>.
</dd>
<dt><a href="w3c.json.html">The <code>w3c.json</code> file</a></dt>
<dd>
This is a small metadata file that is recommended for GitHub repositories under the
<code>w3c</code> organisation.
</dd>
<dt><a href="backup.html">Backup of GitHub organizations</a></dt>
<dd>How W3C keeps a backup of the different GitHub organizations</dd>
</dl>
</main>
<footer>
<address><a href="https://github.com/w3c/w3c.github.io/">We are on GitHub</a></address>
<p>
<a href="https://www.w3.org/"><img src="img/w3c.svg" width="65" height="45" alt="W3C Logo"></a>
</p>
</footer>
</body>
</html>