mozilla / community-spaces

INACTIVE - http://mzl.la/ghe-archive - Tracking the work done in our Mozilla Community Spaces around the world

Mozilla Community Spaces

Tracking the work done in our Mozilla Community Spaces around the world. Find out more at: https://wiki.mozilla.org/Participation/Community_Spaces

community-spaces's Issues

Request Discourse Category

As I wrote on Telegram yesterday:

I think it is a good idea to setup a Discourse category for Community Spaces
Under the Participation category perhaps?
https://discourse.mozilla-community.org/c/participation
Or as a separate high-level category perhaps, so we can have per-city sub-categories?

2016 Wrap-up Blog Post

While we finalise the charts in issue #18, we can start filling out the blog post. I've made a start here:

https://docs.google.com/document/d/1-cMJqR9MjTb-gESs9FFY5ktgL_4LHySygydYS4rECXM/edit?usp=sharing

@yofiesetiawan @irvin @bobreyes Please help me fill it out. In particular, please add your thoughts in the 'Happenings and Highlights' section. The type of information that would be good is:

• How you contributed to certain campaigns (marketing, policy, dev engagement, Activate, ...)
• Examples of events that stood out, and the reasons why
• Strengths of your space
• Challenges you have been having
• What you would like to see in 2017

Standardise Registration and Survey Forms

For reference here are 2 working docs:

@bobreyes : https://docs.google.com/document/d/1bXXuPCdvajju9bt6rBH6lXTUZl9GzfzjcA-NKd3xRRQ/edit
@yofiesetiawan : https://docs.google.com/document/d/1nVYFoT7maDu33EZK9D-sBh4L4YGDTV6EU21SHR2TRFo/edit

We are solving for 2 things here, it seems.

1. Registration on arrival at the venue
2. Gathering sentiment and stats after the visit

I think Manila has #1 solved because of building requirements. Let's try and standardise here.

A few more thoughts:

