# Board F2F at Flock 2024

This is a planning doc for the CentOS Board face-to-face meeting at Flock 2024.

* **When:** Tuesday, August 6, 2024
* **Where:** Hyatt Regency Rochester, in a boardroom

## Attendees

Confirmed:

* Shaun McCance (arrive Aug 5 @ 17:34, depart Aug 11 @ 13:15)
* Pat Riehecky (arrive Aug 4 @13:24, depart Aug 11 @16:45)
* Troy Dawson (arrive Aug 5 @ 11:00am, depart Aug 11 @ 6:50am)
* Amy Marrich (Arrive Aug 5 @ 16:02, depart Aug 11 @ 16:45)
* Davide Cavalca (Arrive Aug 5 @ 18:42, depart Aug 11 @ 10:18am)
* Thomas Oulevey (Arrive Aug 6 @ 08:00, depart Fri 9 ~ 12:00)
* Jeffrey Osier-Mixon (Arrive Aug 5 evening, depart Fri afternoon)
* Mike McLean (arrive Aug 5 @ 14:19, depart Aug 10 @ 10:25am)
* Brian Exelbierd (arrive Aug 5 @ 12:33 am, depart Aug 11 @ 6:16 pm)

Unconfirmed:

* Johnny Hughes

Not attending:

* Josh Boyer (remote as much as possible)

## Topics

* How to prevent miscommunication between maintainers and community(issue [77](https://git.centos.org/centos/board/issue/77) and [78](https://git.centos.org/centos/board/issue/78))
* Conversations have been you should have opened a Jira first but this hasn't been useful in the past. Don't know who maintainer is has been an issue in past.
* Maybe we can reword the Gitlab template to say please open a Jira?
* Possibly include link to Red Hat CVE page that says what versions have what vuln
* A Matrix room with maintainers?
* Template that folks can just and paste into issues thanking them for their effort and exlaination
* We need to create documentation on the process folks should follow when making contributions
* Opportunity to improve maintainer training & support
* SLA in the docs (1 week) and an email alias to send to after SLA
* Where can you make changes - Davide idea package SiG if it gets merged into Stream it gets dropped from the SiG
* What is CentOS Stream and who is our audience for it? And what's it's mission statement.
* Audience?
* People who use RHEL and want to get a preview (How RHEL customers get access to nightly)
* People who use RHEL and affect the current and future versions
* Code - contribute via SiG
* Ideas - that RH could run with
* Contribute to Upstreams
* People who consume CentOS artifacts
* Consumers of source code
* Consumers of the distribution
* Consumers of SIG content
* People who are creating an Operating System based off of the CentOS Stream code
* People who use the direct output from a SiG
* People who like CentOS Stream as a distribution.
* People who build on Stream artifacts in a SIG to produce output adjacent to RHEL (such as RHIVOS, RHOSO, OKD(OpenShift/RHCOS))
* ...and who want to inject hardware support for specific use cases
* Vendor and partners who need a home to discuss implementation and work together to meet the their common use needs and resolve parallel implementations(Telcos, HW vendors, etc)
* Meaningful use case and ability to execute on it
* Bring back to RH that we can't onboard partner how can we get this done
* bex: RH desires to see more partner involvement in the Project - how can we align on this and work together on this
* addressed in the larger section above
* Mission statement for CentOS Stream
* An Enterprise Operating System for developing and establishing Enterprise Linux software tools and workflows for current and next generation computing problems.
* Is this worth having a seperate statement when it is a single part of our project
* Markers for success
* Community members are building cool stuff in our ecosystem
* Users are consuming SIG output
* How does the board feel relative to SIG outputs vs CentOS Stream? We seem to be unconcerned about whether they are successful or have audiences
* CentOS Project
SiGs
Stream Platform/Compose/Release/Baseline - Adam:)
Hyperscale
Cloud
Automative
AltImages
ISA
SiG Contribution process - maintainers, docs
May need to carve out build for Stream release artifacts being different
* Davide: Package++ SiG maybe not be needed?
* Proactive vs Reactive? What policies or procedures can we put in place for the future.
* Packaged talks that we can just give to a person to present at a local event.
* Shaun: How close does the board want to be to Fedora?
* Infra
* All CPE, but we only have Fabian. Occasionally we get someone for a short time
* Cages are separate, chain of custody for secureboot, etc
* New build platforms coming - service?
* Mirrors, mailing lists
* What are Red Hat's plans?
* Matrix?
* Badges
* SiG governance
* Event Costs
* Connect is for folks in the larger space - outward focus
* Flock is for Fedorans - inward focus
* Hard for companies to sponsor events - contracts
* Engineers can only go to one event
* Story from development to the world (inward to outward)
* 3 separate brands
* gitforge
* We (CentOS) are currently using 3 gitforges (pagure, git.centos, gitlab)
* Proposal: when Fedora finally chooses something, consolodate on that.
* Verify our stuff works first. Get into the converstation with our needs.
* Find out what our stuff currently needs.
* CI system?
* [add topic ideas here]

## Schedule

Monday, August 5

* Dinner at 7:30, Pane Vino on the river: https://panevinoriver.com/
* Leave Hyatt lobby at 7:15 if you want to walk with the group
* Reservation for 8: Troy, Amy, Mike, Brian, Shaun, Davide, Jeffro, Adam
* Arrive a bit late: Shaun (17:34), Davide (18:42)

Tuesday, August 6

* [breakfast together before starting?]
* 9:00 - Start in the boardroom
*
* [let's make lunch plans]
*
* 5:00 - End
* [sponsor dinner is Tue evening]

Wednesday, August 7

* Flock Conference
* Dinner: Flock ends at 6:00. Game night and candy swap start at 6:30. Earliest we could leave is 5:30 because of Michel's talk. Play it by ear and try to grab group dinner at either hotel restaurant or Drifters next door.

Thursday, August 8

* Flock Conference
* Flock party at Strong Museum of Play

Friday, August 9

* Flock Conference
* Doc Day Working Session in AM
* EPEL hackfest in PM

Saturday, August 10

* Flock conference, just mentor summit track. Shaun will work on board/promo/web/docs/whatever stuff. Join if you like.

Sunday, August 11

* Niagra Falls pay your way outing
* Some people leaving late Sunday and doing a Rochester day.

______________
Good for the board to have missions and goals as long as we don't go after RHEL and don't ask for money.

Hoped to see more innovation coming from the project. Knows Stream is in a difficult position.
1M downloads from the mirrors (Troy)

Alma in competition for talent and new work

Adam will take lead on filtering through any Jiras opened and help to get them to the right person

Work on maintaining attribution