remove quill integration

[tpolecat]

This removes integration with Quill, which is now part of the ZIO organization, which I will not support.

[deusaquilus]

Is there something that is good and right to say here? I don't know.

I'm really, really sorry that it's come to this. @tpolecat, you're a great author of a wonderful library. Together we made something fun and useful that makes many people's lives easier and more fun. If there was something I knew I could say to somehow reconcile the vast chasm that has opened up between our communities then I would say it right now. If there was something I knew I could say to heal anything and anyone then I would say it right now. I can't undo or un-say anything has has been done or said by others over these past four years and I can't change anyone's opinion about anything at all in these short keystrokes.

Will the whole Scala world be opened up and ripped apart by this conflict? Will every library and every repo have to eventually pick a side to love and a side to spurn? I hope not. I hope that our ideals are not forever irreconcilable and that this conflict will not be the span of decades.

This is sad. Really, really sad.
I don't know what else to say.

[chrilves]

I'm just a user but I want you @tpolecat to know that some users understand this decisions.

[kubukoz]

@tpolecat I understand your decision and the reasoning behind it, but please consider that a lot of people are using both libraries in production. I think this isn't going to hurt the ZIO organization as much as it's going to hurt the widespread community.

Of course, nobody is going to expect you to continue to maintain this integration in your free time. But before this is finalized and people start wondering why they can't upgrade Doobie because of a missing artifact, I would like to start a discussion about alternatives and migration paths.

@deusaquilus would you take a PR porting all of this to the new repository? I also don't want to shift the whole burden to you personally, but if there are more users of the Doobie+Quill combo someone might step up. Maybe if it's going to slow down the evolution of Quill core this could be a separate repository in the ZIO org (although it's just essentially 4 files as far as I can see).

I myself have no particular stake in this integration so I won't volunteer for maintainer (I know some people who might though), but I can try and make the initial step of extracting this.

[ccellado]

Hell is full of good meanings, but heaven is full of good works.

[kubukoz]

I've set up a copy of this in https://github.com/polyvariant/doobie-quill, there's a snapshot on s01.oss.sonatype.org and a numbered release syncing to Maven Central.

@tpolecat just to have paper trail, license-wise is this okay for you?

[Guisanpea]

I firmly believe that we should respect library authors deciding not to maintain a project any longer, regardless of the impact it may have on the community.

Open source contributors are regular people who choose to spend their spare time creating something good for the rest of us. The time they are contributing to their projects is time they are not dedicating to their personal life.

Even if you don't care about library authors, if they work on something they are not comfortable with, they are less likely to make it great.

And I think that it is not a big deal if doobie-quill stops being developed by @tpolecat. It can still be developed by other people who really feel like doing it. That's the good thing about functional programming, we can compose things. Doobie is a lego piece and Quill is another lego piece, if the maintainer of one of those is not a maintainer of the combination it is not that big of a deal.

If we want a healthy open source community let maintainers be free and make their decisions without consequences

[tpolecat]

@kubukoz yes, the fork without attribution is fine. Thanks for asking.

[odersky]

I think this disqualifies both doobie and TypeLevel from further conversation. You can do what you want. But I am sick of this kind of politics.

[nafg]

Will the whole Scala world be opened up and ripped apart by this conflict? Will every library and every repo have to eventually pick a side to love and a side to spurn? I hope not.

So do I. But this childish move is itself a step in this direction. @tpolecat don't you realize how much this harms the entire Scala community and adoption? Someone will probably post this on Reddit and the entire world's existing belief that people in the Scala community are toxic will be reinforced. Please don't do this to us. You're killing Scala adoption when you do things like this.

[kubukoz]

@odersky so this is enough to punish the entirety of Typelevel, but when ZIO maintainers post FUD about TL libraries that's fine?

@nafg that's an interesting way to say "you're a hostage of this code now, keep publishing it or you'll be blamed for the community's downfall"

[tpolecat]

Alright that's about enough. Thanks everyone for your input.