diff --git a/2024/ig-exploration.html b/2024/ig-exploration.html index 99761188..3d97bcbb 100644 --- a/2024/ig-exploration.html +++ b/2024/ig-exploration.html @@ -75,13 +75,13 @@
The mission of the Exploration Interest Group +
The mission of the Exploration Interest Group is to provide W3C Members with a forum to explore and discuss emerging web-related technology trends and consider how the community could collaborate to shape those trends for the benefit of web users.
@@ -98,7 +98,7 @@Updated document status is available on the group publication status page. [or link to a page this group prefers to use]
+Updated document status is available on the group publication status page.
- This Group is expected to coordinate with any relevant group... +
+ This Group is expected to coordinate with any relevant group.
- -Note: Do not list horizontal groups here, only specific WGs relevant to your work.
-Note: Do not bury normative text inside the liaison section. - Instead, put it in the scope section.
-- Technical discussions for this Interest Group are conducted in public: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests. (Does the IG plan to write EDs and WDs?) + Discussions for this Interest Group are conducted in public: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. The meetings themselves are not open to public participation, however.
@@ -285,8 +266,7 @@
- This group primarily conducts its technical work pick one, or both, as appropriate: on the public mailing list public-[email-list]@w3.org (archive) - or on GitHub issues. + This group primarily conducts its work on GitHub issues. The public is invited to review, discuss and contribute to this work.
@@ -308,7 +288,7 @@
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. - A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from [pick a duration within:] one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue. + A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period of one week, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Interest Group.
@@ -332,7 +312,7 @@