Leave the Rustdoc team#689
Conversation
I don't want to keep up with FCPs and I also don't want to block them (@Manishearth has suggested a few times that the minimum work required for being a member is "responding to FCPs in a timely manner"). Additionally, I don't want people to assign me on PRs.
There was a problem hiding this comment.
I'll be sad to see you go, hopefully we still see you around!
I will point out that the thing I mentioned about FCPs was largely for normal team members: I do think it's acceptable for team leads to focus on leadership and defer on FCPs/etc. But it does sound like you're not that interested in continuing, that's fine too. Feel free to reach out if you want to talk about it!
|
I'm sad that you're leaving us too... Thanks to you, rustdoc situation improved a lot. Hopefully, we will see you around. |
|
Thanks for all you've done! You really helped me feel welcomed onto the team when I first started making contributions, so thank you for that in particular. |
|
Thank you for mentoring me as I started contributing and continuing onward, for many fun discussions about how to improve rustdoc, for helping me to learn PR review, and for many other things. It's been a lot of fun the last couple of years! |
|
Thanks @jyn514!! You're the reason I was able to get --scrape-examples off the ground and on nightly. |
|
I have received many comments and help with my PR from you in the past and you are always so patient and enthusiastic. Thank you so much! @jyn514 |
|
I remember my first PR for Rust where you've responded to my questions so quickly, it was almost scary. 😄 Thank you, @jyn514, for all you have done for the Rust community and rustdoc. ❤️ I wish you all the best on your future journey. |
I don't want to keep up with FCPs and I also don't want to block them (@Manishearth has suggested a few times that the minimum work required for being a member is "responding to FCPs in a timely manner").
Additionally, I don't want people to assign me on PRs.