Alexandru Nedelcu

Also, a unified repo should probably fork the current Fantasy-Land repository. It's mostly a social issue — contributors are fond of their contributions and forking without actually forking via Git...

@rpominov great, but I'd fork the repo into another repository in order for collaboration to happen, otherwise we are limited by comments on the PR and that's going to generate...

Given we have that unified repo, might as well talk there on specifics. Opened my first issue: https://github.com/fantasyland/unified-specification/issues/3

I've added a comment here that might be relevant: https://github.com/monix/monix/issues/379#issuecomment-311896969 If you're having resolution problems, then Coursier might be to blame (because otherwise the only other culprit would be Maven...

The badges are problematic as Scala index is also unfamiliar with our practice of publishing hash versions from time to time, for testing purposes and the badges ends up displaying...

@rossabaker > Consider making a more anemic README that drives straight to the site. Many people land on the GitHub repository and I prefer having an easy copy-paste-able version number....

Btw, automation would be cool, but having a checklist for maintainers might be OK too 🙂

Document variables sound cool. Another possibility, to keep the README in sync is to introduce a script that fails the build on version tags.

`Effect` is not very generic as a type class. Once you work with `Effect`, you effectively work with `cats.effect.IO`, hence the extra restriction that `Effect[Task]` requires. The new Cats-Effect has...

@jatcwang I won't provide a minimal example, too much work 🙂 1. see issue I linked in HikariCP's repository 2. also I don't understand what that `mvnrepository.com` is compiling, but...