Next steps for ICE breaker group

[spastorino]

• we need a guide that helps people to get started with this sort of bug -- see create guide to ICE-breaker groups and specifically advice for LLVM rustc-dev-guide#452
• we need some mechanism to make a github team people can subscribe to (as discussed here) -- @spastorino
• we need an announcement (maybe for the new team blog I am setting up!) -- draft blog post in this hackmd doc
• sample PR for adding yourself add nikomatsakis to LLVM ICE-breakers team#140
• we need a github label -- done, ICEBreaker-LLVM
• we need to update our compiler-team page to drive attention to these groups as a way to contribute
• and maybe think about the main contribution page?
• create a triagebot.toml file in rust-lang/rust (sample) add option to ping llvm ice-breakers to triagebot rust#65508
• we need a script people can copy/paste or -- better -- we need some command we can issue the triagebot. This fits with the discussion around "self-subscribing teams". reference the new PR mechanism rustc-dev-guide#463 -- @spastorino
• compiler twitter account that tweets these things out

That bot would assign the label and write something like:

Hey LLVM icebreakers! This bug has been identified as a good
"LLVM ice-breaking candidate". In case it's useful, here are some
[general instructions] for tackling these sorts of bugs. Maybe take a look?

cc @foo @bar @baz ...

[nikomatsakis]

Updates from meeting on 2019.09.26

• to track membership, we will create a team/icebreakers-llvm.toml file with minimal everything (not on website, no github team, etc)
  • but we have to be sure members do not get added to all@, have to check with @pietroalbini on the best way to do that

[nikomatsakis]

Closing as done!