From 23dc7bfc09d13a003dc447b80d843bdba019065c Mon Sep 17 00:00:00 2001 From: sideshowbarker Date: Mon, 19 Aug 2024 13:45:48 -0700 Subject: [PATCH] Clarify that RF commitments are from WG participants --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a0cf4e3..516d3c6 100644 --- a/README.md +++ b/README.md @@ -95,7 +95,7 @@ You can secure [Royalty-Free Licensing Commitments](#rf-licensing-commitments) f 3. Continue to [autopublish](#autopublishing) updated [Working Drafts](#what-are-working-drafts) into [the `w3.org/TR` spec-publication space](#tr-space) and to communicate closely with implementors and others to get the details right. 4. When your group believes a spec is ready to be fully implemented — and ready to be thoroughly tested (by having a [suite of tests](https://github.com/web-platform-tests/wpt/) to test against) — then, follow the process to get the Working Draft warning label dropped from a spec, and to get the [CR](#candidate-recommendation) label added, and publish the first [Snapshot](#what-are-snapshots) for it. - 60 days after you publish that first [Snapshot](#what-are-snapshots), you’ll have [secured Royalty-Free Licensing Commitments](#how-can-i-get-royalty-free-licensing-commitments) for *all* [normative](#normative-requirements) features defined in that [Snapshot](#what-are-snapshots). + 60 days after you publish that first [Snapshot](#what-are-snapshots), you’ll have [secured Royalty-Free Licensing Commitments](#how-can-i-get-royalty-free-licensing-commitments) from all participants in your Working Group for *all* [normative](#normative-requirements) features defined in that [Snapshot](#what-are-snapshots). For information on getting commitments for a Community Group Report, see the [CG Patent Policy](#cg-patent-policy) section.