Michael Kohler

Mozilla Switzerland – Community Meetup June 2016

Posted by in Mozilla, MozillaCH, MozillaParticipation, mozillareps

On June 20th the Swiss Mozillians met in Zurich to discuss the second half of the year. The goal was to come up with objectives for mozilla.ch that are aligned with the current Mozilla strategy and the Participation Team and Mozilla Reps goals.

At first we did a retrospective, here are the key results:

What should we stop doing?

  • Discussions on the mailing list
  • posting “meta” discussions on Github
  • focusing on initiatives we don’t have time for
  • excluding people from discussions (see “meta discussions”)
  • focusing on Zurich
  • creating single point of failures
  • missing to provide clear pathways to contribute when we have a talk

What should we start doing?

  • Create a central hub for all resources MozillaCH-related (in terms of “Get involved”)
  • Focus on a few single strengths we have instead of a lot of single initiatives we can only go so far for
  • Start non-linear discussions on discourse
  • Have more event locations to get to people that can’t come to Zurich or Lausanne
  • Be more clear about the strengths of single community members and support them with initiatives that fit into the general direction of Mozilla
  • Start using communication channels specific to the audience we want to reach

What should we continue doing?

  • Event organization works well
  • Github issues for tracking
  • Team work at meetups
  • Keeping things simple (not having a lot of bureaucracy hassle)

With that in mind, we came up with two objectives. Both are aligned with overall Mozilla strategy pieces. The first one is Core Strength, the second one is Prototyping the Future. None of these Key Results are easy to achieve, but we think that with these we can achieve a good base for the upcoming years.

Objective 1: Grow our core contributor strengths and be amazing at being visible in Switzerland

  • Key Result 1: We have at least 5 core contributors that are active on Discourse
  • Key Result 2: 30% of threads on Discourse are created by non Community Focus Group members
  • Key Result 3: At least 25 GitHub issues are created from a discussion on Discourse with clear steps on how to implement
  • Key Result 4: Have started an at least monthly meetup group around Developer Tools to have “hacking evenings”
  • Key Result 5: At least 3 persons are involved in organizing events
  • Key Result 6: At least 4 persons are involved in creating content for Twitter tweets and answering mentions
  • Key Result 7: The mozilla.ch website clearly reflects on where we want people to get involved in MozillaCH covering all functional areas provided on the Wiki page
  • Key Result 8: At least 80% of functional areas are covered by at least 2 contact persons

Objective 2: We are a driver in prototyping Firefox for the future

  • Key Result 1: We have started a monthly meetup group around Developer Tools to have hacking evenings, providing guidance to new people to get involved in hacking DevTools
  • Key Result 2: We have at least 2 hackathons for 2 different components
  • Key Result 3: We have at least 20 confirmed Nightly users who know how to submit bugs
  • Key Result 4: We are engaging at least 10 people in QA’ing Servo for specific websites
  • Key Result 5: We engage at least 2 persons to work on positron, spidernode or browser.html

What do you find intriguing? What would you like to know more about? Jump into a discussion on Discourse or participate in our GitHub Participation issue repository.

0

Alpha Review – Using Janitor to contribute to Firefox

Posted by in Mozilla, MozillaCH, MozillaParticipation, mozillareps

At the Firefox Hackathon in Zurich we used The Janitor to contribute to Firefox. It’s important to note that it’s still in alpha and invite-only.

Screen Shot 2016-05-05 at 14.37.23

The Janitor was started by Jan Keromnes, a Mozilla employee. While still in an alpha state, Jan gave us access to it so we could test run it at our hackathon. Many thanks to him for spending his Saturday on IRC and helping us out with everything!

Once you’re signed up, you can click on “Open in Cloud9” and directly get to the Cloud9 editor who kindly sponsor the premium accounts for this project. Cloud9 is a pure-web IDE based on real Linux environments, with an insanely fast editor.

Screen Shot 2016-05-05 at 14.38.23

Screen Shot 2016-05-05 at 14.38.50

At the hackathon we ran into a Cloud9 “create workspace” limitation, but according to Jan this should be fixed now.

Setting up

After an initial “git pull origin master” in the Cloud9 editor terminal, you can start to build Firefox in there. Simply running “./mach build” is enough. For me this took about 12 minutes for the first time, while my laptop still needs more than 50 minutes to compile Firefox. This is definitely an improvement. Further you won’t need anything else than a browser!

I had my environment ready in about 15 minutes if you count the time to compile Firefox. Comparing this to my previous setups, this solves a lot of dependency-hell problems and is also way faster.

Running the newly compiled Firefox

