Hello,
Topics discussed:
- a noticeable backlog of "make check" jobs and shaman builds
(>6 hours)
- mostly self-inflicted because folks have been retriggering "make
check" a lot recently in the hopes of working around a number of
transient failures
- even more so if the pool of jenkins workers used for "make check"
and shaman builds is the same
- Laura will confirm in the infra meeting
- Patrick will downgrade github org owners that aren't active to
regular members
- proposal to prune down the list of individuals with write access to
ceph.git repo (Patrick)
- component leads and long-time senior contributors only
- the goal is to enforce our SubmittingPatches.rst rules better
- also some additional security
- concerns over fractured issue tracking
- the most recent example is ceph-nvmeof using github issues, but
there is also nvmeof subproject on tracker.ceph.com
- other notable examples are ceph-csi and go-ceph, although there
hasn't been anything on tracker.ceph.com for these
- conclusion: github issues or any other issue tracking system is
fine as long as there is no tight coupling to ceph.git
- question: does a repo being brought in as a submodule as is the
case with ceph-nvmeof in https://github.com/ceph/ceph/pull/54671
constitute tight coupling?
- in this case the submodule is intended to bring in two .proto
files for use by NVMeofGwMonitorClient daemon, everything else in
ceph-nvmeof repo shouldn't be looked at
- is this the best way to do that -- could these files just be
copied?
- dashboard already carries a copy of one of them
(src/pybind/mgr/dashboard/services/proto/gateway.proto)
- creating a pypy package is another option
- QA nightlies
- now that they are back, need to ensure they are looked at!
- poll among component leads: is status quo where all results go to
ceph-qa list OK or do we need to have teuthology email people/teams
directly?
- let's tally up next week
Topics moved to next week:
- 19.1.0 status
- trello to limit free workspaces to 10 collaborators
- need a replacement for Yuri's board at the very least
Thanks,
Ilya
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
