Nest with Fedora localisation sprint
Wrap up post
Chatting about Debian Conference
Sprint at Nest
Marie to reach out to Sumantro
Blog post
Nest sprint
Hopin access requests
Event Report Template
Lime Survey Docs
Nest hack session
Blog post
Mentorship docs
Ambassador call from June
Nest proposal: translations sprint for docs
Mentorship calls
Ambassador calls
Mentorship
Docs
Mentorship discussion
Upcoming release party
Ambassador Monthly Call
Docs
Council update on Wednesday
Docs
Adding to the Mindshare Quarterly Report
Pre-existing committees
Ambassador Meeting Follow Up
Wrap Up
Update for Council
Ambassador call today!
Hi Ambassadors, folks interested in becoming Ambassadors, or people who enjoy doing outreach for Fedora! We are about to meet for an Ambassador Kick-Off call and you're invited :) join us at 3PM UTC here (7 minutes from now) -> https://meet.jit.si/Fedora-Ambassadors-Call
Ambassador Call Debrief
Docs
Ambassador group cleanup
Ambassador Monthly Call
Ambassador Group Clean up
Docs
Docs To Do
Ambassador Monthly Call
Docs Notes TO DO
Things were thinking about
DevConf.CZ 2022 virtual
Review of Marketing work
Ambassador Monthly Call
Docs
FOSDEM
Review docs updates
Sprint
Docs updates
Marketing team
Ambassador group clean up
To do:
List of current activities for ambassadors
Notes from docs session
Marketing team is getting a revival?
Documentation work
FOSDEM
Discourse Reorg
Discussion.fpo
Informal Polls
Mindshare quarterly updates
DevConf.CZ talk accepted!
Let's add an update to the Mindshare Quarterly Update
Schedule next docs session
Next blog post
Discussion category
Threads on CommOps:
Do the team overviews sections seem sparse? I think we need to add some more general info there, for example for CommOps: https://pagure.io/fedora-commops/issue/220#comment-687545
FOSDEM presence
Informal Polls
Cara visited!
Notes about pushing docs
To DO:
Check in with Mariana and Marie
Let's kick off informal poll writing process
Should we make an Ambassadors category on Discussion?
Ambassador group clean up
Mattdm recommends we call our monthly call something with "ambassadors"
Docs update
F35 release party preso prep
Docs session
Summary of session with Justin
Blog post
Work session
Release Party
Sprint session
Blog Post [Review : https://hackmd.io/ipRwminKQKCGKDg4N8QJfQ]
Updates on the Annual Survey: Community Engagement section
Becoming an Ambassador discussion
Submission for DevConf.CZ
Release Party
Sprint Session
Updated Blog Post
Ambassador Mentorship Notes
Pushing docs
Release Party
F35 Release Party
Docs
F35 Release Party
Docs
2 HOUR DOC SPRINT
make a list of longer term responsibilities for the various teams
Ambassador Emeritus update
Documentation
Ambassador Emeritus
Community Outreach Resource Library
Meetings
Nest Summary
Kick-Off: Meetings & recurring
Next week: Pick a day for docs sprint
Completion of Role Handbooks for CommOps, Join SIG, Advocate, Ambassador, Ambassador Emeritus. Timeline: February 2021 - June 2021 - In progress
Formalized and documented process for reps to Mindshare. Timeline: February 2021 - June 2021 - Completed
Execution and analysis of Community Outreach survey. Timeline: December 2020 - January 2021 - Completed
Execution and documentation of Mindshare Team Interviews Timeline: July 2020 - February 2021 - Revist
Branding for CommOps team/subteams. Timeline: April 2021 - September 2021 - Completed
Draft and execution of Marketing plan. Timeline: June 2021 - December 2021 - Not yet started
Translations of Role Handbooks into 5-8 key languages. Timeline: June 2021 - December 2021 - Blocking on completion of handbooks
Community health survey for future use (periodically, every year). Timeline: September 2021 - December 2021 - Completed
Update and add to CommOps docs page to make it a complete indexed set of resources for each team under the CommOps umbrella. Timeline: June 2021-September 2021 - In progress
Informal polls to be developed and implemented (by the Revamp team at first and later by other teams) to measure awareness. Timeline: September 2021 - December 2021
Quick meetup to discuss Nest
To Do:
TO DO:
Sumantro - opening the ticket, send to Marie
Marie - send an email about nest session invitings folk to join, and to review our docs in advance- please ask us questions, we want the docs to be clear
Review of Contributor Survey results
Talk about badges
How to join Fedora resources done! (almost)
Cheat cube
Resource library outline & manage the process
Nest Session
When will the ambassador/advocate program re-open?
Nest idea
CommOps sticker sheet
We need a blog post update
Mindshare tickets
https://pagure.io/mindshare/issue/234 (needs to be resolved)
https://pagure.io/mindshare/issue/138 (needs to be resolved)
https://pagure.io/mindshare/issue/68 (sumantro commented, waiting feedback)
https://pagure.io/mindshare/issue/25 (needs to be resolved)
OpenSUSE
Mindshare tickets that are ambassador/outreach related:
https://pagure.io/mindshare/issue/3 (closed)
https://pagure.io/mindshare/issue/5 (closed)
https://pagure.io/mindshare/issue/15 (closed)
https://pagure.io/mindshare/issue/25 (needs to be resolved)
https://pagure.io/mindshare/issue/26 (closed)
https://pagure.io/mindshare/issue/68 (sumantro commented, waiting feedback)
https://pagure.io/mindshare/issue/86 (out of scope)
https://pagure.io/mindshare/issue/137 (closed)
https://pagure.io/mindshare/issue/138 (needs to be resolved)
https://pagure.io/mindshare/issue/234 (needs to be resolved)
Role Handbooks
OpenSUSE
Outreachy
Outreachy Intern Tasks Ideas
Updated logos for each team with new Fedora logo
Finish up how to Join Fedora infographic and open up a translation ticket to get it into a handful of other langugages
"Thank you, Fedora" infographic/design in many languages
Fedora bandana art
Sticker sheet for Commops to hand out & also reinforce team identities
Cheat cube - foldable cubes
Org chart breakdown
Infographic for the CommOps team Structure
Infographic for Fedora Organizational Chart
Release Party Presentation
OpenSUSE
Role Handbooks
Community Survey question reviews
Can we leverage hackmd better with a "team"?
Release Party Presentation
Role Handbooks
Can we leverage hackmd better with a "team"?
Survey Questions
All things open Cfp open
https://www.allthingsopen.org/all-things-open-2021-cfp-now-open-through-april-30/
https://pagure.io/mindshare/issue/263
Information we want to gather with the survey questions
All things open Cfp open
https://www.allthingsopen.org/all-things-open-2021-cfp-now-open-through-april-30/
Newest blog post is up! https://communityblog.fedoraproject.org/community-outreach-revamp-update/
Would this be suitable for Commops to incorporate into the revamp:
https://fedoramagazine.org/say-thanks-appreciation-week-2018/
All things open Cfp open
https://www.allthingsopen.org/all-things-open-2021-cfp-now-open-through-april-30/
Blog Post Update
Upcoming intern
Role Handbooks
Intern Tasks - need to organize these by priority
Community Survey
Linux App Summit
OpenSUSE Conference
Blog post update –- Review https://hackmd.io/Hf7mQRdeSkacYAJS4mguKQ
Organize conference submissions
Design internship tasks
Guadec
Outreachy Intern Tasks Ideas
OpenSUSE Conference
Role Handbooks
Outreachy
Community Central
Fedora Linux 34 Release Party
OpenSUSE Conference
Trello
Survey Analysis Blog post
Role Handbooks
https://docs.google.com/document/d/1mBCnQXqpa2fdO9fkhDa-zKlErPI1urV8SuO83BJGx4A/edit
So, we have been phrasing role handbooks as "How new contributors get started with outreach teams" and "the representation of a tight-knit identity of each of the teams and how they work in unison with all of the project"
Commops team used to look at numbers/analytics/helping with community things, could even be code
"Community operations"
Overarching group to help the variety of outreach teams work cohesively.
For the design intern:
Sumantro to move things to the Google Doc for role handbooks and start organizing
Linux App Summit
openSUSE Conference
Outreachy
Trello Board
Role Handbooks
Linux App Summit
openSUSE Conference
Open Source Summit EU
Outreachy
Trello Board
Badges
Role Handbooks
Marie To Do:
Review Sumantros post
Talk to Sayak & Ashlyn
Newest blog post:
https://communityblog.fedoraproject.org/fedora-community-outreach-revamp-update-4/
Outreachy intern
Trello board
Badges
Role Handbooks
CommOps Team Member
Ambassador Team Member
Ambassador Mentor
Advocate
Join SIG
Marketing
Ambassador Reps to Mindshare
Student focused pages
Survey Results
Objective
February Blog post
Summer Intern
New ticket for Revamp Design intern in upcoming Outreachy session
https://pagure.io/mentored-projects/issue/96
Trello board - do we want to update or retire?
Badges
Survey Results
Objective
February Blog Post
Free media again:
pbokoc: ok, going through ambassadors could work. If we have a list of ambassadors, we can mention that people can ask them to request install media somewhere on the same page (or somewhere else and link to the list), and the ambassador can open the request on behalf of whoever actually needs the USB stick
Survey results
Objective
YAY COUNCIL MEMBERS!! First time for Mariana, congrats!
Objective discussion
Devconf.cz Presentation
Let's discuss:
Can we address free media with revamp?
https://pagure.io/mindshare/issue/252
jwf: I think the Free Media program is from a different time in Fedora. But it did one thing uniquely: it provided a decentralized way for contributors to help others use and contribute to Fedora
jwf: Instead of requiring a process to go through Mindshare and take time, it was originally a fast process for someone to help someone else out without contacting the Fedora Board (back in the day)
jwf: It would be nice to see something replace that need that was once a very strong point for us
We feel this is no longer relevant. Not needed for Revamp.
Fedora Design intern for upcoming Outreachy session to work on design assets for the Revamp.
Fit in Fedora Badges to the revamp overall
CommOps "checkup check list"
Community Survey
Results Analysis:
To do:
We need to answer the following questions
Specifically:
Very minor: there’s an Activity to design the new swag and handouts (good) but “distribute new rebrand materials” should be in the Activities column as well somewhere, and a corresponding entry in outputs as well. In general it’d be nice to put numbers on things in the Outputs column where we can.
Less minor: I’d like to see more concrete measurables for Outcomes. How will we determine that teams are functional?
How will we decide that we have clear processes and documentation and an easy-to-participate-in onboarding process?
How will we know if Awareness is at levels we deem successful?
How will we know people feel connected to their team identities?
None of this will block me from voting for this, but having it done up front will make it easier for us to evaluate progress and eventual results.
I think the Outcomes need to be more measurable and specific with a plan for measurement.
The Ambassador team is full of active contributors who know what to do and how to do it
We have completed the first Ambassador group cleanup and we are adding a cadence into the Ambassador program for annual cleanups. This will ensure that the Ambassador team is full of active contributors only. We will also clarify the documentation on "how to become Ambassador Emeritus" so that if folks choose to retire they know what to do.
We will measure their knowledge of the Ambassador activities/processes through a specific survey for the members currently active in the Ambassador Team. This survey should be done 6 months, 1 year, and 2 years after the revamp is complete. The results of the survey should instigate any small or large adjustments that may need to be done to the program. These surveys will be written during the Revamp, and then implemented by CommOps/Mindshare.
The process for how to organize events and request swag is well known to all Ambassadors, and those within the larger CommOps umbrella.
This one will be kind of tough to measure. Ideally, we will be able to tap into some of these self-organized events and outreach activities with a CommOps based "Community Activity Network" of sorts. The community survey is showing us that people are doing things without reporting them back, so the overall community is unaware of the activity. The "CAN" would help boost the signal of these activites with virtually no effort from the people executing these activites but to submit them to the network. Once we are able to capture the events/activity that are happening we believe we will find that our event presence is robust.
We should see a general increase in Mindshare Committee tickets. We will need to measure how many new swag requests are being made, compare them to years past, and continue to look at those numbers. Based on our current pandemic life, this looks a bit different and may be hard to forecast. In the past year swag handouts have been organized centrally through the FCAIC as Red Hat is fulfilling these requests to personal addresses and their is a significant amount of Personal Identification Information (PII) and paperwork involved. The community survey is also showing us that almost everyone is attending events, but the motivation to self organize during the pandemic is low.
Members from CommOps & subteams are practicing new/updated forms of organized community outreach.
Clear onboarding documentation and process on how to get involved in the Community Outreach teams.
Brand awareness from CommOps new structure is beginning to grow based on branding and relevant marketing plans.
More contributors engaged in the Ambassadors program, but also the CommOps teams overall.
Weekly meetings for Community Outreach.
I also want to put out there that a lot of the deliverables here are a one-time thing… but I think some thought should be put towards ongoing / maintenance type activities. Because for example, new docs are great but they have to be maintained, and to keep them maintained they should start with a plan for sustaining them over time. The plan could be something as simple as, for example, scheduling an every 3-6mo review as part of the charter of the relevant team leadership, to review and update. But that thinking I think should take place now and the process be outlined.
- This is a great point and would definitely point us in a healthy direction for sustainability. 6 months seems like a reasonable cadence for folks to be checking in and updating docs pages for their teams. This is most likely something all teams should be doing, so I think it will fit in quite easily to the new structure. It has been noted to include these check-ins.
I also see that as a lot of the output are deliverables, I’d like to know if there is a distribution plan in mind (if not written up) for the materials in terms of how we’ll get them out and make them available. It’s mentioned that it’s a marketing team responsibility but I think understanding at the start what shape that delivery might take shape in (e.g. a special outreach specific website? social media distribution? some other platform like discourse? all of the above?) would help guide the creation of the content to be targeted for the correct target media. I’d suggest starting with a table of potential outlets. And thinking about, not just how do we announce this big change when it happens, but also where do the documents live and get access after the initial big announcement and in the general day-to-day operations over the long term as a reference. (could just be the fedora docs site, thats fine too, or could also involve a physical component like a printed “welcome kit” sent to new folks. would just like to see it written down :slight_smile: )
These are great points, thank you for raising them. The proposal and plan was originally written with the idea that we could include almost every team on the Mindshare side of Fedora. This is still true to an extent, but we are changing our approach based on our experience from the past 6 months. We found that we are able to engage at least 1+ person from each team, but not the team as a whole. For example we opened a CommOps ticket and just one person has been driving that. We opened a D&I ticket and we ended up taking the task back and which the Co-leads completed with assistance from a couple D&I team members who overlap with the TTF/Revamp efforts. Asking skilled individuals to help on specific tasks has been a very successful approach. We reflected upon this in our meetings and came to the conclusion that most Objectives/big changes are implemented by a small group of dedicated people, so we do not view this revised approach as a failure.
We have grabbed the following to-do's/conclusions from your comment. Let us know if we hit all the points :) We feel we need to get a good handle on the plans for these aspects and they will inform the other questions you have raised (where/how/format/sustainability)
Should the Join team have a role here in the logic model? Community Outreach includes new community contributor recruits too, right
During the research phase of the Revamp, executed by the FCAIC, we received feedback from the Join Team that they do not wish to add or remove any processes to their current workflow. The fundamental idea behind the Join Team, if we understood the feedback correctly, is that this group is for folks who want to help guide others with a low barrier to entry. Folks in Join hang out in a channel, and a couple of folks maintain a repo. They feel, as we do we, that they are working functionally currently, and we do not want to be an interference. They will be welcome at the overarching CommOps meetings, will be included in any announcements that are made, and will have access to all the resources that are developed for the Revamp.
We could add in a function for the CommOps team to review the Join repo on a certain cadence to see if there is an increase/trends in tickets for new contributors.
Survey
Objective
Ambassador Group Cleanup
UP NEXT: Role Handbook
Survey
Closes in one week (january 11th)
Promote again
Tweet - Sumantro Mukherjee - retweets! And send to Matthew Miller
Mariana - pinging commops discourse
Instagram - Mariana
Local networks - all of us - OSPO/local space/channels
DevConf.CZ
Feb 18th-20 https://www.devconf.info/cz/
Next week, put together presentation outline during revamp weekly meeting
Marie to make graphics after
FOSDEM
Missed the deadline.
Next time tell the whole story.
Objective
Draft short community blog post Marie Nordin
https://pagure.io/Fedora-Council/tickets/issue/335
Draft:
In June of 2020 the Community Outreach Revamp was developed. The initial plan was written by Marie Nordin and then approved by the Mindshare Committee. Implementation began soon after by co-leads Mariana Balla and Sumantro Mukherjee. It became evident pretty quickly that this initiative is of monumental proportions and will take a lot of coordination, people, and hours to complete. Although we don't often have non-code related objectives, the Revamp falls under similar work-load category to other objectives and is crucial to the future of Fedora's community outreach.
We have opened a ticket on the Council-tickets pagure to gain approval from the Council for this objective proposal. Please provide feedback there or on the Council Discuss discussion page. The Council will vote on this in two weeks.
For more info visit the following:
Initial Proposal
Objective Wiki Page
Temporary Task Force Meeting Notes
https://fedoraproject.org/wiki/Fedora_Ambassadors_Revamp_2020
https://fedoraproject.org/wiki/Objectives/CommunityOutreachRevamp
https://hackmd.io/zUX2PN40Qbea8CCD54hpHA?view
Group clean up
Pinged Alberto & Nick - this is complete!!
Mindshare Team Responsibilities Sumantro Mukherjee
Talk with Alberto, check where incomplete ones are at
Design Team - Mairin Duffy - DONE
Website Team - Rick Relrod
Fedora Docs - Petr Bokoc
Fedora Badges - Marie Nordin -
Fedora Magazine - Ben Cotton - DONE
Localization/Translations - Jean-Baptiste
CommOps - Alberto - DONE
Mentored Projects - Vipul - DONE
FOSDEM
Event is February 6th & 7th
Stands
marianaballa848@gmail.com is opening a mindshare ticket and making a submission for the stand
Distribution dev room info:
Deadline for submission Dec 20th
https://lists.fosdem.org/pipermail/fosdem/2020q4/003128.html
Community dev room info
Deadline for submission Dec 22nd
https://lists.fosdem.org/pipermail/fosdem/2020q4/003134.html
Our talk would fit better here
Note for later: Add in a clear process for Emeritus to come back to Ambassador
Updates made to objective wiki page & pagure ticket
https://pagure.io/Fedora-Council/tickets/issue/335
AMA Questions
Submitted a post to community Blog
https://communityblog.fedoraproject.org/fedora-community-outreach-revamp-ama/
Ambassador Cleanup - Sponsors/mentors
One response, good to make changes.
Ambassador cleanup
Sumantro has contacted 4 people
Almost completed, waiting till the weekend and we will move the unresponsive folks to Ambassador Emeritus
Survey
https://fedoraproject.limequery.com/679163?lang=en
Community blog post - Sumantro Mukherjee
Write emails to mailing lists - marianaballa848@gmail.com
Mindshare Committee
Ambassador
Announce
Diversity & Inclusion
Council discourse
https://discussion.fedoraproject.org/c/project/council-discuss/60
Tweet the survey - Marie Nordin
Telegram
Discord - Radka
AMA
https://discussion.fedoraproject.org/t/questions-for-the-taskforce-on-community-revamp/25040 for Question
https://communityblog.fedoraproject.org/community-outreach-revamp-call-for-ama-questions/ the agenda
Objective
Add timeline to Wiki Page & Trello Board
Meeting November 17th
Ambassador Cleanup
List of “sponsors” https://docs.google.com/spreadsheets/d/1P3vc4ViOWBgk5TtimPfEvtVil0CMJHcMkKhtzmjiBOg/edit#gid=746284534
Need to write up an email, send an email, gather responses, make adjustments as necessary
https://pagure.io/mindshare/issue/244 <- survey is progressing nicely. We are incorporating feedback.
Objective feedback: - need to revise the logic model
Lengthen time to 12-18 months
Determine and add in milestones
Ambassador group cleanup - july-nov 2020
Execution and analysis of Community Outreach survey - dec 2020 - january 2021
Execution and documentation of Mindshare Team Interviews - july 2020 - february 2021
Formalized and documented process for Ambassadors mentors - february 2021 - june 2021
Formalized and documented process for reps to Mindshare - february 2021 - june 2021
Completion of Role Handbooks - january 2021 - june 2021
Branding for CommOps team/subteams - April - september 2021
Draft and execution of Marketing plan - june 2021 - dec 2021
Translations of Role Handbooks into 5-8 key languages - june 2021 - dec 2021
I could change the title to “budget for rebrand”
From mattdm: Ah, yeah. And then that connects to the Design Team Activity "develop new branding", and "swag with new branding" is an Output, and maybe there's an "Engaged" section of Outcomes like "Members of the Mindshare/outreach teams feel engaged, energized, and appreciated"
AMA December 10th 3PM UTC during TTF meeting time.
Discourse thread
Community blog post
Marie finished logic model, Mariana opening council ticket
https://fedoraproject.org/wiki/Objectives/CommunityOutreachRevamp#Objective%3A_Fedora_Community_Outreach_Revamp
https://pagure.io/Fedora-Council/tickets/issue/335
Ideas:
Resource: 5-6 slide presentation, open a design team ticket
AMA for Community Outreach Revamp
Solicit questions
Marie followed up with Alberto & Nick on Ambassador group cleanup
Gave a presentation at the Release Party, it went well!
Mariana closing D&I ticket
Finished draft of survey -
Sumantro Mukherjee to work with Vipul on creating LimeSurvey
Keep it open for a month
Monday December 7th - Monday 11th of January
Goal of 100 responses
https://hackmd.io/dMFelaoqRxia3GMII99iew?view
Finished draft of DevConf.CZ proposal -> https://hackmd.io/Im6IGGxjQaGr6a045qF-tA?view
Mariana submitted it
We need to come up with slides/presentation
Finished draft of comm blog post #3 ->
https://hackmd.io/nfSaqGdPTVCz2NKhDrSAZw
Sumantro working to publish
Ambassador group cleanup -> in progress
Role handbooks -> stalled due to lack of time and we need community survey finished to complete
Mindshare teams responsibilities documentation ->
https://pagure.io/fedora-commops/issue/220
Sumantro ping ticket
Fedora Objective
Marie finish logic model
Release Party
Email D&I ML and ask for feedback
Hello Fedora D&I,
We have noticed that the Fedora D&I has been pretty busy in the past weeks and we would love to move forward with the team's feedback.
If you feel that you have already a lot on your plate, we can close the ticket and find some other way to work this through. I will leave this ticket open until next week.
Let me know what your thoughts are on this. :)
Cheers
Mariana
Sumantro make complete list of FAS accounts to be moved and send to Alberto
Need to finish Devconf proposal and submit by November 1st
Newest community blog post from Mariana []
Marie to finish logic model
TTF progress
Assign someone to write sponsor email
Ask about how they want to work: trello is working? No? Repo?
Ask them to review survey
Objective updates
Finish up logic model
Mariana will then open council ticket
Ambassador cleanup
Sumantro is still getting feedback from people
Sumantro will tally results, and send them to Alberto.
Alberto will make changes.
We need to make a blog post that we are doing that
Devconf.cz CfP -> deadline November 1st
https://www.devconf.info/cz
All on board
Responses from contacting inactive ambassadors https://hackmd.io/Lvk_Bfw2RL6FlHeDktqyLw
Survey Questions
https://etherpad.wikimedia.org/p/Community_Outreach_Survey
https://communityblog.fedoraproject.org/community-outreach-revamp-update-2/
Contacted ‘inactive’ Ambassadors
Ready to open a Council ticket, Mariana will own this.
Sumantro will own.
[Action Required] Fedora Ambassador Activity Status
Hi Fedora Friend!
You may have heard about the current Community Outreach Revamp initiative that is taking place. If not, feel free to check out the links below to learn more. We have run a script to determine who is active in the Ambassadors FAS group, and your account came up as inactive based on the results from the fedmsg system. We are contacting you via your FAS email.
We are reaching out to inquire if you would like to continue your participation on the Fedora Ambassador Team. You are absolutely welcome to stay involved, or if not, we can move you to the Ambassador Emeritus group. Please respond to this email within two weeks or we will consider your participation in the Ambassador group inactive. You can always re-join at a later time!
Kind regards,
Sumantro Mukherjee, Mariana Balla, & the Temporary Task Forcehttps://trello.com/b/XFg3Zgh8/fedora-ambassadors-revamp-2020
https://fedoraproject.org/wiki/Fedora_Ambassadors_Revamp_2020
Upcoming Meetings:
Community Outreach TTF Kick-Off Meeting (Part 2) - 12PM UTC in meet.google.com/eet-brwo-idx
Announcements:
Check out the Community Outreach Revamp (Ambassadors) Kick-Off meeting to learn more about the revamp and how to get involved. https://www.youtube.com/watch?v=K-rkc17V15U&feature=youtu.be
The Mindshare Teams questions have been finalized under the Community Outreach Revamp, and the interviews will begin soon. https://pagure.io/fedora-commops/issue/220
https://docs.fedoraproject.org/en-US/project/objectives/
Logic Model
Vision
The Problem
Goals
Outcomes
Strategy
Deliverables & Timeline
Objective Leads
Mariana Balla & Sumantro Muhkerjee
How do you see co-leadership on the objective working in terms of the Fedora Council?
Both Sumantro and Mariana will join the council, but they will share one vote. They will both attend meetings as necessary and able. Marie will work as back up to provide updates on progress.
I'd like to see some specific measures of success. I am fully in
agreement with the concept, but it would be good to have something to
measure against.
Completion of Role Handbooks
CommOps, Join SIG, Advocate, Ambassador, Ambassador Emeritus
Formalized and documented process for reps to Mindshare
Execution and analysis of Community Outreach survey
Execution and documentation of Mindshare Team Interviews
Branding for CommOps team/subteams
Draft and execution of Marketing plan
Translations of Role Handbooks into 5-8 key languages
CommOps team/subteams are aware and satisfied with new processes/structure
Along the same lines (and to repeat Matthew's question from the
meeting), what do you see being different 6 months from now? 12?
In 6 to 12 months from now:
The Ambassador team is full of active contributors who know what to do and how to do it.
The process for how to organize events and request swag is well known to all Ambassadors, and those within the larger CommOps umbrella.
Members from CommOps & subteams are practicing new/updated forms of organized community outreach.
Clear onboarding documentation and process on how to get involved in the Community Outreach teams.
Brand awareness from CommOps new structure is beginning to grow based on branding and relevant marketing plans.
More contributors engaged in the Ambassadors program, but also the CommOps team overall.
Weekly meetings for Community Outreach.
What kind of help will you need outside the scope of the Objective to
make it successful (e.g. design, documentation, software development,
etc)
The revamp plan includes most of the active teams within Mindshare. These teams have been asked to give their feedback as we worked on approving the proposal. For example, the design team will have to help with several of the tasks (logos, badges), the translation team will help to translate the role handbooks, etc. If you want to read more about how each team will be involved, there is further info on the wiki page. We will be using LimeSurvey to execute a survey.
1 hour long
Introductions from everyone
Name, where you are from, why you are here
Brief description of the Ambassadors revamp efforts (supposedly they have read the wiki)
Introduce the Trello board and explain the tasks that are already there.
Temporary task force starts here: https://trello.com/c/sgVnz6qm/33-update-and-finalize-commops-team-structure
Try to assign first tasks to people and get a feel for how they would like to meet.. Suggesting, bi-weekly IRC meetings??
Results:
http://whenisgood.net/rf7adpy/results/qqrfzrp
Thursday September 10th @ 4PM UTC
Short Commblog post to advertise meeting
1 hour long
Matthew: gives a brief history of the Ambassadors and intros Sumantro/Mariana/Marie
Sumantro/Mariana/Marie: introduce themselves: how long involved with fedora, what teams you participate in, current roles etc
Marie: talks about how the revamp came to be.
Hearing stories from contributors
Reading Switch in my book club
Hacking on the proposal over the course of 2 days
Feedback was gathered from the community and incorporated
Sumantro: talks about what the revamp is meant to do
Successful outreach teams within Fedora
More successful outreach and onboarding
Clarify onboarding, role and structure for teams
Modernize what it means to be a Fedora Ambassador
Contributor fulfillment
Mariana: talks about how we will implement the revamp
Mariana & Sumantro co-leading with support from the Marie
Volunteer task force will be working on some specific tasks
More tasks are being taken on by various teams within Mindshare
We are using a Trello board
Marie: talks briefly about kick-off meeting and what we accomplished
There is another kick off meeting at XYZ time and date
Task force is beginning work
Current open tickets with Mindshare teams:
Commops ticket
D&I ticket
Questions, comments, etc
Team name:
Summary:
Define the current responsibilities of your Team:
Define the current goals of your Team:
What is the greatest strength of your team?
What is the greatest weakness of your team?
What are the long term plans for the team (if applicable)?
Is there anything you can consider a "Mission Statement" for your Team?
Is there a specific task or issue that your Team needs help for from the Mindshare Committee?
Is there some function/activity you would like to see your Team doing that they aren’t doing currently?
Preferred asynchronous communication channel (mailing list, discussion.fp.o, etc):
Preferred synchronous (IRC channel, telegram, etc, none):
Issue tracker:
Documentation:
Meetings times and locations (if applicable):
Objective Idea: Fedora Community Outreach Revamp
This objective will be an initiative to revamp several community outreach teams within Fedora that are struggling to function, or need more support to truly become a success. The objective will bring together Ambassadors, Ambassador Emeritus, Join SIG, and Advocates all under the same umbrella of CommOps in a clear and cohesive structure.Work involved:
The objective will be based on a proposal that has been approved by the Mindshare Committee. [1] The revamp is being co-led by Sumantro Muhkerjee and Mariana Balla with the support of Marie Nordin, FCAIC. Sumantro and Mariana will co-lead the Objective as well if approved.There has been a call for volunteers, and kick off meetings are being arranged. [2] The proposal is also inclusive of the different teams under Mindshare, assigning tasks for each team to own. A further breakdown of tasks, timelines, and blockers can be found on the Revamp Trello board. [3]
Desired outcome:
The desired outcome for the Community Outreach Revamp is for Fedora’s outreach teams to be functioning successfully. The teams should be reinvigorated, understand their different roles clearly, and have all the tools to effectively outreach. Another desired outcome for this revamp is to rebuild contributor fulfillment in various ways.Why this initiative should be a Fedora objective:
This initiative should become a Fedora objective for a variety of reasons. It is a large coordinated effort that will take 6-12 months to complete. Community outreach is an important aspect of the Fedora Project that does not get as much visibility as some technical initiatives. Making the Revamp an Objective will bring increased visibility. It will help to interest more people to contribute, and furthermore it will also bring credibility to the work that is being done. It will also create accountability to the Council to ensure the work is moving forward.Feedback from the Council:
Please respond to this mail with thoughts, considerations, or suggestions for improvement. Once we receive feedback we will begin putting together the formal Objective proposal. [4]– Your Revamp Co-Leads, Sumantro & Mariana
Links:
[1] https://fedoraproject.org/wiki/Fedora_Ambassadors_Revamp_2020
[2] https://pagure.io/mindshare/issue/227
[3] https://trello.com/b/XFg3Zgh8/fedora-ambassadors-revamp-2020
[4] https://docs.fedoraproject.org/en-US/project/objectives/
Add in a recurring task for us to send updates to Ben every two weeks to be included in his weekly update blog posts
Inclusion in Ben’s weekly updates
As described in the Ambassador Revamp process, one of the goals is to ensure that every team has equal stakeholding in the revamp. To make this change more transparent and open for the community to understand, and to include each Mindshare team in the rebuilding process.
The Taskforce would request the CommOps team to develop interview questions and conduct research interviews with active members/leads of each Mindshare team. The goal of the survey will be to accurately document their current responsibilities as well as any goals/ideas they may have for the future. Lastly, the CommOps team will work with each Mindshare to ensure there is one point of reference on line for each team that include the following points.
List:
Team name
Summary
Link
Some indication of it’s not a zombie
Optional:
Preferred Asynchronous communication channel (mailing list, discussion.fp.o)
Preferred Synch (IRC channel, telegram, etc, none)
Issue tracker
Docs
Meetings
Other
The Fedora Docs team will help with the Docs process.
This ticket is to track the person who will be working on the ticket, the progress and communications.
We would like to set up a meeting as well with the CommOps folks who will work on this to provide additional context/support and answer any questions.
Brief position description of the co-leads and the volunteers roles
Plan of action - timeline for plan
Fill out timeline on each task
PRIORITY: timeline for survey (owned by d&i)
Identify blockers
Overall timeline
-
Any changes
Be notified of any changes
-
Mention me
Be notified of mention me
-
Unsubscribe
Subscribe