- W3C Process for Busy People -
- Section 6.1 Technical
+
- Section 6.3 Technical Reports of the W3C Process
+- Considerations for joint deliverables
- Transition requirements for all W3C maturity levels (First Public Draft, Last Call, CR, PR, REC, etc.). Try also our step finder and look at milestones calculator.
- Request Wide diff --git a/process/joint-deliverables.html b/process/joint-deliverables.html new file mode 100644 index 00000000..ce29b15f --- /dev/null +++ b/process/joint-deliverables.html @@ -0,0 +1,115 @@ + + + + +
Joint deliverables between Groups + + + + + + + + +++ ++ +
This Guidebook is the collected +wisdom of the W3C Group Chairs and other collaborators.
+++ +Nearby
+-
+
- + W3C Process Document + +
- + Charter Creation + +
+ ++This document provides details about joint deliverables between W3C Groups.
+ +Joint deliverables between W3C Working Groups
+As a general principle, each Working Group must follow its charter, including in the case of joint deliverables.
+ +-
+
-
+
+ If one of the Working Groups decides to drop a joint deliverable from its charter, + only the charters of the remaining Working Groups involved in that joint deliverable are applicable. +
+
+ -
+
+ A Working Group cannot publish features on the W3C standard track that are outside of its scope. + The scope of the narrower Working Group prevails in joint deliverables. + As such, any feature which is out of scope for one of the Working Groups involved cannot appear in the joint deliverable. +
+
+ -
+
+ Each Working Group is obligated to follow its Success criteria requirements. + So the success criteria of the joint deliverable is the combination of the success criteria of all of the Working Groups involved.
+
+ Any conflict between the success criteria sections ought to be resolved before the charters are approved. +
+ -
+
+ Each Working Group must follow its decision policy. + If conflicting decisions are recorded, the Working Groups need to resolved their differences. +
++ For example, all of the Working Groups must agree to publish a new revision of the joint deliverable in order for the publication + of the joint deliverable to happen. +
+
+ -
+
+ Each Working Group must follow its patent policy.
+
+ Any conflict between the patent policy sections ought to be resolved before the charters are approved. ++ As of 2023, all Working Groups are following the same version of the Patent Policy so no conflict can appear. +
+
+ -
+
+ Each Working Group must follow its licensing requirements.
+
+ Any conflict between the licensing sections ought to be resolved before the charters are approved. +
+
Revision History
+-
+
- 2023-09-14: Document created from #754. +
+ +Philippe Le Hégaret, guidebook editor
+ plh@w3.org
+ Yep, it's on GitHub. + + +