Consider moving to Tokio organisation

[Thomasdezeeuw]

The Tokio organisation has offered to support the socket2 library. I'm creating this issue to have an open discussion about it.

In the past their was were some opinions against doing this, I want to know if these are still present.

/cc @Darksonn

[Darksonn]

The context for this can be found in tokio#4135. We generally want to minimize the amount of distinct projects you have to trust to trust Tokio, and making socket2 part of the Tokio project will allow us to use it as a dependency without increasing that list.

[Thomasdezeeuw]

It's been a month, little to no comments. Not sure how to interpret that.

@rust-lang/libs team how do you feel?

[robjtede]

I think that the Rust community would, buy-and-large, trust any project that the Rust compiler itself sits in (ie. rust-lang). Socket2 feels like a project that has a wider scope than Tokio since it is more general in purpose. I would be surprised, even, to discover that such a project resides in Tokio's org.

[taiki-e]

I believe that what is proposed in RFC3119 "Rust crate ownership policy" (merged a few months ago) is enough to address (most of?) the original concerns from the tokio team, but it is not clear how long it will take to do.

[Thomasdezeeuw]

I believe that what is proposed in RFC3119 "Rust crate ownership policy" (merged a few months ago) is enough to address (most of?) the original concerns from the tokio team, but it is not clear how long it will take to do.

The problem with RFC3119 is that I haven't seen a lot work being done in the area. I think generally people like the idea, but I'm not sure how time is spend actually implementing it all, as per the (lack of) comments on the tracking issue: rust-lang/rust#88867.

For I think the plan is to not move socket2 and instead invite some maintainers from Tokio to this repo.

[Thomasdezeeuw]

Closing this as we're not moving the socket2 crate.