Comments on: BarCampEarth Toronto – "Post Mortem" http://ryancoleman.ca/2006/08/barcampearth-toronto-post-mortem.html FACILITATOR - INNOVATOR - DESIGNER Fri, 10 Feb 2012 12:46:00 +0000 hourly 1 http://wordpress.org/?v= By: Ryan http://ryancoleman.ca/2006/08/barcampearth-toronto-post-mortem.html/comment-page-1#comment-87 Ryan Thu, 31 Aug 2006 17:05:00 +0000 http://rctemp.wordpress.com/2006/08/30/barcampearth-toronto-post-mortem/#comment-87 Agreed. <br/><br/>I think there's a couple of challenges. <br/><br/>1. I'm not sure people entirely understand how the wiki works. We should work hard at helping people understand that the http://barcamp.org/TorCamp page is the central spot to get info about upcoming events. (the next three DemoCamps are listed with "TBD" for dates - I'm sure it's the first place David will update when the date is defined. Maybe a TorCamp RSS feed for events/announcements? I know there is the edit feed on the wiki but that's a bit "rough" I think.<br/><br/>2. These things tend to come together at the last minute. BarCampEarth couldn't be confirmed until the week before the event because the venue wasn't nailed down yet. So I can understand and sympathize with people feeling like they're only learning about the event at the last minute. Agreed.

I think there’s a couple of challenges.

1. I’m not sure people entirely understand how the wiki works. We should work hard at helping people understand that the http://barcamp.org/TorCamp page is the central spot to get info about upcoming events. (the next three DemoCamps are listed with “TBD” for dates – I’m sure it’s the first place David will update when the date is defined. Maybe a TorCamp RSS feed for events/announcements? I know there is the edit feed on the wiki but that’s a bit “rough” I think.

2. These things tend to come together at the last minute. BarCampEarth couldn’t be confirmed until the week before the event because the venue wasn’t nailed down yet. So I can understand and sympathize with people feeling like they’re only learning about the event at the last minute.

]]> By: Ryan *M* http://ryancoleman.ca/2006/08/barcampearth-toronto-post-mortem.html/comment-page-1#comment-86 Ryan *M* Thu, 31 Aug 2006 14:51:00 +0000 http://rctemp.wordpress.com/2006/08/30/barcampearth-toronto-post-mortem/#comment-86 The one thing I heard and have heard at every BarCamp/DemoCamp/TorCamp is "I didn't even know this was going on until yesterday" which leads me to believe there is a general problem of distributing information. Moving forward we really need a centralized way of getting the word out about new events. It's not a good idea to assume that everyone is going to constantly check the wiki or reads certain blogs. While it's great that we have lots of new people every time, I'm sure there are lots of past attendees who are missing these events just because they didn't hear about them until it was too late.<br/><br/>RyanMck The one thing I heard and have heard at every BarCamp/DemoCamp/TorCamp is “I didn’t even know this was going on until yesterday” which leads me to believe there is a general problem of distributing information. Moving forward we really need a centralized way of getting the word out about new events. It’s not a good idea to assume that everyone is going to constantly check the wiki or reads certain blogs. While it’s great that we have lots of new people every time, I’m sure there are lots of past attendees who are missing these events just because they didn’t hear about them until it was too late.

RyanMck

]]> By: Ryan http://ryancoleman.ca/2006/08/barcampearth-toronto-post-mortem.html/comment-page-1#comment-85 Ryan Thu, 31 Aug 2006 10:26:00 +0000 http://rctemp.wordpress.com/2006/08/30/barcampearth-toronto-post-mortem/#comment-85 Thanks Peter,<br/><br/>As for Google Spreadsheets we just started using it right at the end. We used it to lay out all the tasks that had to happen in the last couple of days leading up to, and at, the event. Because we could see in realtime as changes were made we all got on a Skype call and worked through it to assign who was doing what & when. It saved time sending meeting notes/tasklists out because it was right there, built & agreed to during the meeting.<br/><br/>Ryan Thanks Peter,

As for Google Spreadsheets we just started using it right at the end. We used it to lay out all the tasks that had to happen in the last couple of days leading up to, and at, the event. Because we could see in realtime as changes were made we all got on a Skype call and worked through it to assign who was doing what & when. It saved time sending meeting notes/tasklists out because it was right there, built & agreed to during the meeting.

Ryan

]]> By: /pd http://ryancoleman.ca/2006/08/barcampearth-toronto-post-mortem.html/comment-page-1#comment-84 /pd Thu, 31 Aug 2006 03:02:00 +0000 http://rctemp.wordpress.com/2006/08/30/barcampearth-toronto-post-mortem/#comment-84 Hey Ryan,<br/><br/>just some feedback<br/><br/>1) Scheduling : dont move the stickies across the board --regardless of what happens !!! :)- <br/><br/>2) Session Length: The Person who leads/ chairs the session, makes an open call to the particapants /session attendees for a time keeper. <br/><br/>3) Size/Structure of Organizing Group: Yes, thats quite the challenge. I have to agree that you and Ryan did a good job. We could not have asked for more. I have to agree with Maria- ownership is the critical thing. Once that's established, then that's the person who rallies the forces and makes the decesions . Coumminty should honor ownership. We can't and *should* not fingerpoint at indivuduals. Isssues should be managed as part of the community discourse thru goole groups/wiki updates.<br/><br/>3) Venue: Personally speaking, I had back chatter on this aspect. It seemed that venue seemed to be a something our community has to contend with. Getting it --is difficult- we still need to foster a working group that can build the relationships with the companies that are willing to help out the community. I think this is one of the main challenges that is being faced by various Barcamps all over the world. If we have a core group that is dedicated to working the downtown companies for venue, then it becomes easier for the working chair to schedule and do other stuff and focusing on the details of the event. <br/><br/>4) Tools : - "we also started using Google Spreadsheets " - interesting --how what was your experince with GS ? How did you use this ??<br/><br/>Your "Post Mortem" is an excellent post and kudos to you for getting this event organized. Hey Ryan,

just some feedback

1) Scheduling : dont move the stickies across the board –regardless of what happens !!! :)-

2) Session Length: The Person who leads/ chairs the session, makes an open call to the particapants /session attendees for a time keeper.

3) Size/Structure of Organizing Group: Yes, thats quite the challenge. I have to agree that you and Ryan did a good job. We could not have asked for more. I have to agree with Maria- ownership is the critical thing. Once that’s established, then that’s the person who rallies the forces and makes the decesions . Coumminty should honor ownership. We can’t and *should* not fingerpoint at indivuduals. Isssues should be managed as part of the community discourse thru goole groups/wiki updates.

3) Venue: Personally speaking, I had back chatter on this aspect. It seemed that venue seemed to be a something our community has to contend with. Getting it –is difficult- we still need to foster a working group that can build the relationships with the companies that are willing to help out the community. I think this is one of the main challenges that is being faced by various Barcamps all over the world. If we have a core group that is dedicated to working the downtown companies for venue, then it becomes easier for the working chair to schedule and do other stuff and focusing on the details of the event.

4) Tools : – “we also started using Google Spreadsheets ” – interesting –how what was your experince with GS ? How did you use this ??

Your “Post Mortem” is an excellent post and kudos to you for getting this event organized.

]]>