BTW -- I have a dr's appt so I won't be around for meeting tomorrow -- maybe we want to chat a bit async instead? The main thing I've on my mind is figuring out how to make the ICE breaker stuff happen. It'd be good to enumerate out the tasks for that and maybe we can split them?
That plan makes sense to me.
sorry, I forgot to answer but yeah, seems good to me too
ok well we obviously didn't have the meeting, but I think the required steps are:
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 ...
nice write up
yeah, we need all that
and we need to organize ourselves to see how we can tackle those things
a lot of those are pretty small items
yes, some items are little things
what I was wondering is how should we split
do you want to assign tasks? I'd be happy to take some that you want me to tackle
maybe we should just do the short ones and open issues for the large ones?
actually I think the only really larger one is ...
we need a guide that helps people to get started with this sort of bug
the others seems shorter
anyway, let's split tasks?
let's start by opening an issue on compiler-team repo and copying my list of bullets into there
we can create the label, I guess something like ICEBreaker-LLVM ? that can also wait. The hardest part will be picking a nice color :P
the main splittable thing is the bot work ..? I think the guide would probably take a few minutes to draft up
ok that's not true
it'd take a lot longer to do properly
but I got no feedback here so we'll probably start with something ungreat
and maybe ask for help in the announcement in improving it :)
:+1: seems good
I can go ahead an open an issue
@nikomatsakis https://github.com/rust-lang/compiler-team/issues/174 feel free to edit