# Weekly CentOS sync topics

## Next Meeting
- (bex) pre-read on centos board announcement

## 20230306
(bex) Board Meeting Prep:
1. There is a long standing issue about getting Secure Boot working for CentOS SIGs. It'd be great to have something concrete.

2. There is work going on with MSFT to get CentOS outputs into the Azure Community Marketplace. Brian is driving this afaik. It'd be great to know if we can get any kind of an update that isn't too commital - but is useful.

3. There is supposed to be a presentation about SCOS (CentOS Stream CoreOS) at the meeting. Behind the scenes and not public knowledge yet is that their build cluster is going to be shut down soon. They are apparently talking to Fabian about moving their builds for SCOS to the CentOS infra. I'd like that information to become public (the move not hte why). I think the board will want to hear that and it will cut of a round of rabbit-hole conversations. Additionally, I'd like to understand what it would take to move the entire OKD build stuff into CentOS as a SIG or part of hte cloud SIG. It feels like getting this wrapped up in here would be a win and prove value of truly going above hte OS.

## 23 November 2022

(bex) move to every two weeks and/or 30 minutes and add Adam Samalik
(am) cancelling Nov. 21st call & adding Adam Samalik in from Monday 28th Nov. Also decreasing the frequency to every 2nd weel & 30 mins
(bex) should Adam be attending the CentOS Board meetings to provide infra details?
[am] Adam is welcome to attend board meetings but Infra SIG will provide infra-related details for Stream (Brian/Aoife - but most likely Brian)

## 23 Aug 2022

(bstinson) They've been looking at the RHEL 10 Bootstrap timelines. Given dependencies and other issues, CentOS Stream 10 will need to be instatiated much earlier than the past. Likely 2023Q3 (November) - normally we would have expected this to happen in 2024Q1 based on CentOS Stream 9.

CentOS Stream 8 sunsets in May 2024

## 18 July 2022
- Can we talk about the kmod SIG and level set what they are getting done relative to the older way kmods were done in CentOS Linux. I feel like I lost the thread (this can also be an email)

### 06 Jun 2022

- CentOS Stream EOL Decision (effective 8.10 and beyond in 2024)
- Commits to c8s branches in gitlab.com: Allowed
- Builds in koji: Allowed
- Outside MRs: May be **This needs to be clarified for both today and post 8.10 so people have the correct expectations
- Composes: Discontinued
- Mirror: Discontinued (archived to vault)
- [ ] Clarify dates and timing
- [ ]

### 28 Mar 2022
- There was some question about the EOL of CentOS Stream 8. Did that get resolved?
- Mirrors

### 21 Feb 2022
- Discussion on community optics for the proposal that the Kernel ABI would only be 'stable' within a Y-stream/minor release, not across them
- https://docs.google.com/presentation/d/177x-b3sGuwUckw4gtEZJQEIY4Z7B2rQqf-I-Xqe5Dc0/edit#slide=id.g3d946fe0a1_0_0
-

### 24th Jan 2022
- Welcome new ~~hostage~~ members Shaun + Josh!
- Pod item: Bex unavailable so will move to next meeting
- Update on Homework Assignment: How would an external person go about finding out more about CentOS Stream? What are the forums we want Stream updates/new 'stuff' published to?
* Currently RSS feeds for c8s + c9s are published here by 3rd party https://centos.passthejoe.net/
* Possibility to cross link developer portal blog with CentOS Stream development or updates, etc https://developers.redhat.com/topics/linux/all
* (Brian) ACTION: Shortlist of maintainers who would be willing to write a blog on some work they have done/are doing for CentOS Stream
* There are marketing materials available on RHEL offerings, inc Stream, that could be used for further comms out to lists, ie ping POs PMs to ask for some talking points on the material in existance already
* ACTION: Find those appropriate people/groups and review and 'borrow' their material (its in RHEL BU jira)
* RHEL Program mgmt meets twice per year to look at marketing features that are RHEL specific but it could be a good slot to find ones that are 'fair game' for community/public consumption
* How can IRC channels be used better? With the availablility of Matrix this could be a more user friendly way to engage with people
* IDEA: Ask people in the CentOS Stream gchat channel if a conversation could be moved to IRC/upstream
- **ACTIONS:**
* (Shaun) Email blast to RHEL maintainers (rhel devel list) with reminders that Stream jira board is open, IRC chats can be bridged with matrix, <other things here>
* (Josh + Brian + Shaun) Promote community engagement at a Linux Extended Staff call, and possibly other similar venues

* (All For next week) How can we rejuinate the Feature Stream SIG? What would get people excited to see in Stream and to get people involved and engaged in CentOS Stream?

### 17th Jan 2022
- No Meeting

