-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add 2021 Roadmap for Clippy #6
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is amazing, thank you!
I like this clear outlook for the future, with focus not just on technical things, but on the maintenance/social aspect too.
I feel like the list of big ticket items is going to be a great way to grow more contributors: working on something like this is how @yaahc went from helping with random lints to working on a large, highly needed architectural change. It's going to be great to point growing contributors at this document as a way of saying "pick something if you want!".
Thanks so much for working on this ❤️
I really like this. 👍 |
Just wanted to drop by and add that I'm super excited for folks to be doing this work, happy to see you've kicked it off here ❤️ Do you mind if I include a link to this RFC (or if you plan to publish it on the main clippy repository?) in the Rust 2021 Roadmap RFC? I think it's great as a reference to the sort of individual team roadmap I was hoping for, and would be a great example for all of us :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this!
We need to organize to address the growing pains of the project, and I think this comes at the right time.
@matthiaskrgr That's great! Keep in mind that I want to keep the scope of this document on what we want to do and figure out the "How" in dedicated issues.
@Mark-Simulacrum Sure! But please wait until we publish it. Maybe we can coordinate and publish it at the same time as the Rust roadmap. Do you already know a date when you want to publish it? |
I am planning on posting the main roadmap on the 17th. |
@Manishearth @ebroto @phansch @matthiaskrgr @Mark-Simulacrum I pushed the re-written Roadmap document: Rendered. This is also the version I want to publish. Some open questions before publishing:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we write a blog post after publishing it?
Yes, I think more feedback will help us with prioritization a lot, especially since we don't have the call for blog posts like the main roadmap.
I think I addressed all comments. Please re-review :)
👍 from my side
+1 from me, I'm okay with a blog post if folks wanna do it. I'm excited! |
FYI: My plan is to edit in a link to this roadmap after publishing the initial PR of mine, just to avoid any need for coordinating that to happen at similar times or anything. |
02f736b
to
bfdc307
Compare
This should be ready to get published now. I want to wait for the Rust roadmap before publishing this though, since I reference it quite a bit. |
@flip1995 the rust roadmap is already a PR: rust-lang/rfcs#3037, i think it's fine to merge this first since it will want to refer to us too. |
Thanks for notifying me! I'll open a PR to the Clippy repo in a bit (~1h). I want to get community feedback for this before actually merging it in the main repo. (you can also open a PR for me, if you want) |
New lint: option_manual_map fixes: #6 changelog: Added lint: `match_map`
I'd like to write a roadmap for the Clippy repo and release it approximately at the same time as the Rust 2021 roadmap. This is a list of things I'd like to see happen in 2021 for Clippy.
Before opening this up for everyone, I'd like the input of the team members. After we have some consensus in the team what we want to do, I will write this in a format similar to the Rust roadmap and request comments from the broader community.
Feel free to comment about stuff you have in mind or comment what you don't like. This currently is just a semi-organized dump of ideas I have and every point needs to be written out in a separate tracking issue once we have consensus in the team and the community.
Rendered