From 1a39a739d66249c7997fde462828fe575159f87d Mon Sep 17 00:00:00 2001 From: plehegar Date: Fri, 15 Sep 2023 08:53:25 +0200 Subject: [PATCH 1/2] About... joint deliverables --- process/joint-deliverables.html | 115 ++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 process/joint-deliverables.html diff --git a/process/joint-deliverables.html b/process/joint-deliverables.html new file mode 100644 index 000000000..ce29b15fd --- /dev/null +++ b/process/joint-deliverables.html @@ -0,0 +1,115 @@ + + + + +Joint deliverables between Groups + + + + + + + + + + +
+

Nearby

+ +
+ +
+ +

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.

+ +
    +
  1. +

    + 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. +

    +
    2. +
  2. +

    + 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. +

    +
    3. +
  3. +

    + 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. +

    +
    4. +
  4. +

    + 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. +

    +
    5. +
  5. +

    + 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. +

    +
    6. +
  6. +

    + Each Working Group must follow its licensing requirements.
    + Any conflict between the licensing sections ought to be resolved before the charters are approved. +

    +
    7. +
+ +

Revision History

+ + +
+
+ +
Philippe Le Hégaret, guidebook editor
+ plh@w3.org
+ Yep, it's on GitHub. +
+ + From c2cf8def9bc2082fcf7cdc2b5c73fce3b460a40b Mon Sep 17 00:00:00 2001 From: plehegar Date: Tue, 19 Sep 2023 13:00:30 -0400 Subject: [PATCH 2/2] Added a link to the joint deliverables from our index page --- index.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/index.html b/index.html index 67326b0aa..4535f71ff 100644 --- a/index.html +++ b/index.html @@ -214,8 +214,9 @@

Specification Development

  • Advancement on the Recommendation Track: