Skip to content
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.

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

Expand CODEOWNERS to each learn section owner/advocate #7292

Open
3 tasks
bmuenzenmeyer opened this issue Nov 29, 2024 · 4 comments
Open
3 tasks

Expand CODEOWNERS to each learn section owner/advocate #7292

bmuenzenmeyer opened this issue Nov 29, 2024 · 4 comments
Labels
learn Issues/pr concerning the learn section

Comments

@bmuenzenmeyer
Copy link
Collaborator

bmuenzenmeyer commented Nov 29, 2024

Broken out of #7197
Might be related to #7198

CODEOWNERS improvements associated to teams related to the APIs highlighted in the learn content

for each identified api module / team:

  • add a team, or expand access to write access if missing (CODEOWNERS must have write access)
  • add the team and content paths to CODEOWNERS
@bmuenzenmeyer
Copy link
Collaborator Author

@AugustinMauroy identified these already

test-runner should be under the test-runner team
typescript should be under typescript team

@bmuenzenmeyer bmuenzenmeyer added the learn Issues/pr concerning the learn section label Nov 29, 2024
@AugustinMauroy
Copy link
Member

Note that we can only take action on this when we have clearly defined the learning path/graph and each subsection is associated with one or two teams max.

@AugustinMauroy
Copy link
Member

I've added it to the agenda to get their opinion on the matter.

@marco-ippolito
Copy link
Member

No problem with adding @nodejs/typescript as codeowner of the typescript related content for review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
learn Issues/pr concerning the learn section
Projects
None yet
Development

No branches or pull requests

3 participants