### 10 Jan 2022
- Status of Stream Pod
- Still in progress and remit is still being defined
- AOB - What does AOB mean? (Any Other Business)
- Transparency for CentOS Stream increased - how?
- Potential to help RHEL maintainers to move to a central/canon platform to discuss work. This may be a 6-month min effort
- **Homework** How would an external person go about finding out more about CentOS Stream? Pick two places you would think to check. Eg would you check/know to check the IDM system to see what updates are there/coming up? Is there a better place to check than git? Can we translate a feature roadmap to a more technical, or working roadmap for people consuming CentOS Stream OS? Would we get away with calling something 'Upate Notes' that would contain what has been updated, versions, etc? We (I think) want a 'call to action' type email announcement to the devel-list when CentOS Stream gets a particular feature or function or something good and useful to community members/consumers that notifys them its not only available to use, but we want them to test them, consume them and contribute back.
- How can we welcome RH maintainers to 'the community' as recognition of the work they do in and for the project to make it more perecivable as an even playing field for everyone
- We need one canon platform for everyone to write about new and good things landing/happening in Stream that is agnostic from where they are contributing from (ie not just RH)
- Candidates:
- [e-mail] and cc rhel-devel list
- blog.centos.org for any bigger announcements
- How do we get threads over to the centos one?
- We contact the publisher privately or we contact the people who are over reading lists to see if they can promote this comms

## 6 December 2021
### New Topics
- [am] Q1 planning: what are your requests for CentOS Stream Eng to work on?
- bex: In case I am late, EPEL efforts (ongoing), ImageBuilder (for personal not RH reasons :D), SIG Kernel "signing" and kernel drivers
- [am] Image builder can be done by Stream Eng
- Being worked on in Q1 for integration in Fedora infra so this can be investigated and worked on by Stream also in new year
- [am] SIG Kernel signing + kernel drivers work, if approved, to be triaged to Infra SIG
- [am] EPEL efforts can be triaged to EPEL side of CPE
- this relates purely to edge cases of EPEL next for EUS that the BU may need to find funding for. most of these cases are potentially bugs for RHEL and could be worked through engineering, so this is a 'just in case' this happens we have an idea on how to handle it
- [am] should we work on c8s -> c9s upgrade?
- [bs] no as traditionally this was work that was taken up through community members. tooling is available and open to external people to consume
- [am] Possible dc move for CentOS infra in 2022 so this may slow/stop development efforts while the move is underway
### Outstanding Actions
- [Bex] Role breakdown of/for pod members
- bex: still incomplete

## 8 November 2021
- How about that pod?
- We've skipped a lot of these meetings, should we do better about that?

## 11 October 2021

* Discussion of Infra SIG and people helping versus ideas being discussed
* Onboarding the CentOS Stream PM (and update by bex)
* Who are the CentOS Stream user personas/those who can define our success?
* Notes from today re:success
* What is the Success Factor for Stream
* -> RH Perspective
* -> CentOS Board
* -> Community
* We are using this criteria for decision tree processes
* It shows good community sentiment and keeps them in the loop
* There is an independent definition of success because this means that there is an active community and it shows a desire to keep them engaged and developing
* *RH would like to have guardrails, and the community wants to know why they are there and what they are

## 30 August 2021

* Upcoming bug squash event - https://hackmd.io/5iuWQJUmQAKPhfMtko34zw (bstinson heading this up. rbowen doing publicity, scheduling)
* Docs SIG - Karsten, Shaun want to start something more formal.
* Hyperkitty for CentOS lists - proving to be much more complicated (both technically and socially) than I anticipated
* Overlap with work that Alain was already doing on site themes
* Dependency hell in both Fedora and CentOS make this a lot more complicated than just deploying a service
* (AM) CPE ARC team investigating x3 solutions, at the end of ARC investigation there should be a clear path forward. Review call to be set by mobrien (team lead) for stakeholder attendance - Rich, Aoife, Bex
* (bex) RHEL access for Fedora/CentOS
* (bex) TLS mirror lists and gpgcheck=1
* (bstinson)Mirrormanager, dnf countme, and mitigating the gpgcheck thing^
* (bex) Open: Communicating to the community
* Twitter topics:
* Timeliness, and transparency (ie, errata!), of updates
* Community "permission" to provide additional data around the update stream
* https://twitter.com/Det_Conan_Kudo/status/1430539037769703426
* Scott Williams/Steven Rosenberg are useful canaries, and we should take their complaints seriously, even if we cannot promise them "fixes"
* September newsletter draft - https://hackmd.io/3apS467QQGityMOwC9DWUw - does CPE/Infra have anything to give advance notice of?

###### tags: `centos`