Hi Damian, hi all!

On Tue, 28 Oct 2008 16:01:00 +0100
Damian Wojslaw <dwojslaw at opensolaris.com.pl> wrote:
> 
> Three days later, it is time to have some critical thoughts on our 
> event. I sum what went wrong, so that anyone doing their conference
> from scratch, won't make the same mistakes.

I'm in the (voluntary) conference business for several years now,
working on 2+ technical conferences a year (mostly Unix/Linux related),
and after each single conference, the orga team finds some new bugs and
improvements for the next time. 

But the most important thing IMHO is, to get the idea started at the
first place. And this you did!

> Given the above, I agree with Roman Strobl, that a guide for
> conference organiser should be made. I volunteer to give my
> experiences. Anoyne there to help?

We're running an osdevcon-discuss Mailing list on opensolaris.org. This
was initially to discuss things on and around OSDevCon, but why not
discuss there, how to make good community driven OpenSolaris
conferences all over the world and learn from each other.

There is already a short discussion in the archive about how to
improve OSDevCon, which was started shortly after the 2nd OSDevCon (June
2008, Prague):

  http://mail.opensolaris.org/pipermail/osdevcon-discuss/

You'll find the discussion in the July 2008 archive. Some older threads
in the archive are worth a reading as well.

Regards from a rainy Munich, Germany
wolfgang

-- 
  Jabber/XMPP: stief at guug.de                http://www.guug.de/
 ---------------------------------------------------------------
  German Unix User Group @ Xing   https://www.xing.de/net/guug/
  Linux-Kongress 2008            http://www.linux-kongress.org/
  Open Solaris Developer Conference    http://www.osdevcon.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: 
<http://mail.opensolaris.org/pipermail/advocacy-discuss/attachments/20081028/6e4ce825/attachment.bin>

Reply via email to