feat: ✨ add section about GitHub teams and how we use them#372
Open
lwjohnst86 wants to merge 1 commit into
Open
feat: ✨ add section about GitHub teams and how we use them#372lwjohnst86 wants to merge 1 commit into
lwjohnst86 wants to merge 1 commit into
Conversation
Member
Author
|
@joelostblom @signekb @martonvago @K-Beicher @DanMazJen I haven't connected the GitHub team to this repo yet (going to update it soon), could you all review this? |
signekb
requested changes
Jun 15, 2026
signekb
left a comment
signekb
left a comment
Member
There was a problem hiding this comment.
Nice update. A couple of minor, minor suggestions:
| - "tools" for software packages or other code-based resources. | ||
| - "docs" for documentation-only websites. | ||
| - "templates" for templates for different types of repositories (e.g. Python | ||
| package). |
Member
There was a problem hiding this comment.
Suggested change
| package). | |
| packages). |
|
|
||
| - People are only added to a team when there is work to be done on a repository | ||
| in that team for a given iteration. This limits the number of notifications | ||
| that everyone in Seedcase will get, so that only those relevant people are |
Member
There was a problem hiding this comment.
Suggested change
| that everyone in Seedcase will get, so that only those relevant people are | |
| that everyone in Seedcase gets, so that only those relevant people are |
Comment on lines
+83
to
+84
| - The admin team/organization owners are responsible for adding or removing | ||
| people from teams as needed, based on an iteration's aims. |
Member
There was a problem hiding this comment.
Does that mean I'm responsible for this too?
| - The admin team/organization owners are responsible for adding or removing | ||
| people from teams as needed, based on an iteration's aims. | ||
|
|
||
| - A member is on a team if they are assigned work on the repository. |
Member
There was a problem hiding this comment.
Suggested change
| - A member is on a team if they are assigned work on the repository. | |
| - A member is on a team if they are assigned work on the repository for the current iteration. |
Maybe?
| - Each higher-level grouping of teams ("product" or "platform") has their own | ||
| project board. Multiple teams can work on the same project board, as long as | ||
| the work is under the same grouping (e.g. "platform-tools" and "platform-docs" | ||
| can share a project board). |
Member
There was a problem hiding this comment.
Suggested change
| can share a project board). | |
| are both on the platform project board). |
Maybe?
github-project-automation
Bot
moved this from In Review
to In Progress
in Product development
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Explain how the new GitHub teams are used and what they are for.
Closes #369
Needs a thorough review.
Checklist
just run-all