From Fedora Project Wiki
m (Added link to explain the term FCAIC)
(Switch out Ramya for Graham)
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Objective: Websites & Apps Community Revamp =
= Objective: Websites & Apps Community Revamp =


<!-- EDITOR NOTES:
<!-- Notes for Ramya:
Logic model draft for Websites & Apps: https://hackmd.io/3AK29tvGT5y6jJOmSfdAPw?view
 
Example of a proposed Objective: https://fedoraproject.org/wiki/Objectives/CommunityOutreachRevamp
Next steps for this revamp draft:
 
1. Add a "People" section near the top, which identifies co-leads, support, and any teams that we need to involve or mention in the Objective. (similar but different to https://fedoraproject.org/wiki/Objectives/CommunityOutreachRevamp#Objective_Leads )
2. Communicate changes to the Fedora Design team once made, in order to incorporate latest changes for the logic model https://pagure.io/design/issue/751
3. Post a thread inviting folks to review in the Websites & Apps section on Discourse: https://discussion.fedoraproject.org/c/project/websites/66 (example: https://discussion.fedoraproject.org/t/fedora-objective-proposal-community-outreach-revamp/25928?u=jflory7 )
 
-->
-->
== People ==


== Goal ==
* Co-leads: [[User:grahamwhiteuk|Graham White]], [[User:T0xic0der|Akashdeep Dhar]]
* Support: [[User:Jflory7|Justin W. Flory]], [[User:Riecatnor|Marie Nordin]]
* Other teams:
** RH OSPO: [[User:Misc|misc]]
** Community Platform Engineering: TBD ([[User:Pingou|pingou]]?)


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.  
== Mission ==
 
To reboot the websites team to include webapps in the scope of work and set up the team so that they can grow capacity in the future to build new exciting apps to meet community needs.


=== Logic Model ===
=== Logic Model ===
[[File:Websitesandappsrevamp logicmodel.png|center|thumb|800px]]


<!--
<!--
Line 17: Line 31:
-->
-->


== Vision ==


== Deliverables & Outcomes ==
Fedora has an active, engaged team that takes care of our main websites and all of our various community webapps. New folks who show up with an interest in code contributions find this an easy place to jump in. Members of the team are empowered to do the work they’re interested in and are connected to the other parts of the project related to getting those things done.


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.
== Outcomes ==


=== Deliverables ===
# The team is happy, excited, recognized, and rewarded.
# The team has experience and ability with updating legacy Fedora webapps and sites.
# The Fedora websites are reliably updated when new Fedora Linux releases come out.
# The team knows what they’re focused on, and that focus meets user needs.
# Information about Fedora Websites & Apps is accessible and easy to find.
# It’s easy to find tasks for every skill level and interest.
# Requests and PRs are handled promptly.
# Mentorship is available, both for interested new members and for all members needing to get things done in Fedora infrastructure.
# Websites team is participating in the Mindshare Committee.


* Completion of Role Handbooks for CommOps, Join SIG, Advocate, Ambassador, Ambassador Emeritus. Timeline: February 2021 - June 2021
=== Outputs ===
* Formalized and documented process for reps to Mindshare. Timeline: February 2021 - June 2021
* Execution and analysis of Community Outreach survey. Timeline: December 2020 - January 2021
* Execution and documentation of Mindshare Team Interviews Timeline: July 2020 - February 2021
* Branding for CommOps team/subteams. Timeline: April 2021 - September 2021
* Draft and execution of Marketing plan. Timeline: June 2021 - December 2021
* Translations of Role Handbooks into 5-8 key languages. Timeline: June 2021 - December 2021
* Community health survey for future use (periodically, every year). Timeline: September 2021 - December 2021
* 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
* 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


=== Outcomes ===
# Badges! Team swag!
# At least one webapp (møte) is modernized, as well as one web site (spins/labs).
# A documented plan for updating websites on new Fedora Linux releases, with understood team roles and resposibilities.
# A selected list of apps and websites with service level expectations. The websites in use are the most maintained ones.
# A continuously curated list of issues and tasks, organized by skillset and interest.
# Updated Fedora Websites documentation that explains the inventory of websites and how to get involved.
# A documented process is in plce for making sure requests (both PRs and requests for work) are triaged in a timely manner.
# "Websites Apprentices" program in place, and connections with Fedora Infrastructure team established.
# Fedora Mindshare Committee has an active, engaged representative to represent Fedora's Websites & Apps community.


* The Ambassador team is full of active contributors who know what to do and how to do it.
=== Activities ===
* 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.


Community feedback on the Discussion topic: https://discussion.fedoraproject.org/t/fedora-objective-proposal-community-outreach-revamp/25928
# Create team badges https://badges.fedoraproject.org/badge/rock-the-web%21 Request team swag.
# Develop new version of møte. Update  [spins website](https://spins.fedoraproject.org) to new framework. [Link to tasks]
# Document new release procedures and roles. Document specific team member responsibilities for release days and other critical needs.
# Inventory the existing apps and websites and decide what can be done about each. Where possible, mark older versions of websites as "outdated" and redirect to proper place. Encourage users (via design, documentation, and communication) towards the newer, maintained tools.
# Add new modules to the Fedora Websites docs based on different apps. Gradually migrate old docs in GitHub to the Docs repository.
# Regular meetings for the team that include triaging the W&A repo. [Smaller task: update repo with new tags]
# Continous review of incoming work; create reports showing response time and regularly reflect on those metrics.
# Define Website Apprentice & mentorship role.
# Create updated process for Web & Apps Team Rep to Mindshare and implement.


== Resources ==


== Scope of Work ==
# Badges team to create badges. FCAIC and Design team for team swag. #action riecat
# Developers working on møte. Infra team or CPE for updating where it runs. Rick to mentor in porting Spins website?
# Program management team to help with documented processes. (#action bcotton). Docs skills to update team docs.fp.o website (#action relrod+jwf).
# OSPO and CPE list of existing apps. _Someone_ to build a comprehensive map. Designers to work on best pratices for unified UX.
# Fedora Docs team for documentation operations ("doc ops"). Websites & Apps team to maintain the documentation content.
# The team and people interested in doing the triage work. Program Management team may help here too?
# As #6!
# Interested team members. Mentorship training provided by Council.
# Mindshare team to help onboarding. Someone to update docs in project docs.




== Examples ==


 
[Modernized version of the Logic Model](https://i.imgur.com/bsJi0hH.png)
== Objective Leads ==
 
[[user:marianab|Mariana Balla]]
 
[[user:sumantrom|Sumantro Mukherjee]]
 
* Note: Mariana & Sumantro will share one vote in Council votes.  
 
Support:
 
[[user:riecatnor|Marie Nordin]]




== Timeframe ==
== Timeframe ==


8-12 months.
8-12 months.
 
 
== Relevant Links ==
 
* [https://pagure.io/mindshare/issue/218 Original ticket on Mindshare repo]
* [https://fedoraproject.org/wiki/Fedora_Ambassadors_Revamp_2020 Proposal approved by the Mindshare Committee]
* [https://pagure.io/mindshare/issue/227 Temporary Task Force Mindshare ticket (comment to receive updates!)]
 
 
== History ==
 
Proposal written by [[user:riecatnor|Marie Nordin]], the current [https://docs.fedoraproject.org/en-US/council/fcaic/ FCAIC]. The proposal was approved by the Mindshare Committee. Co-leads were brought on, the TTF was assembled, and the work has been scoped. From there it was decided to ask the Council if it would be a good fit for an Objective. The proposal was discussed on council-discuss ML with some clarifying questions and positive feedback to move the initiative to an Objective.

Revision as of 14:00, 17 December 2021

Objective: Websites & Apps Community Revamp

People

Mission

To reboot the websites team to include webapps in the scope of work and set up the team so that they can grow capacity in the future to build new exciting apps to meet community needs.

Logic Model

Websitesandappsrevamp logicmodel.png


Vision

Fedora has an active, engaged team that takes care of our main websites and all of our various community webapps. New folks who show up with an interest in code contributions find this an easy place to jump in. Members of the team are empowered to do the work they’re interested in and are connected to the other parts of the project related to getting those things done.

Outcomes

  1. The team is happy, excited, recognized, and rewarded.
  2. The team has experience and ability with updating legacy Fedora webapps and sites.
  3. The Fedora websites are reliably updated when new Fedora Linux releases come out.
  4. The team knows what they’re focused on, and that focus meets user needs.
  5. Information about Fedora Websites & Apps is accessible and easy to find.
  6. It’s easy to find tasks for every skill level and interest.
  7. Requests and PRs are handled promptly.
  8. Mentorship is available, both for interested new members and for all members needing to get things done in Fedora infrastructure.
  9. Websites team is participating in the Mindshare Committee.

Outputs

  1. Badges! Team swag!
  2. At least one webapp (møte) is modernized, as well as one web site (spins/labs).
  3. A documented plan for updating websites on new Fedora Linux releases, with understood team roles and resposibilities.
  4. A selected list of apps and websites with service level expectations. The websites in use are the most maintained ones.
  5. A continuously curated list of issues and tasks, organized by skillset and interest.
  6. Updated Fedora Websites documentation that explains the inventory of websites and how to get involved.
  7. A documented process is in plce for making sure requests (both PRs and requests for work) are triaged in a timely manner.
  8. "Websites Apprentices" program in place, and connections with Fedora Infrastructure team established.
  9. Fedora Mindshare Committee has an active, engaged representative to represent Fedora's Websites & Apps community.

Activities

  1. Create team badges https://badges.fedoraproject.org/badge/rock-the-web%21 Request team swag.
  2. Develop new version of møte. Update [spins website](https://spins.fedoraproject.org) to new framework. [Link to tasks]
  3. Document new release procedures and roles. Document specific team member responsibilities for release days and other critical needs.
  4. Inventory the existing apps and websites and decide what can be done about each. Where possible, mark older versions of websites as "outdated" and redirect to proper place. Encourage users (via design, documentation, and communication) towards the newer, maintained tools.
  5. Add new modules to the Fedora Websites docs based on different apps. Gradually migrate old docs in GitHub to the Docs repository.
  6. Regular meetings for the team that include triaging the W&A repo. [Smaller task: update repo with new tags]
  7. Continous review of incoming work; create reports showing response time and regularly reflect on those metrics.
  8. Define Website Apprentice & mentorship role.
  9. Create updated process for Web & Apps Team Rep to Mindshare and implement.

Resources

  1. Badges team to create badges. FCAIC and Design team for team swag. #action riecat
  2. Developers working on møte. Infra team or CPE for updating where it runs. Rick to mentor in porting Spins website?
  3. Program management team to help with documented processes. (#action bcotton). Docs skills to update team docs.fp.o website (#action relrod+jwf).
  4. OSPO and CPE list of existing apps. _Someone_ to build a comprehensive map. Designers to work on best pratices for unified UX.
  5. Fedora Docs team for documentation operations ("doc ops"). Websites & Apps team to maintain the documentation content.
  6. The team and people interested in doing the triage work. Program Management team may help here too?
  7. As #6!
  8. Interested team members. Mentorship training provided by Council.
  9. Mindshare team to help onboarding. Someone to update docs in project docs.


Examples

[Modernized version of the Logic Model](https://i.imgur.com/bsJi0hH.png)


Timeframe

8-12 months.