Can you tell me about what kinds of responsibilities/privileges you would like to see from a “collaborator” position? One reason why we haven’t gotten around to giving the commit bit to most people is that, right now, it’s a relatively small step from what contributors can already do: the core CLI team itself puts all our changes through the PR process, and beyond that, the big thing I can think of is that we’re the ones with the actual final commit bit and ability to publish new npm CLI versions.
We’re pretty open to talking more about what a more involved collaborator looks like on the CLI. The last time I talked with @iarna about it, we were waiting for the migration to npm.community to be done, so we could start leaning on the trust level and badge system of this space to help find higher-privilege collaborators. This space also gives us way more leeway in granting piecemeal privileges to various people, instead of giving full write access to, say, someone who’s only around for triage, or only around for support. I think we can definitely have some more tiers/categories of collaborator for sure.
To this day, I think it continues to be important that the core (full-time, salaried) maintainers of the CLI have a certain amount of standing when it comes to decision-making and product stuff. We’re an open source project, though, and I think it’s high time we integrate our development process with the community a bit more, even though we’ve had over 600 collaborators send us patches, some with a certain amount of regularity. One thing that has stopped me -personally- is that I’m uncomfortable dumping a timesink of responsibility on someone who is not being paid for the labor they do for us. That’s more of an ethical thing on my end, so I might lobby for “full collaborator” status to only be grantable to folks who are being paid for their time either by npm, Inc itself, or by a third party who’s offered reserved time for this work. It’s a lot. Please don’t do it for free.
Finally, I think we should talk about a system of grandparenting in collaborators who have already been participating regularly in the npm community and the CLI’s development, like @KenanY, @legodude17, and you, @watilde. I think it’s high time we recognize your contributions a bit more than we already have.
So, what do you think? What are you looking for? What do you think would work best for the community and the project?