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

announce Cleanup Crew ICE-breaker group #504

Merged
merged 5 commits into from
Feb 6, 2020
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 43 additions & 0 deletions posts/inside-rust/2020-01-27-Cleanup-Crew-ICE-breakers.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
---
layout: post
title: "Announcing the Cleanup Crew ICE-breaker group"
author: Santiago Pastorino
description: "A new blog where the Rust team can post updates on the latest developments"
team: the compiler team <https://www.rust-lang.org/governance/teams/compiler>
---

Following Niko Matsakis' announcement of the [**LLVM ICE-breaker
group**](https://blog.rust-lang.org/inside-rust/2019/10/22/LLVM-ICE-breakers.html),
I'm pleased to announce the **Cleanup Crew ICE-breaker group**. It
follows the same principle, if you know Rust and would like to
contribute to rustc -- but without knowing about the compiler or taking
on a large commitment -- then the Cleanup Crew ICE-breaker group might
well be for you!

### What is the Cleanup Crew ICE-breaker group?

The "Cleanup Crew" are focused on improving bug reports. Specifically,
the goal is to try to ensure that every bug report has all the
information that will be needed for someone to fix it:

- a minimal, standalone example that shows the problem
- links to duplicates or related bugs
- if the bug is a regression (something that used to work, but no
longer does), then a bisection to the PR or nightly that caused
the regression

This kind of cleanup is invaluable in getting bugs fixed.

### Who should join?

It can be done by anybody who knows Rust, without any particularly deep
knowledge of the compiler. If you want to be part of it and be notified
about things to do, just add yourself to the list ([instructions here])! When we come across a suitable
spastorino marked this conversation as resolved.
Show resolved Hide resolved
bug, we'll write a message that `@`-mentions every Github user on that
team. If you have some time, maybe you can provide some useful
information.

[open a PR]: https://rust-lang.github.io/rustc-guide/ice-breaker/about.html#join
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've just followed the same idea of the LLVM ICE Breaker announcement but maybe isn't it better to just point to the PR?


You can find more information about the group on it's [rustc-guide
section](https://rust-lang.github.io/rustc-guide/ice-breaker/cleanup-crew.html).