From 210189aa51179a190a7a52d6ed0ca1f007342c53 Mon Sep 17 00:00:00 2001 From: langdon Date: Sep 17 2019 21:53:40 +0000 Subject: [PATCH 1/3] proposal for a new modularity objective --- diff --git a/project/modules/ROOT/pages/objectives.adoc b/project/modules/ROOT/pages/objectives.adoc index fb3572c..1c3614b 100644 --- a/project/modules/ROOT/pages/objectives.adoc +++ b/project/modules/ROOT/pages/objectives.adoc @@ -40,24 +40,24 @@ Will be appearing in the xref:minimization::index.adoc[Fedora Minimization objec ''' -=== Fedora Modularization — The Release +=== Fedora Modularization — Modularity Stabilization & Improvements image::modularity-badge.png[float="right"] Summary:: -Implement a new https://docs.pagure.org/modularity/[modular Fedora] design, building on lessons learned in prototype phase. +As https://docs.pagure.org/modularity/[Modularity] in Fedora comes in to widespread use, the Modularity Team would like to address issues discovered and improve the experience. Objective Lead:: https://fedoraproject.org/wiki/User:Langdon[Langdon White] Timeframe:: -Release with F28, improvements in F29, with publicity to follow. +Ongoing changes and improvements F31 through F33. Latest Status Report:: – Objective Details:: -https://fedoraproject.org/wiki/Objectives/Fedora_Modularization_%E2%80%94_The_Release[Fedora Modularization — The Release] +xref:objectives/objective-modularity-f30-f33.adoc[Fedora Modularization -- Modularity & Stabilization Improvements] Documentation:: https://docs.pagure.org/modularity/ diff --git a/project/modules/ROOT/pages/objectives/objective-modularity-f30-f33.adoc b/project/modules/ROOT/pages/objectives/objective-modularity-f30-f33.adoc new file mode 100644 index 0000000..2dc7694 --- /dev/null +++ b/project/modules/ROOT/pages/objectives/objective-modularity-f30-f33.adoc @@ -0,0 +1,62 @@ += Objective: Modularity Stabilization & Improvements + +== Goal + +Modularity has landed in Fedora and we are starting to see gaps in the implementation and the packager experience. +As a result, we have identified a number of projects that will improve the usefulness of Modularity and the experience of creating modules for packagers. + +== Detailed Goals + +At present, the buildroot can not contain content provided by modules + +As a result, the content that may be turned in to modules is limited. +One of the Objective efforts, nicknamed “Ursa Prime,” focuses on supporting modules in the buildroot. + +Many packagers find the effort to create and support modules to be too high. +Despite having a number of tools to support module creators and maintainers, they are not well integrated into the Fedora ecosystem. +There are also gaps in these tools for some use cases. We will focus efforts on improving integration & documentation and addressing gaps in the tooling. + +The Modularity Team has also recieved a number of documentation requests. +Requests have included clarification architecture, modular approaches, and when and how to use tools. +During this objective effort, we would like to address these documentation gaps and solicit new ones as much as possible. + +== Deliverables + +_Items in consideration for deliverables. TBD at Flock 2019: ursa prime; flatpaks; dnf tracker bug(s); 2-3 hackfests; publicity; automatic modulemd creation._ + +Flock 2019 + +* hackfest/workshop to define deliverables for this objective + +F31: + +* TBD + +F32: + +* TBD + +F33: + +* TBD + +== Modularity Team + +This group was established as part of a prior phase of the Modularity Objective, and it will continue. +However, in light of the Council change to the “team” nomenclature, the group is now called the “Modularity Team.” +Nothing else about the group’s operations have changed. + +== Objective Lead + +https://fedoraproject.org/wiki/User:Langdon[Langdon White] + (langdon) + +== Timeframe +We are outlining this Objective to cover the F31 through F33 development cycles as described in the Deliverables above. + +== History +Follows from : + +* https://fedoraproject.org/wiki/Objectives/Fedora_Modularization,_Prototype_Phase[Fedora Modularization, Prototype Phase] +* https://fedoraproject.org/wiki/Objectives/Fedora_Modularization,_Requirements_Phase[Fedora Modularization, Requirements Phase] +* https://fedoraproject.org/wiki/Objectives/Fedora_Modularization_%E2%80%94_The_Release[Fedora Modularization — The Release] From beb5149f23762c1be5ed74573d311111d9788e94 Mon Sep 17 00:00:00 2001 From: langdon Date: Sep 18 2019 14:00:08 +0000 Subject: [PATCH 2/3] now with deliverables! --- diff --git a/project/modules/ROOT/pages/objectives/objective-modularity-f30-f33.adoc b/project/modules/ROOT/pages/objectives/objective-modularity-f30-f33.adoc index 2dc7694..2890194 100644 --- a/project/modules/ROOT/pages/objectives/objective-modularity-f30-f33.adoc +++ b/project/modules/ROOT/pages/objectives/objective-modularity-f30-f33.adoc @@ -2,49 +2,56 @@ == Goal -Modularity has landed in Fedora and we are starting to see gaps in the implementation and the packager experience. +Modularity has landed in Fedora and we are starting to see gaps in the implementation and the packager experience. As a result, we have identified a number of projects that will improve the usefulness of Modularity and the experience of creating modules for packagers. == Detailed Goals At present, the buildroot can not contain content provided by modules -As a result, the content that may be turned in to modules is limited. -One of the Objective efforts, nicknamed “Ursa Prime,” focuses on supporting modules in the buildroot. +As a result, the content that may be turned in to modules is limited. +One of the Objective efforts, nicknamed “Ursa Prime,” focuses on supporting modules in the buildroot. -Many packagers find the effort to create and support modules to be too high. -Despite having a number of tools to support module creators and maintainers, they are not well integrated into the Fedora ecosystem. +Many packagers find the effort to create and support modules to be too high. +Despite having a number of tools to support module creators and maintainers, they are not well integrated into the Fedora ecosystem. There are also gaps in these tools for some use cases. We will focus efforts on improving integration & documentation and addressing gaps in the tooling. -The Modularity Team has also recieved a number of documentation requests. -Requests have included clarification architecture, modular approaches, and when and how to use tools. +The Modularity Team has also recieved a number of documentation requests. +Requests have included clarification architecture, modular approaches, and when and how to use tools. During this objective effort, we would like to address these documentation gaps and solicit new ones as much as possible. == Deliverables -_Items in consideration for deliverables. TBD at Flock 2019: ursa prime; flatpaks; dnf tracker bug(s); 2-3 hackfests; publicity; automatic modulemd creation._ +Fedora 31 Cycle (Ending Oct '19): -Flock 2019 + - Simple local, offline module builds and documentation + - Hackfest at Flock -* hackfest/workshop to define deliverables for this objective +Fedora 32 Cycle (Ending May '20): -F31: +- Module Tagging Service: auto tags builds in to multiple releases of Fedora +- Ursa Prime: Allow the default streams of modules to make their RPMs available in the buildroot +- Rolling Defaults: When a user makes "no choice," they get the default stream on upgrade. +When a user makes a choice, even matching the default stream, they will stay on that stream on upgrade. +- EPEL supports modules +- Hackfest (to be scheduled) -* TBD +Fedora 33 Cycle (Ending Oct '20): -F32: - -* TBD - -F33: - -* TBD +- Support for changing dependencies within a stream +- Support for RPM module header in dnf + - do the right thing on missing modulemd + - modulemd caching +- Only active module streams considered for dependency solving +- Complex local, offline module builds (alternate archs, Fedora versions, etc) +- Module scratch builds +- Hackfest (to be scheduled) == Modularity Team -This group was established as part of a prior phase of the Modularity Objective, and it will continue. -However, in light of the Council change to the “team” nomenclature, the group is now called the “Modularity Team.” -Nothing else about the group’s operations have changed. +This group was established as part of a prior phase of the Modularity Objective, and it will continue. +However, in light of the Council change to the “team” nomenclature, the group is now called the “Modularity Team.” +Nothing else about the group’s operations have changed. == Objective Lead From a96650426dbf6e058a49cd631690ca3effdf6028 Mon Sep 17 00:00:00 2001 From: langdon Date: Sep 18 2019 19:06:32 +0000 Subject: [PATCH 3/3] adds explanation for modularity hackfests --- diff --git a/project/modules/ROOT/pages/objectives/objective-modularity-f30-f33.adoc b/project/modules/ROOT/pages/objectives/objective-modularity-f30-f33.adoc index 2890194..a806658 100644 --- a/project/modules/ROOT/pages/objectives/objective-modularity-f30-f33.adoc +++ b/project/modules/ROOT/pages/objectives/objective-modularity-f30-f33.adoc @@ -31,7 +31,7 @@ Fedora 32 Cycle (Ending May '20): - Module Tagging Service: auto tags builds in to multiple releases of Fedora - Ursa Prime: Allow the default streams of modules to make their RPMs available in the buildroot -- Rolling Defaults: When a user makes "no choice," they get the default stream on upgrade. +- Rolling Defaults: When a user makes "no choice," they get the default stream on upgrade. When a user makes a choice, even matching the default stream, they will stay on that stream on upgrade. - EPEL supports modules - Hackfest (to be scheduled) @@ -47,6 +47,12 @@ Fedora 33 Cycle (Ending Oct '20): - Module scratch builds - Hackfest (to be scheduled) +== Modularity Hackfests + +While somewhat open-ended, the intent of these get togethers is to have 1-2 days to collaborate, in person, with the team. +We also would like to use these events to explicitly elicit feedback from the community. +We plan to follow the model that has been successful in the past with one or two non-core team members joining for the entirety of the hackfest and/or a 2 hour session with a number of non-core team members participating. + == Modularity Team This group was established as part of a prior phase of the Modularity Objective, and it will continue.