Closed wenjiaswe closed 2 months ago
Here is our list of all repos for reference:
Archive - Don't add OWNERS:
etcd-io/etcd-play
- Already public archiveetcd-io/cetcd
https://github.com/etcd-io/cetcd/issues/5etcd-io/maintainers
https://github.com/etcd-io/maintainers/issues/19etcd-io/zetcd
https://github.com/etcd-io/zetcd/issues/124etcd-io/dbtester
https://github.com/etcd-io/dbtester/issues/367OWNERS file completed
etcd-io/raft
https://github.com/etcd-io/raft/pull/102etcd-io/gofail
https://github.com/etcd-io/gofail/pull/56etcd-io/discovery.etcd.io
https://github.com/etcd-io/discovery.etcd.io/pull/77etcd-io/bbolt
- https://github.com/etcd-io/bbolt/pull/569etcd-io/jetcd
https://github.com/etcd-io/jetcd/pull/1230etcd-io/etcd
- https://github.com/etcd-io/etcd/pull/16600etcd-io/website
https://github.com/etcd-io/website/pull/725etcd-io/protodoc
https://github.com/etcd-io/protodoc/pull/12etcd-io/discoveryserver
https://github.com/etcd-io/discoveryserver/pull/7etcd-io/etcdlabs
https://github.com/etcd-io/etcdlabs/pull/291etcd-io/govanityurls
https://github.com/etcd-io/govanityurls/pull/2Hey Team - I've confirmed with @mrbobbytables that repositories marked as public archive do not need to be included in this work of seeding initial OWNERS
files.
With that in mind I would like to propose @etcd-io/maintainers-etcd mark the etcd-io/maintainers
, etcd-io/zetcd
and etcd-io/cetd
repositories as public archive as they are no longer maintained.
Based on my list above that would then leave us 12 pr's to raise. I have made a start on the first one to get us moving: https://github.com/etcd-io/etcd/pull/16600
Update: All required OWNERS
files have now been merged. There were four repositories proposed for public archival, 3/4 have been completed, the other one is in progress pending maintainer majority approval.
We have an active pr in progress on the kubernetes/org repo to implement automated management for the etcd-io org: https://github.com/kubernetes/org/pull/4498.
Once that is merged we should cleanup to ensure:
1 - Any process documentation about repository access management is updated
2 - Remove the now defunct / duplicate MAINTAINERS
files.
The following repositories will need a cleanup pr to at minimum remove old MAINTAINERS
file:
All etcd-io subprojects now have a top level OWNERS
file where required and followup action to tidy up old MAINTAINERS
files has also been completed, closing.
As a next step we should begin exploring more fine grained code ownership for specific aspects of etcd-io/etcd
but that can be addressed in subsequent issues.
Reopen to backport OWNERS
to release-3.5
and release-3.4
in support of improved automation via prow.
Discussed during sig-etcd triage meeting, assigned to @thedtripp for backport https://github.com/etcd-io/etcd/pull/16794 to release-3.5
and release-3.4
.
/assign @thedtripp
@jmhbnz: GitHub didn't allow me to assign the following users: thedtripp.
Note that only etcd-io members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
/assign @thedtripp
@thedtripp: GitHub didn't allow me to assign the following users: thrdtripp.
Note that only etcd-io members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
/assign @thedtripp
Hey @thedtripp - Now that we have release-3.5
completed do you have capacity to also tackle the backport release-3.4
so we can close this out? 🙏🏻
Hey @jmhbnz, yes, I will work on this over the next few days.
Backports completed - closing 🎉
What would you like to be added?
Add a top level OWNERS file to top each etcd.io subproject.
Why is this needed?
It's a hard requirement to set up sig-etcd: https://github.com/kubernetes/community/pull/7372#discussion_r1282462443.