Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custodians #14

Open
waywardmonkeys opened this issue Mar 22, 2018 · 3 comments
Open

Custodians #14

waywardmonkeys opened this issue Mar 22, 2018 · 3 comments

Comments

@waywardmonkeys
Copy link

I think it would be useful to have a team dedicated to custodianship.

This isn't the same as a blitz on a single library, as it seeks to do things across the ecosystem:

  • Submit markdown fixes.
  • Typo fixes in documentation.
  • Clippy fixes.
  • Warning fixes.
  • Updating dependencies.
  • Updating bindgen output / usage.
  • Improve CI.

It should include doing reverse dependency searches on crates.io to see who is still using older versions of popular libraries (like docopt 0.7) or who is using deprecated libraries (like rustc-serialize) and submitting updates to address that.

This can be fun as it can be an easy point of entry into doing something broadly useful for people who are newer and a lot of people seem happy to get random drive-by patches that fix things.

@KodrAus
Copy link
Collaborator

KodrAus commented Apr 9, 2018

This is an interesting idea! How do you typically find issues that need to be fixed at the moment? I'm thinking if we had a group dedicated to custodianship we'd probably need to try make it really easy for folks to get started fixing issues and submitting PRs, even if they're totally new to Rust/open source.

@kinggoesgaming
Copy link

I would love to be part of this... I love using clippy :D

@Dylan-DPC-zz
Copy link
Collaborator

Count me in :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants