(modularity update) |
m (Jflory7 moved page Objectives/Completed to Initiatives/Completed: Change namespace: Objectives are retired and are now known as Initiatives. https://docs.fedoraproject.org/en-US/project/initiatives/) |
||
| (5 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
The following Fedora Project 12-18 Month objectives have been completed. We might still care about these things, but they're not the current focus. For that, see [[Objectives]]/ | The following Fedora Project 12-18 Month objectives have been completed. We might still care about these things, but they're not the current focus. For that, see [[Objectives]]/ | ||
=== Fedora Modularization | === Websites & Apps Revamp === | ||
''Summary:'' 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. | |||
''Objective Leads:'' Akashdeep Dhar | |||
''Timeframe:'' June 2021 – April 2023 | |||
''Details:'' [[Objectives/Websites_%26_Apps_Community_Revamp]] | |||
=== Community Outreach Revamp === | |||
''Summary:'' 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. | |||
''Objective Leads:'' Mariana Balla and Sumantro Mukherjee | |||
''Timeframe:'' March 2020 – September 2022 | |||
''Details:'' [[Objectives/CommunityOutreachRevamp]] | |||
=== Minimization === | |||
''Summary:'' Helping open source developers, sysadmins, and Linux distribution maintainers to focus on what’s relevant for them. | |||
''Objective Lead:'' Adam Šamalík | |||
''Timeframe:'' Fedora Linux 32-34 | |||
''Details:'' [https://docs.fedoraproject.org/en-US/minimization/ Docs] | |||
=== Fedora IoT === | |||
''Summary:'' Fedora IoT makes Fedora the default for open source innovation on IoT hardware, endpoint, edge, middleware, cloud, and backend platforms. | |||
''Objective Lead:'' Peter Robinson | |||
''Timeframe:'' Fedora 33 | |||
''Details:'' [https://docs.fedoraproject.org/en-US/iot/prd/ Product Requirements Document] | |||
=== Continuous Integration and Delivery of Fedora Atomic Host === | |||
''Summary:'' We aim to deliver Atomic Host in Fedora via Continuous Integration and Continuous Delivery. | |||
''Objective Lead:'' Dominik Perpeet | |||
''Timeframe:'' Release via CI/CD in F27, with refinements in F28 | |||
''Details:'' [[Objectives/Continuous_Integration_and_Delivery_of_Fedora_Atomic_Host]] | |||
=== Fedora Modularization === | |||
==== Prototype Phase ==== | |||
''Summary:'' Deliver a functional implementation of modular Fedora | ''Summary:'' Deliver a functional implementation of modular Fedora | ||
| Line 11: | Line 60: | ||
''Details:'' [[Objectives/Fedora Modularization, Prototype Phase]] | ''Details:'' [[Objectives/Fedora Modularization, Prototype Phase]] | ||
==== Requirements Phase ==== | |||
''Summary:'' Requirements-gathering from stakeholders for "Rings" aspect of [[Fedora.next]] | |||
''Objective Lead:'' [[User:langdon|Langdon White]] | |||
''Timeframe:'' F23 release - Flock; replaced in early 2016 with [[Objectives/Fedora_Modularization,_Prototype_Phase]] | |||
'' | ''Details:'' [[Objectives/Fedora Modularization, Requirements Phase]] | ||
==== The Release ==== | |||
''Summary:'' Implement a new modular Fedora design, building on lessons learned in prototype phase. | |||
''Objective Lead:'' [[User:langdon|Langdon White]] | ''Objective Lead:'' [[User:langdon|Langdon White]] | ||
''Timeframe:'' | ''Timeframe:'' Release with F28, improvements in F29, with publicity to follow. | ||
''Details:'' [[Objectives/ | ''Details:'' [[Objectives/Fedora_Modularization_%E2%80%94_The_Release]] | ||
=== Fedora Editions, Phase 2 === | === Fedora Editions, Phase 2 === | ||
| Line 35: | Line 91: | ||
''Result:'' Seems very successful. Very positive reviews of Fedora OS in general, and we're starting to see Fedora Server reviewed (while in the prior years Fedora was only positioned in the media as a desktop OS). Working groups are active and building and attracting community contributors. And, we've shipped some different configurations in the different editions, with room for more change in the future as needed. | ''Result:'' Seems very successful. Very positive reviews of Fedora OS in general, and we're starting to see Fedora Server reviewed (while in the prior years Fedora was only positioned in the media as a desktop OS). Working groups are active and building and attracting community contributors. And, we've shipped some different configurations in the different editions, with room for more change in the future as needed. | ||
=== University Involvement Initiative === | === University Involvement Initiative === | ||
Latest revision as of 14:04, 7 February 2024
The following Fedora Project 12-18 Month objectives have been completed. We might still care about these things, but they're not the current focus. For that, see Objectives/
Websites & Apps Revamp
Summary: 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.
Objective Leads: Akashdeep Dhar
Timeframe: June 2021 – April 2023
Details: Objectives/Websites_&_Apps_Community_Revamp
Community Outreach Revamp
Summary: 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.
Objective Leads: Mariana Balla and Sumantro Mukherjee
Timeframe: March 2020 – September 2022
Details: Objectives/CommunityOutreachRevamp
Minimization
Summary: Helping open source developers, sysadmins, and Linux distribution maintainers to focus on what’s relevant for them.
Objective Lead: Adam Šamalík
Timeframe: Fedora Linux 32-34
Details: Docs
Fedora IoT
Summary: Fedora IoT makes Fedora the default for open source innovation on IoT hardware, endpoint, edge, middleware, cloud, and backend platforms.
Objective Lead: Peter Robinson
Timeframe: Fedora 33
Details: Product Requirements Document
Continuous Integration and Delivery of Fedora Atomic Host
Summary: We aim to deliver Atomic Host in Fedora via Continuous Integration and Continuous Delivery.
Objective Lead: Dominik Perpeet
Timeframe: Release via CI/CD in F27, with refinements in F28
Details: Objectives/Continuous_Integration_and_Delivery_of_Fedora_Atomic_Host
Fedora Modularization
Prototype Phase
Summary: Deliver a functional implementation of modular Fedora
Objective Lead: Langdon White
Timeframe: Prototype should be available around F25 release, with demos at conferences in early 2017.
Details: Objectives/Fedora Modularization, Prototype Phase
Requirements Phase
Summary: Requirements-gathering from stakeholders for "Rings" aspect of Fedora.next
Objective Lead: Langdon White
Timeframe: F23 release - Flock; replaced in early 2016 with Objectives/Fedora_Modularization,_Prototype_Phase
Details: Objectives/Fedora Modularization, Requirements Phase
The Release
Summary: Implement a new modular Fedora design, building on lessons learned in prototype phase.
Objective Lead: Langdon White
Timeframe: Release with F28, improvements in F29, with publicity to follow.
Details: Objectives/Fedora_Modularization_—_The_Release
Fedora Editions, Phase 2
Summary: Take the initial Server/Workstation/Cloud split from Fedora 21 from an experiment into solid production. Increase autonomy from FESCo and improve targeted outreach.
Objective Lead: Stephen Gallagher
Timeframe: F22 and F23 releases, ending shortly after Flock 2015.
Details: Objectives/Fedora Editions, Phase 2
Result: Seems very successful. Very positive reviews of Fedora OS in general, and we're starting to see Fedora Server reviewed (while in the prior years Fedora was only positioned in the media as a desktop OS). Working groups are active and building and attracting community contributors. And, we've shipped some different configurations in the different editions, with room for more change in the future as needed.
University Involvement Initiative
Summary: Increase Fedora's exposure in university environments, particularly engineering universities.
Objective Lead: Remy DeCausemaker
Timeframe: 2015-2016 academic year
Details: Objectives/University_Involvement_Initiative
Result: Effort died out; could be restarted but needs new focus.