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 Asynch communication channel (mailing list, discussion.fp.o, etc) 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.
Metadata Update from @bt0dotninja: - Issue assigned to bt0dotninja
@bt0dotninja thanks for taking this up. Please let me know if you need any more info :)
Hello @sumantrom ,
Sorry for the delay, I have a crazy week (and weekend) at work, here a draft of the questions, maybe you can give me some feedback and then I will start the interviews
Sorry (again) for the delay :persevere:
Hi @bt0dotninja, no worries, this looks great! We also need to ask for all the info I put into the description. I combined mine and yours together and tried to make it a bit more readable, see below.
WDYT? cc: @marianab @sumantrom
Mindshare Team Interview - 2020
Team name:
Summary:
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):
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?
I like it :smile:
if @sumantrom and @marianab agree I can start the interviews ASAP :)
Hi @bt0dotninja, no worries, this looks great! We also need to ask for all the info I put into the description. I combined mine and yours together and tried to make it a bit more readable, see below. WDYT? cc: @marianab @sumantrom Mindshare Team Interview - 2020 Team name: Summary: 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): 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? Looks great! Thanks @riecatnor
Looks great! Thanks @riecatnor
I like it :smile: if @sumantrom and @marianab agree I can start the interviews ASAP :)
I am +1 to start the interview. @marianab WDYT?
Same from my side. I am good with the questions. You can start the interviews :)
Summary: The Community operations team is working with sub-projects and teams to improve communitation, onboarding and generate creative solutions for common issues.
Preferred asynchronous communication channel (mailing list, discussion.fp.o, etc.): * https://discussion.fedoraproject.org/c/project/commops
Preferred synchronous (IRC channel, telegram, etc, none): #fedora-commops on Freenode @fedoracommops on Telegram
Issue tracker: * https://pagure.io/fedora-commops
Documentation: * https://docs.fedoraproject.org/en-US/commops/
Meetings times and locations (if applicable): * https://apps.fedoraproject.org/calendar/meeting/9812/
Define the current responsibilities of your Team: * Community Operations (CommOps) provides tools, resources, and utilities for Fedora's sub-projects to improve effective communication.
What is the greatest strength of your team? * CommOps member's skill sets allow creative solutions to a myriad of problems.
What is the greatest weakness of your team? A series of lucky events (After all the Fedora Community evolves quickly) generate new groups or individuals taking many of the main activities of CommOps. by example: The Community Blog editor activities were carried almost completely for bcotton. Making IRC-Telegram bridges is now done for the TeleIRC SIG. * The onboarding of new contributors is now done for the Join SIG. So CommOps is reducing its action field and relevance.
What are the long term plans for the team (if applicable)? * Update and generate metrics tools for the whole community then don't need technical knowledge to be used.
Is there anything you can consider a "Mission Statement" for your Team? * No
Is there a specific task or issue that your Team needs help for from the Mindshare Committee? * No, the revamp process will make commops active in many areas again,
Is there some function/activity you would like to see your Team doing that they aren't doing currently? * More tooling and solutions for the community.
Mentored Project (in the future I would like to see this change into outreach projects because things like hactoberfest which I do not think need mentor would also be included. All the outreach -> projects related initiatives can be a part of this.. but a future thing!)
Summary: Fedora Project participates in multiple mentored project programs and is actively looking for new mentors, projects, and programs that fit the criteria and can help the project/community grow.
Preferred asynchronous communication channel (mailing list, discussion.fp.o, etc): * summer-coding@lists.fedoraproject.org
Preferred synchronous (IRC channel, telegram, etc, none): * #fedora-summer-coding@Freenode.irc.net
Issue tracker: * https://pagure.io/mentored-projects/issues
Documentation: * https://docs.fedoraproject.org/en-US/mentored-projects/mentored_project/Info/
Meetings times and locations (if applicable): * None
Define the current responsibilities of your Team: Ensure timely participation of the org in GSoC and Outreachy Facilitate with anything to make the participation and projects a success
Define the current goals of your Team: * Enable contribution outside of the mentored-project timeline and sustain participants as the community members. Also, look and participate in other outreach programs to promote the project.
What is the greatest strength of your team? * Every mentored-project submitted (and accepted) has a defined goal/outcome and is not a shot in the dark.
What is the greatest weakness of your team? * No proper process to guide mentors on how to make students a community member and not just get the work done.
What are the long term plans for the team (if applicable)? Focus more on diversity and inclusive aspects of outreach participation. Select projects that the community wants and brings value to the community. * Projects that can help with Infra technical debts
Is there a specific task or issue that your Team needs help for from the Mindshare Committee? * Budget for outreachy (afaik, often pulled from diversity section)
Design Team - Mairin Duffy Website Team - Rick Relrod Fedora Docs - Petr Bokoc Fedora Badges - Marie Nordin Fedora Magazine - Ben Cotton Localization/Translations - Jean-Baptiste CommOps - Alberto Mentored Projects - Vipul
These are the teams we should be interviewing
@bt0dotninja , do we have an update on this?
here the status of the ticket:
Fedora Design Team
The Fedora Design Team is Fedora's in-house design agency. We provide artwork, user experience, usability, and general design services to the Fedora project.
https://lists.fedoraproject.org/archives/list/design-team@lists.fedoraproject.org/
https://matrix.to/#/#fedora-design:matrix.org
(these are synced to each other)
https://pagure.io/design/issues
https://fedoraproject.org/wiki/Design
N/A
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?
(Discussed in Discussion thread)
Design Team - Mairin Duffy (Status: Done) Marketing team - Eduard Lucena (Status: mail sent) Website Team - Rick Relrod (Status: mail sent) Fedora Docs - Petr Bokoc (Status: mail sent) Fedora Badges - Marie Nordin (Status: mail sent) Fedora Magazine - Ben Cotton (Status: Done) Localization/Translations - Jean-Baptiste (Status: Mail sent) CommOps - Alberto (Status: Done) Mentored Projects - Vipul (Status: Done)
I send a mail to the Localization/Translation ML.
https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org/thread/7JDSVQFZSNMXRLRDXZGLHQC6UASRYMJ6/
Fedora Localization team ... Mailing list ... Preferred synchronous (IRC channel, telegram, etc., none):
None probably is the best answer.
We have #fedora-l10n on IRC but it really is quiet and unfriendly for non technical expert.
... Issue tracker: https://pagure.io/fedora-l10n/tickets ... Documentation:
https://fedoraproject.org/wiki/L10N
We should move to docs someday, but we are quite far from it: https://docs.fedoraproject.org/en-US/localization/ is almost empty.
... Meetings times and locations (if applicable): none. ... Define the current responsibilities of your Team:
Make Fedora resource multilingual by translating or adapt content.
Contribute the global effort to make Linux a multilingual system by translating FLOSS projects.
... Define the current goals of your Team: Be fully integrated in the Fedora community processes. ... What is the greatest strength of your team?
Were are a decentralized team, hundreds of volunteers each in its language. Few teams have multiple members.
... What is the greatest weakness of your team?
We have almost no way to help each other and really collaborate.
... What are the long term plans for the team (if applicable)?
Last time we talked about it, was at Flock Krakow in 2019.
From my notes (sorry I did not publish that anywhere):
Support local communities by allowing them to use Fedora tools in their languages in their projects
Support translators by providing them tools to make them more efficient
Examples:
Translate FAS and Nuancier
Organize virtual FAD focused on translation
Translate the Silverblue webiste, its toolbox and its documentation
make our documentation multilingual
Half of these objectives are now done :)
Some thanks to our actions:
Some thanks to external people:
FAS 2, aka Noggin can be translated thanks to infra team
Silverblue doc moved to Fedora docs
... Is there anything you can consider a "Mission Statement" for Your Team?
Fedora mission is: /The Fedora Project envisions a world where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities./
I feel like it does the job for our team too, we make our part to make this mission comes true for the billions of Human who are not English native.
... Is there a specific task or issue that your Team needs help for from the Mindshare Committee?
Localization is a fine place to discover the Fedora community, a fine place for inclusion, help us to make multilingualism part of the Fedora community. We have too many initiatives which can't be translated just because the toolkit was chosen without taking internationalization in the balance.
Wish list:
... Is there some function/activity you would like to see your Team doing that they aren’t doing currently? Virtual FAD would be most welcome. ... Thank you so much for your attention and participation.
thank you for your work, sorry for slow response,
Design Team - Mairin Duffy (Status: Done) Marketing team - Eduard Lucena (Status: mail sent) Website Team - Rick Relrod (Status: mail sent) Fedora Docs - Petr Bokoc (Status: mail sent) Fedora Badges - Marie Nordin (Status: mail sent) Fedora Magazine - Ben Cotton (Status: Done) Localization/Translations - Jean-Baptiste (Status: Done) CommOps - Alberto (Status: Done) Mentored Projects - Vipul (Status: Done)
Login to comment on this ticket.