Fedora Marketing Team Restructure

josephgayoso commented

2025-07-16 02:25:47 +00:00

(Migrated from gitlab.com)

Today we have the Marketing Team, a group of people who have social media access, and the Fedora Ready Team. The social media people are guided by the Marketing Team. The Fedora Ready Team is made up of the Marketing Team plus a few more members. Below is the latest policy on how the team is structured.

https://discussion.fedoraproject.org/t/managing-who-has-direct-access-to-our-social-media-accounts/45882/17

I would like to change it to the following.

In order to join the Marketing Team:

You must have been collaborating with the Marketing Team for at least a month.
After that, someone in the team can nominate you to join the team.
Your nomination will be put to vote to in the team. A simple majority of the Marketing Team must vote in favor.
If the vote passes, you’re in.
In order for a team member to be removed from the Marketing Team, a 2/3 vote must pass to remove the person in question.
The membership will reset each release cycle, meaning that you have to claim that you still want to be an active team member in order to continue. Otherwise your membership will be marked as inactive and you will need to be approved again.

In order to make decisions as a team:

A team member can make a ticket with their proposal. If someone wants to take an action, another team member can request that we vote on it before action is taken.
A simple majority passes the motion.
There is no quorum, but adequate time of 1 week with notice must be given.

To become a member of the social media access group:

The Marketing Team will nominate someone with their consent, and upon their approval with simple majority be given access to the social media account.
Below are guidelines that the team should consider, but are not beholden to:
- Contributor should have been involved in the Fedora Project for 9 months at least.
- Contributor should be a member of the Marketing Team for at least 3 months.
- There must be a need for someone to gain access to a social media account as judged by the Marketing Team.
In order to remove someone from the social media access group, a 2/3 vote must pass to remove the person in question.
Marketing Team members reserve the right to cut someone's access to an account in an emergency.

How to change the rules for the Marketing Team:

Team member suggests a change to the rules, policy, or structure.
Team votes on the change and passes with a majority vote.

The Fedora Ready Team is its own team that happens choose who can join as a member on its own, as needed. Not everyone needs to be in the team in order to collaborate on the initiative. This is just the team in charge of pushing the initiative forward.

At first this may not seem like a big change, but the new rules allow for the team to take action more quickly. We will know who is still in the team, not wait for responses from folks who may or may not be active at a given moment, and bias toward action unless we think a given situation demands putting something to vote. The social media access group will be managed by the Marketing Team and we can clean up who does or doesn't have access. The Fedora Ready Team will also be split off into its own team because we have different needs in that group than we do for the Marketing Team.

If we take these steps and use this opportunity to reset the team with just Justin and myself as members, we can rebuild and clear out old stuff that is not a priority for the group right now.

For now this is what I will run with until Justin comes back from his leave, especially because this isn't too different from the latest version of our defined structure. I'll leave this ticket open as a space for discussion.

Today we have the Marketing Team, a group of people who have social media access, and the Fedora Ready Team. The social media people are guided by the Marketing Team. The Fedora Ready Team is made up of the Marketing Team plus a few more members. Below is the latest policy on how the team is structured. https://discussion.fedoraproject.org/t/managing-who-has-direct-access-to-our-social-media-accounts/45882/17 I would like to change it to the following. In order to join the Marketing Team: 1. You must have been collaborating with the Marketing Team for at least a month. 2. After that, someone in the team can nominate you to join the team. Your nomination will be put to vote to in the team. A simple majority of the Marketing Team must vote in favor. 3. If the vote passes, you’re in. 4. In order for a team member to be removed from the Marketing Team, a 2/3 vote must pass to remove the person in question. 5. The membership will reset each release cycle, meaning that you have to claim that you still want to be an active team member in order to continue. Otherwise your membership will be marked as inactive and you will need to be approved again. In order to make decisions as a team: 1. A team member can make a ticket with their proposal. If someone wants to take an action, another team member can request that we vote on it before action is taken. 2. A simple majority passes the motion. 3. There is no quorum, but adequate time of 1 week with notice must be given. To become a member of the social media access group: 1. The Marketing Team will nominate someone with their consent, and upon their approval with simple majority be given access to the social media account. 2. Below are guidelines that the team should consider, but are not beholden to: * Contributor should have been involved in the Fedora Project for 9 months at least. * Contributor should be a member of the Marketing Team for at least 3 months. * There must be a need for someone to gain access to a social media account as judged by the Marketing Team. 3. In order to remove someone from the social media access group, a 2/3 vote must pass to remove the person in question. 4. Marketing Team members reserve the right to cut someone's access to an account in an emergency. How to change the rules for the Marketing Team: 1. Team member suggests a change to the rules, policy, or structure. 2. Team votes on the change and passes with a majority vote. The Fedora Ready Team is its own team that happens choose who can join as a member on its own, as needed. Not everyone needs to be in the team in order to collaborate on the initiative. This is just the team in charge of pushing the initiative forward. ___ At first this may not seem like a big change, but the new rules allow for the team to take action more quickly. We will know who is still in the team, not wait for responses from folks who may or may not be active at a given moment, and bias toward action unless we think a given situation demands putting something to vote. The social media access group will be managed by the Marketing Team and we can clean up who does or doesn't have access. The Fedora Ready Team will also be split off into its own team because we have different needs in that group than we do for the Marketing Team. If we take these steps and use this opportunity to reset the team with just Justin and myself as members, we can rebuild and clear out old stuff that is not a priority for the group right now. For now this is what I will run with until Justin comes back from his leave, especially because this isn't too different from the latest version of our defined structure. I'll leave this ticket open as a space for discussion.