The Janitor includes a VNC viewer which opens a new tab and you can run your compiled Firefox in there. You can start a shell and run “./mach run” in the Firefox directory and you can start testing your changes.

Screen Shot 2016-05-05 at 14.49.08

Screen Shot 2016-05-05 at 14.50.20

Running ESLint

For some of the bugs we tackled at the hackathon, we needed to run ESLint (well, would be good to run this anyway, no matter what part of the code base you’re changing). The command looks like this:

user@e49de5f6914e:~/firefox$ ./mach eslint --no-ignore devtools/client/webconsole/test/browser_webconsole_live_filtering_of_message_types.js
0:00.40 Running /usr/local/bin/eslint
0:00.40 /usr/local/bin/eslint --plugin html --ext [.js,.jsm,.jsx,.xml,.html] --no-ignore devtools/client/webconsole/test/browser_webconsole_live_filtering_of_message_types.js

/home/user/firefox/devtools/client/webconsole/test/browser_webconsole_live_filtering_of_message_types.js
8:1   warning  Could not load globals from file browser/base/content/browser-eme.js: Error: ENOENT: no such file or directory, open '/home/user/firefox/browser/base/content/browser-eme.js'  mozilla/import-browserjs-globals
8:1   warning  Definition for rule 'mozilla/import-globals' was not found                                                                                                                     mozilla/import-globals
8:1   error    Definition for rule 'keyword-spacing' was not found                                                                                                                            keyword-spacing
18:17  error    content is a possible Cross Process Object Wrapper (CPOW)                                                                                                                      mozilla/no-cpows-in-tests

✖ 4 problems (2 errors, 2 warnings)

0:02.85 Finished eslint. Errors encountered.

As you might see from the input, running this in the Janitor environment results in not finding the Mozilla-specific rules. The reason here is that the eslint npm package is installed globally. Globally installed eslint can’t find the locally installed mozilla-eslint-plugin. In my opinion the easiest fix would be to not install it globally, just within the firefox directory (running “./mach eslint –setup”) while spinning up the instance should be enough here.

We could circumvent this problem by changing the global npm prefix and then running it with “/new/path/eslint …” so it doesn’t call the other one. In hindsight, we could just have installed it to the directory and then call it through node_modules.

Update, May 5, 15:09: Jan has has fixed this plugin issue :)

Creating a patch

Creating a patch is really easy, following the tutorial on MDN is enough. We were very happy to see that the moz-git-tools are already installed by default, so you can just create your own branch, checkin your changes and run “git format-patch -p -k master” to get a Git patch file. Since we need a Mercurial patch, you then run “git-patch-to-hg-patch” and you can upload the resulting file to Bugzilla and you’re set!

Those two commands could maybe be aliased by default so running “create-patch” or similar would directly do this for you to further decrease the work you need to do manually.

Seeing it in action

Conclusion

After some initial account problems, we didn’t really find any other bugs apart from the ESLint situation. Again, thanks a lot to Jan for providing us the environment and letting us test it. This will change the live of a lot of contributors! For now The Janitor supports contributions to Firefox, Chrome, Thunderbird, Servo and KDE. There is also a GitHub repository for it.

4

Firefox Hackathon Zurich April 2016

Posted by in Mozilla, MozillaCH, MozillaParticipation, mozillareps

Last Saturday we’ve held a Firefox Hackathon in Zurich, Switzerland. We’ve had 12 people joining us.

Introduction

At first I gave an introduction to Firefox and introduced the agenda of the hackathon.

Dev Tools Talk

After my talk we heard an amazing talk from Daniele who came from Italy to attend this hackathon. He talked about the Dev Tools and gave a nice introduction to new features!

Hackathon

Before the hackathon we created a list of “good first bugs” that we could work on. This was a great thing to do, since we could give the list to the attendees and they could pick a bug to work on. Setting up the environment to hack was pretty easy. We’ve used “The Janitor” to hack on Firefox, I’ll write a second blog post introducing you to this amazing tool! We ran into a few problems with it, but at the end we all could hack on Firefox!

We worked on about 13 different bugs, and we finished 10 patches! This is a great achievement, we probably couldn’t have done that if we needed more time to set up a traditional Firefox environment. Here’s the full list:

Thanks to everybody who contributed, great work! Also a big thanks to Julian Descolette, a Dev Tools employee from Switzerland who supported us as a really good mentor. Without him we probably couldn’t have fixed some of the bugs in that time!

Feedback

At the end of the hackathon we did a round of feedback. In general the feedback was rated pretty well, though we might have some things to improve for the next time.

40% of the attendees had their first interaction with our community at this hackathon! And guess what, 100% of the attendees who filled out the survey would be joining another hackathon in 6 months:

