-
Notifications
You must be signed in to change notification settings - Fork 47
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
W3C Solid Community Group Meeting Guidelines
- Loading branch information
Showing
1 changed file
with
57 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
# W3C Solid Community Group Meeting Guidelines | ||
|
||
To reach consensus where no consensus has been reached before. | ||
|
||
It is recommended that meetings adopt the guidelines in this document as well as the [W3C Process](https://www.w3.org/Consortium/Process/) where applicable. | ||
|
||
The [Solid Code of Conduct](https://github.com/solid/process/blob/main/code-of-conduct.md) and [Positive Work Environment at W3C: Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/) must be followed by all meeting participants. | ||
|
||
## Meeting Recordings and Transcripts | ||
|
||
No audio or video recording, or automated transcripts without consent. Meetings are transcribed and made public. If consent is withheld by anyone, recording/retention must not occur. | ||
|
||
There is a [minutes template](https://github.com/solid/specification/blob/main/meetings/template.md) (Markdown) that can be used. | ||
|
||
## Roles in Meetings | ||
|
||
Below are some common roles and their descriptions as useful guidelines. It is not a complete or strict list of duties. | ||
|
||
### Participants | ||
|
||
* Includes everyone present in the meeting. | ||
* Participants may switch roles provided that it is clear to the other participants and there are no conflicts of interest. | ||
* Participants other than the moderator should add themselves to the queue to talk, remove themselves, or allow others to go ahead. | ||
* State name to scribe. Be concise. Stay within topic. | ||
* May correct or improve fields marked by scribes during meeting. | ||
* Makes recommendations to improve meeting minutes, e.g., PRs. | ||
* Can recommend meeting topics before or during the meeting. | ||
* Participants should first attempt to use chats and repositories to work out concerns about the minutes or group decisions before meetings. Specific responses, e.g., clarifications or objections to previous group decisions can be proposed as topics to the meeting agenda. | ||
* Only Solid Community Group members may vote or raise objections during the meeting. | ||
|
||
### Guests | ||
|
||
* Anyone can join a public meeting as a guest whether invited by someone or not. | ||
* Guests cannot vote or raise objections in discussions. | ||
|
||
### Moderator | ||
|
||
* Defines and announces meeting agenda prior to the meeting. | ||
* Runs the meeting agenda; announcements, topics. | ||
* Generally stays neutral in discussion but can participate in discussions if announces in advance their "hat" at that time. | ||
* Facilitate reaching consensus. | ||
* Asks participants to approve prior meeting minutes. If no objections, notes approval to scribe. | ||
* Ensures minutes are taken and posted in due time. | ||
|
||
### Scribes | ||
|
||
* Transcribes the meeting *as is*. | ||
* Stops transcribing on speaker's request. | ||
* Requests assistance to improve transcription, e.g., mark text that needs correction or improvement, ask speaker or moderator for clarification. | ||
* Publishes minutes "soon after" the meeting (unless an another arrangement is made - to ensure it is on the same day). | ||
* Announces (draft and published) minutes in chats and elsewhere. | ||
|
||
### Solid Community Group Chair | ||
|
||
* May adopt or request to take on a role before or during the meeting. | ||
* Provides guidance to processes, charters and the Solid ecosystem. | ||
* Follows up on Community Group related actions. |