Transfer

[rust-unofficial]

Transfer

[mixedCase]

As someone still learning Rust, I wouldn't like to see this list deprecated in favor of crates.io. The "awesome" curated lists is a sort of community staple I intuitively reach for when I want to learn more about the ecosystem of a specific technology/tool.

At least, if the crates.io recommendations are going to follow the same curation style, it'd be nice to have this repo mirror it.

[Freyskeyd]

Why not let rustlang organisation handle it?

[aturon]

@Freyskeyd My point is that we need people to commit to the effort if it's going to happen. There are several rust-lang repos that are languishing due to lack of leadership bandwidth.

[booyaa]

Looks like there's three volunteers (me, @Freyskeyd and @luciusmagn). I'm happy to be the main maintainer.

[Manishearth]

Come to think of it, if @booyaa and I both want to help, it's worth considering just moving this to the rust-community org and making it officially-unofficially maintained by the community team. Whatsay @erickt?

[luciusmagn]

@Manishearth That is actually quite a good idea. I am still unsure, but I am becoming more inclined to rust-community. The way I see it, the project will be transferred rather than abandoned, so rust-community seems like a better fit.

I will just be glad if awesome-rust gets a good new home, though.

[Freyskeyd]

@aturon I would imagine some self driven repository. Maybe a little group can create with influential people and use the Rust weekly newsletter (like https://this-week-in-rust.org/).

The point about QA is interesting, we need to automate this kind of stuff.

[kud1ing]

@nasa42 That would only replace the section "Libraries", wouldn't it?

[booyaa]

All, Does anyone have any objections if we transfer this repo into the rust-unofficial org so it can continue to be maintained? I've already cleared this with the org team. The current maintainers will be transferred over and in a earlier in this thread I staked my claim to be the main point of contact. Cheers, Mark Rust Community Team

On Mon, 8 May 2017 at 12:25, kud1ing ***@***.***> wrote: @booyaa <https://github.com/booyaa>: If the decision was finalized, i can do it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#289 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AALxYK2fc7_TfRHLUB-5evrsAPW-JKbqks5r3vvEgaJpZM4NQgX0> .

-- Sent from Gmail BatMobile

[kud1ing]

I've always wanted to hold an emotional speech but have yet to be invited to give one. So here we go ... cling cling

awesome-rust wouldn't have been possible without the countless people contributing to it and of course without all the people writing Rust and using Rust to do awesome things. I hope Rust and awesome-rust will prosper for a long time.

[steveklabnik]

Hmmmmmmmmmmmmm. I'll give it some thought.

[aturon]

@Freyskeyd Even if we head that direction, it still needs leadership and helping hands.

[nasa42]

I've planned to deprecate a related project - libs.rs in favour of upcoming recommendation ranking (and categories) feature in crates.io. I think with these features, crates.io may also supersede awesome-rust.

[booyaa]

Once the caretakers have been found, I'm sure it could live here in rust-unofficial org? i.e. rust-unofficial/too-many-lists or rust-unofficial/patterns.

I'm willing to put my hat in for the interim, it would be a shame to see this resource get bitrot.

[nasa42]

@nasa42 That would only replace the section "Libraries", wouldn't it?

A short preliminary review suggests that pretty much everything except "IDEs" section is a crate (though not all may exist on crates.io).

[Manishearth]

FWIW https://github.com/rust-unofficial is a holding yard for things that need maintainers, and is somewhat maintained (accepting PRs and such) by various folks in the community.

We'd be happy to accept this repo and partially maintain it, but we probably can't make major improvements/etc. If there are folks who want to help we can add them to the org.

[Freyskeyd]

I'm interested in helping on awesome-rust but not as a main maintainer in fact..

[luciusmagn]

I would love to help in any way. I am not sure if I would be a good main maintainer, but as a last resort, I would be open to anything.

[Freyskeyd]

@Manishearth that's what I was thinking too

[ctjhoa]

Hi,
I'm the rust-learning's owner
I could bring my help too as I already got some CI things for markdown to manage my repository.
Moreover I've got the same issue of dead links (so we could help each other).
On the other hand, I agree with @nasa42. It seems like most of the content (description, build status, link to the repo) are redundant with crates.io

[Manishearth]

It seems like most of the content (description, build status, link to the repo) are redundant with crates.io

It's good to have these in one place instead of having to click twice to get there though.

But yes, the crates recommendation stuff may supersede this.

[brson]

Thanks for maintaining awesome-rust @kud1ing.

I would be sad to see this resource go, and like @mixedCase think it's good to have our own "awesome" list.

Seems like there's a good plan here to maintain it.

[kud1ing]

So, until the final destination is figured out, i've added Mark, Manish, Simon and Lukáš as collaborators.

[booyaa]

@kud1ing thanks for making us collaborators. I'd like to get the ball moving and transfer the repo to the rust-unofficial org. As the creator, I think you're the only one who can initiate this.

On Mon, 8 May 2017 at 06:56, kud1ing ***@***.***> wrote: So, until the final destination is figured out, i've added Mark, Manish, Simon and Lukáš as collaborators. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#289 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AALxYNWUTgHywDFAz1CUAIILhZp_Nw3Iks5r3q6JgaJpZM4NQgX0> .

-- Sent from Gmail BatMobile

[kud1ing]

@booyaa: If the decision was finalized, i can do it.

[luciusmagn]

@booyaa I think it's a good idea.

regards,
Lukáš

[Manishearth]

I agree. Though I would prefer rust-community since I think this is something that falls perfectly within the responsibilities of the team. We can discuss that at the next meeting though.

[Manishearth]

(I can do the transfer to unofficial if needed, I don't know who else has access to both)

[kud1ing]

Fine. So @Manishearth please give an update once we can move forward.

[carols10cents]

I'd just like to mention that crates.io is not adding manual curation anytime soon (for a variety of reasons I detailed in various comments on RFC 1824), so there's definitely still a need for people maintaining lists of crates they think are good.

[kud1ing]

Also, compared to every library author choosing their own categories/keywords via Cargo.toml, i think a central curation can give a more coherent overview more effectively.

[Freyskeyd]

Hey,

If we can't move to rust-lang/awesome-rust I think rust-community is a better place.

[erickt]

I'm +1 to rust-community! Wonderful idea. Then we can fold this into https://community.rs to help with discoverability.

[Manishearth]

We discussed this today in the community team meeting, rust-unofficial seems a better place for now. We can try to give this more visibility from official locations though.

[Manishearth]

I don't have admin access so someone else will have to do the transfer. I can set up perms for maintainers on rust-unofficial for whoever needs them.

[luciusmagn]

Alright, understood, rust-unofficial is also a great place, although I was more inclined to rust-community.

@Manishearth mind if I ask what reasons make rust-unofficial a better fit than rust-community? I am just curious, not trying to disprove the decision.

[Manishearth]

The argument made was that rust-community shouldn't be a sort of catch-all for anything community related. I personally feel that this repo should be maintained by the community team (+ others) but folks seem divided on that.

[luciusmagn]

I see, thanks for clarifying

[kud1ing]

It seems i can not transfer the repository by myself: "You don’t have the permission to create repositories on rust-unofficial". Anyone have experience with this?

[Manishearth]

I can do it with admin to this repo :) You need admin on rust-unofficial to do the transfer I think On May 10, 2017 10:44 PM, "kud1ing" <[email protected]> wrote: It seems i can not transfer the repository by myself: "You don’t have the permission to create repositories on rust-unofficial". Anyone have experience with this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#289 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABivSMPXjgdpvRlaz9p7Jqq7a0Ftyh_9ks5r4qAwgaJpZM4NQgX0> .

[kud1ing]

@Manishearth Let me know if you need anything. I am ready to let go. :)

