Consider moving the project to an org

[pmazzini]

I am only opening this to discuss whether we should move the project to github.com/coredhcp/dhcp.

The cons are that we already have the issues, stars and metrics in the current repo.

[stapelberg]

The cons are that we already have the issues, stars and metrics in the current repo.

AFAIK, you can move a repository without losing any of these.

[insomniacslk]

yeah, you can move a repo and retain commit history, issues, etc, it would be just like a rename. Also, there is automatic redirection from the old to the new repo, so even importing code via go get should keep working with the old import path. However CoreDHCP is not yet mature enough, and I'd rather not move it until then.

[pmazzini]

Inspired by the go-ping and go-zookeeper orgs, I registered the go-dhcp one. I am happy to transfer ownership or add more owners to it.

[hugelgupf]

I'm for it.

[pmazzini]

Reviving this, would it make sense to move it to an org?

[insomniacslk]

No objections, I would use the existing coredhcp org though