For the next hackathon, we might want to have a talk about the Firefox Architecture in general to give some context to the different modules. Also for the next hackathon we probably will have a fully working Janitor (meaning not alpha status anymore) which will help even more as well.

Lessions learned

  • Janitor will be great for hackathons (though still Alpha, so keep an eye on it)
  • The mix of talk + then directly start hacking works out
  • The participants are happy if they can create a patch in a few minutes to learn the process (Creating Patch, Bugzilla, Review, etc) and I think they are more motivated for future patches

All in all I think this was a great success. Janitor will make every contributor’s life way easier, keep it going! You can find the full album on Flickr (thanks to Daniele for the great pictures!).

2

Reps Council Working Days Berlin 2016

Posted by in Mozilla, MozillaParticipation, mozillareps

From April 15th through April 17th the Mozilla Reps Council met in Berlin together with the Participation Team to discuss the Working groups and overall strategy topics. Unfortunately I couldn’t attend on Friday (working day 1) since I had to take my exams. Therefore I could only attend Saturday and Sunday. Nevertheless I think I could help out a lot and definitely learned a lot doing this :) This blog posts reflects my personal opinions, the others will write a blog post as well to give you a more concise view of this weekend.

 

Alignment Working Group

The first session on Saturday was about the Alignment WG. Before the weekend we (more or less) finished the proposal. This allowed us to discuss the last few open questions, which are now all integrated in the proposal. This will only need review by Konstantina to make sure I haven’t forgotten to add anything from the session and then we can start implementing it. We are sure that this will formalize the interaction between Mozilla goals and Reps goals, stay tuned for more information, we’re currently working on a communication strategy for all the RepsNext changes to make it easier and more fun for you to get informed about the changes.

Meta Working Group

For the Meta Working Group we had more open questions and therefore decided to do brainstorming in three teams. The questions were:

  • Who can join Council?
  • Which recognition mechanisms should be implement now?
  • How does accountability look in Reps?

We’re currently documenting the findings in the Meta working group working proposal, but we probably will need some more time to figure out everything perfectly. Keep an eye out on the Discourse topic in case we’ll need more feedback from you all!

Identity Working Group

A new working group? As you see, I didn’t believe it at first and Rara was visibly shocked!

Fun aside, yes, we’ll start a new Working group around the topics of outwards communication and the Rep program’s image. During our discussions on Saturday, we came up with a few questions that we will need to answer. This Friday we had our first call, follow us in the Discourse topic and it’s not too late to help out here! Please get involved as soon as possible to shape the future of Reps!

Communication Session

On Sunday we ran a joint session with the rest of the Participation team around the topic “How we work together”. We came up with the questions above and let those be answered / brainstormed in groups. I started to document the findings yesterday, but this is not yet in a state where it will be useful for anybody. Stay tuned for more communication around this (communication about communication, isn’t it fun? :)). The last question around “How might we improve the communication between the Participation-Team and the Council?” is already documented in the Alignment Working group proposal. Further the Identity working group will tackle and elaborate further the question around visibility.

Reps Roadmap for 2016

Wait, there is a roadmap?

Yes!

At the end of our sessions we put up a timeline for Reps for all our different initiatives on a wall. Within the next days we’ll work on this to have it digitally per months. For now, we have started to create GitHub issues in the Reps repo. Stay tuned for more information about this, the current information might confuse you since we haven’t updated all issues yet! It basically includes everything from RepsNext proposal implementations to London Work Week preparations to Council elections.

Conclusion

This weekend showed that we currently have an amazing, hard-working Council. It also showed that we’re on track with all the RepsNext work and that we can do a lot once we all work together and have Working Groups to involve all Reps as well.

Looking forward to the next months! If you haven’t yet, have a look at the Reps Discourse category, to keep yourself updated on Reps related topics and the working groups!

The other Council members will write their blog post in the next few days as well, keep an eye out for link on our Reps issues. Once again, there are a lot of changes to be implemented and discussed, we are working on a strategy for that. We believe that just pointing to all proposals is not easy enough and will come up with fun ways to chime into these and fully understand them. Nevertheless, if you have questions about anything I wrote here, feel free to reach out to me!

Credit: all pictures were taken by our amazing photographer Christos!

0

Mozilla Switzerland IoT Hackathon in Lausanne

Posted by in Mozilla, MozillaCH, MozillaParticipation, mozillareps

On April 2nd 2016 we held a small IoT Hackathon in Lausanne to brainstorm about the Web and IoT. This was aligned with the new direction that Mozilla is taking on.

