Proposal: Add New Staff Roles to Membership Charter

[chandeleer1698]

Discussed here: https://discord.com/channels/1072614816579063828/1072617059265032342/1465976562506661994
Split off from my previous governance proposal #2029 hopefully this one will be easier to pass.

Purpose

I would like to update the Membership page to include the new roles in Universal Blue that have naturally taken shape. I believe Universal Blue has grown bigger than just a github repo and the site should reflect that. Non maintainers deserve to be properly recognized as apart of the team. Individuals in the org are allowed to wear multiple hats. But being approved for one role won't automatically approve you for another.

Proposal

1. Rename current "Member" role to Maintainer.

This better reflects the terminology and phrasing currently used in community spaces for better consistency. The current term member also implies only maintainers are "real" parts of the Org.

2. Rename current "Approver" role to Administrator

Clearer name for the project heads and leadership.

3. Add Community Manager role

Community Managers are the head moderators and social media managers for their respective project's community spaces. They are entrusted with upholding and enforcing the Code of Conduct and cultivating an engaging and positive environment for the community to flourish.

Defined by: Granted access to all Social Media accounts for their associated project, and Super Moderator/Administrator Privileges in community spaces where applicable (Reddit/Discord)

• Enabled two-factor authentication on all accounts used in the project. (GitHub, Discord, Reddit etc.)
• Is a continuously active member in the community and contributes to community discussions
• Have fully read the Code of Conduct
• Approved by the majority of Administrators from their respective projects

Responsibilities and privileges

• Active in the process of appointment and removal of community moderators
• Maintains an active and engaging presence for the project on official social media accounts
• Responsive to community feedback and reports
• Cross posts any and all public statements, blog posts, and announcements from the org
• Personally reviews any and all ban appeals from community spaces
• The first immediate PR contact for their project
• Included in votes that pertains to community space governance, and Code of Conduct enforcement
• Included in all Org meetings as a representative for the greater community and its interests

4. Add Designer role

Designers are the continuously active contributors that provide ongoing graphical services for the org. They are the creative back bone for the org and are the primary creators of artwork, logos, wallpapers, marketing, and branding for the org.

Defined by: Entrusted with the creation of visual media for the org. They can be commissioned and financially compensated by the org for their services.

• Maintains a continuous relationship with the org to fulfill the marketing and branding needs of the project
• Respects the guidelines and restrictions set and defined by Administrators
• Maintains a positive reputation and active presence in the community
• Approved by the majority of Administrators from their respective projects

Responsibilities and privileges

• Maintains an active status in contributing visual media across the org
• Entrusted with the creation of mascots, wallpapers, logos, conference slides, marketing material, stickers, merchandise, etc.
• Granted involvement, creative control, and oversight over the creation of tie in material such as books, web comics, games, conference toys, coloring books, videos, animations, and merch designs
• Included in votes that pertain to tie in material, merchandise, and visual media
• Included in Org meetings that pertain to tie in material, merchandise, and visual media

5. Add Community Moderator role

Community Moderators are the ground enforcers keeping our community spaces safe and compliant with the Code of Conduct. They keep the peace and ensure the org is a welcoming place for everyone regardless of Race, Religion, Gender, or Nationality.

Defined by: Granted moderator power in the community spaces for their respective project.

• Enabled two-factor authentication on all accounts used in the project. (GitHub, Discord, Reddit etc.)
• Is a continuously active member in the community and contributes to community discussions
• Have fully read the Code of Conduct
• Has been an active member of the community for at least 3 months
• Approved by all Community Managers from their respective project

Responsibilities and privileges

• Maintains a positive reputation and active presence in the community spaces for their associated project.
• Entrusted in the enforcement of the Code of Conduct and upholding all platform rules and terms of service in their community space.
• Responds to user reports and staff pings in a timely manner
• Granted full discretion on determining the level of punishment they deem necessary for Code of Conduct violations.
• Answers community questions to the best of their ability
• Helps out new users in their respective community spaces

[KyleGospo]

Points 1 and 2 I am -1 on, but points 3 and 4 I think we can do without even adjusting the org structure or charter. Would the team be in favor of expanding the website to list these non-github contributors (and dynamically pull other contributors from GitHub like bazzite.gg does) based on this request?

I can do this work.

For point 5 It might make sense to outline the responsibilities of that role since they'd be outside of GitHub entirely.

[chandeleer1698]

