Ceph Steering Committee Meeting
9 March 2026
* [Ernesto/AnthonyM]: Github Plan migration to Enterprise Account.
- Upgrading Github to enterprise is generally pretty straightforward
- The main issue is permissions with github actions
- Benjamin Sternthal from the LF can help audit and get things ready.
- The main issue is default permissions and needing to update actions
to specify them.
- [Ilya] We don't have all that many actions, so some temporary
breakage probably wouldn't be the end of the world.
- [Benjamin Sternthal] Probably the best thing to do is pick a time
and work back from there.
- The banner from Github suggests it's going to happen automatically
eventually, and it's better if we do it on our timeline.
- LF Requested the upgrade about a week ago, it usually comes in two
weeks, so it should be soon.
- #github-enterprise-upgrade is open for anyone wanting to be involved.
* [Anthony Middleton] CSC Election
https://docs.google.com/document/d/12zmuG6qVWU33dlcR4aXkCG2z4MdAGT8A3F36ofnfHUQ/edit?usp=sharing
- Continuing from previous conversations, this is a planning document
for how the election could go.
- Lots of questions about voting.
- There seems to be a consensus about having up to three co-chairs. If
we want to have a vote about that, Anthony's happy and Benjamin
Sternthal says there's no LF objection.
- This election is happening now because we didn't have an election on
2025, so there will be another election later this year as well.
- We could have an election about leadership now, and handle other
matters around October/November.
- Do we need to move forward with the leadership? Or is there more
that needs done soon?
- [Greg] We need to clean up our rolls. Anthony has a list of who
voted in the 2024/2025 elections.
- We can make a list of people who didn't vote in the last two
elections and vote about removing them.
- [Benjamin Sternthal] Now would be a good time to think about how to
run things, conduct votes, etc.
- [Dan van der Ster] We could do concrete procedural changes in pull
requests, put our procedural documents on github, so we can iterate
and vote on them. That's how we did it in the past with our
governance rules.
- [Matt V] ARIN/RIPE revokes voting for orgs that haven't voted in two
years, which sounds similar.
- Mark Nelson and Anthony will work on a draft. We've talked about
auto-expiration, an annual event where people have to affirm their
voting status (but there were concerns the note might be missed), or
we vote every year on pruning our rolls.
- [Ilya] We have to vote once a year to rotate council members. We
could have whoever's organizing that vote propose removal of
inactive members (based on some rules) as part of the same ballot. If we
have to vote every year anyway, then doing it then will go much more
smoothly.
- [Dan van der Ster] This is how we did it last time, we just didn't
have a specific procedure for determining inactive members.
- [Anthony Middleton] Who will represent the CSC to the quarterly
meeting of the Ceph Governing Board at the LF? That could be one of
the leadership people or any member of the CSC.
- [Dan van der Ster] The CEC can decide among themselves who will be
the voting representative/single point of contact.
- [Benjamin Sternthal] There's a Voting Representative and this
organization decides who it is. The whole CSC is invited to the
quarterly meetings with the Governing Board.
- [Anthony Middleton] So the vote will be about leadership and the
removal process for inactive members. Then there will be another
election in October or November.
* [Mark] Do we have a policy on which QA runs should pass before PRs are merged?
continue discussion from last meeting.
- Mark remembered Ilya saying there was a policy somewhere.
- Ilya qualified that he was saying the general consensus, not a
policy. Components scheduling test runs, with merges happening only
after test runs are finished and reviewed.
- The point was that you can do your own run, but it should be a
coordinated process where the relevant component team reviews the
results, since not everyone is up to speed on all of the ongoing
issues.
- [Mark] We know what the expectaiton from the leads is, but don't have
anything written down.
- [Greg] Someone should just write something up and put up a PR
- [Laura Flores] It should probably be component-by-component.
Component leads should write down their own process.
- Adam E will get it started and the component leads can fill it in.
* [Radoslaw] Conclusion on "Should the `reef` branch be opened for merging"
question.
- Moving to next week since Patrick isn't here
* [Anthony Middleton] CSC and Ceph Governing Board Q1 meeting, Monday March
30th 1 pm EDT
- [Greg] The agenda looks very long and that is not a one hour meeting
- Anthony Middleton will edit the agenda, moderate the call, etc.
- This meeting will be led by the governing board this quarter, next
quarter the CSC will be.
* [Patrick] Shall we archive ceph/ceph-deploy and other vestiges?
- Bumped to next week since Patrick isn't here.
* [Yaarit] Rocky 10 update
- We are working on merging the patches for having Rock 10 in main and
the Python 3.12 changes.
- Shortly after, we would like to change the base image to be Rocky 10
instead of CentOS 9.
- Will have a separate discussion with David G, but wants to ask all
the component leads to review and fix the test branches.
- We saw an unreasonable amount of failures last week, and we're
currently looking into that.
- Once everything looks green, we hope to be able to merge the changes.
- There are pending issues for CephFS and RBD as well.
_______________________________________________
ceph-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
