Participation/Community Spaces/Best Practices

Best Practices of Community Space Initiative

"Keyholder" system

• Organized a group of core contributors to managing the space and keep it transparent.
• In Taipei, new keyholder candidate need to go thought a voting process:
  • The candidate need to be a vouch Mozillians, and nominate by at least one of the current keyholders.
  • The candidate need to get votes from more then half of the Mozillians who had visit the space in the past 3 monthes.
  • We vote for new keyholders on Hackpad, check https://moztw.hackpad.com/-Keyholder-FourDollars-QWVujvzPSVX for example. The candidate will also write what (s)he willing to do in the space.

Work with other local FLOSS communities

• In Taipei, we share the space partial time with other open culture community such as Wikipedia, OSM community and other local open source communities.
  • We couldn't have any chances to fill all the available spot, and share the free time with other friendly communities can not only broaden our contributor base but also make it more cost-efficiency.
  • Once they share this space, they will feel belonging.
• Keyholders in Taipei have discussed about the events we do / don't want to have in the space , and we suggest that every space do the same. A few conditions could be:
  • Is it have to be fully OpenSource-related?
    • Say you want to teach people about MS PowerPoint and your teaching materials will be release under CC-BY license.
  • Can the event-facilitators get benefit financially via the event?

Special Case: Someone was willing to host a event to teach kids programming. Though the event is free of charge, the teach materials was modified from CC:BY-SA resources. Since the teacher refuse to release her modified version under the same license after a long email discussion, we rejected her application.