Red Hat's Community Platform Engineering Team¹ works on Fedora infrastructure and release engineering as part of Red Hat's overall Linux organization, which runs on a quarterly planning process. Q4 planning is coming up in early September, and CPE leadership has asked for "insights" from the Fedora community as an input into that process.
Obviously a lot of that team works directly in Fedora on a day-to-day basis, so this isn't meant to be a low-level work request detail. The request is for a high-level overview of what we as a project care about from RH's contribututions to the project via this team for October, November, and December.
This is the start of what I expect will be a new routine — we'll do this again in late November for Q1 2021² and so on. But for now the focus is on Q4. With the datacenter move wrapping up, the auth system replacement hopefully by then successful, etc., what is now most important and most urgent?
1. https://docs.fedoraproject.org/en-US/cpe/ 2. Red Hat is now on calendar-year-aligned quarters!
As a follow-on, here are the initial docs[1] for how we're going to use the Infrastructure Priorities board[2].
[1] https://docs.fedoraproject.org/en-US/council/procedures/infra_priorities_boa... [2] https://teams.fedoraproject.org/project/fedora-council-infrastructure-priori...
On Fri, Aug 21, 2020 at 11:00:36AM -0400, Matthew Miller wrote:
hopefully by then successful, etc., what is now most important and most urgent?
I was hoping someone else would start, but I'll go. :)
1. Finish up the FAS migration, get everything across the project functional with new system.
2. Search for docs.fedoraproject.org
3. Image builder in composes (leading to image builder distinct from main compose for spins)
4. Updated Fedora notifications system
On Tue, Sep 1, 2020 at 10:22 AM Matthew Miller mattdm@fedoraproject.org wrote:
I was hoping someone else would start, but I'll go. :)
Strategic silence wins again!
Finish up the FAS migration, get everything across the project functional with new system.
Search for docs.fedoraproject.org
Image builder in composes (leading to image builder distinct from main compose for spins)
Updated Fedora notifications system
I'd flip 3 and 4. I actually want 3 more but putting 4 above it can enable a lot of other work by CPE and others.
To kick more conversations around this lets try and give more context on all items par number 1, which is in flight and on track, for people who might not have awareness. Have we some links to proposals or conversations. My default question would be 'what does success look like here' for both of these!
On Tue, Sep 1, 2020 at 3:22 PM Matthew Miller mattdm@fedoraproject.org wrote:
On Fri, Aug 21, 2020 at 11:00:36AM -0400, Matthew Miller wrote:
hopefully by then successful, etc., what is now most important and most urgent?
I was hoping someone else would start, but I'll go. :)
Finish up the FAS migration, get everything across the project functional with new system.
Search for docs.fedoraproject.org
Image builder in composes (leading to image builder distinct from main compose for spins)
- Updated Fedora notifications system
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ council-discuss mailing list -- council-discuss@lists.fedoraproject.org To unsubscribe send an email to council-discuss-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedorapr...
On Tue, Sep 1, 2020 at 3:22 PM Matthew Miller mattdm@fedoraproject.org wrote:
On Fri, Aug 21, 2020 at 11:00:36AM -0400, Matthew Miller wrote:
hopefully by then successful, etc., what is now most important and most urgent?
I was hoping someone else would start, but I'll go. :)
Finish up the FAS migration, get everything across the project functional with new system.
Search for docs.fedoraproject.org
Image builder in composes (leading to image builder distinct from main compose for spins)
Updated Fedora notifications system
Finnish the container build pipeline (or what ever it's currently called) for aarch64 to enable container/flatpak builds for aarch64.
On Wed, Sep 2, 2020, 16:46 Peter Robinson pbrobinson@gmail.com wrote:
On Tue, Sep 1, 2020 at 3:22 PM Matthew Miller mattdm@fedoraproject.org wrote:
On Fri, Aug 21, 2020 at 11:00:36AM -0400, Matthew Miller wrote:
hopefully by then successful, etc., what is now most important and most urgent?
I was hoping someone else would start, but I'll go. :)
Finish up the FAS migration, get everything across the project functional with new system.
Search for docs.fedoraproject.org
Image builder in composes (leading to image builder distinct from main compose for spins)
Updated Fedora notifications system
Finnish the container build pipeline (or what ever it's currently called) for aarch64 to enable container/flatpak builds for aarch64.
The good news is this was deployed in staging. The bad news is we had a colo move and this would need to be redeployed in staging and ultimately production. Its a non trivial amount of work but at least we have knowledge of it. I will get amoloney to include it in our briefs.
council-discuss mailing list -- council-discuss@lists.fedoraproject.org To unsubscribe send an email to council-discuss-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedorapr...
Hi,
On Tue, Sep 1, 2020 at 4:22 PM Matthew Miller mattdm@fedoraproject.org wrote:
On Fri, Aug 21, 2020 at 11:00:36AM -0400, Matthew Miller wrote:
hopefully by then successful, etc., what is now most important and most urgent?
I was hoping someone else would start, but I'll go. :)
I've added mine to the taiga board.
One I'd like to highlight is the Community Openshift instance https://teams.fedoraproject.org/project/fedora-council-infrastructure-priori...
It didn't survive the datacenter move, but it is a key project for Fedora if we want to decentralize the infrastructure and let community maintainers and not just CPE to work on services for Fedora.
The other is transparency for infra resources which we use https://teams.fedoraproject.org/project/fedora-council-infrastructure-priori...
The argument like "we can not do X because we don't have resources for it" appears often, but currently we don't have data to make any meaningful decisions here. For example: how much does it "cost" for Fedora to enable ELN builds? How much resources COPR takes? What is the impact of flatpacks? How much it takes to add testing for new architecture? We need to be able to measure these things so we can plan and negotiate better.
- Finish up the FAS migration, get everything across the project functional with new system.
+1 This is the key service for the Infra.
- Search for docs.fedoraproject.org
I am not sure it needs to be a CPE priority. This is one those self-contained tasks which basically anyone from community can do, with a bit of a guidance. So i'd rather see it as a project for Outreachy or whatever entry point projects we have for
- Image builder in composes (leading to image builder distinct from main compose for spins)
+1
- Updated Fedora notifications system
I think we need a better description what does it mean "updated" . What are the expectations and acceptance criteria?
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ council-discuss mailing list -- council-discuss@lists.fedoraproject.org To unsubscribe send an email to council-discuss-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedorapr...
-- Aleksandra Fedorova bookwar
On Thu, Sep 03, 2020 at 11:01:21AM +0200, Aleksandra Fedorova wrote:
I've added mine to the taiga board.
One I'd like to highlight is the Community Openshift instance https://teams.fedoraproject.org/project/fedora-council-infrastructure-priori...
It didn't survive the datacenter move, but it is a key project for Fedora if we want to decentralize the infrastructure and let community maintainers and not just CPE to work on services for Fedora.
See the status update email to devel-announce.
The other is transparency for infra resources which we use https://teams.fedoraproject.org/project/fedora-council-infrastructure-priori...
The argument like "we can not do X because we don't have resources for it" appears often, but currently we don't have data to make any meaningful decisions here. For example: how much does it "cost" for Fedora to enable ELN builds? How much resources COPR takes? What is the impact of flatpacks? How much it takes to add testing for new architecture? We need to be able to measure these things so we can plan and negotiate better.
I don't disagree, but I don't think it's just that we are lazy and don't calculate this, I think estimating things is really hard.
How would you estimate ELN builds? There's disk space, there's cpu cycles (but some of that would have just been idle?) There's composes disk space and cpu... some amount of BW I guess. But with just "ELN will have a subset of packages of rawhide, we aren't sure yet which" how are we supposed to estimate it?
Note that we have a initiative on the board for metrics... this I think would be the first step for this. See what we are using at X and then again at Y after something lands, or at least give us more information.
...snip...
- Image builder in composes (leading to image builder distinct from main compose for spins)
+1
IMHO this needs more widespread discussion and agreement on a plan before we should work on it. This changes lots of fundamental things (release cycle) that lots of teams (qa, releng, infra, websites, fesco, docs) use. It's going to rearrange how almost all of the project works.
- Updated Fedora notifications system
I think we need a better description what does it mean "updated" . What are the expectations and acceptance criteria?
The current Fedora Notifications System (FMN), is running on an EOL version of Fedora. It's python2. It only knows fedmsg, not fedora-messaging. It takes hours to restart. So, basically this is rewriting it to be maintainable and make the interface easier to use.
kevin
council-discuss@lists.fedoraproject.org
-
Aleksandra Fedorova -
Ben Cotton -
Kevin Fenzi -
Leigh Griffin -
Matthew Miller -
Peter Robinson