Move repository to a separate organisation so responsibility could be shared

[kfh]

@nomisRev As briefly mentioned here: #203

Side-note: I would be more than happy to move this project to a separate organisation such as to share responsibility between other contributors.

I think this is a sound idea and something that would be positive for a broader usage of the library. I have used it for some time now and think it's a wonderful, small library that solves the coroutines layering on top of the standard java client in a very nice way.

I have been in discussions though when i try selling it in new projects where other developers are somewhat sceptical because they feel it's a single-point-of-failure library with only you in charge. And i can absolutely understand that argument.

Do you think this could be a sub-project of Arrow with your strong connection to that environment or do use see it more as it's own thing ?

[nomisRev]

Hey @kfh,

Thank you for bringing this up! I think it's time to bite the bullet and move forward with this. Besides developers being skeptical of a library living on a personal account, I think people are also more hesitant to contribute due to this.

I did have some plans in mind for the future, in regards to Ktor integration but that can also happen in an organisation inside or outside of this repository.

In my personal opinion I think this belongs outside of Arrow, but for simplicity we could move the repository there. I am afraid that this might also make some developers skeptical because they might assume that it depends on Arrow in some way or form. Which I have no intention of. WDYT?

[kfh]

In my personal opinion I think this belongs outside of Arrow, but for simplicity we could move the repository there. I am afraid that this might also make some developers skeptical because they might assume that it depends on Arrow in some way or form. Which I have no intention of. WDYT?

Yeah, i don't disagree with that take. But on the other hand, with the reputation of Arrow both as a community and rock solid libraries built around functional concepts i can also see that it will attract a broader usage.

Could possibly add a line or two in the README that is doesn't depend on Arrow directly but is a supported sub-project.

Anyways, the most important thing is to move it off your personal account which hopefully will engage more developers to contribute and use it.

[nomisRev]

Okay, based on your feedback I will discuss it in the #arrow-contributors channel on Slack. Feel free to jump in there to join the discussion.

[kfh]

Okay, based on your feedback I will discuss it in the #arrow-contributors channel on Slack. Feel free to jump in there to join the discussion.

Any progress here ?

[nomisRev]

Hey @kfh,

My apologies for the long delays. There is little interest from the other Arrow maintainers, since there is not many core maintainers.

I am still looking for people to help lead this organisation. I would gladly support and help out but it's too much to do by myself in my spare time in addition to my other work 😅

The library is in a decent state, and there are some things I am quite proud about. The producer DSL in particular is extremely efficient, and convenient to use. I'd be super happy if it got some usage.

Let me know your thoughts. If you want to create a GH org ping me, or invite me, and we'll move things over 👍 I know there is more people that are interested in these efforts. I get pinged regularly about it. Maybe we can get some natural contribution growth 🤞