[Manishearth]

Right, I need admin access to this repo so that I can use the rename settings

[Manishearth]

Er, the move repo settings

[kud1ing]

I have the impression that user account repositories do not have that role: https://help.github.com/articles/permission-levels-for-a-user-account-repository/

[Manishearth]

Hm. I invited you to the unofficial org, you should be able to transfer once you accept that. If that doesn't work idk what's happening :)

[kud1ing]

Interesting, i had to visit rust-unofficial to view the invitation.

[Manishearth]

Cool. Can you still add maintainers to the repo? May have to fiddle perms to make that work.

(And is there anyone who should have been added and isn't yet?)

[kud1ing]

Nope, i've lost the "Settings" tab. Probably i am not an admin in the new repository.

[Manishearth]

You should have admin now. Thanks for all your hard work!

[luciusmagn]

@kud1ing That is a nice idea, I'd love to contribute

[kud1ing]

@luciusmagn I've just discovered https://brson.github.io/rust-cookbook/ Our efforts probably should go there instead,

[luciusmagn]

@kud1ing awesome, I'll check it out when I get home!

[kud1ing]

If anyone is still interested, this project is looking for maintainers again: #807

[Freyskeyd]

@kud1ing is it really time consuming?

[kud1ing]

@Freyskeyd That depends on multiple things: how many pull requests people submit, how quickly you want to react, how much there is to cleanup (e.g. due to repository renames, or if you want to cleanup/regorganize the structure), how many people there are to share the maintenance workload.

And besides quantity, there is also qualitity of time as an important happiness factor.