Upgrade to Pro — share decks privately, control downloads, hide ads and more …

BUILDING REGIONAL MEEGO COMMUNITY – CASE MEEGO ...

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →

BUILDING REGIONAL MEEGO COMMUNITY – CASE MEEGO NETWORK FINLAND (MNFI)

Presentation given at MeeGO Conference 2011, San Francisco. It tells a tale of how MeeGo Network Finland was build from scratch.

Jarkko Moilanen, PhD

May 24, 2011

Transcript

16 slides
  1. BUILDING REGIONAL MEEGO COMMUNITY – CASE MEEGO NETWORK FINLAND (MNFI)

    Jarkko Moilanen, MeeGo Network Finland / Hermia Ltd
  2. 2 Content • Overview of MNFI • National and local

    level activity • About communication • About organizing Summits • Sum up
  3. 3 Current situation • 2 active local MeeGo networks (Tampere

    & Helsinki) + a few hibernating networks • Nearly 300 members • 16 local meetups since Sep 2010 • Organized (Apr 2011) 2-day MeeGo Summit FI
  4. 5 National level (MNFI) • Umbrella for local networks and

    activities • Teams (members from local networks and partners) • Responsible for Summit and bigger events • Co-operation with partners • Provides & maintains communication tools • Coordination, promotion and marketing • IRC community meetings (bi-weekly)
  5. 6 National level teams • Self organizing • Occasionally needs

    pushing (from community manager) • 2-10 members • Members intertwined, a lot of joint activity • Own mailing lists (and some have IRC channel)
  6. 8 National level activity • Summit (annual) • Bug munching

    one day event (planned) • Assembly Summer 2011 – joint booth with other Linux groups (planned) • App projects (starting) → meetup content
  7. 9 Local level - now • Independent (from each other

    & national level) • Main events are meetups (once a month) • Content varies (presentations to visits) • Own mailing lists (google) • Own 'homepage' (meetup.com) • commercial
  8. 10 Local level - future • Still independent • Organizers

    are part of national Events team • Meetups organized in MNFI portal • More project / hands-on oriented – less talking, more doing!
  9. 11 Communication - now • National IRC channel (#meego-fi) •

    Summit channel (#meego-summit-fi) • National mailing list (freelists.org) • Team mailing lists (meegonetwork domain) • Information collected to wiki.meego.com • Social media accounts
  10. 12 Communication - future • Information collected to national portal

    • Meetups (signups, details, location) • Teams and local networks related • Projects, issue tracking • Entry point to all information – Still some parts external
  11. 13 Organizing Summits • Possibility to unite ameegos regionally •

    Functions as a shared goal • Plans are needed, but change all the time • Requires local partners • Self-organizing teams
  12. 14 Sum up (1/2) • Let local networks be free!

    As long as... • Embrace cross-team/network memberships • Enhances information transfer • IRC is most common communication tool • Mailing list not so popular
  13. 15 Sum up (2/2) • Communication must be simple •

    Transparency in (nearly) everything • Builds trust • Summit: get external partners

More Decks by Jarkko Moilanen, PhD

Other Decks in Programming