Preparation
We started to organize the Hackathon on Github, so everyone can participate. Geoffroy was really helpful to organize the space for it at Liip.ch. Thanks a lot to them, without them organizing our events would be way harder!

The Hackathon
We expected more people to come, but as mentioned above, this is our first self-organized event in the French speaking part of Switzerland. Nevertheless we were four persons with an interest in hacking something together.

Geoffroy and Paul started to have a look at Vaani.iot, one of the projects that Mozilla is currently pushing on. They started to build it on their laptops, unfortunately the Vaani documentation is not good enough yet to see the full picture and what you could do with it. We’re planning to send some feedback regarding that to the Vaani team.

In the meantime Martin and I set up my Raspberry Pi and started to write a small script together that reads out the temperature from one of the sensors. Once we’ve done that, I created a small API to have the temperature returned in JSON format.

At this point, we decided we wanted to connect those two pieces and create a Web app to read out the temperature and announce it through voice. Since we couldn’t get Vaani working, we decided to use the WebSpeech API for this. The voice output part is available in Firefox and Chrome right now, therefore we could achieve this goal without using any non-standard APIs. After that Geoffroy played around with the voice input feature of this API. This is currently only working in Chrome, but there is a bug to implement it in Firefox as well. In the spirit of the open web, we decided to ignore the fact that we need to use Chrome for now, and create a feature that is built on Web standards that are on track to standardization.

After all, we could achieve something together and definitely had some good learnings during that.

Lessions learned

  • Organizing a hackathon for the first time in a new city is not easy
  • We probably need to establish an “evening-only” meetup series first, so we can attract participants that identify with us
  • We could use this opportunity to document the Liip space in Lausanne for future events on our Events page on the wiki
  • Not all projects are well documented, we need to work on this!

After the Hackathon

Since I needed to do a project for my studies that involves hardware as well, I could take the opportunity and take the sensors for my project.

You can find the Source Code on the MozillaCH github organization. It currently regularly reads out the two temperature sensors and checks if there is any movement registered by the movement sensor. If the temperature difference is too high it sends an alarm to the NodeJS backend. The same goes for the situation where it detects movement. I see this as a first step into my own take on a smart home, it would need a lot of work and more sensors to be completely useful though.

 

 

 

1

Mozilla Switzerland Goals H1 2016

Posted by in Mozilla, MozillaCH, mozillareps

Back in November we had a Community Meetup. The goal was to get a current status on the Community and define plans and goals for 2016. To do that, we started with a SWOT-Analysis. You can find it here.

With these remarks in mind, we started to define goals for 2016. Since there are a lot of changes within one year, the goals will currently only focus on the first part of the year. Then we can evaluate them, shift metrics if needed, and define new goals. This allows us to be more flexible.

The goals are highly influenced by the OKR (Objective – Key Results) Framework. To document open issues that support this goal, I have created a repository in our MozillaCH GitHub organization. The goal is to assign the “overall goal” label to each issue. You can find a good documentation on GitHub issues in their documentation. There is a template you can use for new issues.

  • Objective 1: The community is vibrant and active due to structured contribution areas
  • Objective 2: MozillaCH is a valuable partner for privacy in Switzerland
  • Objective 3: There is a vibrant community in the “Romandie” which is part of the overall community
  • Objective 4: The MozillaCH website is the place to link to for community topics
  • Objective 5: With talks and events we increase our reach and provide a valuable information source regarding the Open Web
  • Objective 6: Social Media is a crucial part of our activities providing valuable information about Mozilla and the Open Web

CRhvD5rWwAEDmGp

We know that not all of those goals are easily achievable, but this gives us a good way to be ambitious. To a successful first half of 2016, let’s bring our community further and keep rocking the Open Web!

CL52IqpWIAAQN0Y

0

Mozillas strategische Leitlinien für 2016 und danach

Posted by in Mozilla, MozillaDeutsch

Dieser Beitrag wurde zuerst im Blog auf https://blog.mozilla.org/community veröffentlicht. Herzlichen Dank an Aryx und Coce für die Übersetzung!

Auf der ganzen Welt arbeiten leidenschaftliche Mozillianer am Fortschritt für Mozillas Mission. Aber fragt man fünf verschiedene Mozillianer, was die Mission ist, erhält man womöglich sieben verschiedene Antworten.

Am Ende des letzten Jahres legte Mozillas CEO Chris Beard klare Vorstellungen über Mozillas Mission, Vision und Rolle dar und zeigte auf, wie unsere Produkte uns diesem Ziel in den nächsten fünf Jahren näher bringen. Das Ziel dieser strategischen Leitlinien besteht darin, für Mozilla insgesamt ein prägnantes, gemeinsames Verständnis unserer Ziele zu entwickeln, die uns als Individuen das Treffen von Entscheidungen und Erkennen von Möglichkeiten erleichtert, mit denen wir Mozilla voranbringen.

