From 98e3f25cbe48df5b88c1d77b857736d5f8e18c0a Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Fri, 16 Feb 2024 15:42:31 +0100 Subject: [PATCH 1/4] Add guidelines for proposing, reviewing, publishing meeting agenda and minutes --- CONTRIBUTING.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 790da87..2c88712 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -398,6 +398,24 @@ describes how to participate and record meetings. There is a template](https://github.com/w3c-cg/solid/blob/main/meetings/template.md) that can be used by scribes to transcribe the meeting. +The general steps to propose, review, and publish meeting agenda and minutes +as follows: + +1. Create a PR containing the agenda for the upcoming meeting with: + * Title: "Add `YYYY-MM-DD` agenda and minutes" + * Description: "Request to merge in 24 hours following meeting." + * Assignees: to yourself (or others) + * Labels: "category: meeting" +2. Copy the agenda to a collaborative editor which, would be used + during the meeting. +3. Share the URLs to both the agenda PR and live editor across various + communication channels such as chats and mailing lists. Include these + URLs in the description of the calendar event for the meeting. +4. Following the meeting, update the PR with the minutes collected from the + live editor. +5. Merge the PR once substantial feedback has been reviewed and integrated for + publication. + ## Communication From e9d6af29177346ef7abdcc5fdf0a52f04495cfc5 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Fri, 16 Feb 2024 15:50:31 +0100 Subject: [PATCH 2/4] Mention co-authored-by and squash merge --- CONTRIBUTING.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2c88712..5e96516 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -412,9 +412,10 @@ as follows: communication channels such as chats and mailing lists. Include these URLs in the description of the calendar event for the meeting. 4. Following the meeting, update the PR with the minutes collected from the - live editor. -5. Merge the PR once substantial feedback has been reviewed and integrated for - publication. + live editor, acknowledging scribes by adding them as `Co-authored-by: NAME + `. +5. Squash merge the PR once substantial feedback has been reviewed and + integrated for publication. ## Communication From eca9b68d60d9873cd711bad90ee2e812cd7bbc84 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Fri, 16 Feb 2024 16:09:35 +0100 Subject: [PATCH 3/4] Minor --- CONTRIBUTING.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5e96516..1be942a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -406,11 +406,11 @@ as follows: * Description: "Request to merge in 24 hours following meeting." * Assignees: to yourself (or others) * Labels: "category: meeting" -2. Copy the agenda to a collaborative editor which, would be used - during the meeting. +2. Copy the agenda to a collaborative editor, which would be used during the + meeting. 3. Share the URLs to both the agenda PR and live editor across various - communication channels such as chats and mailing lists. Include these - URLs in the description of the calendar event for the meeting. + communication channels such as chats and mailing lists. Include these URLs + in the description of the calendar event for the meeting. 4. Following the meeting, update the PR with the minutes collected from the live editor, acknowledging scribes by adding them as `Co-authored-by: NAME `. From 3c524dd84ababf12c57051fef358620918d00607 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Fri, 1 Mar 2024 10:57:58 +0100 Subject: [PATCH 4/4] Add expected PR review period for meeting minutes --- CONTRIBUTING.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1be942a..c11f035 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -377,6 +377,12 @@ Unless there is a prior CG decision otherwise, changes to TRs use the W3C Proces |[New features](https://www.w3.org/Consortium/Process/#class-4)|MUST PR.|Within 10 days or 2 meetings.| |[Changes to the contents of a registry table](https://www.w3.org/Consortium/Process/#class-5)|Editors or chairs MUST PR.|Within 10 days or 2 meetings.| +For PRs involving other types of changes: + +|Document Type|Requirements|Time| +|-|-|-| +|Meeting Minutes|MUST PR.|After 1 day; within 2 days.| + ## Vocabulary Management @@ -403,7 +409,6 @@ as follows: 1. Create a PR containing the agenda for the upcoming meeting with: * Title: "Add `YYYY-MM-DD` agenda and minutes" - * Description: "Request to merge in 24 hours following meeting." * Assignees: to yourself (or others) * Labels: "category: meeting" 2. Copy the agenda to a collaborative editor, which would be used during the