Here is the summary of the CLT meeting held on Jan 25th 2023:
- Following up on the recent issues with the LRC, there is a desire to
standardize the ops processes, clarify responsibilities and
escalations now that there is no longer a single person responsible
for the infrastructure. One idea is to add health alerts to the Slack
#sepia channel, which David Orman volunteered to look into. It was
also suggested to set up a weekly infra call to organize and
eventually scrub the tracker Sepia issues weekly. Not finding a good
time for this meeting, it was agreed to use the first 30mins of the
CLT weekly for the time being.
- Dev / Community chat seems to be centralizing on Slack, which looks
popular but has a couple issues. First there was a limitation on
allowed domains. Mike has cleared this and anyone should be able to
register now. There is also work ongoing to bridge between Slack and
IRC. (In an informal poll of the CLT, 13 responded that they will use
Slack directly, and 2 will continue using IRC).
- Next there was a discussion about the status of the upcoming Reef
release. Josh asked that leads please update the ceph-backlog trello.
Next it was discussed if the release timing should be delayed to
account for the build and test infrastructure issues these past
months. All leads chimed in, and it was agreed that the freeze will be
moved back to the end of February, with the new target release date
being end of June. The team will still target an RC to be available
for Cephalocon mid-April.
is often overloaded -- Adam will check the confirm
wrt. rate limits or throttles.
- There is a significant backlog in the ML moderation queues. (And
also in the tracker account signup queue, which Ilya and Adam
discussed how to clear). It was noted that the ML moderation is
currently manual, via the web UI -- it would be appreciated if anyone
knows how to enable moderation by email or some other automation.
- Mike announced that ceph-devel is now archived to MARC at
-- It was asked if MARC
allows importing historical mails, which e.g. could be bundled into an
mbox and uploaded somewhere. Mike will inquire.
- Lastly, major kudos to everyone that pacific 16.2.11 was in the
process of being published! Some user confusion re: the publishing
process was discussed (e.g. currently packages trickle into the repos
prior to release notes being merged or published). It was proposed
that going forward the notes+announcement would come out before the
repos would be updated.