(→I plan to present ...) |
|||
| (13 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| + | '''Please add session notes to the wiki under [[MeeGo Conference 2010]], and link to them in the [[#Session notes]] section''' | ||
| + | |||
Day 3 of the [http://conference2010.meego.com MeeGo Conference] will be primarily an unconference run in the BarCamp style. We will also have one room with scheduled activities running in parallel to the unconference for Birds of a Feather sessions, lightning talks and similar activities. | Day 3 of the [http://conference2010.meego.com MeeGo Conference] will be primarily an unconference run in the BarCamp style. We will also have one room with scheduled activities running in parallel to the unconference for Birds of a Feather sessions, lightning talks and similar activities. | ||
| Line 65: | Line 67: | ||
* [[MeeGo_Conference2010/MCTS_CSA_Future|MeeGo Core Test Suite Current State and future workshop]] -- | * [[MeeGo_Conference2010/MCTS_CSA_Future|MeeGo Core Test Suite Current State and future workshop]] -- | ||
* [http://wiki.meego.com/User_talk:Alok.1.mishra Collaborative discussion about social networking touch points in MeeGo] [[User:alok.1.mishra|alok.1.mishra]] -- | * [http://wiki.meego.com/User_talk:Alok.1.mishra Collaborative discussion about social networking touch points in MeeGo] [[User:alok.1.mishra|alok.1.mishra]] -- | ||
| + | * [http://conference2010.meego.com/session/office-suite-meego-platform Will discuss about KOffice based office suite for MeeGo platform] --[[http://meego.com/users/chande |Chande] | ||
=== I would like to see someone talk about ... === | === I would like to see someone talk about ... === | ||
| Line 71: | Line 74: | ||
* Tips for contributing code to MeeGo and getting it accepted --[[User:Dawnfoster|Dawnfoster]] 22:09, 21 September 2010 (UTC) | * Tips for contributing code to MeeGo and getting it accepted --[[User:Dawnfoster|Dawnfoster]] 22:09, 21 September 2010 (UTC) | ||
| - | |||
* How to become a MeeGo platform hacker/developer- How to become part of the specification, design and development of the core platform, in one's favorite vertical. | * How to become a MeeGo platform hacker/developer- How to become part of the specification, design and development of the core platform, in one's favorite vertical. | ||
| - | |||
* Q&A and technical discussion of core compliance package list --[[User:Joel|Joel Clark]] 09:04, 5 November 2010 (UTC) | * Q&A and technical discussion of core compliance package list --[[User:Joel|Joel Clark]] 09:04, 5 November 2010 (UTC) | ||
| + | * Running MeeGo images under qemugl and kvm, especially handset and IVI images. MeeGo images as vehicles for platform testing. --[http://meego.com/users/alison | Alison Chaiken] | ||
| + | |||
| + | == Session notes == | ||
| + | |||
| + | Please add a link to your session notes and a one-line description of your session here. | ||
| + | |||
| + | * [[MeeGo Conference 2010/Example session notes | Example session notes]]: We discussed the relationship between the dollar exchange rate and the European Central Bank's inflationary policies. | ||
| + | * [[MeeGo Conference 2010/Hardware Hacking session | Hardware Hacking session]]: Hardware hacking based on Arduino. | ||
| + | * [http://bugreports.qt.nokia.com/browse/QTCOMPONENTS-200?focusedCommentId=132890&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-132890 Qt Quick components Common API] -- [[User:hhartz|hhartz]] | ||
| + | * [[File:CameraBoFNotes.txt | Camera BoF notes]]: Discussion about libQuill and camera hacking. | ||
| + | * [[MeeGo_Conference_2010/Python_BoF|Python BoF notes]]: Discussion about PySide and development of Python apps | ||
| + | * [[MeeGo Conference 2010/Unconference KDE-mobile UX | KDE-mobile User eXperience]]: Discussion about the look and feel of KDE applications on MeeGo/mobile platforms. | ||
== Schedule == | == Schedule == | ||
Please add session notes to the wiki under MeeGo Conference 2010, and link to them in the #Session notes section
Day 3 of the MeeGo Conference will be primarily an unconference run in the BarCamp style. We will also have one room with scheduled activities running in parallel to the unconference for Birds of a Feather sessions, lightning talks and similar activities.
Contents |
We've been getting a lot of questions about the unconference day from people who aren't convinced that it is worth their time to attend. I (Dawn) have attended many unconferences and organized several of them, and I can honestly say that I usually get as much, if not more, out of them than I do from traditional conferences.
An unconference is an ad-hoc gathering organized by the attendees for the attendees. The concept originated out of a desire for people to share and learn in an open environment. It is an intense event with discussions, demos and interaction from participants. You never quite know what to expect at an unconference, since each one is shaped by the attendees. When you arrive on Wednesday morning, there will be an agenda framework (times / rooms), but the content for the sessions will be decided by the participants.
To Present and Lead
To Collaborate and Network
To Learn and Innovate
IMPORTANT: Adding a session to the list below does not reserve a spot on the schedule board on Wednesday. The only way to guarantee a schedule slot is by showing up early and putting your session on the grid in person. See the #Schedule section below for more details.
Leave a note with the topic you plan to present along with your name and a link to more information about yourself.
Have something that you want to see someone else talk about? Feel free to use this space to brainstorm topics.
Please add a link to your session notes and a one-line description of your session here.
We will have a big grid on the wall where people can post their session ideas on the morning of the event (no sessions reserved in advance). Make sure you arrive on time if you plan to lead a session!
To Schedule a Session:
Things to keep in mind:
This is an example of how the grid will look and is for planning purposes only - please do not enter sessions or add other information to the grid
| Time | Presidents 1 (sits 300) | Presidents 2 (sits 280) | Vavasour (sits 80) | 1872 area (sits 120) | Havelock (sits 130) | Box 1 (sits 20) | Box 2 (sits 20) | Box 3 (sits 20) | Box 4 (sits 20) | Box 5 (sits 20) | Box 6 (sits 20) | Other | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 9:00 - 9:15 | Atrium: Welcome - What is an unconference and how do I participate? | ||||||||||||
| 9:15 - 9:45 | Atrium: Schedule board open - people post sessions on the grid. | ||||||||||||
| 9:45 - 10:00 | Atrium: Schedule board adjustments (combine duplicates, adjust rooms, etc.) | ||||||||||||
| 10:00 - 10:45 | BOFs / Scheduled | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | ||
| 11:00 - 11:45 | BOFs / Scheduled | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | ||
| 12:00 - 12:45 | Lightning Talks | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | ||
| 12:45 - 13:45 | Lunch and Networking | ||||||||||||
| 13:45 - 14:30 | BOFs / Scheduled | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | ||
| 14:45 - 15:30 | BOFs / Scheduled | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | Unconf Session | ||
| 15:30 - 16:00 | We need to be out of Aviva no later than 16:00. | ||||||||||||
| 17:45 | Doors open for the Ireland / Norway Football game. | ||||||||||||
Note: The BOF / Scheduled session room is out of scope of the unconference team and will be decided and planned by the content committee.