Changes between Version 1 and Version 2 of ProposedParrotsketchProtocol

Timestamp:

06/30/09 07:19:53 (13 years ago)

Author:

cotto

Comment:

Revert preposting recommendation to the original 30m. We can change it later if needed.

ProposedParrotsketchProtocol

@@ -1 +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. 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 two hour 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 IRC backlog 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.
+1. 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 IRC backlog 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.
 
 2. In their reports, everybody should list