Mozillas Mission können wir nicht alleine erreichen. Die Tausenden von Mozillianern auf der ganzen Welt müssen dahinter stehen, damit wir zügig und mit lauterer Stimme als je zuvor Unglaubliches erreichen können.

Deswegen ist eine der sechs strategischen Initiativen des Participation Teams für die erste Jahreshälfte, möglichst viele Mozillianer über diese Leitlinien aufzuklären, damit wir 2016 den bisher wesentlichsten Einfluss erzielen können. Wir werden einen weiteren Beitrag veröffentlichen, der sich näher mit der Strategie des Participation Teams für das Jahr 2016 befassen wird.

Das Verstehen dieser Strategie wird unabdingbar sein für jeden, der bei Mozilla in diesem Jahr etwas bewirken möchte, denn sie wird bestimmen, wofür wir eintreten, wo wir unsere Ressourcen einsetzen und auf welche Projekte wir uns 2016 konzentrieren werden.

Zu Jahresbeginn werden wir näher auf diese Strategie eingehen und weitere Details dazu bekanntgeben, wie die diversen Teams und Projekte bei Mozilla auf diese Ziele hinarbeiten.

Der aktuelle Aufruf zum Handeln besteht darin, im Kontext Ihrer Arbeit über diese Ziele nachzudenken und darüber, wie Sie im kommenden Jahr bei Mozilla mitwirken möchten. Dies hilft, Ihre Innovationen, Ambitionen und Ihren Einfluss im Jahr 2016 zu gestalten.

Wir hoffen, dass Sie mitdiskutieren und Ihre Fragen, Kommentare und Pläne für das Vorantreiben der strategischen Leitlinien im Jahr 2016 hier auf Discourse teilen und Ihre Gedanken auf Twitter mit dem Hashtag #Mozilla2016Strategy mitteilen.

 

Mission, Vision & Strategie

Unsere Mission

Dafür zu sorgen, dass das Internet eine weltweite öffentliche Ressource ist, die allen zugänglich ist.

Unsere Vision

Ein Internet, für das Menschen tatsächlich an erster Stelle stehen. Ein Internet, in dem Menschen ihr eigenes Erlebnis gestalten können. Ein Internet, in dem die Menschen selbst entscheiden können sowie sicher und unabhängig sind.

Unsere Rolle

Mozilla setzt sich im wahrsten Sinne des Wortes in Ihrem Online-Leben für Sie ein. Wir setzen uns für Sie ein, sowohl in Ihrem Online-Erlebnis als auch für Ihre Interessen beim Zustand des Internets.

Unsere Arbeit

Unsere Säulen

  1. Produkte: Wir entwickeln Produkte mit Menschen im Mittelpunkt sowie Bildungsprogramme, mit deren Hilfe Menschen online ihr gesamtes Potential ausschöpfen können.
  2. Technologie: Wir entwickeln robuste technische Lösungen, die das Internet über     verschiedene Plattformen hinweg zum Leben erwecken.
  3. Menschen: Wir entwickeln Führungspersonen und Mitwirkende in der Gemeinschaft, die das Internet erfinden, gestalten und verteidigen.

Wir wir positive Veränderungen in Zukunft anpacken wollen

Die Arbeitsweise ist ebensowichtig wie das Ziel. Unsere Gesundheit und bleibender Einfluss hängen davon ab, wie sehr unsere Produkte und Aktivitäten:

  1. Interoperabilität, Open Source und offene Standards fördern,
  2. Gemeinschaften aufbauen und fördern,
  3. Für politische Veränderungen und rechtlichen Schutz eintreten sowie
  4. Netzbürger bilden und einbeziehen.

 

0

German-speaking Community mid-term planning

Posted by in Mozilla, MozillaParticipation, mozillareps

Mozilla’s Participation Team has started to do “mid-term plannings” with a few focus communities back in September. The goal was to identify potential and goals for a six month plan which would then be implemented with the help of all the community. Since Germany is one of the focus markets for Firefox, it’s clear that the German-speaking community was part of that as well

Everything started out at the end of September, when we formed a focus group. Everybody was invited to join the focus group to brainstorm about possible plans we can set in stone to drive Mozilla’s mission forward. I’d like to thank everybody who chimed in with their ideas and thoughts on the German-speaking community and its future in our own Discourse category:

