Re: npw2012
[email protected] ("Jonas B. Nielsen") Wed, 24 Aug 2011 16:36:24 +0200
| Newsgroups | perl.nordic.workshop |
|---|---|
| Message-ID | <[email protected]> |
Hep Salve's points are totally valid. It is also our experience in Copenhagen, it is important to be an = integrated part of the conference not a side-track. Side-tracks can = always happen, but it is important to emphasize on general Perl talks, = which introduces some of the Perl bling, line web frameworks (dancer, = mojolicious and catalyst) or other talks, which go well with the = expected audience. We did primarily Perl6, which was probably a bit over = the head of most of the attendees even though it was a lot of fun. jonasbn -- AIM: BjonasN Gtalk: [email protected] ICQ: 62401545 MSN: [email protected] twitter: jonasbn blog: http://e-diot.dk/ On 24/08/2011, at 16.01, Salve J Nilsen wrote: > Lars Thegler said: >> On Wed, Aug 24, 2011 at 2:40 PM, Claes Jakobsson <[email protected]> = wrote: >>=20 >>> My plan is to organize a two or three day multi-track technology = focused open source event/conference in Stockholm late may/early june = next year and if it's ok with people having NPW as an part of that might = be nice as it would also broaden the audience a bit. >=20 > Awesome! \o/ >=20 >=20 >> Sounds perfectly fine, a bit like what Oslo did in 2009 with the Go = Open conference? >=20 > We tried this in 2009, and it didn't work out as well as I hoped. Here = are a couple of things I learned from that event. I hope this obvious, = yet completely unsolicited advice doesn't fill your brain with = unnecessary redundancies that are not necessary. ;) >=20 >=20 > - Find a conference venue that holds the full set of tracks. We got = stowed away at the top floor of the building where Go Open happened, and = even if there were good things about that, we failed in many ways to be = visible to the other attendees. >=20 > - Make sure there's NO "special NPW program section" for any track. = One conference, one program. >=20 > - If you can, try to allow plenty of time for the hallway track. 10 = minute breaks are too short in my experience, especially if moving = between tracks requires more than a short walk across the hallway. >=20 > - A common lunch area helps a lot. Make sure to have interesting = and/or provoking talks before lunch, so everyone has someting to talk = about during lunch. >=20 > - Don't pitch competing views or technology alternatives against = eachother on different tracks at the same time. If you want people to = learn different (opposing) arguments in a discussion, let them attend = the all necessary talks. >=20 >=20 > - Salve >=20 > --=20 > #!/usr/bin/perl > sub AUTOLOAD{$AUTOLOAD=3D~/.*::(\d+)/;seek(DATA,$1,0);print# Salve = Joshua Nilsen > getc DATA}$"=3D"'};&{'";@_=3Dunpack("C*",unpack("u*",':4@,$'.# = <[email protected]> > '2!--"5-(50P%$PL,!0X354UC-PP%/0\`'."\n"));eval "&{'@_'}"; __END__ is = near! :)