josephgayoso commented

2025-07-16 02:25:47 +00:00

(Migrated from gitlab.com)

set status to To do

set status to **To do**

josephgayoso commented

2025-07-16 02:26:28 +00:00

(Migrated from gitlab.com)

If we decide this is what we want to do at a later date, then I will merge this into our Marketing Team docs.

josephgayoso commented

2025-07-22 02:51:55 +00:00

(Migrated from gitlab.com)

mentioned in issue #13

justwheel commented

2025-08-09 18:09:53 +00:00

(Migrated from gitlab.com)

I'm still on leave until 2025-08-26, but I wanted to weigh in here with some feedback and thoughts. Overall, I think this proposal is sound. We have talked about something like this for sometime. I am in favor of implementing it and providing more structure for newcomers to the Marketing Team.

I have some specific points of feedback. In order to use the GitLab.com comment threads feature, I am going to split out my specific feedback points as individual comments. We can have ongoing discussion about the specific feedback points as threads.

Thanks for spending the time to work on this, @josephgayoso. :pray_tone1:

I'm still on leave until 2025-08-26, but I wanted to weigh in here with some feedback and thoughts. Overall, I think this proposal is sound. We have talked about something like this for sometime. I am in favor of implementing it and providing more structure for newcomers to the Marketing Team. I have some specific points of feedback. In order to use the GitLab.com comment threads feature, I am going to split out my specific feedback points as individual comments. We can have ongoing discussion about the specific feedback points as threads. Thanks for spending the time to work on this, @josephgayoso. :pray_tone1:

justwheel commented

2025-08-09 18:11:55 +00:00

(Migrated from gitlab.com)

In order to join the Marketing Team:

[…]

You must have been collaborating with the Marketing Team for at least a month.

I think this step is too subjective. In my opinion, it makes more sense to make the process begin with a nomination. Of course, we can make a comment or note that if you are involved for less than a month, it is unlikely you will be nominated.

Also, to make it less intimidating, maybe we make a note that it is okay to ask for a nomination in the team chat room or on Fedora Discussion.

> In order to join the Marketing Team: > > […] > > 1. You must have been collaborating with the Marketing Team for at least a month. I think this step is too subjective. In my opinion, it makes more sense to make the process begin with a nomination. Of course, we can make a comment or note that if you are involved for less than a month, it is unlikely you will be nominated. Also, to make it less intimidating, maybe we make a note that it is okay to _ask_ for a nomination in the team chat room or on Fedora Discussion.

justwheel commented

2025-08-09 18:14:29 +00:00

(Migrated from gitlab.com)

In order to join the Marketing Team:

[…]

After that, someone in the team can nominate you to join the team. Your nomination will be put to vote to in the team. A simple majority of the Marketing Team must vote in favor.

I propose we adopt a lazy consensus voting model similar to the DEI Team. It is not a very refined model but it is useful as a starting point for updating the Marketing Team new member status.