After the community meetup at the beginning of the year we had a lot of momentum which enabled us to get quite a lot done. Unfortunately this momentum has decreased over time, with a low since September (my opinion). Therefore our main areas we picked for our mid-term plans focused on internal improvements we can make, so we can focus on Mozilla top-organizational goals once we have implemented our improvements. This doesn’t mean that the German-speaking community won’t focus on product or mission, but it’s just not where we can commit as a whole community right now.

We have identified four areas we’d like to focus, which I will explain in detail below. Those are documented (in German) on a Wiki page as well to be as transparent as possible. We also asked for feedback through the community list and didn’t get any responses that would say anything against this plan.

Community Structure

In 6 months it’s clear for new and existing contributors who is working in which functional area and who to contact if there are any questions. New contributors know which areas need help and know about good first contributions to do.

Goals:

  • Understandable documentation of every contribution area the German-speaking community is active in. At least 60% of the areas are documented initially.
  • There are contact persons listed per contribution area with clear means of contact. At least 80% of the initially defined areas have at least one contact person for new contributors. For the three biggest areas there are at least two contact persons.
  • Handling of new contributors is defined clearly for all contribution areas, including responsibilities for individuals and groups. The onboarding process is clearly specified and we get at least two new long-term contributors per area. These new contributors can be onboarded within a few weeks with the help of the contact persons as mentors. Further mentors can be defined without them needed to be “contact persons”.

Website

In 6 months the mozilla.de website is the base for all information about Mozilla, its local community and contribution possibilities. Users of the website get valuable information about the community and find contribution possibilities which can be started without a lot of time investment to get used to the product. The website is the portal to the community.

Goals:

  • The website clearly states the possibilities to contribute to the German-speaking community (even if this is only a link to a well defined /contribute page)
  • The website lists all current Mozilla product and projects
  • The content defined in February 2015 is re-evaluated and incorporated as needed
  • The website is the main entry point to the community and promoted as such
  • Through the new website we get at least 10% of new contributors which found us trough it

Meetings / Updates

In 6 months discussions among the community members are well distributed. New topics are started by a broad basis and topics are being discussed by a wide range of contributors.

Goals:

  • There are at least 6 active participants per meeting
  • The meeting is structured for efficiency and brings in a reasonable ratio between discussion and update topics. There are enough enough discussion points so that updates can be treated as “read only” in 60% of the time.
  • The satisfaction of the participants who would like to join is increased by 30%
  • There are at least 10 unique participants in discussions on the mailing list

Social Media

In 6 months the German-speaking community is active on the most important social media channels and represents Mozilla’s mission and the community achievements to the public. Followers learn more about the community and learn about the newest updates and initiatives the community is supporting. Additionally these channels are used to promote urgent call-to-actions.

Goals:

  • The different channels are clearly separated and the user knows what content needs to be expected.
  • We have at least 1200 followers with @mozilla_deutsch, @MozillaDe and @FirefoxDe (not unique followers)
  • We have at least 750 “likes” on our Facebook page
  • We keep users engaged and updated with at least 8 tweets per month per channel
  • There are at least 3 maintainers for the different accounts

 

To track the progress we created a GitHub repository in our organization, where everybody can create issues to track a certain task. There are four labels which make it possible to filter for a specific improvement area. Of course, feel free to create your own issues in this GitHub repo as well, even if it might not be 100% tied to the goals, but every contribution counts!

I have put together a share-able summary slides for easy consumption in case you don’t want to forward the link to this blog post.

Even though I’m going to focus my time on the Mozilla Switzerland community, I will still help with and track the progress we’re doing with the mid-term plan implementations.

Feel free to get in touch with any of the focus group members linked above or the community-german mailing list in general for any questions you might have.

2

MozCoffee Framework – Wie organisiere ich ein Meetup?

Posted by in Mozilla, MozillaDeutsch

Einführung

Dieses Dokument soll als kurzes Tutorial dienen, um ein erfolgreiches Meetup zu organisieren. In diesem Dokument werden die wichtisten Punkte erläutert und einige Tipps gegeben, wie das ganze organisiert werden kann. Es besteht kein Anspruch auf Vollständigkeit. Zudem ist allen Mozillians selbst überlassen, wie die Organisation stattfindet.

Was ist das Ziel des Meetups?

Als erstes sollte man sich überlegen, was das Ziel für das Meetup ist. Mögliche Fragen dazu sind:

  • Ist es ein Meetup, um neue Mitwirkende in die Community zu integrieren?
  • Ist es ein Meetup, um sich innerhalb der bestehenden Community besser kennenzulernen und ein regelmässiger Ideenaustausch zu gestalten?
  • Soll dies “generell Mozilla” oder ist es eine Serie von möglichen, verschiedenen Themen?
  • Wem will ich was bieten? Dies kann Mitarbeiter im Büro, Kollegen/Freunde oder auch Fremde sein.

