Participation/Community Spaces/Best Practices

Best Practices of Community Space Initiative

"Keyholder" system

Goal: To organized a group of core contributors to manage the space and keep it transparent.

In Taipei, new keyholder candidate need to go thought a voting process:

• The candidate needs to be a vouched Mozillian, and nominated by at least one of the current keyholders.
• The candidate needs to get votes from more then half of the Mozillians who had visited the space in the past 3 months.
• 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 part-time with other open culture communities such as Wikipedia, the OSM community and other local open source communities.

• This fills all the available spots, optimises the usage of the space, and share the free time with other friendly communities
• It broadens our contributor base but also make it more cost-efficient.
• Once they share this space, they will share a sense of 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 have similar discussions on a regular basis. A few conditions could be:

• Does it align with Mozilla's mission?
• Does it 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 benefit financially from the event?

Case Study: 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.