Final Comment: Formal subteams #18
Conversation
|
@philpax maybe @karashiiro's callout on issue house keeping commenting could be added as a sub-team task. #21 |
Mmm, maybe under documentation or community? |
|
I've addressed the initial round of feedback. We still have a few open concerns:
|
|
Was writing up my reply to #22, and it occurred to me that we could potentially benefit from a reverse engineering subteam if our reversers are interested. This would allow developers to know who to ask to find something / for help reversing, and if a variant of #22 is actioned, a dedicated team can be responsible for helping integrate people's reversed findings into ClientStructs etc. |
|
sorry to get on your goat @goaaats but your eyes would be appreciated on this soon |
I imagine having package mantainers in the Linux/Unix team would be a good choice - at the moment that's me, ashkitten, Caliel666, Centzilius. Marzent is from XoM and helps with wine. Dormanil is an user and helps out with xlcore stuff. |
text/0000-formal-subteams.md
Outdated
|
|
||
| [reference-level-explanation]: #reference-level-explanation | ||
|
|
||
| The initial members of each subteam will be as follows: |
There was a problem hiding this comment.
I think we should make sure that the people listed here want to actually be listed and are in the right category, either way - if you want, I can do that.
There was a problem hiding this comment.
I'd appreciate that if you could! If you're okay with the members as listed, reach out to them, confirm they're okay, and we can lock them in 🙏
There was a problem hiding this comment.
Although having been involved with all the *nix stuff, I also quite like working on the launcher side of things if people are still wanted there.
|
We've just identified a need for a "support" subteam that manages support channels/tools, is there a space for this? With Franz + Nite + me for now, I guess. Maybe this can be combined with community? |
|
I'm going to institute an informal final comment period. If there's no major objections, I'll merge this in a week's time (the 29th) and we can action it by creating the relevant GitHub teams/Discord roles, setting up permissions, and unblocking the other PRs. |
I'd honestly like to move to support and out of moderation if that's not a big deal. I don't mind helping peeps or slowmoding general chat but I just don't have the best judgement calls for dev relations and how to moderate them in that regard. |
happy to update this in the DIP if goat approves your Goatcorp Employee Transfer REQuesT. |
This comment was marked as resolved.
This comment was marked as resolved.
text/0000-formal-subteams.md
Outdated
|
|
||
| [future-possibilities]: #future-possibilities | ||
|
|
||
| We could potentially develop policies around how to join a subteam, so that people interested in participating know how to start. |
There was a problem hiding this comment.
I have a prototype discord bot in a private repo that does have an online form that can be filled out as an application that then creates a thread in a discord channel and can ping relevant members to discuss said application/applicant. Not sure if you all would find that useful or if it's too much.
|
Congratulations on the first DIP, everyone! goat's not feeling well today so we won't action it immediately, but we'll get the ball rolling soon 🎉 |
Very rough proposal. Need to better select people for each subteam, and answer the unresolved questions.