Add "The incoming Summer of Clippy" post #1613
Conversation
There was a problem hiding this comment.
That was quick! I don't have time to review the blog post today. But should this go into content/inside-rust instead? I feel like this is more of an inside-rust blog post.
There was a problem hiding this comment.
I'm not sure, this serves as a half announcement to overall the Rust community (they won't be getting new features for a while) and also to the contributors, as they now have distinct goals to aim to. (That tracking issue)
There was a problem hiding this comment.
I don't think it will be really noticable to non-contributors, if there aren't any new lints for 2 releases. And the ones that do notice, will probably find this blog post, even when published in internal-rust
The internal-rust blog is for the contributors.
| upping the standard for lints all around the project we can allow users to | ||
| expect even more from the already great linter. | ||
|
|
||
| If you have a lint which you want to be implemented, you can still open and |
There was a problem hiding this comment.
| If you have a lint which you want to be implemented, you can still open and | |
| If you have a lint which you want to be implemented, you can still open an |
Typo
|
|
||
| If you have a lint which you want to be implemented, you can still open and | ||
| issue for it, but no one will implement it (also, lint-adding pull requests | ||
| opened after the starting date will be blocked for the duration of the period) |
|
|
||
| Note that pull requests opened before the starting date can still be reviewed | ||
| and merged, but unless they are already in a very advanced state they will not | ||
| be priorized over bugfixes. |
There was a problem hiding this comment.
| be priorized over bugfixes. | |
| be prioritized over bugfixes. |
| ## Can I help? | ||
|
|
||
| As always, any help on the project is very appreciated. Apart from opening bug | ||
| reports, you can follow our [contributing guidelines] and check [our suggested |
There was a problem hiding this comment.
Not: the "our" should be let in or out of the link consistently.
| for current and future changes in the compiler as a whole. | ||
|
|
||
| As a team we’ll focus on making contributing the best it can be, we’ll try to | ||
| bisect all the issues possible and mark the issues that could be great as a |
There was a problem hiding this comment.
Don't you mean "dissect" here? (because bisection would probably give us the point of introduction of the lint)
This is the initial draft for "The incoming Summer of Clippy", talked about in our All Hands.
For reviewing ease, here's everything I wanted to talk about:
We are currently blocked on not having a tracking issue for the good first issues (and we do not have a lot of issues marked with the label in the repo). But I think that this is still ready for an initial review from the team.
Related to https://hackmd.io/nubu1rGOTliW1MZPilplaA
@rust-lang/clippy
Rendered