Anhand dieser Fragen, kann die Agenda mit möglichen Themen zusammengestellt werden.

Mögliche Themen / Formate

Für das Meetup gibt es grundlegend zwei mögliche Formate. Entweder kann es sich um eine “Diskussionsrunde” handeln, bei der allgemeine Themen besprochen werden. In den meisten Fällen kann dies als “Zusammenkunft gleicher Interessen” bezeichnet werden. So kann einfach auf Fragen von Teilnehmenden eingegangen werden. Dies ist die einfachere Version, welche weniger Organisationsaufwand benötigt und eignet sich gut für ein erstes Meetup. Hierfür benötigt man auch keine Agenda, höchstens ein paar Themen, die man ansprechen kann.

Das andere Format ist ein Vortrag-basiertes Meetup. Hier spielt es grundsätzlich keine Rolle, welche Themen besprochen werden. Wichtig ist, dass es sich um ein Thema handelt, bei welchem du dich wohl fühlst und gerne Auskunft gibst.

Mögliche Themen für Vorträge (kann von 10 bis 60 Minuten reichen):

  • Mozilla generell (Mission, Struktur, Gemeinschaft)
  • Was sind die möglichen funktionalen Gebiete, bei denen sich man engagieren kann?
  • Produkt-spezifisch, z.B. Firefox, Firefox OS, Webmaker, ..
  • Gebiet-spezifisch, z.B. UX, Design, Coding, Lokalisierung, ..
  • Web Developer spezifische Talks, wie z.B. “Demo Firefox Developer Tools”
  • Netzneutralität, Privatsphäre

Für beide Formate gilt: es macht nichts, wenn du auf eine Frage nicht antworten kannst. Auch “ich weiss, wen ich da fragen kann und ich werde mich bei dir melden” ist eine gute Antwort.

Mögliche Agenda mit Vorträgen

  • 18:30 Eintreffen
  • 18:40 kurze Intro zu “Was ist Mozilla?”
  • 18:45 Vortrag
  • xx:xx Fragerunde
  • danach gemütliches Beisammensein und Diskussionsrunde

Dies ist natürlich nur ein Vorschlag. Wenn es sich herausstellt, dass ein Treffen über den Mittag besser geeignet wäre, kann dies natürlich auch gemacht werden.

Was ist das gewünschte Resultat des Meetups?

Eine wichtige Frage ist, was das Resultat des Meetups sein soll.

  • Generelle Information über Mozilla, Produkte, etc, damit die Leute informiert sind?
  • Gewinnen von neuen Contributorn?
  • Mischung aus beidem?

Um die weitere Planung zu vereinfachen, sollte hier 2-3 Ziele definiert werden. Mögliche Beispiele sind:

  • Am Ende des Meetups wissen 5 weitere Personen für was Mozilla einsteht und wie man helfen könnte
  • Am Ende des Meetups sind 2 Personen interessiert bei Mozilla mitzumachen und wissen, wo sie beginnen können
  • 10 neue Personen werden Firefox zuhause runterladen und ausprobieren
  • 2 Personen erzählen ihren Freunden vom Meetup und laden diese zum nächsten Treffen ein

Grösse

Anhand des Themas kann die Grösse des Meetups ungefähr abgeschätzt werden. Am Anfang werden die Meetups etwas kleiner ausfallen, da diese noch nicht so bekannt sind. Dies ist aber absolut kein Problem! Auch kleinere Meetups können Spass machen und andere Personen wichtige Informationen über Mozilla vermitteln.

Die Grösse gegen oben ist offen, benötigt aber mehr Organisationsaufwand, je grösser das Meetup wird.

Geeignete Location finden

Anhand der Grösse und Thema kann nun ein geeigneter Ort für das Meetup gesucht werden. Dies sollte zur Sicherheit mind. 2 Wochen vor dem Meetup erledigt werden. So kann sichergestellt werden, dass alle Teilnehmer wissen, wo das Meetup stattfinden wird.

Level 1 (bis zu 8-10 Personen): Kleinere Meetups können ohne Probleme in Restaurants durchgeführt werden. Hierbei ist jedoch zu beachten, dass es sich nicht um ein zu überfülltes Restaurant handeln sollte, damit Gespräche möglich sind. Einander anzuschreien bringt nichts ;) Achtung: Reservierung nicht vergessen, damit auch genügend Platz vorhanden ist. Orte wie Starbucks funktionieren auch wunderbar.

