# Logic Model for Websites & Apps Objective: Detailed

This document is part of a September 2021 reflection activity for us to look back on the original logic model and decide if it still meets the current objectives and vision for the W&A Objective.

## Logic model flow

| Resources | Activities | Outputs | Outcomes | Impact |
| --------- | ---------- | -------- | -------- | -------- |
| Text | Text | Text | Text | Text |

## Resources

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

## Activities

1. Create team badges https://badges.fedoraproject.org/badge/rock-the-web%21 Request team swag.
* Team Swag
* Process
* Decide what and how many we want
* Open a ticket with Mindshare requesting funds
* Open a ticket with design team to get approved artwork
* Give that back to FCAIC to get printed
* Who gets the swag? How do they get it?
* Track this somehow?
* They should be sent to the general Fedora community as well
* Keeping track of folks making valuable contributions(?)
* Sending to folks around an event (?)
* Once the revamp is complete do a swag drive for current members (?)
* In an "in person" world, we could award these at Flock or at a Fedora Activity Day for the team
* Badge
* Team Member Badge
* Open a ticket for revamped team member artwork
* https://pagure.io/fedora-badges/issue/807
* Work on art, get approvals
* Work with Badge devs to get it pushed
* Repo Badges
* https://pagure.io/fedora-websites
* https://pagure.io/fedora-web/websites
* https://github.com/t0xic0der/fedora-easyfix (To be moved to fedora-infra)
* https://github.com/t0xic0der/fragment (To be moved to fedora-infra)

2. Develop new version of møte. Update [spins website](https://spins.fedoraproject.org) to new framework. [Link to tasks]
* Fragment
* Akashdeep & CPE are working together
* Potential Outreachy project

3. Document new release Of Fedora procedures and roles. Document specific team member responsibilities for Fedora release days and other critical needs.
* Gather current documentation links
* https://pagure.io/fedora-docs/websites
* Identify the different processes that are involved in the release
* Work with current owners/stakeholders
* Justin notes: thinks the Nest session was successful from the FCOR Revamp
* https://fedoraproject.org/wiki/Community_Outreach_Revamp_Knowledge_Base
* For each edit/revise/add
* Sprint/hackfest
* Stakeholders review of proposed new processes
* Push them out

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.
* We have an informal inventory
* https://apps.fedoraproject.org/
* Where can we find all the websites & apps?
* A good starting place would be the presentation done at Nest
* Akash made a list? An informal list here https://github.com/t0xic0der/t0xic0der/blob/master/NestWithFedora2021_1141IST_10Aug2021_FedoraWebsitesAndApps.pdf
* Create wiki page
* Review by stakeholders
* The intern will be working on Fedora Graphs- a visualization of fedora web & apps
* We need the inventory completed by Dec. 6, 2021

5. Create common process and procedure for creating and sharing information about Fedora Websites. (completed)
* https://docs.fedoraproject.org/en-US/websites/
* https://pagure.io/fedora-websites/blob/main/f/docs
* Identify places where written content already exists.
* Agree on a final resting place for documentation about Fedora Websites to live.
* Define a process for creating, modifying, and changing information/docs on Fedora Websites.

6. Add new modules to the Fedora Websites docs based on different apps. Gradually migrate old docs in Wiki to the Docs repository.
* Research into what "old docs" on Github is? — clarified by mattdm as wiki page content!
* Who is our audience for the documentation?
* Contributor, user, or community style
* Akash: contributor focused seems to be a good starting point. This would live on the docs page. This includes README.md and CONTRIBUTING.md for the web and apps as a whole.
* Ramya: Developer docs for setting up the environments, tech stacks, etc. This would live on the individual Pagure repo(?). Each repo can have its own developer guide
* Justin: We need baseline/common steps for contributors to take on setting up development tools and envs as well. Making sure they are using the active pieces of tech
* Avoiding duplication of common content across multiple projects! Same general steps for Python, or Ruby, or JS, etc. before branching out to project-specific steps and docs
* Where does this kind of generic set-up content live currently? Developer portal
* https://developer.fedoraproject.org/
* Possible docs "flow" to answer question "I want to contribute to X project":
1. Generic set-up instructions for a project (e.g. is it a Python/JavaScript/Ruby project etc.) => dev.fp.o
2. Specific steps to set up an individual project => README.md
* Docs flow for contributing and getting involved:
1. What projects are there? => docs.fp.o/websites/
2. Jump out to a specific project => docs.fp.o to git repo

We could use this to store our development, review would happen here: https://pagure.io/fedora-websites/blob/master/f/docs

We need 3 buckets: Contributor focused, developer focused, process focused docs

---
To do steps:
1. Gather all the old wiki pages, inventory
1. Evaluate what is on current docs page
1. Identify modules to create or add based on inventory and content that already exists
1. Evaluate, update, and write documentation in work sessions
1. Stakeholder feedback and editing sessions
1. Push documentation to docs page
1. Final resting places
a. https://docs.fedoraproject.org/en-US/websites/
b. https://developer.fedoraproject.org/
---

7. Regular meetings for the team that include triaging the W&A repo. [Smaller task: update repo with new tags]
- This is complete? Maybe? Yes!
- https://docs.fedoraproject.org/en-US/websites/#_meetings

8. Continuous review of incoming work; create reports showing response time and regularly reflect on those metrics.
- Reports/Metrics, to try to figure out if things are moving forward
- Two sets of "participants"- team members and community
- Measure team performance
- Measure team health
- How does community feel about the web & apps team revamp
- short survey
- 6-8 question about community engagement and awareness
- can we do a badge/swag for this?
- process for survey: through mindshare
- Define and document exact things we are measuring
- Create a cadence
- what do we think is a good cadence?
- once a month seems good to start
- quarterly check-ins for the future
- We need to document the process
- Can we make a script for this?
- we need to think this through re: move from pagure to gitlab
- does seem most convenient
- Rotation or sign up for folks to do this task?
- We need an active contributor to do this a couple times to start at least
- Gregory seems like a good choice for this? if he is ready
- Track this process by ticket? Team Kanban board?
- Ticket seems like a good way to track.
- Could be converted to a quarterly report?

9. Define Website Apprentice & mentorship role.
-

10. Create updated process for Web & Apps Team Rep to Mindshare and implement.
- We need to talk with relrod
- We should work up updated process/docs based on: https://docs.fedoraproject.org/en-US/commops/handbooks/mindshare-reps/
- Translate into web & apps team lingo
- Live on Web & apps docs
- (Marie??)

## Outputs

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

## Outcomes

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

## Impact

### 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.

### 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.

## Inventory for the documentation
1. All documentation to be combined here https://pagure.io/fedora-websites/blob/master/f/docs