You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title = "What we learned with Clippy's feature freeze"
4
4
authors = ["blyxyas"]
5
5
@@ -26,8 +26,7 @@ that started contributing to Clippy, 47 new contributors who opened a total of 1
26
26
On a team meeting, we concluded that the results of the feature freeze were positive enough to warrant a future one.
27
27
The cadence and duration of these is still being decided.
28
28
29
-
58% of all pull requests by new contributors were opened by the same person. This single contributor opened 114 pull requests of the
30
-
total 195. We held a meeting with her ([ada4a] on Github) to iron out some of the details of
29
+
58% of all pull requests by new contributors (114 out of the total 195) were opened by the same person. We held a meeting with her ([ada4a] on Github) to iron out some of the details of
31
30
the codebase and our procedures for new contributors. We are currently analyzing that meeting in order to improve
32
31
the experience for future and current contributors.
33
32
@@ -38,7 +37,7 @@ We also asked some questions to Ada (ada4a) to include as a mini Q&A, here are s
38
37
> Why do you like contributing to Clippy? What's so fun about it?
39
38
40
39
I came to enjoy improving the suggestions that Clippy makes: they are
41
-
fascinating in how they point out of the exact part of code that is
40
+
fascinating in how they point out the exact part of code that is
42
41
problematic, and show the (sometimes pretty complex) manipulations required to
43
42
fix it. Also, It has been empowering to learn the machinery behind the
44
43
compiler, and use that knowledge to refine these diagnostics even further.
0 commit comments