-
Notifications
You must be signed in to change notification settings - Fork 92
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: add docs on how to run community meetings (#711)
- Loading branch information
1 parent
f60574c
commit 78a3558
Showing
1 changed file
with
58 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,58 @@ | ||
# Community meetings | ||
|
||
Component Detection community meetings happen every four weeks on Wednesdays at 9:00 AM Pacific Time. The meeting is open to everyone and is a great way to get involved with the project. We have [an overarching issue][1] listing the upcoming meeting, as well as all previous meetings. | ||
|
||
## Running the meeting | ||
|
||
Our community meetings are run by members of our team. Here's a checklist of things to do before, during and after the meeting. | ||
|
||
### Before the meeting | ||
|
||
1. Open the discussion for the meeting (You should be able to find it in the [overarching issue][1]) | ||
1. Open the issues and pull requests search since the last meeting (It should be linked in the discussion) | ||
|
||
### During the meeting | ||
|
||
1. Record the meeting | ||
1. Discuss the issues and pull requests that have been opened since the last meeting | ||
- Highlight any issues or pull requests that need attention | ||
1. Discuss any other topics that have been added to the agenda | ||
|
||
### After the meeting | ||
|
||
1. Update: | ||
- The agenda with any notes from the meeting | ||
- The attendees list | ||
- Upload the recording | ||
1. Create a new discussion for the next meeting. Use the following template, and update the dates for: "Find in your timezone", "Issues opened since last meeting" and "PRs opened since last meeting" | ||
|
||
```markdown | ||
<!-- Check out https://github.com/microsoft/component-detection/blob/main/docs/community-meetings --> | ||
📆 Wednesday dd mm yyyy | ||
🕙 10AM Pacific Time ([Find in your timezone][timezone]) | ||
☎️ [Teams meeting][teams] | ||
|
||
## Agenda | ||
|
||
Comment agenda items below | ||
|
||
- [Issues opened since last meeting][issues] | ||
- [PRs opened since last meeting][prs] | ||
|
||
## Attendees | ||
|
||
* | ||
|
||
## Recording | ||
|
||
[timezone]: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230712T17 | ||
[teams]: https://teams.microsoft.com/l/meetup-join/19%3ameeting_YmVmMjcxMmEtMmYwYi00MGNiLTg4MDgtODNiMDY5ZjNkYjY3%40thread.v2/0?context=%7b%22Tid%22%3a%2272f988bf-86f1-41af-91ab-2d7cd011db47%22%2c%22Oid%22%3a%22bb41e436-5c77-44e2-b783-1ad2b9f7aa7f%22%7d | ||
[issues]:https://github.com/microsoft/component-detection/issues?q=is%3Aissue+created%3A%3E2023-07-12 | ||
[prs]:https://github.com/microsoft/component-detection/pulls?q=is%3Apr+created%3A%3E2023-07-12 | ||
``` | ||
|
||
1. Update the [overarching issue][1] with a link to the new discussion, and move the old discussion to the "Past meetings" section. | ||
1. Update [the pinned discussions][2]. There should be one pinned discussion for the next meeting, and one for the latest past meeting. | ||
|
||
[1]: https://github.com/microsoft/component-detection/issues/47 | ||
[2]: https://github.com/microsoft/component-detection/discussions |