Skip to content

Conversation

@bjohansebas
Copy link
Member

@bjohansebas bjohansebas commented Dec 15, 2025

As mentioned here #641 (comment), the idea of captains is adapted so that it is not necessary to be a member of this team to maintain a package that is under pkgjs

cc: @nodejs/package-maintenance

@bjohansebas bjohansebas changed the title docs: update governance structure to include captains and committers model docs: update governance structure to include captains model Dec 15, 2025
Copy link
Member Author

@bjohansebas bjohansebas Dec 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’m not sure if anyone else wants to be a captain or if we’re missing someone here, please add it as a suggestion or let me know.

- [pkgjs/detect-node-support](https://github.com/pkgjs/detect-node-support):
- [pkgjs/membership-updater](https://github.com/pkgjs/membership-updater):
- [pkgjs/dependents](https://github.com/pkgjs/dependents):
- [pkgjs/meet](https://github.com/pkgjs/meet): @bjohnansebas @ctcpip @wesleytodd
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc: @ctcpip

captains.md Outdated
@@ -0,0 +1,19 @@
# Captains (pkgjs repositories)

- [pkgjs/create-package-json](https://github.com/pkgjs/create-package-json):
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does anyone want to continue maintaining this package, given that you’re on the create-collaborations team?

cc: @ruyadorno @darcyclarke @thescientist13 @wesleytodd @rodion-arr @rxmarbles @zackschuster @jonchurch @Ethan-Arrowood

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [pkgjs/create-package-json](https://github.com/pkgjs/create-package-json):
- [pkgjs/create-package-json](https://github.com/pkgjs/create-package-json): @wesleytodd

I am doing so. Just pushed some PRs yesterday (added y'all as reviewers if you have time).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will review the PRs, but yes @bjohansebas keep me in there please and thank you 😄

captains.md Outdated
- [pkgjs/create-package-json](https://github.com/pkgjs/create-package-json):
- [pkgjs/statusboard](https://github.com/pkgjs/statusboard): @bjohansebas
- [pkgjs/gh-pages](https://github.com/pkgjs/gh-pages):
- [pkgjs/support](https://github.com/pkgjs/support):
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does anyone want to continue maintaining this package, given that you’re on the support-collaborations team?
cc: @ljharb @wesleytodd @rodion-arr @mhdawson @Eomm

Copy link
Member

@ljharb ljharb Dec 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please keep me on the list, but I think this package should be deprecated soon in favor of the new CLE standard. (and i'm happy to do that work when it's time)

captains.md Outdated
- [pkgjs/gh-pages](https://github.com/pkgjs/gh-pages):
- [pkgjs/support](https://github.com/pkgjs/support):
- [pkgjs/triagebot](https://github.com/pkgjs/triagebot):
- [pkgjs/create-pkg](https://github.com/pkgjs/create-pkg):
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does anyone want to continue maintaining this package, given that you’re on the create-collaborations team?

cc: @ruyadorno @darcyclarke @thescientist13 @wesleytodd @rodion-arr @rxmarbles @zackschuster @jonchurch @Ethan-Arrowood

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [pkgjs/create-pkg](https://github.com/pkgjs/create-pkg):
- [pkgjs/create-pkg](https://github.com/pkgjs/create-pkg): @wesleytodd

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto here

captains.md Outdated
- [pkgjs/support](https://github.com/pkgjs/support):
- [pkgjs/triagebot](https://github.com/pkgjs/triagebot):
- [pkgjs/create-pkg](https://github.com/pkgjs/create-pkg):
- [pkgjs/nv](https://github.com/pkgjs/nv): @wesleytodd
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does anyone want to continue maintaining this package, given that you’re on the nv-collaborations team?

cc: @wesleytodd @rxmarbles @dominykas

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd be happy to be added as well

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah toss me in that

captains.md Outdated
- [pkgjs/dependents](https://github.com/pkgjs/dependents):
- [pkgjs/meet](https://github.com/pkgjs/meet): @bjohnansebas @ctcpip @wesleytodd
- [pkgjs/wiby](https://github.com/pkgjs/wiby): @bjohansebas
- [pkgjs/parseargs](https://github.com/pkgjs/parseargs):
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [pkgjs/parseargs](https://github.com/pkgjs/parseargs):
- [pkgjs/parseargs](https://github.com/pkgjs/parseargs): @bjohansebas

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does anyone else want to take responsibility for this package?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to be added, yes :-)

Copy link
Member

@wesleytodd wesleytodd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! My only concern is that we don't outline giving captains "admin" on the repo, this was a problem in our original Express version as well. Should we consider giving them admin for this?

Not blocking, but would be nice to decide before we land this so we don't need to revisit it.

captains.md Outdated
@@ -0,0 +1,19 @@
# Captains (pkgjs repositories)

- [pkgjs/create-package-json](https://github.com/pkgjs/create-package-json):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [pkgjs/create-package-json](https://github.com/pkgjs/create-package-json):
- [pkgjs/create-package-json](https://github.com/pkgjs/create-package-json): @wesleytodd

I am doing so. Just pushed some PRs yesterday (added y'all as reviewers if you have time).

captains.md Outdated
- [pkgjs/gh-pages](https://github.com/pkgjs/gh-pages):
- [pkgjs/support](https://github.com/pkgjs/support):
- [pkgjs/triagebot](https://github.com/pkgjs/triagebot):
- [pkgjs/create-pkg](https://github.com/pkgjs/create-pkg):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [pkgjs/create-pkg](https://github.com/pkgjs/create-pkg):
- [pkgjs/create-pkg](https://github.com/pkgjs/create-pkg): @wesleytodd

- [pkgjs/create-pkg](https://github.com/pkgjs/create-pkg):
- [pkgjs/nv](https://github.com/pkgjs/nv): @ljharb @wesleytodd
- [pkgjs/detect-node-support](https://github.com/pkgjs/detect-node-support):
- [pkgjs/membership-updater](https://github.com/pkgjs/membership-updater):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This project was barely an idea, so is one we for sure should either archive or re-home until someone has a reason to work on it.

@bjohansebas
Copy link
Member Author

Looks good! My only concern is that we don't outline giving captains "admin" on the repo, this was a problem in our original Express version as well. Should we consider giving them admin for this?

Yes, we should give admin access to the captains, so they have full freedom to properly manage the package they maintain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants