Peter Haworth wrote: > As for the announcement, some indication of which areas are going to > be investigated would be useful. Also, giving an idea of what form > such investigations might take would clarify things immensely, not to > mention making them less aimless. It may also help if each group was > lead by someone with a relatively clear idea of what there was to > investigate. > > Basically, we need to make it a bit less abstract and vague.
Time consuming planning I was trying to avoid :( But yes, a total winging it might not be the best approach. How about some open discussion on areas? Perl 6 Operator fun (http://perlcabal.org/syn/S03.html, etc) Blocks and Statements (http://perlcabal.org/syn/S04.html), etc) Regexs and Rules (http://perlcabal.org/syn/S05.html, etc) Or just 2..14 from:- http://perlcabal.org/syn/ Also how long for the workshop? I was thinking 2hrs per group session. Possibly 2 group sessions. So I propose the very loose, draft format:- 10am Meet and greet 10:30am Divide into groups (I was thinking do a quick experience check, and give each group an even skill spread) 10:40am Assign area(s) (maybe two areas at a time) 12:30pm Presentations 1:30pm Lunch 2:00pm Possibly re-jig groups 2:15pm Assign area(s) 4:00pm Presentations 4:30pm Closing & Thanks Everyone has an opinion, so feedback please. Lyle _______________________________________________ BristolBathPM mailing list [email protected] http://mailman.bristolbath.org/mailman/listinfo/bristolbathpm
