Tony Morris

I don't believe a good path forward is for Stackage to create and recommend a competing versioning strategy. https://github.com/haskell/pvp/issues/21 …

Is it viable to just ignore the issue and continue as we presently do? I mean, Stack/Stackage has worked fine until now, although the personal conflicts are of course unfortunate.

As I see it, there are two options right now for how we move forward. Option A: we do the hard work of trying to find common ground, ensure that infrastructure like Hackage remains useful and workable for different people, etc.

Option B is we just ignore each other and let things drift farther apart. Stackage could say explicitly "yeah, don't bother with version bounds, we don't need them," causing more upset with dep solving/PVP fans, for instance.

I'm trying out option A the only way I know how: encouraging more public discussion instead of silencing debates by having them in private or closing out issues while disagreements still exist.

At the same time: for users of Stack/Stackage, and day to day administration of the projects, we need to just move forward with whatever is best for people using the projects.

As a consumer rather than a producer of Haskell libraries and infrastructure, I am very grateful that someone else is fighting these battles for me.