MeeGo Events Meeting - April 4th 2011 - Notes

Posted on Wed 06 April 2011 in MeeGo

MeeGo Conference Updates

We have 315 registrants as of today for the conference, so numbers are looking good without having any agenda published yet! A good portion of sessions should be approved by April 8th, this Friday and you will receive an email when/if your session has been approved yet. Not all the sessions will be approved by Friday though so if you do not hear from the committee then do not worry they are probably just working through it. The program committee is tenatively planning to have a first draft of the Agenda up by April 15th. Sponsored Travel attendees should start receiving approvals during next week and approvals will continue through April 25th.


You can follow the updates and planning on the Warm-up at

T-shirt design contest

For anyone who didn't see it on the mailing list this morning from Brian the winner of the T-shirt contest will receive sponsored airfare and hotel for the event in San Francisco. The contest closes next Friday, so get drawing!

MeeGo Summit FI update

MeeGo Summit FI (15-16th Apr). Summit will be 2-day developer oriented event as planned. Program contains keynotes, three tracks, meegathon competition, AR.Drone fun, evening party, Intel AppUp Lab, BoFs and more.
Interest towards summit has been huge, beyond our expectations. We were fully booked after one week. We have \~350 participants (limited by facilities and other details), over 140 are (still) in queue for cancellation seat.

MeeGo Corporate Guidelines and Regional and Local Assets and Guidelines

We in conjunction with Jarkko and the Finland team, the many contributors from the community, the Linux foundation, the events team, and the Caffelli design team have pulled together the guidelines for MeeGo Events. Thank you all for your contributions in putting these together! The Guidelines and Collateral Assets are posted on the Event's page at we would like your feedback and input so please email me [email protected] please send us things that you think we missed or things we could change to make the guidelines better.

Note: you can find the original log hereĀ