Skip to content

Proposal: Working Group Annual Report #383

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Proposal: Working Group Annual Report #383

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/01-membership.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -299,6 +299,14 @@ Changing the eligibility framework can be made through a PR to the [documentatio

The eligibility start date for the project is the date at which the project met the Eligibility criteria above (eg. after open sourcing). This is the earliest date that future Protocol Guild members can use to count contributions towards the project.

#### Annual Working Group Updates

In order to ensure working group information does not go stale, each working group must post an annual report in the "#annual-reports" Discord channel during Q3 membership updates. This timing allows teams to discuss any issues as part of Devcon/Devconnect.

This report should be brief (1-2 paragraphs, <10 minutes to write, ~1 minute to read). Updates should explain what the project did in the past year, what it intends to do in the next year, and why the project remains eligible. This report must also include links to outputs such as GitHub repos or relevant published works. Teams with external governance (Linux Foundation, Apache Software Foundation, etc.) may reference existing organizational documentation instead of writing new summaries if those reports include the needed context.

Failure to submit an annual update is sufficient cause to remove a working group from Protocol Guild eligibility. This requirement begins Q3 2025.

### Adding and removing members

An existing member should make a PR at [this repo](https://github.com/protocolguild/documentation) which proposes an addition to the member list above, along with the accompanying info:
Expand Down