> In order to join the Marketing Team: > > […] > > 2. After that, someone in the team can nominate you to join the team. Your nomination will be put to vote to in the team. A simple majority of the Marketing Team must vote in favor. I propose we adopt a [lazy consensus voting model](https://docs.fedoraproject.org/en-US/dei/policy/decision-process/#_lazy_approval) similar to the DEI Team. It is not a very refined model but it is useful as a starting point for updating the Marketing Team new member status.

justwheel commented

2025-08-09 18:17:36 +00:00

(Migrated from gitlab.com)

In order to join the Marketing Team:

[…]

In order for a team member to be removed from the Marketing Team, a 2/3 vote must pass to remove the person in question.

I suggest lazy consensus model unless we have a good reason to do so otherwise.

Note that the official Marketing Team membership is at 55 people. Obviously, this does not reflect the reality of the team's current size and capacity.

> In order to join the Marketing Team: > > […] > > 3. In order for a team member to be removed from the Marketing Team, a 2/3 vote must pass to remove the person in question. I suggest [lazy consensus model](https://docs.fedoraproject.org/en-US/dei/policy/decision-process/#_lazy_approval) unless we have a good reason to do so otherwise. Note that the [official Marketing Team membership](https://accounts.fedoraproject.org/group/marketing/?page_size=48&page_number=1) is at 55 people. Obviously, this does not reflect the reality of the team's current size and capacity.

justwheel commented

2025-08-09 18:32:13 +00:00

(Migrated from gitlab.com)

In order to join the Marketing Team:

[…]

The membership will reset each release cycle, meaning that you have to claim that you still want to be an active team member in order to continue. Otherwise your membership will be marked as inactive and you will need to be approved again.

This step is necessary. However, it needs two refinements:

A mechanism: How will members be noted as inactive? I suggest creating a new FAS group, e.g. "marketing-emeritus", add all inactive members there, and then remove them from the main "marketing" FAS group in a single, coordinated request to Fedora Infra.
A delegation: This is a new responsibility to be completed every release cycle. We need to come up with a way to make sure this gets "assigned" to someone in each release cycle. Is it a team lead role? Is it a team secretary? How can we document this responsibility so that it gets reliably executed?

> In order to join the Marketing Team: > > […] > > 4. The membership will reset each release cycle, meaning that you have to claim that you still want to be an active team member in order to continue. Otherwise your membership will be marked as inactive and you will need to be approved again. This step is necessary. However, it needs two refinements: 1. A mechanism: How will members be noted as inactive? I suggest creating a new FAS group, e.g. "marketing-emeritus", add all inactive members there, and then remove them from the main "marketing" FAS group in a single, coordinated request to Fedora Infra. 2. A delegation: This is a new responsibility to be completed every release cycle. We need to come up with a way to make sure this gets "assigned" to someone in each release cycle. Is it a team lead role? Is it a team secretary? How can we document this responsibility so that it gets reliably executed?

justwheel commented

2025-08-09 18:33:37 +00:00

(Migrated from gitlab.com)

In order to make decisions as a team:

[…]

A team member can make a ticket with their proposal. If someone wants to take an action, another team member can request that we vote on it before action is taken.

I think all tickets identified as proposals should have a required time period for a vote, e.g. 5 days. This is how the DEI Team does it in their lazy consensus voting model. We can choose a number of days that makes sense for our team.

> In order to make decisions as a team: > > […] > > 1. A team member can make a ticket with their proposal. If someone wants to take an action, another team member can request that we vote on it before action is taken. I think all tickets identified as proposals should have a required time period for a vote, e.g. 5 days. This is how the DEI Team does it in their [lazy consensus voting model](https://docs.fedoraproject.org/en-US/dei/policy/decision-process/#_lazy_approval). We can choose a number of days that makes sense for our team.

justwheel commented

2025-08-09 18:34:29 +00:00

(Migrated from gitlab.com)

To become a member of the social media access group:

[…]

Marketing Team members reserve the right to cut someone's access to an account in an emergency.

Simplify this by making it Marketing Team sponsors (per the role in FAS) can cut someone's access in an emergency. I think this is a responsibility we don't want everyone in the team to have to shoulder.

Thoughts?

> To become a member of the social media access group: > > […] > > 4. Marketing Team members reserve the right to cut someone's access to an account in an emergency. Simplify this by making it Marketing Team _sponsors_ (per the role in FAS) can cut someone's access in an emergency. I think this is a responsibility we don't want everyone in the team to have to shoulder. Thoughts?

justwheel commented

2025-08-09 18:36:01 +00:00

(Migrated from gitlab.com)

How to change the rules for the Marketing Team:

[…]

Team votes on the change and passes with a majority vote.

Simplify with lazy consensus voting model, per my previous comments.

> How to change the rules for the Marketing Team: > > […] > 2. Team votes on the change and passes with a majority vote. Simplify with [lazy consensus voting model](https://docs.fedoraproject.org/en-US/dei/policy/decision-process/#_lazy_approval), per my previous comments.

jflory7 added the

labels

2026-07-01 00:13:37 +00:00

Rows
Columns

Fedora Marketing Team Restructure #196