Split the repo into multiple, one per package and change the format a bit

[arybczak]

Now that there is an org, we can split the repo into more reasonable pieces like effectful-log, effectful-crypto-rng, effectful-time etc. with dedicated maintainers.

Current format of effectful-contrib is unsustainable - it's "fire and forget", i.e. people submit new packages, but then who will maintain them?

[Kleidukos]

@arybczak From my experience with the Servant ecosystem it's usually better to have every cabal project in the same repo, so that CI can cover larger ground and incompatibilities can be caught earlier.

And indeed, dedicated maintainers will be needed.

[arybczak]

it's usually better to have every cabal project in the same repo, so that CI can cover larger ground and incompatibilities can be caught earlier.

I disagree. That's what versioning is for ;)

If I choose to make an api breaking change in effectful, I'm not going to fix every package that needs changes by myself just so CI passes.

[Kleidukos]

@arybczak Very well! :) I'll start the repos then

[mmhat]

@arybczak @Kleidukos I'd like to be a member of that organisation, too. Is there any chance I get an invitation?

[arybczak]

@mmhat I've sent you an invitation but I see you didn't accept. Did you get it?

[mmhat]

@arybczak No, I didn't get one. Can you resend it?

[mmhat]

@arybczak Thank you, the invitation arrived this time :+1: However, I don't have sufficient permissions to work on the repositories listing me as a maintainer. In particular:

• https://github.com/haskell-effectful/effectful-typed-process
• https://github.com/haskell-effectful/effectful-log-elasticsearch
• https://github.com/haskell-effectful/effectful-log-base

@Kleidukos I am volunteering to co-maintain your repositories. Please let me know if that would be ok for you.

[Kleidukos]

I've created a team called "Maintainers" in which you all are, and should have associated permissions on the repos.