Points 1 and 2 I am -1 on, but 3, 4, and 5 I think we can do without even adjusting the org structure or charter. Would the team be in favor of expanding the website to list these non-github contributors (and dynamically pull other contributors from GitHub like bazzite.gg does) based on this request?

I can do this work.

If you do that, you should consider copying a similar template to what Aurora and Bluefin are doing for their contributor sections

https://getaurora.dev/en/contributors

[inffy]

Don't think we need 1 and 2. Even 3 is propably something that Bazzite/aurora/bluefin can decide to do if they want to. So -1 for those.

The others are fine so +1 for those

[chandeleer1698]

For point 5 It might make sense to outline the responsibilities of that role since they'd be outside of GitHub entirely.

so do you mean what i currently have listed in the "responsibilities and privileges section" for Community Moderator isnt defined enough?

because I laid out one for every role in the proposal

[chandeleer1698]

Don't think we need 1 and 2. Even 3 is propably something that Bazzite/aurora/bluefin can decide to do if they want to. So -1 for those.

The others are fine so +1 for those

My biggest point for 3 and 5 is that

is so that essentially maintainers arent automatically always moderators in community spaces. which is why I put the caveat in the purpose section. Not everyone who is fit to be a maintainer is a good fit to be moderating and vice versa. And they are both roles that already defacto exist. So I feel like they should be recognized by the org in general.

[ZachrielForever]

Points 1 and 2 I am -1 on, but points 3 and 4 I think we can do without even adjusting the org structure or charter. Would the team be in favor of expanding the website to list these non-github contributors (and dynamically pull other contributors from GitHub like bazzite.gg does) based on this request?

I can do this work.

For point 5 It might make sense to outline the responsibilities of that role since they'd be outside of GitHub entirely.

I think it would be a somewhat decent idea to have the Moderator and Social Media roles be more identified on the website. It at least gives potential users a 'at a glance' view that theres more than just github contributers that are helping, or trying to help, this project grow.

[KyleGospo]

Points 1 and 2 I am -1 on, but points 3 and 4 I think we can do without even adjusting the org structure or charter. Would the team be in favor of expanding the website to list these non-github contributors (and dynamically pull other contributors from GitHub like bazzite.gg does) based on this request?

I can do this work.

For point 5 It might make sense to outline the responsibilities of that role since they'd be outside of GitHub entirely.

I think it would be a somewhat decent idea to have the Moderator and Social Media roles be more identified on the website. It at least gives potential users a 'at a glance' view that theres more than just github contributers that are helping, or trying to help, this project grow.

I agree, though them being on the website isn't inherently useful outside of giving credit. Discourse already has a mod list and Discord has groups, we could discuss how to better inform people of who's in those positions or treat them as "contributors" thanks to their time contribution rather than code.

Who's moderating a space can also change on a per project basis since we moved to separate communities for users and a shared Universal Blue one.

[chandeleer1698]

I agree, though them being on the website isn't inherently useful outside of giving credit. Discourse already has a mod list and Discord has groups, we could discuss how to better inform people of who's in those positions or treat them as "contributors" thanks to their time contribution rather than code.

Who's moderating a space can also change on a per project basis since we moved to separate communities for users and a shared Universal Blue one.

well on the ublue website maybe it can only list people who are moderator for just the Universal Blue server specifically

[KyleGospo]

I agree, though them being on the website isn't inherently useful outside of giving credit. Discourse already has a mod list and Discord has groups, we could discuss how to better inform people of who's in those positions or treat them as "contributors" thanks to their time contribution rather than code.

Who's moderating a space can also change on a per project basis since we moved to separate communities for users and a shared Universal Blue one.

well on the ublue website maybe it can only list people who are moderator for just the Universal Blue server specifically

Yeah that's what I was getting at, I'm plus one for that. I see no reason we can't do that.

My point also is that doesn't need a change to the org or anything, it's no different than any other PR. If nobody is opposed I can just start working on this.

[chandeleer1698]

well on the ublue website maybe it can only list people who are moderator for just the Universal Blue server specifically

Yeah that's what I was getting at, I'm plus one for that. I see no reason we can't do that.

My point also is that doesn't need a change to the org or anything, it's no different than any other PR. If nobody is opposed I can just start working on this.

sounds like a fair compromise to me. and then this proposal can just be turned into a vote on whether these new roles should actually be added to the charter or not