Level 2 (für Vorträge oder ab 10 Personen): Für Vorträge oder bei grösseren Meetups wird zwingend ein eigener Raum benötigt. In den meisten Fällen haben Universitäten abends freie Räume, die man (wenn man lieb fragt), gerne für ein Meetup benützen darf. Als Alternative kann auch der Arbeitgeber gefragt werden, ob ein Sitzungszimmer dafür verwendet werden darf. Falls beides nicht möglich ist, können auch andere Firmen angefragt werden. Webentwickler-nahe Firmen hosten in vielen Fällen gerne Meetups.

Level 3 (längerfristig): wenn absehbar ist, dass es in Zukunft weitere, regelässige Meetups geben wird, ist es sinnvoll, sich nach einer längerfristigen Lösung umzusehen. Falls in “Level 2” eine Möglichkeit gefunden wurde, kann man den Anbieter des Raums fragen, ob man mit einer Frist von n Wochen da jederzeit (sofern verfügbar) den Raum haben dürfte.

Meetup durchführen

Hier gibt es nur etwas zu sagen: habt Spass! Die Durchführung soll kein Zwang sein, sondern euch und den Teilnehmer Spass machen.

Nachfolgende Arbeiten

Um Teilnehmer über neue Meetups zu informieren, ist es nötig, eine Kontaktmöglichkeit zu haben. Dies kann ein Newsletter sein, eine meetup.com Gruppe oder auch einfach eine eMail-Liste.

Damit potentielle Mitwirkende optimal unterstützt werden können, ist es am Anfang nötig, eine nahe Beziehung mit ihnen zu führen und so gut wie möglich zu unterstützen.

Periodizität

Solange die Meetups regelmässig stattfinden, spielt es keine Rolle, wie oft dies der Fall ist. Dies kann einmal im Quartal sein, oder einmal im Monat. Dies ist abhängig von der Zeit, die man für die Organisation aufwenden kann.

Werkzeuge / Promotion

Gibt es andere Stammtische, Meetups, etc in dieser Stadt?

Gibt es in deiner Stadt andere Stammtische oder Meetups? Das findest du u.a. über meetup.com raus. Falls es welche gibt, wäre es sinnvoll, einen davon zu besuchen, um zu sehen, wie das da gehandhabt wird. Ist bereits ein Datum für ein Mozilla Meetup bekannt, kann an diesen anderen Meetups auch Werbung dafür gemacht werden.

Gegebenenfalls gibt es auch die Möglichkeit, Vorträge bei anderen Meetups zu halten, um zu sehen, ob in dieser Stadt überhaupt Interesse besteht.

Meetup.com

Für regelmässige Meetups kann auf meetup.com eine Meetup-Gruppe erstellt werden. Weitere Informationen dazu gibt es direkt auf meetup.com.

Beispiele:

Twitter / Soziale Medien

Die Promotion kann, sofern für diese Stadt überhaupt sinnvoll, über Twitter und andere soziale Medien gemacht werden. Dabei ist es wichtig, dass man irgendwo eine Seite hat, die man in den Beiträgen verlinken kann. Diese Seite sollte mind. eine Beschreibung, Datum und Ort erwähnen.

Budget

Normalerweise sollte es nicht nötig sein, für ein Meetup Budget zu erhalten. Sollte dies aber trotzdem nötig sein, meldest du dich bei Michael Kohler, da dies über Reps läuft.

Swag

Sticker sind ein gutes Mittel, um Leuten eine Freude zu bereiten. Wenn diese auf einem Laptop landen und Firefox promoten, umso besser. Falls ihr für ein Meetup Swag benötigt, meldet euch bei Michael Kohler, da dies über Reps läuft.

0

Mozilla Tech Weekend in Berlin – November 28th & 29th

Posted by in Mozilla, MozillaParticipation, mozillareps

The Berlin Mozilla Community would like to invite all of you to the Mozilla Tech Weekend on November 28th 2015. There will be tech talks on Saturday and workshops on Sunday.

Location:

Kulturkantine
Saarbrücker Str. 24, Haus C, Berlin
http://www.kuka-berlin.de/lageskizze/

Sign up for free at http://www.meetup.com/Berlin-Mozilla-Meetup/events/226461969/

Schedule for Saturday 28th November:

  • Servo: Mozilla’s Parallel & Safe Next-Generation Browser Engine
  • Data reporting at Mozilla
  • Firefox OS: Why we exist
  • What’s new in Firefox

After the talks there will be some food and time to get in touch with developers and each other.

On Sunday there will be workshops on similar topics to follow up or get you all set up if you would like to start contributing to Mozilla projects. Sign-up for the workshops will be on-site on Saturday.

Cheers,
The Berlin Mozilla Community
https://lists.mozilla.org/listinfo/community-berlin

0