Move etcd to github.com/etcd-io/etcd*

[gyuho]

We are moving etcd and other sub-projects to its own GitHub organization.

The new org will be https://github.com/etcd-io.

Many popular Go projects have done this, for better project management:

• Move protobuf to its own github organization. protocolbuffers/protobuf#4796
• Move kubernetes to github.com/kubernetes/kubernetes kubernetes/kubernetes#12211, Use Go canonical import paths kubernetes/kubernetes#29014
• Move Go import path redirect to vitessio/vitess. vitessio/vitess#3702, Mass-replace youtube/vitess -> vitessio/vitess. vitessio/vitess#3725

Some of our motivations are:

• Better team management.
• Better CI resource utilization; currently, etcd relies on free-tier public CI service, and sharing all resources with other github.com/coreos projects slows down development process.
• More visibilities to sub-projects and adopt more community projects under etcd organization.

Move github.com/coreos/etcd and github.com/coreos/bbolt:

• Decide which namespace we will be using (1 ~ 2 weeks)
• Announce to etcd and Kubernetes communities (Mon, August 6, 2018)
• Update all internal github.com/coreos/etcd import paths in all branches (5PM PST, Mon, August 27, 2018)
• Disable CI integration with current org (5PM PST, Mon, August 27, 2018)
• Transfer ownership (5PM PST, Mon, August 27, 2018)
• Set up new CIs (5PM PST, Mon, August 27, 2018)
  • Add environmental variable ETCD_ELECTION_TIMEOUT_TICKS=600
• Make sure old URL redirects to new URL (5PM PST, Mon, August 27, 2018)
• Set up vanity import paths to go.etcd.io/$proj

Sub-projects that do not have downstream projects can be transferred right away:

• https://github.com/coreos/cetcd (9PM PST, Tue, August 7, 2018)
• https://github.com/coreos/zetcd (9PM PST, Tue, August 7, 2018)
• https://github.com/coreos/gofail (9PM PST, Tue, August 7, 2018)
• https://github.com/coreos/dbtester (Mon, August 6, 2018)
• https://github.com/coreos/etcdlabs (Mon, August 6, 2018)
• https://github.com/coreos/etcd-play (Mon, August 6, 2018)
• https://github.com/coreos/protodoc (Mon, August 6, 2018)
• https://github.com/coreos/jetcd (9PM PST, Tue, August 7, 2018)

Projects that won't be moved:

• https://github.com/coreos/etcd-operator
• https://github.com/coreos/discovery.etcd.io

Note: GitHub will redirect all requests to new URL.

/cc @xiang90 @jpbetz @lburgazzoli @philips @jberkus

[xiang90]

probably we should try to get etcd org? Can someone try to contact the current owner?

[gyuho]

@xiang90 We have been already doing that for the past several months :)
Will keep you updated here.

[tamalsaha]

What does etcd mean?

[gyuho]

@tamalsaha http://etcd.readthedocs.io/en/latest/faq.html#how-to-pronounce-etcd

[lburgazzoli]

+1 for jetcd

[jpbetz]

Fingers crossed that we can get the etcd org. If not, some alternatives that come to mind: etcd-project, cncf-etcd, etcd-development (as already suggested), etcd-org

[hexfusion]

perhaps a few others to consider etcd-io etcd-dev

[philips]

I think etcd-io is reasonable given the ownership of etcd.io. Brandon

…

On Tue, Jul 31, 2018 at 1:42 PM Sam Batschelet ***@***.***> wrote: perhaps a few others to consider etcd-io etcd-dev — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9965 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACDCDhGuhP7SZYsFBJe6vanCbwfPaxCks5uMME8gaJpZM4Vkztd> .

[hexfusion]

FTR I have secured etcd-io and can move to any user if we decide to go with that.

[jberkus]

Is there already a list of org owners for once we move? That is, folks who should have org admin rights?

[hexfusion]

Probably the maintainers should be owners? https://github.com/coreos/etcd/blob/master/MAINTAINERS

…

On Jul 31, 2018, at 6:36 PM, Josh Berkus ***@***.***> wrote: Is there already a list of org owners for once we move? That is, folks who should have org admin rights? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[gyuho]

etcd-io sounds good to me, if we don't get etcd by this week.

@xiang90 @jpbetz Any thoughts?

[jpbetz]

@gyuho I'm happy with etcd-io. It's nice and short and maps clearly a domain CoreOS already owns. Kubernetes has gotten a lot of usage out of k8s.io and kubernetes.io domains. It's okay for the etcd.io domain to be donated to CNCF along with etcd, I assume?

[philips]

Yes. Etcd.io will be donated along with the other things like mailing groups, etc

…

On Wed, Aug 1, 2018, 11:38 AM Joe Betz ***@***.***> wrote: @gyuho <https://github.com/gyuho> I'm happy with etcd-io. It's nice and short and maps clearly a domain CoreOS already owns. Kubernetes has gotten a lot of usage out of k8s.io and kubernetes.io. It's okay for the etcd.io domain to be donated to CNCF along with etcd, I assume? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9965 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACDCEzJGz4Vgme69pbGuoYOW8CI8mOnks5uMfWJgaJpZM4Vkztd> .