[Meta] clarify policy around collaborator status for this repo

[aspiers]

Hi there,

I would like to know if there is a possibility to add other collaborators to this repo? Yes, to be perfectly honest I am asking primarily for myself, since I have contributed quite a lot to this repo (57 issues at the time of writing, of which I submitted 27 myself), but there's a limit to how much I can contribute without having collaborator access. For example, I can't:

• Add or amend labels on issues
• Close issues which are resolved, unless I submitted them myself

However the question is not just for me: I'm sure there are other contributors out there who would be able to help make this repo even better if they had collaborator privileges.

I see from #430 and #459 that there has been some kind of process for adding collaborators in the past, but it would be nice if the policy around this was clarified, even if the policy is "we won't ever add any new collaborators, sorry".

Thanks for any clarification you can offer here!

[cirosantilli]

@isaacs hasn't replied in a while to at mentions, and no one else can add new people.

The only solution is a side channel contact with him, try email or the contact form on his website or twitter.

For the record, I support adding @aspiers as a collaborator.

[aspiers]

Thanks a lot @cirosantilli. I'll see if I can reach @isaacs some other way.

[aspiers]

I just emailed @isaacs about this.

[aspiers]

@isaacs responded very quickly and has kindly made me and @TPS collaborators. Since this issue was mainly about the policy / process around changing collaborator status, I'll leave it open for now.

[TPS]

I did close #619, though - that's specifically re: myself. 😊

[TPS]

Also, is there anyplace there's a complete public list of collaborators, &/or a way to notify the whole group @isaacs/collaborators - style? I'd like to open perhaps some meta-issues to hammer things out between us (e.g., labeling or comment policy), or have users ping us.

[clarkbw]

Also, is there anyplace there's a complete public list of collaborators, &/or a way to notify the whole group @isaacs/collaborators - style?

No, that’s only visible in the settings and you need to be an admin for that tab. Also no way to notify this meta group, something that’s a good idea.

I’m a collaborator as well. I also work at GitHub. ✨

[aspiers]

Awesome to have you on board @clarkbw!

[TPS]

Welcome, @clarkbw!

@isaacs, other admins & all collaborators: Whaddy'all think of #792 & #1510, which are proposals for issue templates, containing policies, &c?

[TPS]

What happened to #459?

Also, should we do anything more w/ https://github.com/isaacs/github/community?

[TPS]

I'd also love a discussion/overhaul re: the 94 (!) labels in this repo: IMHO, too many are overly specific or vague, which makes it a bit of a 🎱 [Magic 8-Ball] kinda choice to properly categorize issues. I've done a little work w/ them, but some collaboration might be more effective.

[clarkbw]

Would be happy to audit the labels at some point. There are some names I’ve used like render which are internal to GitHub and need explanation to have meaning. I want the labels to be obvious and useful internally and externally.

[aspiers]

@TPS @clarkbw Brilliant idea to have a labels overhaul! However it's off-topic for this issue, so I submitted #1549. Let's track it there.

Regarding https://github.com/isaacs/github/community, again it's off-topic for this issue, but I suggest that we have one issue for each aspect which needs addressing. [EDIT]: here's a list - once a separate issue is filed for an item, let's tick the checkbox and link to it:

• implementing a code of conduct (filed as [Meta] add a code of conduct policy #1591)
• adding a license, or at least deciding if we need one (filed as [Meta] add a license #1592)
• creating an issue template ([meta] Set up issue templates #1550 and PR Create ISSUE_TEMPLATE.md #792)
• creating a PR template (filed as [Meta] create a pull request template #1593)
• policy around locking of conversations (filed as [Meta] create policy around locking of conversations #1594)

[TPS]

@aspiers How about adding to above list (& then deleting this entire comment):

• policy re: locking (especially, mega-) threads

[aspiers]

@TPS Good idea re locking! - I've added it to the list, and updated my comment above about how to use the list. I've also started filing more new issues. Would prefer not to delete your comment as it makes the history harder for others to follow.