List of practical issues/items to get things going on as planned. Pick a job which you can do. Put your nick to 'assigned to' cell. When task is done, set status to 'done!'
| Task description | Assigned to | Status |
|---|---|---|
| Need to 'sketch' a template for the Summit Plan. http://wiki.meego.com/Template:Summit. Semantic Wiki extensions would be nice and useful. That way, information would be in one place (minimize human errors) and displayed elsewhere through queries. For example the lists of future and past Summits could be constructed with queries. The basic information about Summit would be inputted through form to make sure required data would be given at all times. | Kyber | not finished |
| Need an extension to mediawiki to enable (graphical) visual display of the Summits, based on summit dates. See for example. Example uses semantic wiki features. | none. | not finished |
| description | assigned to | status |
The National MeeGo Summits (shortly NMS) are held once or twice a year. The conferences function as a meeting place for MeeGo hobbyists and professionals, independents and corporations. The summits must be directly related to MeeGo project. Furthermore, collaboration with The Linux Foundation is desired (or mandatory?).
Remember to scale your NMS to fit the needs of your Local MeeGo Networks. In other words, NMS does not have to be a huge event. It can be a chance to meet fellow aMeeGos, do some hacking, share your local network's ideas with others, get ideas from others or something like that. On the other hand, it can also be an event where you can invite talented MeeGo hackers to talk about something interesting, demonstrate achievements and brag with your talent. MeeGo Summits can be the highlights of your Local MeeGo Network Community and an opportunity to share thoughts with other aMeeGos, developers and members of other local communities.
Summits ought to be more or less developer oriented events. In other words, business related topics should be minimized and hands-on events/tracks should be maximized.
Summit can be either one or two days long. Simple examples for the structure:
One day Summit
Two day Summit
Q: Could equivalent Maemo, MeeGo and/or Symbian events be combined together?
This list contains the MeeGo Summits to be held. Candidate summits are marked with suffix (CANDIDATE). Add a link to your Summit wiki page which includes the plan for the summit. Do you want to organize a MeeGo Summit in your area? See How to organize NMS in your region. Past summits are listed here
NOTE: automatically generated timeline display of the Summits here. Also the list would be generated IF semantic extensions would be used as suggested.
Organizing a MeeGo Summit in your region is usually a team effort. Before building a new team for Summit in mind, check the list of future MeeGo Summits. The team might already be started and you should join them. In addition, check Community Forum and mailing list to see if someone has started a thread concerning a MeeGo Summit in your region. If you don't find an existing effort, start a new one. Below is a list of items to follow.
Sharing information and granting access to Summit related discussions and people is important. Suggestions to enhance communication:
The funding should be organized by the Local MeeGo Networks. Find sponsors for conference venue, refreshments and other items to arrange. Support (from who?) can be given to arrange über MeeGo speakers from abroad. Ideas for funding:
Summit Plan includes your plan howto organize MeeGo Summit. Start a new Summit Plan using a template designed for it. Name your plan as 'MeeGo Summit $DOMAIN'.
I would use a template for the Summit Plan. See for example: use case template. Using a template for the Summit would also enable showing a timeline of the summits. Of course, for the timeline wiki needs an extension to be installed. Furthermore, using templates would unify the work of separate Teams and make the output consistent.
About knowledge base: what, why, where...
Knowledge-base includes notes about organizing aMeeGos national summits. All notes are written by different aMeeGos around the world. The knowledge-base includes 'DOs and DONTs'. 'DONTs' includes notes about mistakes for others to learn from. 'DOs' could also be labelled as best practices. In other words, what has been discovered useful.
Problem: common problem is that people are often reluctant to write notes to such knowledge-base. Or simply forget to do so. Knowledge tend to remain tacit without ever becoming explicit knowledge
For the sake of consistency the MeeGo summits should be named as MeeGo Summit <domain>. Short examples:
Longer example of Summit details:
MeeGo Summit UK, The Barbican, London May 7-8, 2011
Once the summit has been held, rename the your NMS wiki page to MeeGo Summit $DOMAIN $YEAR. For example MeeGo Summit FI 2011 and add it to the list of past Summits. Remove your NMS from the list of future MeeGo Summits. The experiences, mistakes and successes should also be written down to knowledge base (a sticky thread)
About Summit Team:
Normally members of the group are experienced community members with a passion towards MeeGo Networks and Summits. Group members are nominated by the Community. The group oversees the MeeGo Summit Teams without interfering their work unless necessary. Primary function is to ease the work of Summit Teams. In the beginning one aMeeGo could form the steering group. When the amount of Summits grow in the future, more members would be nominated to SSG.
NOTE: The list would be generated IF semantic extensions would be used as suggested.