1. How can we provide incentives for people to fill it out?
2. The registration on entry is the source of truth for numbers, as not everyone will fill out the survey after. So we need to capture there is they are new or return visitors.
3. I like the idea of having a single form (e.g. http://survey.mozspaces.org/) for all spaces. Do we know anyone who could work on this? We might need to ensure that random people coming to the form don't fill it out (spam) -- maybe a unique id (assigned to each event) passed to it unlocks it or something like that.
4. We need to ensure, for the next 3-6 months at least, that we are surfacing up numbers and sentiment around developer focused events.

Meetup mentor for Firefox DevTools meetups

Identify, confirm, and schedule a Q&A session with a mentor for Firefox DevTools meetups.

Explore Innovation Lab idea for India Spaces with Innovation Team

In Berlin a few weeks ago we (Participation and Innovation teams) talked about the possibility of working with our communities in India to start 1-2 innovation spaces. I'm starting this conversation to see if we want to pursue this.

There are plenty of models for hubs (business incubator, co-working, maker space, ...) but what we need to figure out is what model we want to use that is best for our needs, provides the best value to volunteers, and contains Mozilla values from the ground up.

Some very broad framing questions:

1. Is India the right place to start?
2. What criteria should we have for applications?
3. What would the first 6-12 months look like in the space?

Jakarta Opening Blog Post

Blog post on https://blog.mozilla.org/community about the successful opening event, and what the Space means in the local and global context.

Can use some of @yofiesetiawan 's photos, with permission.
https://flic.kr/s/aHskwtBAYH

• @rara79 @alamanda

Setup repository for sharing materials

One thing we discussed in London is where to share resources that are common among all spaces, or where any space can store their materials.

One solution is to use this github repository. We could start with a folder for each space, and sub-folders for docs, presenations, and so on. And then we would have a 'global' folder with useful assets for all spaces.

Open to alternative proposals.

@bobreyes @yofiesetiawan @bobchao @rara79 @alamanda @irvin

Manila - June 2016 Report

Compile and publish the space report for Manila, for June 2016.

Aggregration of Space Metrics

We are now getting monthly metrics from the community spaces. Now is the time to set up somewhere to capture them in one place to crunch the numbers, and to show visualisations and trends over time for analysis and sharing.

The first pass may be a spreadsheet, but I'll consult with the Part Infra team to see if they have any suggestions / tools we can use.

April 2016 Blog Post

Aggregate April blogs post into summary blog post pulling out the highlights.

Manila - May 2016 Report

Compile and publish the space report for Manila, for May 2016.

Manila - April 2016 Report

Compile and publish the space report for Manila, for April 2016.

Taipei - April 2016 Report

Compile and publish the space report for Taipei, for April 2016.

Taipei - June 2016 Report

Compile and publish the space report for Taipei, for June 2016.

Meetup mentor for Rust meetups

Identify, confirm, and schedule Q&A session with a mentor for Rust meetups.

Meetup mentor for Connected Devices meetups

Identify, confirm, and schedule Q&A session with mentor for Connected Device meetups.

Jakarta - May 2016 Report

Compile and publish the space report for Jakarta, for May 2016.

Taipei - May 2016 Report

Compile and publish the space report for Taipei, for May 2016.

Community space report

Objective Goal:

Nice graphs and charts for April-December 2016 data gathered by the space stewards.

Related documents and links

• Data dashboard https://docs.google.com/spreadsheets/d/1h8nsKT00FVrRLUu1-2hpM-p0GD3eHztYB5AqdKm0suw/edit#gid=2022809174

Item list:

• Pie chart showing total number of events all spaces (R:)
• Pie chart showing total number of events per space (R:)
• Pie chart showing total number of attendees in all spaces (R:)
• Pie chart showing total number of attendees per space (R:)
• Total number of new attendees (R:)
• Total number of returning attendees (R:)
• Recap page (R:)

Related Issues

[Reference meta issues and past issues] #

Meetup mentor for Firefox Engineering meetups

Identify, confirm, and schedule Q&A session with mentor for Firefox Engineering meetups.

Jakarta - April 2016 Report

Compile and publish the space report for Jakarta, for April 2016.

Jakarta - June 2016 Report

Compile and publish the space report for Jakarta, for June 2016.

Update Affiliate Spaces SOP

This document is out of date and was designed for the first wave of pilot spaces to get budget:

https://wiki.mozilla.org/ReMo/SOPs/Affiliate_Space

I also propose a terminology change.

Community Spaces = Official community spaces are ones where Mozilla provides funding for month-to-month costs such as rent and utilities, and provides guidance on activities in the space.

Affiliate Spaces = Affiliate community spaces are ones where Mozillians use other financial means to support a physical space that they work out of.

New documentation based on this is being tracked in issue #1

Meetup mentor for Web Development meetups

Identify, confirm, and schedule Q&A session with mentor for Web Development meetups.

Events Dashboard for Spaces

Objective Goal:

To show statistics on events in community spaces (primarily dev events) to determine the health of the developer engagement program and the spaces in general

R: @couci
A: @brianking
C: @yofiesetiawan
I:

Tasks & To Dos Related to This Project:

• Tracking events spreadsheet: https://docs.google.com/a/mozilla.com/spreadsheets/d/1h8nsKT00FVrRLUu1-2hpM-p0GD3eHztYB5AqdKm0suw/edit?usp=sharing

Sub-Goal Success:

• Update spreadsheet with latest numbers - end May ( @rara79 @bobchao @bobreyes )
• Determine event types for dropdown ( @brianking )
• Design advice ( @yofiesetiawan )
• Build dashboard ( @couci )

Related Issues & Links:

[Reference meta issues and past issues] #

Create New Wiki Page

Right now we have:
https://wiki.mozilla.org/Contribute/WPR/Community_Space_Initiative

TODO:
Create new page with updated information about the project, under the Participation section of the wiki.

Wiki changes

FYI: The following changes were made to this repository's wiki:

• defacing spam has been removed

• Restricting write access to contributors is strongly encouraged. Please make that change (documentation).

These were made as the result of a recent automated defacement of publically writeable wikis.

Meetup mentor for Python meetups

Identify, confirm, and schedule mentor for Python meetups.

CODE_OF_CONDUCT.md file missing

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)