Open TheGlitch76 opened 1 year ago
We usually wouldn't put an FCP on small changes like this, but since I know that some poeple are still looking for better wording, I'll give them one FCP period to bring them up before we merge this.
What's the conclusion here?
As long as the conflict remains and no further discussion happens, we won't have a definitive conclusion
Alright, I think the simplest way to about this is to leave three additional days for other ideas to come in, and vote on the different solutions. This will force this fairly minor problem to get resolved, and make this compliant with the rest of the RFCs.
I want to clarify the reasoning behind this PR and my personal opinion on it.
This PR was made because Community Managers would not implement the RFC as written in our Toolchain Discord and name the team role "Team: QSL Triage" because it the naming is similar to the entirely different "Triage: Mappings" role, whose members are not full Quilt Developers. The understanding was that we'd continue to call the team "Team: QSL" and hash out the exact name details in a PR.
I also want to note that, following the established process to change QSL policies, this PR should be approved by all QSL Core Team members before merge.
I won't be engaging with this PR further for personal reasons, except to update it as directed by the QSL Core team.
We've had a discussion on Discord about this RFC and reached the conclusion that QSL doesn't fit the organisation structure. I'll let someone from the team outline the changes required, do we want to work on them in this PR?
Community managers feel it 's inappropriate to use "triage" to define a full Quilt Developer team.