Changes between Version 3 and Version 4 of ProposedParrotsketchProtocol

Show
Ignore:
Timestamp:
12/13/09 18:28:30 (5 years ago)
Author:
jkeenan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProposedParrotsketchProtocol

    v3 v4  
    1 We had a short BOF meeting between a few Parrot people Monday evening at YAPC::NA. We discussed the idea of changing the #parrotsketch meeting format to try to include more necessary information (but at the same time, a strong concern was voiced that those meetings tend to be too long). I want to put some of those ideas here into the open so we can all get a good look at them, and maybe start changing some things as early as next week if we like these ideas enough. 
     1= Parrotsketch Weekly Meeting Protocol = 
     2 
     3Parrot developers conduct a weekly online meeting on #parrotsketch.  The meeting is held on Tuesdays at 18:30 UTC.  The format for this meeting was developed following an in-person BOF meeting held at YAPC|10 in Pittburgh, PA in June 2009. 
    24 
    351. Everybody should prepost reports (or links to reports) well before the meeting at 18:30UTC, so we don't waste time at the meeting going through the list of reports.  A thirty minute window should be long enough to ensure that most attendees have enough time to get up-to-date before the meeting starts.  Everything will be in the [http://irclog.perlgeek.de/parrotsketch/ IRC log] so people can review them later at their leisure.  The ideal format for a report is a blog post or some other format designed to convey content rather than log realtime conversations, but pre-posting in #parrotsketch is also acceptable. 
     
    810  c. things that they are blocking on 
    911 
    10 3.  Get better status reports from people working on milestones, especially critical milestones, so we can identify when things are in danger of slipping and we can get more people assigned to it. 
    11  
    12 I'm sure I'm missing some things here too, so if anybody remembers stuff mentioned during the BOF at YAPC, or if other people have ideas they would like to add this is the place to do it. 
     123. It is important to get good status reports from people working on milestones, especially critical milestones, so we can identify when things are in danger of slipping and we can get more people assigned to it.