Marketing Team/Events/MiniCamp Paris 2009/Christoph's Notes

From Sugar Labs
Jump to navigation Jump to search

Here's a list of notes from the various sessions and discussions I attended here at MiniCamp Paris 2009.

Sessions

School Server

  • XS-0.6 is looking sweet;-)
  • timeframe for 0.6: July (?)
  • bootable SD card to turn an (unlocked) XO into an XS

GCompris

  • need a maintainer for the Sugar branch (!)
  • GCompris admin interface and student progress => something we need for all Sugar activities

OLPC Quebeque

  • get template of 'in-school-use document'

Sugar 0.86

  • take information with a grain of salt and await details and confirmation from the development team
  • estimated release: end of September, to coincide with
    • GNOME 2.28 (final release: Sept. 23)
    • Fedora 12 release (final freeze: Sept. 22, final release: Nov 3rd)

Random Discussions

  • How can European grassroots initiate and run successful Sugar pilot?
  • frameworks, frameworks, frameworks
  • Uruguay contact (Italian students)
  • improve research angle, collect related information and contacts from around the world

Organization of similar future events

General thoughts

  • 2 Sugar focused days as minimum (4 days as a maximum)
  • WiFi needs to be available all the time
  • location should have one large room to assemble everyone, smaller seperate spaces to get work done
  • food and drinks should be available (Lebanese food prefered;-)
  • don't put too much strain on one person (e.g. Sean during Sugar Camp Paris 2009)
  • make it possible for remote contributors to attend during the event

Pre-Event

  • announce meeting date and location in due time
  • find sponsorship for event
  • find suitable location for meetups
  • find accomodation for attending people (Urban Camping)

During Event

  • introductory round at the beginning of the day (esp. when new people are present)
  • announce how remote contributors can attend during the event
    • preferably organize a certain time-slot (e.g. mid-day and/or at the end of the day)

Post-Event

  • end with what people liked and didn't like
  • follow up on what was discussed
  • make summaries of what was discussed available to the larger community