sctp-proto changed ownership

[algesten]

Hi @Qizot @mickel8 @LVala!

Sorry for ping. I'm the original author of str0m – a WebRTC impl in Rust. For the longest time we have shared the sctp-proto crate with the webrtc-rs project, however they don't want to maintain it anymore, so the the repo and crate has now changed owner to me.

Because there were not much dependencies, we were debating whether to roll the code into str0m itself, when ValorZard pointed out that you guys are also using it. If it's helpful, we could definitely keep it as a separate crate.

I wanted to create a direct line of communication with you to see what your plans are. We can discuss it here, or even better, we are also talking about this stuff in our Discord (invite link).

[LVala]

Hi @algesten, that's very considerate of you! Unfortunately, me and @mickel8 are no longer involved in the elixir-webrtc project. Let me ping current maintainers, maybe they can help you resolve this quicker @sgfn @Karolk99

[Karolk99]

Hi @algesten!
Thanks so much for reaching out and for the heads-up. We’re definitely open to whichever path makes maintenance easiest for you but I would like to ask you a few questions.

Do you intend to keep sctp-proto as a separate crate/package within a Cargo workspace in the str0m repo, or would it become a private internal module within the str0m crate itself?

If it is merged into the main repo, do you still plan to publish sctp-proto as a standalone crate to crates.io, or should we expect to point our dependencies directly toward the str0m crate (or the git repo) moving forward? If it's the latter, would we be able to use the SCTP logic as a standalone feature without pulling in the full WebRTC stack?

[algesten]

Hi @Karolk99

Do you intend to keep sctp-proto as a separate crate/package within a Cargo workspace in the str0m repo, or would it become a private internal module within the str0m crate itself?

If it is merged into the main repo, do you still plan to publish sctp-proto as a standalone crate to crates.io

This is why I'm reaching out. I'm gathering information about your plans, and if you intend to keep using sctp-proto, that's a strong argument for keeping it as a separate crate. I've also had other people on Discord also express an interest in keeping it separate.

To me it looks like that there is enough interest to keep the crate separate. Thus even if we merge the code into str0m main repo, we keep publishing it separately to crates.io.

I just now published 0.7.0 to make it clear the ownership has changed (and some minor cleanups). I believe you're on 0.3.0, and there are some breaking changes to get to 0.7.0, but as far as I recall there isn't a massive amount to do. I've stared a CHANGELOG to make it easier.