Move Finch under finch/finch (instead of finagle/finch)?

[vkostyukov]

This may help with discoverability. I don't really have a strong preference at the moment but eager to hear what people think.

As a side bonus we can have a little nicer URL for a website: https://finch.github.io - I'm not super sure though we can't already do that.

[frgomes]

This would be a good opportunity for consolidating internal/external dependencies across the entire suite of projects. At the moment, a certain project A depends on X.x whilst a certain project B depends on X.y. We have to eye-ball several projects in order to avoid jar hell. Ideally, all internal/external version numbers should be sitting on a single place, shared across the entire suite.

[ghost]

@vkostyukov I don't see a lot of reason to prefer com.github.finagle to com.github.finch or io.finch as the groupId for new releases as long as there are warnings (and perhaps dual publishing) I personally like having finagle in some part of the the name but that's just due to me being used to it. If there ends up being wide agreement to move I'd prefer io.finch as it's what the code uses now.

[sergeykolbasov]

It'll damage SEO for some time, but in a long-term sense it should be better.

[vkostyukov]

I created https://issues.sonatype.org/browse/OSSRH-41890 so we can register io.finch group id and start publishing Finch there (even before we move).

UPDATE: We couldn't do io.finch as a group id as we don't own finch.io domain. I opted in for io.github.finch for now.