Skip to content

Commit 43c2800

Browse files
plehegarplehegar
authored
About... joint deliverables (#182)
* About... joint deliverables * Added a link to the joint deliverables from our index page
1 parent 0fdbe5f commit 43c2800

File tree

2 files changed

+117
-1
lines changed

2 files changed

+117
-1
lines changed

‎index.html

+2-1
Original file line numberDiff line numberDiff line change
@@ -214,8 +214,9 @@ <h3 id="Deliverables">Specification Development</h3>
214214
<li>Advancement on the Recommendation Track:
215215
<ul>
216216
<li><a href="https://github.com/w3c/wg-effectiveness/blob/master/process.md">W3C Process for Busy People</a></li>
217-
<li><a href="https://www.w3.org/Consortium/Process/#rec-advance">Section 6.1 Technical
217+
<li><a href="https://www.w3.org/Consortium/Process/#rec-advance">Section 6.3 Technical
218218
Reports</a> of the W3C Process</li>
219+
<li>Considerations for <a href="process/joint-deliverables.html">joint deliverables</a></li>
219220
<li><a href="https://www.w3.org/Guide/transitions">Transition requirements</a> for all W3C
220221
maturity levels (First Public Draft, Last Call, CR, PR, REC, etc.). Try also our <a href="https://w3c.github.io/transitions/nextstep.html">step finder</a> and look at <a href="https://w3c.github.io/spec-releases/milestones/">milestones calculator</a>.</li>
221222
<li><a href="https://www.w3.org/Guide/documentreview">Request Wide

‎process/joint-deliverables.html

+115
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,115 @@
1+
<!DOCTYPE html>
2+
<html lang="en">
3+
<head>
4+
<meta charset="utf-8" >
5+
<title>Joint deliverables between Groups</title>
6+
<link rel="stylesheet" href="/StyleSheets/generic-base-1.css"
7+
type="text/css">
8+
<link rel="stylesheet" type="text/css" href="../assets/main.css">
9+
<link rel="shortcut icon" href="/Icons/WWW/Literature.gif">
10+
<link rel="start" href="../" >
11+
<style>
12+
.IssueLabel-big {
13+
font-weight: 600;
14+
padding: 4px 8px;
15+
border-radius: 3px;
16+
line-height: 1.5;
17+
box-sizing: border-box;
18+
text-decoration: none;
19+
}
20+
</style>
21+
</head>
22+
<body>
23+
24+
<div id="header">
25+
<span class="logo"><a href="/"><img src="/Icons/WWW/w3c_home_nb"
26+
alt="W3C" height="48" width="72"></a></span>
27+
<div class="breadcrumb"><a href="/Guide/">The Art of
28+
Consensus</a> &#x2192;
29+
<h1>Joint deliverables<hh1>
30+
</div>
31+
<p class="baseline">This <strong>Guidebook</strong> is the collected
32+
wisdom of the W3C Group Chairs and other collaborators.</p>
33+
</div>
34+
35+
<div class="toolbox box">
36+
<h4>Nearby</h4>
37+
<ul>
38+
<li>
39+
<a href="/Consortium/Process/#WGCharter">W3C Process Document</a>
40+
</li>
41+
<li>
42+
<a href="charter.html#creation">Charter Creation</a>
43+
</li>
44+
</ul>
45+
</div>
46+
47+
<div id="Content">
48+
49+
<p>This document provides details about joint deliverables between W3C Groups.</p>
50+
51+
<h2 id="between-wgs">Joint deliverables between W3C Working Groups</h2>
52+
<p>As a general principle, each Working Group must follow its charter, including in the case of joint deliverables.</p>
53+
54+
<ol>
55+
<li id="dropping">
56+
<p>
57+
If one of the Working Groups decides to drop a joint deliverable from its charter,
58+
only the charters of the remaining Working Groups involved in that joint deliverable are applicable.
59+
</p>
60+
</li>
61+
<li id="scope">
62+
<p>
63+
A Working Group cannot publish features on the W3C standard track that are outside of its scope.
64+
The scope of the narrower Working Group prevails in joint deliverables.
65+
As such, any feature which is out of scope for one of the Working Groups involved cannot appear in the joint deliverable.
66+
</p>
67+
</li>
68+
<li id="success-criteria">
69+
<p>
70+
Each Working Group is obligated to follow its Success criteria requirements.
71+
So the success criteria of the joint deliverable is the combination of the success criteria of all of the Working Groups involved.<br>
72+
<em>Any conflict between the success criteria sections ought to be resolved before the charters are approved.</em>
73+
</p>
74+
</li>
75+
<li id="decision-policy">
76+
<p>
77+
Each Working Group must follow its decision policy.
78+
If conflicting decisions are recorded, the Working Groups need to resolved their differences.
79+
</p>
80+
<p class='example'>
81+
For example, all of the Working Groups must agree to publish a new revision of the joint deliverable in order for the publication
82+
of the joint deliverable to happen.
83+
</p>
84+
</li>
85+
<li id="patent-policy">
86+
<p>
87+
Each Working Group must follow its patent policy.<br>
88+
<em>Any conflict between the patent policy sections ought to be resolved before the charters are approved.</em>
89+
</p>
90+
<p class='example'>
91+
As of 2023, all Working Groups are following the same version of the Patent Policy so no conflict can appear.
92+
</p>
93+
</li>
94+
<li id="licensing">
95+
<p>
96+
Each Working Group must follow its licensing requirements.<br>
97+
<em>Any conflict between the licensing sections ought to be resolved before the charters are approved.</em>
98+
</p>
99+
</li>
100+
</ol>
101+
102+
<h3>Revision History</h3>
103+
<ul>
104+
<li>2023-09-14: Document created from <a href="https://github.com/w3c/w3process/issues/754#issuecomment-1719014704">#754</a>.</li>
105+
</ul>
106+
107+
</div>
108+
<hr >
109+
110+
<address><a href="https://www.w3.org/People/LeHegaret/">Philippe Le Hégaret</a>, guidebook editor<br>
111+
<a href="mailto:[email protected]">[email protected]</a><br>
112+
<a href="https://github.com/w3c/Guide">Yep, it's on GitHub</a>.
113+
</address>
114+
</body>
115+
</html>

0 commit comments

Comments
 (0)