commops/tickets
19
4
Fork 0
Code Issues 16 Pull requests Activity

New CommOps representative needed on the Mindshare committee #145

New issue
Open
opened 2026-06-11 10:15:06 +00:00 by gwmngilfen · 4 comments
gwmngilfen commented 2026-06-11 10:15:06 +00:00
Owner
Copy link

Summary

A new CommOps rep needs to be selected for Mindshare

Function

Experience: Community Experience, including onboarding, events, outreach, and contributor journeys

Scope

Improvement: Something we are either repeating or improving

Category

Meta: Improvements and changes to the CommOps Team itself

Background

My term as CommOps rep to Mindshare is about to expire, so a new person needs to be selected. I'm not putting myself forward, as it's become clear I took on too much this year. Who is interested? :grin

Details

A person is selected

Expected Outcome

No response

### Summary A new CommOps rep needs to be selected for Mindshare ### Function Experience: Community Experience, including onboarding, events, outreach, and contributor journeys ### Scope Improvement: Something we are either repeating or improving ### Category Meta: Improvements and changes to the CommOps Team itself ### Background My term as CommOps rep to Mindshare is about to expire, so a new person needs to be selected. I'm not putting myself forward, as it's become clear I took on too much this year. Who is interested? :grin ### Details A person is selected ### Expected Outcome _No response_
jflory7 commented 2026-06-23 15:57:33 +00:00
Owner
Copy link

Discussed in the 2026-06-23 Community Ops Team meeting.

The team formally announced the need for a new Community Ops representative to the Fedora Mindshare Committee as @gwmngilfen steps down from the role. This is a critical position for ensuring CommOps interests are represented in Fedora's global outreach and event activities.

Follow-up Items:

  • Open Call: Community members interested in serving as the CommOps Mindshare representative should reach out. @gwmngilfen is available for questions regarding the role's responsibilities.
_Discussed in the [2026-06-23 Community Ops Team meeting](https://discussion.fedoraproject.org/t/fedora-community-ops-meeting-2026-06-23-f45-release-party-kickoff-matrix-news-bot/194602)_. --- The team formally announced the need for a new Community Ops representative to the Fedora Mindshare Committee as @gwmngilfen steps down from the role. This is a critical position for ensuring CommOps interests are represented in Fedora's global outreach and event activities. **Follow-up Items:** * **Open Call**: Community members interested in serving as the CommOps Mindshare representative should reach out. @gwmngilfen is available for questions regarding the role's responsibilities.
jflory7 added the due date 2026-07-01 2026-06-23 15:57:43 +00:00
jflory7 self-assigned this 2026-06-23 15:58:46 +00:00
jflory7 commented 2026-06-25 23:39:01 +00:00
Owner
Copy link

Rolling this ticket from Q2 to Q3 Team Goals. The nomination process needs more runway to identify candidates, and the team can use the next quarter to socialize the role and its responsibilities.

Rolling this ticket from Q2 to Q3 Team Goals. The nomination process needs more runway to identify candidates, and the team can use the next quarter to socialize the role and its responsibilities.
jflory7 commented 2026-07-16 03:43:11 +00:00
Owner
Copy link

We are one month past the start of the new Mindshare Committee term. No new volunteers were identified. For now, I am closing this ticket as state/wontfix and we will leave the seat vacant until further notice. If we want to fill that seat later in the term, then let's discuss this when we are ready to do so.

We are one month past the start of the new Mindshare Committee term. No new volunteers were identified. For now, I am closing this ticket as `state/wontfix` and we will leave the seat vacant until further notice. If we want to fill that seat later in the term, then let's discuss this when we are ready to do so.
theprogram commented 2026-07-23 12:38:30 +00:00
Owner
Copy link

We have decided to reopen the ticket (in Mindshare meeting 2026-07-23) and as thus still require a CommOps member to join us in Mindshare for the remainder of the year.

Please come along and help us run Mindshare!

We have decided to reopen the ticket (in Mindshare meeting 2026-07-23) and as thus still require a CommOps member to join us in Mindshare for the remainder of the year. Please come along and help us run Mindshare!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
releaseparty
datagov-datause
No results found.
Labels
Clear labels   
meeting topic request
Use this label to request follow-up on an item in the next scheduled team meeting. The meeting chair triages and prioritizes items for discussion on the meeting agenda.

  
function
analytics
 Community Social Analytics. One of the two main functions of the Community Operations Team. All issues/tasks should identify a function as different team members are responsible for different function

  
function
communications
 Community Blog, newsletters, outreach content, Magazine coordination, and community messaging

  
function
docs
 Documentation site, playbooks, guides, knowledge base, and contributor reference materials

  
function
events
 Event production, release parties, conferences, streaming, video processing, and community event logistics

  
function
onboarding
 Newcomer experience, mentoring, intern programs, team growth, and contributor onboarding

  
function
operations
 Team governance, repo management, meeting logistics, infrastructure, and internal process

  
good first issue
Good tickets to begin with (if you want to get involved, try working on one of these!)

  
help wanted
Tickets where we need help or need feedback from the wider Fedora community

  
needs
changes
 Needs changes or fixes before closing

  
needs
reporter feedback
 Additional feedback or information from the reporter is needed to advance

  
needs
team vote
 A vote is required from Fedora Community Operations Team members in order to advance

  
needs
triage
 A repository maintainer is needed to triage this further

  
scope
bug
 Something isn't working

  
scope
improvement
 Requests for something we are either repeating or improving

  
scope
new
 Requests for a new task or project for the team

  
state
approved
 Tickets that received approval by the Fedora Community Operations Team

  
state
blocked
 Cannot move forward: blocked by feedback, other tickets, etc.

  
state
duplicate
 This issue or merge request already exists

  
state
invalid
 This doesn't seem right

  
state
wontfix
 This will not be worked on

No labels
meeting topic request
function
analytics
function
communications
function
docs
function
events
function
onboarding
function
operations
good first issue
help wanted
needs
changes
needs
reporter feedback
needs
team vote
needs
triage
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
jflory7
gwmngilfen
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2026-07-01

Dependencies

No dependencies set.

Reference
commops/tickets#145
No description provided.