Donate auger to sig-etcd

[jmhbnz]

The auger utility was discussed at the recent sig-etcd meeting, recording (https://youtu.be/M4r6aM45zEk?t=61).

It was proposed the auger utility be adopted by sig-etcd given it is a useful utility that is regularly used by the community[1][2] and specifically the kubernetes etcd user community.

Historically in #30 it was proposed that sig-instrumentation take over ownership for auger however that was prior to sig-etcd existing and sig-etcd is the more natural fit moving forward.

During the sig-etcd meeting both co chairs (@jmhbnz, @wenjiaswe) expressed support, +1s noted in meeting doc.

This issue is intended to confirm repo owner (@jpbetz), sig tech lead (@ahrtr, @serathius) and wider community consensus to proceed and then track work required.

---

There is some administrivia that needs to be sorted out before the project can be donated:

• All contributors must have signed the CNCF CLA. This was confirmed in Donate auger to sig-instrumentation #30.
• Project must have an acceptable licence - Apache 2.0 is fine.
• We need an official sig-etcd owner - @siyuanfoundation, @jmhbnz
• Additions of the standard Kubernetes header to code created by the contributors can occur post-transfer, but should ideally occur shortly thereafter.
• Repo should contain template files as per the kubernetes-template-project.

cc @logicalhan

[wenjiaswe]

cc @siyuanfoundation who is interested in being a maintainer of auger

[serathius]

LGTM

[jpbetz]

Thank you all for doing this!

[ahrtr]

This is really a nice tool. I am supportive on this.

If we decide to add it into etcd-io, then it means we will spend more resources and effort on it. I just had a quick read through this repo, it needs some expertise on etcd, bbolt and apimachinery. It would be great if existing contributors (CCed below) are still interested in maintain & contributing to this tool after the migration (into etcd-io).

• @jpbetz
• @hongchaodeng
• @wenjiaswe
• @jingyih
• @cheftako
• @caesarxuchao
• @Quentin-M
• @vasrem

Note: adding it into the list of tools is another option, if nobody in the existing contributors is willing to contributing to the tool anymore.

[wenjiaswe]

Thanks @ahrtr. @jmhbnz @siyuanfoundation volunteered to be the maintainer of Auger, and I myself am willing to help as well.

[liangyuanpeng]

It looks like the checklist has been completed here!

[haiwu]

What's the next step? Will there be a new release tag? (since 2019)

[jmhbnz]

To the best of my knowledge every pre-requisite for the transfer to occur is now met, we just need to carry out the actual transfer.

@ahrtr, @serathius normally projects like this would transfer to kubernetes-sigs github org. But given sig-etcd has the etcd-io org I think it makes sense to transfer there to keep all our etcd repos together as much as possible. Do you agree?

[ahrtr]

I think it makes sense to transfer there to keep all our etcd repos together as much as possible. Do you agree?

Either adding it into etcd-io as a new repo or adding it into the list of tools works for me. It seems most people prefer to the former (adding it as a new repo under etcd-io), so let me create a new repo add add you as an admin.

[ahrtr]

so let me create a new repo add add you as an admin.

I am not an owner of the org anymore. Please ping the owner to create the repo for you. @jmhbnz

[jmhbnz]

Confirming the migration has been completed, https://github.com/etcd-io/auger is now live 🎉

With the new repo in place we need to either delete this one or mark it public archive with a clear update in the README.md to point to the new repository.

I'm happy with either option, let us know how you would prefer to approach it @jpbetz?