Meego Wiki
Views

Local MeeGo Networks/Regional MeeGo Summits

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Tasks)
Line 1: Line 1:
-
 
= National MeeGo Summits [NMS] (Draft)=
= National MeeGo Summits [NMS] (Draft)=
Line 105: Line 104:
* Create/join IRC channel for the Summit. Having a country/region specific channel enables the possibility to have discussions in local language as well as in English.   
* Create/join IRC channel for the Summit. Having a country/region specific channel enables the possibility to have discussions in local language as well as in English.   
* Keep the Summit plan updated
* Keep the Summit plan updated
 +
* postlists?
== Funding ==
== Funding ==

Revision as of 08:34, 23 September 2010

Contents

National MeeGo Summits [NMS] (Draft)

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.

Q: Could equivalent Maemo, MeeGo and/or Symbian events be combined together?

Things to consider while drafting this plan

  • Direct link with the MeeGo project. We can't leave a disconnected agency or guy run a show in some corner and call it a MeeGo conference just like that.
  1. every Summit must have a Summit Team which takes care of the core functions. Social pressure might minimize 'goofing'. Summit Team consists of Local MeeGo Network active aMeeGos around the national/regional area.
  • Autonomy and emancipation. But we can't be tutoring 20 regional events from the MeeGo core organization. This simply doesn't scale.
  1. Gather knowledge-base somewhere. People who organize Summits write down DOs & DON'Ts. Perhaps a sticky thread in the forum
  2. Use Summit Teams (see above)
  3. Separate controlling body (2-3 active aMeeGos from different LMNs) to maintain/guide the Summit Teams and make decisions. Might be necessary to have some kind control what Summit candidates qualify as 'good enough'. The controlling body would not interfere with the work of Summit Teams, but would have power to pull the plug if necessary. Name: Summit Steering Group
  1. Joint event?
  • Guarantees of success. Sure, nobody has a crystal ball but some checks need to be in place to avoid empty or badly organized MeeGo conferences.
  1. Require open planning. A good plan minimizes risks of failure. Risk is still always present.

Tasks

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

Future MeeGo Summits

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. 

Asia

Europe

  • MeeGo Summit FI (CANDIDATE)
  • your NMS

North America

South America


How to organize NMS in your region

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.

Gather sufficient amount of committed aMeeGos

  • use community forum and/or mailing list to find critical mass of aMeeGos from your region's Local MeeGo Networks. Start a new thread:

When you have gained the critical mass, organize the first meeting

  • can also take place in IRC.
  • create a IRC channel (#meego-summit-$DOMAIN, for example #meego-summit-fi) for the Summit to enable faster communication and participation.

Hold the first meeting

  1. Members of the Team (sample assembly here?)
  2. Date of NMS
  3. Summit venue (location, etc)
  4. Funding (simple budget)
  5. Program (Speakers, demos, etc.)
  6. Marketing plan(website if available, other issues? )
  7. Howto join the team (preferred tools such as Meetup.com etc.)

Add a new wiki page for your NMS.

  • Use template! which includes your draft described above. Naming policy: MeeGo Summit $DOMAIN. For example: MeeGo Summit FI

Add your Summit to Future MeeGo Summits

When you are confirmed that the conference will be arranged

Share the experiences - use knowledge-base

  • During and after the conference add notes of "do's and dont's" to where? Sharing your experiences will help others to organize future MeeGo Summits.

After the Summit

  • move your summit wiki page to archives (see more here).

Start from the beginning...


Tools

Communication

Sharing information and granting access to Summit related discussions and people is important. Suggestions to enhance communication:

  • Create/join IRC channel for the Summit. Having a country/region specific channel enables the possibility to have discussions in local language as well as in English.
  • Keep the Summit plan updated
  • postlists?

Funding

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

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.

Knowledge Base

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

Naming the Summits

For the sake of consistency the MeeGo summits should be named as MeeGo Summit <domain>. Short examples:

  • MeeGo Summit FI
  • MeeGo Summit US
  • MeeGo Summit DE

Longer example of Summit details:

MeeGo Summit UK, The Barbican, London May 7-8, 2011

After the Summit

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)

Teams & roles

Summit Team

About Summit Team:

  1. functions and purpose
  2. examples of roles

Summit Steering Group [SSG]

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.

Past MeeGo Summits

NOTE: The list would be generated IF semantic extensions would be used as suggested. 

Asia

Europe

  • MeeGo Summit FI 2010 (just an example)
  • your NMS

North America

South America

Personal tools