I have some concerns about how effective it could be for Desktop bug
council esp given the number of people who generally participate in
the discussion it takes to analyze impact of each bug fix across
components, evaluating risk factors and understanding use-case
scenarios. I am not sure people will be comfortable typing long
explanations on IRC.
Having said that I am fine with trying out the new process and seeing
for ourselves if it works out.
On Jul 30, 2007, at 3:34 PM, Philippe Bossut wrote:
Hi,
Sending the Bug Council reminder, I realized I forgot to ask
something to the list: it was suggested thatwe do triage sessions
on IRC like Cosmo does. I'm all for it personally though it takes a
little more structure to make sure the meeting goes well.
Pros:
- everybody can participate / see what's happening
- devs can react in real time when we talk about bugs assigned to them
Cons:
- can disrupt the flow of IRC conversation on the channel
(whichever we choose though I think #chandler would be the most
appropriate)
- need a little more policing of the meeting flow
We won't do this for the upcoming meeting (today @ 4pm) but I
thought I'd ask around. +1? veto?
Cheers,
- Philippe
Philippe Bossut wrote:
Hi Bug Council members,
Just a reminder that we have a Bug Council @ 4pm this afternoon. I
(finally) added this to the Office Calendar...
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
