https://wiki.mozilla.org/api.php?action=feedcontributions&user=Bacharakis&feedformat=atomMozillaWiki - User contributions [en]2024-03-29T12:38:15ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=Community:SummerOfCode19:Brainstorming&diff=1207263Community:SummerOfCode19:Brainstorming2019-02-05T16:57:47Z<p>Bacharakis: Update mentor's name</p>
<hr />
<div>Once again, Mozilla intends to apply to participate in Google's Summer Of Code.<br />
<br />
Mozilla community members, please submit proposals here for 2019 Google Summer of Code projects with Mozilla. This page is for brainstorming - as we approach the deadline, those ideas that are accepted will be transferred to the [[Community:SummerOfCode19|official list]].) <br />
<br />
Our application for summer of 2019 goes into Google on '''February 4th''', so get those project ideas in well ahead of time.<br />
<br />
<b>Are you a student looking to apply to GSoC with Mozilla?</b> Your first stop should be the [[Community:SummerOfCode19|official list of ideas]]. This page is full of weird ideas, only some of which will make the cut. It could be that they are not properly defined, the wrong size, or don't have a mentor. That makes them less likely to get accepted. You <i>can</i>, of course, also submit your own ideas - you don't have to put an idea on this page and get it 'made official' in order to send in a proposal for it.<br />
<br />
==How To Write A Good Project Proposal==<br />
<br />
Before adding an proposal to this list, please consider the following:<br />
<br />
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.<br />
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.<br />
* '''Do your research'''. Support the idea with well-researched links.<br />
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment. <br />
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know who you are, leave contact details.<br />
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.<br />
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.<br />
<br />
==Suggestion List==<br />
<br />
[[SummerOfCode|Here are the ideas lists from previous years]].<br />
<br />
Proposals can be in almost any part of the Mozilla project, though they do need to be mostly focused on code.<br />
<br />
Here are the proposals. Feel free to add a new one.<br />
<br />
== 2019 Proposed Project List ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details <br />
! Skills Needed <br />
! Reporter <br />
! Mentor(s) <br />
! Additional Comments<br />
|-<br />
| Improve Python in the browser<br />
| The [https://github.com/iodide-project/pyodide pyodide] project allows the Python scientific stack to run in the browser by compiling it to WebAssembly. Help make stuff run better and faster there.<br />
| Python and JavaScript. Can learn the WebAssembly parts as you go.<br />
| [https://mozillians.org/en-US/u/mdboom/ Michael Droettboom]<br />
| [https://mozillians.org/en-US/u/mdboom/ Michael Droettboom]<br />
| There are a number of specific projects we have in mind, but are open to other proposals that are within scope and seem practical within the timeframe. (1) Implement matplotlib's display on top of Web APIs (HTML5 Canvas, etc.) This would allow us to avoid shipping a whole separate rendering engine to the browser. (2) Build WebAssembly support into the conda packaging system to make it easier to distribute new compiled packages for Pyodide. (3) Make multi-dimensional arrays sharable between Python and Javascript. See Pyodide's [https://github.com/iodide-project/pyodide/issues list of issues] for additional ideas. About the mentor: Michael Droettboom is a Staff Data Engineer at Mozilla, and a former lead developer of matplotlib with years of experience building the Python scientific ecosystem.<br />
|-<br />
| ReSpec <br />
| [https://github.com/w3c/respec/ ReSpec] is a JS-based tool used to write W3C Specifications (Web Standards) that is widely used by the Web Standards Community. With 6+ years of development, it's heavily depended upon by the W3C community at large (of which Mozilla is an active participant). ReSpec's code is in need of some modernization, optimizations, and bug fixes - and we could use your help! In this project, you would have the opportunity to make ReSpec's UI more accessible, making it leaner and faster using distributed processing with Web Workers, and/or adding new features to make the lives of W3C spec Editor's better. <br />
| JavaScript, HTML, CSS. <br />
| [https://mozillians.org/en-US/u/mcaceres/ Marcos Caceres]<br />
| [https://mozillians.org/en-US/u/mcaceres/ Marcos Caceres]<br />
| ReSpec offers students the opportunity to work on a large code base that has extensive real world use and impact. The project offers students an extensive range of problems to tackle, from UI design, to concurrent processing (using Web Workers to do distributed text processing), dealing with accessibility and internationalization, writing and learning about unit and integration tests, security, code review, etc. - as well as exposure to the W3C and the web standards community, this project also aims at teaching students about how web standards are put together. To determine if this is a project you would like to be part of, see the [https://github.com/w3c/respec/issues/ list of issues] you could work on. It's a great opportunity to learn about all aspects of open source software development, but with the freedom to take on small to large challenges over the Summer (depending on your skill level and level of confidence). About the mentor: Marcos Caceres is a Staff Engineer at Mozilla who has been working on Web Standards for over a decade. Marcos is the lead maintainer of ReSpec. Marcos has extensive experience mentoring developers and has previously successfully mentor a GSO student. <br />
|-<br />
| Ship Public Suffix List (PSL) over Remote Settings<br />
| The list of public domain suffixes (DNS) is shipped with every release, with no way to update it on long term releases for example.<br />
Now that Remote Settings has become a solid solution to ship data, we could use it to publish updates of the PSL.<br />
The task consist in migrating the current client code to read from Remote Settings instead of a file, and implement a scheduled job (like Python) to push updates automatically (most likely compiled as a DAFSA file) <br />
| JavaScript and some Python basics <br />
| [https://mozillians.org/en-US/u/leplatrem/ Mathieu Leplatre]<br />
| [https://mozillians.org/en-US/u/leplatrem/ Mathieu Leplatre]<br />
| https://bugzilla.mozilla.org/show_bug.cgi?id=1083971<br />
|-<br />
| [https://github.com/marco-c/bugbug bugbug]<br />
| A platform for machine learning projects applied on Bugzilla, VCS and other software development data.<br />
| Python<br />
| [https://github.com/marco-c Marco Castelluccio] (FIRST_NAME@mozilla.com)<br />
| [https://github.com/marco-c Marco Castelluccio] (FIRST_NAME@mozilla.com)<br />
| The project will involve one or more of:<br />
i) building additional classifiers (e.g., to detect bugs with no steps to reproduce, or to suggest a developer to assign to a bug, and so on);<br />
<br />
ii) improving accuracy/precision/recall of the existing classifiers by implementing other machine learning techniques (e.g., by using convolutional neural networks or recurrent neural networks);<br />
<br />
iii) improving accuracy/precision/recall by implementing additional feature extraction steps or making the already existing ones better.<br />
|-<br />
| Make the Firefox WebAuthn Soft Token a Real Thing<br />
| The Web Authentication Soft Token provides second-factor login support without needing a Security Key dongle. It would be very usable if the Soft Token were a) synchronized across an account using Sync, b) could be controlled via a Web Extension, and perhaps c) had some UI. If these things were true, most people could get quality authentication support without buying another device.<br />
| C++, Javascript, Basic cryptography<br />
| [https://mozillians.org/en-US/u/jcjones/ J.C. Jones] <br />
| [https://mozillians.org/en-US/u/jcjones/ J.C. Jones] <br />
| https://wiki.mozilla.org/Security/CryptoEngineering#Web_Authentication<br />
|-<br />
| WebSocket Monitor<br />
| Support for WebSocket monitoring and inspection in Firefox DevTools.<br />
| JavaScript/React<br />
| [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko]<br />
| [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko]<br />
| This project aims at providing support for WebSocket monitoring and inspection in Firefox DevTools. The feature should be built on top of the existing Network panel UI and responsible for visualizing data sent through WebSocket connection (i.e. WS frames). The user should be able to use the UI to see as well as analyse the data (search, filter, etc.).<br />
* [https://docs.google.com/document/d/1ruHk-BA3cqzU7VHoVltnAwWt_2OXKOOAI4nTHwYllzk/edit# Detailed Project Description]<br />
|-<br />
| Helpful crash reporter<br />
| The crash reporter only allows users to send crash reports but in some cases it might help the user diagnose the crash and solve it on his/her own<br />
| C++, Javascript<br />
| [https://mozillians.org/en-US/u/gsvelto/ Gabriele Svelto] <br />
| [https://mozillians.org/en-US/u/gsvelto/ Gabriele Svelto] <br />
| There's a few things that could be implemented:<br />
* A quick test of the memory owned by the crashed process (such as those in [http://www.memtest.org/ memtest86+]) might catch faulty memory, a common cause for crashes<br />
* The crash reporter client might try and validate Firefox files which can sometimes become corrupted (usually because of hardware issues). If they are it can prompt the user to re-install Firefox<br />
* Many crashes are caused by buggy graphics drivers, while we blacklist the most egregious offenders we can't cover them all. The crash reporter might identify a faulty driver (if a bug for it has already been filed) and point the user to up-to-date drivers<br />
* For crashes caused by known bugs it should be possible to point the user to the bug filed on bugzilla<br />
|-<br />
| Debugger Inline Variable Preview<br />
| When the Firefox DevTools debugger is paused, users can hover over variables to get a useful tooltip that details the variable's value at that time. While this popup is very informative, one valuable enhancement would be displaying relevant contextual variables values alongside the variable inline, alleviating the need for tooltips and allowing the user to more quickly get the information they need. The applicant will work alongside the Debugger's team to implement this feature based on UX mockups and be given space to share and implement ideas of their own.<br />
| Javascript<br />
| [https://mozillians.org/en-US/u/davidwalsh/ David Walsh] <br />
| [https://mozillians.org/en-US/u/davidwalsh/ David Walsh] <br />
| <br />
|-<br />
| GitHub Checks Support Improvements<br />
| [https://github.com/taskcluster/taskcluster Taskcluster] currently supports reporting results to the [https://github.com/taskcluster/taskcluster/pull/129/checks?check_run_id=54327344 GitHub Checks API], but only reports success or failure. Let's add support for showing [https://developer.github.com/v3/checks/runs/ annotations] - snippets of log output, more detailed results, images, and so on. We can even add support for additional "actions" on the task, such as re-running with debugging enabled.<br />
| Server-side JS<br />
| [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell] <br />
| [https://mozillians.org/en-US/u/ireneOwl/ Irene Storozhko], [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell] <br />
| <br />
|-<br />
| Support GitHub Logins in Taskcluster<br />
| [https://github.com/taskcluster/taskcluster Taskcluster] currently supports logging in with Auth0, the Mozilla login system. We would like to make it useful outside of Mozilla, and most other users do their development on GitHub, making GitHub logins a good solution. This project would involve adding support for signing in with GitHub, as well as the more challenging task of assigning appropriate permissions to users based on the setup of their GitHub account.<br />
| Server-side JS<br />
| [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell] <br />
| [https://mozillians.org/en-US/u/ireneOwl/ Irene Storozhko], [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell] <br />
| <br />
|-<br />
| Improve Webdriver support in Servo<br />
| [https://github.com/servo/servo/ Servo] currently supports a minimal subset of the [https://w3c.github.io/webdriver/ Webdriver standard]. We would like to improve Servo's support, and verify its correctness by passing a [https://github.com/web-platform-tests/wpt/tree/master/webdriver set of automated tests]. This project would involve writing Rust code to extend the webdriver server inside of Servo, as well as JavaScript and Python to support the [https://web-platform-tests.org/writing-tests/testdriver.html testdriver.js] testharness.<br />
| Familiarity with Python & JavaScript; interest in learning Rust<br />
| [https://mozillians.org/en-US/u/jdm/ Josh Bowman-Matthews] <br />
| [https://mozillians.org/en-US/u/jdm/ Josh Bowman-Matthews]<br />
| [https://github.com/servo/servo/wiki/Support-Webdriver-based-tests-project Project description]<br />
|-<br />
| Support importing Instruments profiles in perf.html<br />
| [https://github.com/devtools-html/perf.html/ perf.html] visualizes performance data recorded from various performance analysis tools. It is a tool designed to consume performance profiles from Gecko Profiler but can visualize any profiler able to output JSON. It currently supports Gecko, Chrome and perf profile formats. Instruments is a performance analyzer that comes with Xcode. This project would involve adding support for Instruments profile import in perf.html.<br />
| Familiarity with JavaScript & React<br />
| [https://mozillians.org/en-US/u/canaltinova/ Nazım Can Altınova]<br />
| [https://mozillians.org/en-US/u/canaltinova/ Nazım Can Altınova]<br />
| https://github.com/devtools-html/perf.html/issues/1138<br />
|-<br />
| Common Voice - WebAssembly MP3 Encoding<br />
| Currently Common Voice doesn’t support Safari, which is also why we have an iOS app. The only reason being the missing MediaRecorder API. It could be polyfilled (rebuilt in “userspace”) by compiling an MP3 encoder to WebAssembly. I’ve tried that a couple of times, but never had enough time to fix the opaque bugs happening in Safari. This could also be turned into its own library and would be a nice story overall of how WASM can help with WebCompat and missing APIs.<br />
| JavaScript<br />
| [https://mozillians.org/u/gweber/ Gregor Weber]<br />
| [https://mozillians.org/u/gweber/ Gregor Weber]<br />
| [https://github.com/mozilla/voice-web/issues/469 This GitHub issue] lines out some thoughts around how to implement it and you can find references to closed PRs which tried implementing it in various ways.<br />
|-<br />
| Common Voice - Voice Wave Avatar<br />
| We’d like our users to have unique(ish) avatars based either on the characteristics of their voice or a visualization of how their name (or an utterance of their choosing) is pronounced. It could also be a combination of the two ideas. We’re very open to explore this space together, though the a candidate should have some knowledge in sound theory.<br />
| JavaScript, Some knowledge of sound theory<br />
| [https://mozillians.org/u/gweber/ Gregor Weber]<br />
| [https://mozillians.org/u/gweber/ Gregor Weber]<br />
|-<br />
| Tab Manager menu in Firefox <br />
| This project will extend the tab overflow menu - which shows tabs not visible in the browser's tab strip - to allow management of all open tabs across all browser windows. The selected student will be working directly in the Firefox codebase to add functionality and new menu structures to make this easily accessible for end users. <br />
| JavaScript, CSS, and web experience<br />
| [https://mozillians.org/en-US/u/sfoster/ Sam Foster], [https://mozillians.org/en-US/u/bbell/ Bryan Bell]<br />
| [https://mozillians.org/en-US/u/sfoster/ Sam Foster]<br />
| We have [https://mozilla.invisionapp.com/share/4SNCEPDUEZ6#/screens UX mockups] for this feature, which could be broken into two phases. We also have a [https://bugzilla.mozilla.org/show_bug.cgi?id=1480542 bug on file], where discussion has begun. While working on this you will become very familiar with the Browser Toolbox, our own "Inspector" tool for the browser user-interface, as well as writing automated tests for the new feature you're adding. The existing tab overflow code lives in our [https://searchfox.org/mozilla-central/source/browser/base/content/browser-allTabsMenu.js browser-allTabsMenu.js] file, which will be the starting point for the new tab manager. You can look at this and the existing tab code to get an idea of how this currently works. <br />
-<br />
|-<br />
|-<br />
| Firefox Reader Redesign<br />
| The design of Firefox’s Reader Mode has languished behind as Quantum has implemented the new Photon Design System. The interface needs to be rebuilt using new visual and interaction styles to match the Photon Design System.<br />
| JavaScript, CSS, and web experience<br />
| [https://mozillians.org/en-US/u/awallin/ Abraham Wallin]<br />
| [https://mozillians.org/en-US/u/eeejay/ Eitan Isaacson]<br />
| [https://mozilla.invisionapp.com/share/87N9YQYCTJZ#/315073983_Reader_View_Redesign UX Mockups] for this feature are available with visual bugs have been reported [https://bugzilla.mozilla.org/show_bug.cgi?id=1187696 here] and [https://github.com/devtools-html/ux/issues/5 here]. Functional bugs and feature enhancements have been documented [https://github.com/mozilla/readability/issues?q=is%3Aissue+is%3Aopen+label%3Areader-mode-has-issues here], [https://github.com/mozilla/readability/issues?q=is%3Aissue+is%3Aopen+label%3Ashould-be-readerable here], [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=comp%3Areader%20prod%3DToolkit%20whiteboard%3Areadability-algorithm&list_id=14539703 here], and [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=comp%3Areader%20prod%3DToolkit%20whiteboard%3Aisreadable&list_id=14539704 finally here]. The request is for an engineering student to implement the designs and tackle the queue of bugs/enhancements within the Firefox code base. Mentors will support with prioritization, design direction/assets, and technical guidance.<br />
<br />
<br />
|-<br />
| An Android file downloader designed for Emerging Markets<br />
| A lesson learned thanks to our UX team is in Emerging Markets the data plan is dynamic: in late nights we have the most affordable bandwidth. Here's the question: Why not schedule big files and videos and have them downloaded when you're sleeping? The mvp would be an App which we can send urls to. After receiving these urls the App either downloads it directly or defer it to late night. As there are more and more background restrictions enforced on new Android APIs, this should be a fun and challenging journey.<br />
<br />
A stretch goal would be to embed this downloader in our browser for Emerging Markets, Firefox Lite. Firefox Lite is not satisfied with the current Android Download Manager in several ways: We'd like to give users the ability to pause/resume a download, we'd like to download a file directly to SDcard (opposed to download it to the main storage and move it into SDcard).<br />
<br />
We've also prepared an even more ambitious mission for those who want tough challenges: Design the app and make it dynamic deliverable. With aabs we can satisfy both light and heavy users by defaulting Android Download Manager as the download tool and prepare the aforementioned downloader dynamically so that Firefox Lite itself is still minimized in terms of disk size. Nevin and mTwTm are Android developers who can provide assistance to Android App design.<br />
| Android Java/Kotlin<br />
| [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)]<br />
| [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)] (mTwTm@mozilla.com), [https://github.com/cnevinc/ Nevin Chen] (nevin@mozilla.com)<br />
| <br />
|-<br />
| Toolkit for sandboxing third-parties libraries in Firefox<br />
| Firefox supports a long tail of infrequently used image and audio formats to<br />
support the occasional website that uses them. Each such format requires the<br />
Firefox decoder to use a new open source library for parsing and decoding.<br />
This, unfortunately, increases the attack surface of Firefox and as we saw in<br />
Pwn2Own 2018, Firefox was successfully exploited via a bugs in such libraries<br />
(libogg in this case).<br />
<br />
This project proposes to sandbox third-party libraries in Firefox by building a<br />
new software-fault isolation toolkit. Our tookit will build on the WebAssembly<br />
compiler to isolate libraries in Firefox. But, as part of this toolkit we will<br />
also develop and apply a library for safely interfacing with sandboxed libraries (and<br />
sanitizing data coming from them). with this toolkit we can ensure that any<br />
vulnerability in third-party libraries (e.g., libogg or libpng) cannot be used<br />
to be used to compromise Firefox.<br />
| C/C++, experience with WebAssembly<br />
| [https://mozillians.org/en-US/u/erahm/ Eric Rahm]<br />
| [https://mozillians.org/en-US/u/froydnj/ Nathan Froyd]<br />
| <br />
|-<br />
| Test automation our linting tools<br />
| We have a several linting tools running on Firefox code base, they currently don't have a test suite. <br />
The goal of this project is to make sure that tests are executed. We currently have a similar [https://bugzilla.mozilla.org/show_bug.cgi?id=1432410 test automation for static analyzer jobs]. The idea would be to extend (or replicate) this model for [https://searchfox.org/mozilla-central/source/tools/lint/ ./mach lint] (which run flake8, eslint, etc) and [https://searchfox.org/mozilla-central/source/python/mozbuild/mozbuild/mach_commands.py#2327 ./mach clang-format]<br />
The bug is https://bugzilla.mozilla.org/show_bug.cgi?id=1448008<br />
| Python<br />
| [https://github.com/sylvestre Sylvestre] (s@mozilla.com)<br />
| [https://github.com/abpostelnicu Andi Postelnicu] (andi@mozilla.com)<br />
| <br />
|-<br />
| Firefox Account Security Dashboard<br />
| Firefox Account administrators and users need an easily digestible view into the important events that have occurred on an account, providing a way to audit for irregularities.<br />
| JavaScript, HTML, CSS, MySQL<br />
| [https://mozillians.org/u/vbudhram/ Vijay Budhram], [https://mozillians.org/u/stomlinson/ Shane Tomlinson]<br />
| [https://mozillians.org/u/vbudhram/ Vijay Budhram], [https://mozillians.org/u/stomlinson/ Shane Tomlinson]<br />
| The Firefox Account platform tracks security information about an account, but does not surface this information in an easily consumable format. Users and administrators should be able to see a timeline of an account’s security related events, such as connecting devices, signing into services, changing or resetting passwords, and adding or removing 2FA. Each event in the timeline should include a timestamp, IP address, and location information when they occurred. <br />
<br />
This project would entail updating our security event API to ensure we track and expose the required data. The first phase is to build a script that consumes the API and pretty prints the timeline. The second phase is to provide a web interface for the security timeline.<br />
<br />
|-<br />
| Improving FastParquet<br />
| FastParquet is a Python library that needs improvement to how it writes the parquet file format <br />
| Python<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://github.com/klahnakoski/mo-parquet/blob/dev/docs/StudentProject%202019.md Read more]<br />
<br />
|-<br />
| Faster Pyparsing<br />
| Pyparsing is a Python library that provides a DSL for language specification. It could use some optimization. <br />
| Python<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://github.com/mozilla/moz-sql-parser/blob/dev/docs/Student%20Project%202019.md Read more]<br />
<br />
|-<br />
| Regression Detection<br />
| Use machine learning to guide statistical model selection, then use the model(s) to detect regressions in future data. <br />
| Machine Learning, Statistics, Python<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://github.com/mozilla/ActiveData/blob/dev/docs/Student%20Project%20190121.md Read more]<br />
<br />
|-<br />
| Bugzilla Kanban Board<br />
| Show bugs like [https://en.wikipedia.org/wiki/Post-it_Note post-it notes] on a [https://en.wikipedia.org/wiki/Whiteboard whiteboard]. Much like a [https://en.wikipedia.org/wiki/Kanban_board Kanban board]<br />
| JSX/React<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://github.com/mozilla/bugzilla-tiles Read more]<br />
<br />
|-<br />
| More ActiveData Recipes<br />
| Build out the user interface of the [https://github.com/mozilla/active-data-recipes active-data-recipes] project so that making new recipes is even easier<br />
| JSX/React some Python<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://github.com/mozilla/active-data-recipes/pull/112/files#diff-0f126940e57c54541662345b499622f1 PR with proposal] or [https://github.com/mozilla/active-data-recipes/tree/master/docs/Student%20Project%20190130.md Read more]<br />
<br />
|-<br />
| TUID service improvments<br />
| The TUID service handles millions of requests daily from hundreds of machines. It must go faster, and be stabilized.<br />
| Python/Flask/Sqlite <br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [mailto:gmierzwinski@mozilla.com Gregory Mierzwinski]<br />
| [https://github.com/mozilla/TUID/blob/dev/docs/Student%20Project%20190204.md Read more]<br />
<br />
|-<br />
| Firefox Source Docs Infrastructure<br />
| Improve the infrastructure underpinning Firefox's [https://firefox-source-docs.mozilla.org/ in-tree documentation].<br />
| Python, Sphinx, Rst<br />
| [https://mozillians.org/en-US/u/ahal/ Andrew Halberstadt]<br />
| TBD<br />
| Writing docs for Firefox's in-tree [https://firefox-source-docs.mozilla.org/ source docs] is time consuming and difficult and the end result is difficult to navigate.<br />
<br />
With [https://developer.mozilla.org/en-US/ MDN] de-prioritizing build and workflow docs, we need a suitable replacement for all of Firefox's contribution and workflow documentation. The great advantage of documentation living in-tree, is that it can be updated along with the source. Unfortunately the current system to build and generate docs is difficult to write for, slow to build and generates poorly organized documentation. These factors discourage developers from creating or updating docs.<br />
<br />
This project aims to improve the documentation experience via static analysis tools (e.g hint when docs might need to be updated), enabling linters, faster build times, additional language support and well structured hierarchies. Help make documentation a bigger part of our developer's day to day workflow.<br />
|-<br />
| Improve FixMe<br />
| [http://fixme.ossn.club/ Improve FixMe], a tool for surfacing meaningful contribution opportunities to new contributors. This project started two years ago as a GSoC project and we are looking into adding more capabilities. The tool currently fetches issues only from GitHub and relays a lot into the tags project maintainers use in their repositories. We want to add gitlab support and come up with a more sophisticated way of identifying technologies and skills needed for new contributors <br />
| - Backend: Go, Buffalo, Postgresql. - Front-end: React, typescript, Redux<br />
| [https://mozillians.org/en-US/u/bacharakis/ Christos Bacharakis]<br />
| [https://mozillians.org/en-US/u/bacharakis/ Christos Bacharakis]<br />
| [https://github.com/ossn/fixme Link to] front-end source code, [https://github.com/ossn/fixme_backend link to backend] source code. [http://fixme.ossn.club/ FixMe tool in action]<br />
|-<br />
| ..your next idea here!<br />
| some details<br />
| skills/language<br />
| reporter<br />
| mentor<br />
| comments</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Community:SummerOfCode19:Brainstorming&diff=1207262Community:SummerOfCode19:Brainstorming2019-02-05T16:56:46Z<p>Bacharakis: Add FixMe project</p>
<hr />
<div>Once again, Mozilla intends to apply to participate in Google's Summer Of Code.<br />
<br />
Mozilla community members, please submit proposals here for 2019 Google Summer of Code projects with Mozilla. This page is for brainstorming - as we approach the deadline, those ideas that are accepted will be transferred to the [[Community:SummerOfCode19|official list]].) <br />
<br />
Our application for summer of 2019 goes into Google on '''February 4th''', so get those project ideas in well ahead of time.<br />
<br />
<b>Are you a student looking to apply to GSoC with Mozilla?</b> Your first stop should be the [[Community:SummerOfCode19|official list of ideas]]. This page is full of weird ideas, only some of which will make the cut. It could be that they are not properly defined, the wrong size, or don't have a mentor. That makes them less likely to get accepted. You <i>can</i>, of course, also submit your own ideas - you don't have to put an idea on this page and get it 'made official' in order to send in a proposal for it.<br />
<br />
==How To Write A Good Project Proposal==<br />
<br />
Before adding an proposal to this list, please consider the following:<br />
<br />
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.<br />
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.<br />
* '''Do your research'''. Support the idea with well-researched links.<br />
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment. <br />
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know who you are, leave contact details.<br />
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.<br />
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.<br />
<br />
==Suggestion List==<br />
<br />
[[SummerOfCode|Here are the ideas lists from previous years]].<br />
<br />
Proposals can be in almost any part of the Mozilla project, though they do need to be mostly focused on code.<br />
<br />
Here are the proposals. Feel free to add a new one.<br />
<br />
== 2019 Proposed Project List ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details <br />
! Skills Needed <br />
! Reporter <br />
! Mentor(s) <br />
! Additional Comments<br />
|-<br />
| Improve Python in the browser<br />
| The [https://github.com/iodide-project/pyodide pyodide] project allows the Python scientific stack to run in the browser by compiling it to WebAssembly. Help make stuff run better and faster there.<br />
| Python and JavaScript. Can learn the WebAssembly parts as you go.<br />
| [https://mozillians.org/en-US/u/mdboom/ Michael Droettboom]<br />
| [https://mozillians.org/en-US/u/mdboom/ Michael Droettboom]<br />
| There are a number of specific projects we have in mind, but are open to other proposals that are within scope and seem practical within the timeframe. (1) Implement matplotlib's display on top of Web APIs (HTML5 Canvas, etc.) This would allow us to avoid shipping a whole separate rendering engine to the browser. (2) Build WebAssembly support into the conda packaging system to make it easier to distribute new compiled packages for Pyodide. (3) Make multi-dimensional arrays sharable between Python and Javascript. See Pyodide's [https://github.com/iodide-project/pyodide/issues list of issues] for additional ideas. About the mentor: Michael Droettboom is a Staff Data Engineer at Mozilla, and a former lead developer of matplotlib with years of experience building the Python scientific ecosystem.<br />
|-<br />
| ReSpec <br />
| [https://github.com/w3c/respec/ ReSpec] is a JS-based tool used to write W3C Specifications (Web Standards) that is widely used by the Web Standards Community. With 6+ years of development, it's heavily depended upon by the W3C community at large (of which Mozilla is an active participant). ReSpec's code is in need of some modernization, optimizations, and bug fixes - and we could use your help! In this project, you would have the opportunity to make ReSpec's UI more accessible, making it leaner and faster using distributed processing with Web Workers, and/or adding new features to make the lives of W3C spec Editor's better. <br />
| JavaScript, HTML, CSS. <br />
| [https://mozillians.org/en-US/u/mcaceres/ Marcos Caceres]<br />
| [https://mozillians.org/en-US/u/mcaceres/ Marcos Caceres]<br />
| ReSpec offers students the opportunity to work on a large code base that has extensive real world use and impact. The project offers students an extensive range of problems to tackle, from UI design, to concurrent processing (using Web Workers to do distributed text processing), dealing with accessibility and internationalization, writing and learning about unit and integration tests, security, code review, etc. - as well as exposure to the W3C and the web standards community, this project also aims at teaching students about how web standards are put together. To determine if this is a project you would like to be part of, see the [https://github.com/w3c/respec/issues/ list of issues] you could work on. It's a great opportunity to learn about all aspects of open source software development, but with the freedom to take on small to large challenges over the Summer (depending on your skill level and level of confidence). About the mentor: Marcos Caceres is a Staff Engineer at Mozilla who has been working on Web Standards for over a decade. Marcos is the lead maintainer of ReSpec. Marcos has extensive experience mentoring developers and has previously successfully mentor a GSO student. <br />
|-<br />
| Ship Public Suffix List (PSL) over Remote Settings<br />
| The list of public domain suffixes (DNS) is shipped with every release, with no way to update it on long term releases for example.<br />
Now that Remote Settings has become a solid solution to ship data, we could use it to publish updates of the PSL.<br />
The task consist in migrating the current client code to read from Remote Settings instead of a file, and implement a scheduled job (like Python) to push updates automatically (most likely compiled as a DAFSA file) <br />
| JavaScript and some Python basics <br />
| [https://mozillians.org/en-US/u/leplatrem/ Mathieu Leplatre]<br />
| [https://mozillians.org/en-US/u/leplatrem/ Mathieu Leplatre]<br />
| https://bugzilla.mozilla.org/show_bug.cgi?id=1083971<br />
|-<br />
| [https://github.com/marco-c/bugbug bugbug]<br />
| A platform for machine learning projects applied on Bugzilla, VCS and other software development data.<br />
| Python<br />
| [https://github.com/marco-c Marco Castelluccio] (FIRST_NAME@mozilla.com)<br />
| [https://github.com/marco-c Marco Castelluccio] (FIRST_NAME@mozilla.com)<br />
| The project will involve one or more of:<br />
i) building additional classifiers (e.g., to detect bugs with no steps to reproduce, or to suggest a developer to assign to a bug, and so on);<br />
<br />
ii) improving accuracy/precision/recall of the existing classifiers by implementing other machine learning techniques (e.g., by using convolutional neural networks or recurrent neural networks);<br />
<br />
iii) improving accuracy/precision/recall by implementing additional feature extraction steps or making the already existing ones better.<br />
|-<br />
| Make the Firefox WebAuthn Soft Token a Real Thing<br />
| The Web Authentication Soft Token provides second-factor login support without needing a Security Key dongle. It would be very usable if the Soft Token were a) synchronized across an account using Sync, b) could be controlled via a Web Extension, and perhaps c) had some UI. If these things were true, most people could get quality authentication support without buying another device.<br />
| C++, Javascript, Basic cryptography<br />
| [https://mozillians.org/en-US/u/jcjones/ J.C. Jones] <br />
| [https://mozillians.org/en-US/u/jcjones/ J.C. Jones] <br />
| https://wiki.mozilla.org/Security/CryptoEngineering#Web_Authentication<br />
|-<br />
| WebSocket Monitor<br />
| Support for WebSocket monitoring and inspection in Firefox DevTools.<br />
| JavaScript/React<br />
| [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko]<br />
| [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko]<br />
| This project aims at providing support for WebSocket monitoring and inspection in Firefox DevTools. The feature should be built on top of the existing Network panel UI and responsible for visualizing data sent through WebSocket connection (i.e. WS frames). The user should be able to use the UI to see as well as analyse the data (search, filter, etc.).<br />
* [https://docs.google.com/document/d/1ruHk-BA3cqzU7VHoVltnAwWt_2OXKOOAI4nTHwYllzk/edit# Detailed Project Description]<br />
|-<br />
| Helpful crash reporter<br />
| The crash reporter only allows users to send crash reports but in some cases it might help the user diagnose the crash and solve it on his/her own<br />
| C++, Javascript<br />
| [https://mozillians.org/en-US/u/gsvelto/ Gabriele Svelto] <br />
| [https://mozillians.org/en-US/u/gsvelto/ Gabriele Svelto] <br />
| There's a few things that could be implemented:<br />
* A quick test of the memory owned by the crashed process (such as those in [http://www.memtest.org/ memtest86+]) might catch faulty memory, a common cause for crashes<br />
* The crash reporter client might try and validate Firefox files which can sometimes become corrupted (usually because of hardware issues). If they are it can prompt the user to re-install Firefox<br />
* Many crashes are caused by buggy graphics drivers, while we blacklist the most egregious offenders we can't cover them all. The crash reporter might identify a faulty driver (if a bug for it has already been filed) and point the user to up-to-date drivers<br />
* For crashes caused by known bugs it should be possible to point the user to the bug filed on bugzilla<br />
|-<br />
| Debugger Inline Variable Preview<br />
| When the Firefox DevTools debugger is paused, users can hover over variables to get a useful tooltip that details the variable's value at that time. While this popup is very informative, one valuable enhancement would be displaying relevant contextual variables values alongside the variable inline, alleviating the need for tooltips and allowing the user to more quickly get the information they need. The applicant will work alongside the Debugger's team to implement this feature based on UX mockups and be given space to share and implement ideas of their own.<br />
| Javascript<br />
| [https://mozillians.org/en-US/u/davidwalsh/ David Walsh] <br />
| [https://mozillians.org/en-US/u/davidwalsh/ David Walsh] <br />
| <br />
|-<br />
| GitHub Checks Support Improvements<br />
| [https://github.com/taskcluster/taskcluster Taskcluster] currently supports reporting results to the [https://github.com/taskcluster/taskcluster/pull/129/checks?check_run_id=54327344 GitHub Checks API], but only reports success or failure. Let's add support for showing [https://developer.github.com/v3/checks/runs/ annotations] - snippets of log output, more detailed results, images, and so on. We can even add support for additional "actions" on the task, such as re-running with debugging enabled.<br />
| Server-side JS<br />
| [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell] <br />
| [https://mozillians.org/en-US/u/ireneOwl/ Irene Storozhko], [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell] <br />
| <br />
|-<br />
| Support GitHub Logins in Taskcluster<br />
| [https://github.com/taskcluster/taskcluster Taskcluster] currently supports logging in with Auth0, the Mozilla login system. We would like to make it useful outside of Mozilla, and most other users do their development on GitHub, making GitHub logins a good solution. This project would involve adding support for signing in with GitHub, as well as the more challenging task of assigning appropriate permissions to users based on the setup of their GitHub account.<br />
| Server-side JS<br />
| [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell] <br />
| [https://mozillians.org/en-US/u/ireneOwl/ Irene Storozhko], [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell] <br />
| <br />
|-<br />
| Improve Webdriver support in Servo<br />
| [https://github.com/servo/servo/ Servo] currently supports a minimal subset of the [https://w3c.github.io/webdriver/ Webdriver standard]. We would like to improve Servo's support, and verify its correctness by passing a [https://github.com/web-platform-tests/wpt/tree/master/webdriver set of automated tests]. This project would involve writing Rust code to extend the webdriver server inside of Servo, as well as JavaScript and Python to support the [https://web-platform-tests.org/writing-tests/testdriver.html testdriver.js] testharness.<br />
| Familiarity with Python & JavaScript; interest in learning Rust<br />
| [https://mozillians.org/en-US/u/jdm/ Josh Bowman-Matthews] <br />
| [https://mozillians.org/en-US/u/jdm/ Josh Bowman-Matthews]<br />
| [https://github.com/servo/servo/wiki/Support-Webdriver-based-tests-project Project description]<br />
|-<br />
| Support importing Instruments profiles in perf.html<br />
| [https://github.com/devtools-html/perf.html/ perf.html] visualizes performance data recorded from various performance analysis tools. It is a tool designed to consume performance profiles from Gecko Profiler but can visualize any profiler able to output JSON. It currently supports Gecko, Chrome and perf profile formats. Instruments is a performance analyzer that comes with Xcode. This project would involve adding support for Instruments profile import in perf.html.<br />
| Familiarity with JavaScript & React<br />
| [https://mozillians.org/en-US/u/canaltinova/ Nazım Can Altınova]<br />
| [https://mozillians.org/en-US/u/canaltinova/ Nazım Can Altınova]<br />
| https://github.com/devtools-html/perf.html/issues/1138<br />
|-<br />
| Common Voice - WebAssembly MP3 Encoding<br />
| Currently Common Voice doesn’t support Safari, which is also why we have an iOS app. The only reason being the missing MediaRecorder API. It could be polyfilled (rebuilt in “userspace”) by compiling an MP3 encoder to WebAssembly. I’ve tried that a couple of times, but never had enough time to fix the opaque bugs happening in Safari. This could also be turned into its own library and would be a nice story overall of how WASM can help with WebCompat and missing APIs.<br />
| JavaScript<br />
| [https://mozillians.org/u/gweber/ Gregor Weber]<br />
| [https://mozillians.org/u/gweber/ Gregor Weber]<br />
| [https://github.com/mozilla/voice-web/issues/469 This GitHub issue] lines out some thoughts around how to implement it and you can find references to closed PRs which tried implementing it in various ways.<br />
|-<br />
| Common Voice - Voice Wave Avatar<br />
| We’d like our users to have unique(ish) avatars based either on the characteristics of their voice or a visualization of how their name (or an utterance of their choosing) is pronounced. It could also be a combination of the two ideas. We’re very open to explore this space together, though the a candidate should have some knowledge in sound theory.<br />
| JavaScript, Some knowledge of sound theory<br />
| [https://mozillians.org/u/gweber/ Gregor Weber]<br />
| [https://mozillians.org/u/gweber/ Gregor Weber]<br />
|-<br />
| Tab Manager menu in Firefox <br />
| This project will extend the tab overflow menu - which shows tabs not visible in the browser's tab strip - to allow management of all open tabs across all browser windows. The selected student will be working directly in the Firefox codebase to add functionality and new menu structures to make this easily accessible for end users. <br />
| JavaScript, CSS, and web experience<br />
| [https://mozillians.org/en-US/u/sfoster/ Sam Foster], [https://mozillians.org/en-US/u/bbell/ Bryan Bell]<br />
| [https://mozillians.org/en-US/u/sfoster/ Sam Foster]<br />
| We have [https://mozilla.invisionapp.com/share/4SNCEPDUEZ6#/screens UX mockups] for this feature, which could be broken into two phases. We also have a [https://bugzilla.mozilla.org/show_bug.cgi?id=1480542 bug on file], where discussion has begun. While working on this you will become very familiar with the Browser Toolbox, our own "Inspector" tool for the browser user-interface, as well as writing automated tests for the new feature you're adding. The existing tab overflow code lives in our [https://searchfox.org/mozilla-central/source/browser/base/content/browser-allTabsMenu.js browser-allTabsMenu.js] file, which will be the starting point for the new tab manager. You can look at this and the existing tab code to get an idea of how this currently works. <br />
-<br />
|-<br />
|-<br />
| Firefox Reader Redesign<br />
| The design of Firefox’s Reader Mode has languished behind as Quantum has implemented the new Photon Design System. The interface needs to be rebuilt using new visual and interaction styles to match the Photon Design System.<br />
| JavaScript, CSS, and web experience<br />
| [https://mozillians.org/en-US/u/awallin/ Abraham Wallin]<br />
| [https://mozillians.org/en-US/u/eeejay/ Eitan Isaacson]<br />
| [https://mozilla.invisionapp.com/share/87N9YQYCTJZ#/315073983_Reader_View_Redesign UX Mockups] for this feature are available with visual bugs have been reported [https://bugzilla.mozilla.org/show_bug.cgi?id=1187696 here] and [https://github.com/devtools-html/ux/issues/5 here]. Functional bugs and feature enhancements have been documented [https://github.com/mozilla/readability/issues?q=is%3Aissue+is%3Aopen+label%3Areader-mode-has-issues here], [https://github.com/mozilla/readability/issues?q=is%3Aissue+is%3Aopen+label%3Ashould-be-readerable here], [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=comp%3Areader%20prod%3DToolkit%20whiteboard%3Areadability-algorithm&list_id=14539703 here], and [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=comp%3Areader%20prod%3DToolkit%20whiteboard%3Aisreadable&list_id=14539704 finally here]. The request is for an engineering student to implement the designs and tackle the queue of bugs/enhancements within the Firefox code base. Mentors will support with prioritization, design direction/assets, and technical guidance.<br />
<br />
<br />
|-<br />
| An Android file downloader designed for Emerging Markets<br />
| A lesson learned thanks to our UX team is in Emerging Markets the data plan is dynamic: in late nights we have the most affordable bandwidth. Here's the question: Why not schedule big files and videos and have them downloaded when you're sleeping? The mvp would be an App which we can send urls to. After receiving these urls the App either downloads it directly or defer it to late night. As there are more and more background restrictions enforced on new Android APIs, this should be a fun and challenging journey.<br />
<br />
A stretch goal would be to embed this downloader in our browser for Emerging Markets, Firefox Lite. Firefox Lite is not satisfied with the current Android Download Manager in several ways: We'd like to give users the ability to pause/resume a download, we'd like to download a file directly to SDcard (opposed to download it to the main storage and move it into SDcard).<br />
<br />
We've also prepared an even more ambitious mission for those who want tough challenges: Design the app and make it dynamic deliverable. With aabs we can satisfy both light and heavy users by defaulting Android Download Manager as the download tool and prepare the aforementioned downloader dynamically so that Firefox Lite itself is still minimized in terms of disk size. Nevin and mTwTm are Android developers who can provide assistance to Android App design.<br />
| Android Java/Kotlin<br />
| [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)]<br />
| [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)] (mTwTm@mozilla.com), [https://github.com/cnevinc/ Nevin Chen] (nevin@mozilla.com)<br />
| <br />
|-<br />
| Toolkit for sandboxing third-parties libraries in Firefox<br />
| Firefox supports a long tail of infrequently used image and audio formats to<br />
support the occasional website that uses them. Each such format requires the<br />
Firefox decoder to use a new open source library for parsing and decoding.<br />
This, unfortunately, increases the attack surface of Firefox and as we saw in<br />
Pwn2Own 2018, Firefox was successfully exploited via a bugs in such libraries<br />
(libogg in this case).<br />
<br />
This project proposes to sandbox third-party libraries in Firefox by building a<br />
new software-fault isolation toolkit. Our tookit will build on the WebAssembly<br />
compiler to isolate libraries in Firefox. But, as part of this toolkit we will<br />
also develop and apply a library for safely interfacing with sandboxed libraries (and<br />
sanitizing data coming from them). with this toolkit we can ensure that any<br />
vulnerability in third-party libraries (e.g., libogg or libpng) cannot be used<br />
to be used to compromise Firefox.<br />
| C/C++, experience with WebAssembly<br />
| [https://mozillians.org/en-US/u/erahm/ Eric Rahm]<br />
| [https://mozillians.org/en-US/u/froydnj/ Nathan Froyd]<br />
| <br />
|-<br />
| Test automation our linting tools<br />
| We have a several linting tools running on Firefox code base, they currently don't have a test suite. <br />
The goal of this project is to make sure that tests are executed. We currently have a similar [https://bugzilla.mozilla.org/show_bug.cgi?id=1432410 test automation for static analyzer jobs]. The idea would be to extend (or replicate) this model for [https://searchfox.org/mozilla-central/source/tools/lint/ ./mach lint] (which run flake8, eslint, etc) and [https://searchfox.org/mozilla-central/source/python/mozbuild/mozbuild/mach_commands.py#2327 ./mach clang-format]<br />
The bug is https://bugzilla.mozilla.org/show_bug.cgi?id=1448008<br />
| Python<br />
| [https://github.com/sylvestre Sylvestre] (s@mozilla.com)<br />
| [https://github.com/abpostelnicu Andi Postelnicu] (andi@mozilla.com)<br />
| <br />
|-<br />
| Firefox Account Security Dashboard<br />
| Firefox Account administrators and users need an easily digestible view into the important events that have occurred on an account, providing a way to audit for irregularities.<br />
| JavaScript, HTML, CSS, MySQL<br />
| [https://mozillians.org/u/vbudhram/ Vijay Budhram], [https://mozillians.org/u/stomlinson/ Shane Tomlinson]<br />
| [https://mozillians.org/u/vbudhram/ Vijay Budhram], [https://mozillians.org/u/stomlinson/ Shane Tomlinson]<br />
| The Firefox Account platform tracks security information about an account, but does not surface this information in an easily consumable format. Users and administrators should be able to see a timeline of an account’s security related events, such as connecting devices, signing into services, changing or resetting passwords, and adding or removing 2FA. Each event in the timeline should include a timestamp, IP address, and location information when they occurred. <br />
<br />
This project would entail updating our security event API to ensure we track and expose the required data. The first phase is to build a script that consumes the API and pretty prints the timeline. The second phase is to provide a web interface for the security timeline.<br />
<br />
|-<br />
| Improving FastParquet<br />
| FastParquet is a Python library that needs improvement to how it writes the parquet file format <br />
| Python<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://github.com/klahnakoski/mo-parquet/blob/dev/docs/StudentProject%202019.md Read more]<br />
<br />
|-<br />
| Faster Pyparsing<br />
| Pyparsing is a Python library that provides a DSL for language specification. It could use some optimization. <br />
| Python<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://github.com/mozilla/moz-sql-parser/blob/dev/docs/Student%20Project%202019.md Read more]<br />
<br />
|-<br />
| Regression Detection<br />
| Use machine learning to guide statistical model selection, then use the model(s) to detect regressions in future data. <br />
| Machine Learning, Statistics, Python<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://github.com/mozilla/ActiveData/blob/dev/docs/Student%20Project%20190121.md Read more]<br />
<br />
|-<br />
| Bugzilla Kanban Board<br />
| Show bugs like [https://en.wikipedia.org/wiki/Post-it_Note post-it notes] on a [https://en.wikipedia.org/wiki/Whiteboard whiteboard]. Much like a [https://en.wikipedia.org/wiki/Kanban_board Kanban board]<br />
| JSX/React<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://github.com/mozilla/bugzilla-tiles Read more]<br />
<br />
|-<br />
| More ActiveData Recipes<br />
| Build out the user interface of the [https://github.com/mozilla/active-data-recipes active-data-recipes] project so that making new recipes is even easier<br />
| JSX/React some Python<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [https://github.com/mozilla/active-data-recipes/pull/112/files#diff-0f126940e57c54541662345b499622f1 PR with proposal] or [https://github.com/mozilla/active-data-recipes/tree/master/docs/Student%20Project%20190130.md Read more]<br />
<br />
|-<br />
| TUID service improvments<br />
| The TUID service handles millions of requests daily from hundreds of machines. It must go faster, and be stabilized.<br />
| Python/Flask/Sqlite <br />
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br />
| [mailto:gmierzwinski@mozilla.com Gregory Mierzwinski]<br />
| [https://github.com/mozilla/TUID/blob/dev/docs/Student%20Project%20190204.md Read more]<br />
<br />
|-<br />
| Firefox Source Docs Infrastructure<br />
| Improve the infrastructure underpinning Firefox's [https://firefox-source-docs.mozilla.org/ in-tree documentation].<br />
| Python, Sphinx, Rst<br />
| [https://mozillians.org/en-US/u/ahal/ Andrew Halberstadt]<br />
| TBD<br />
| Writing docs for Firefox's in-tree [https://firefox-source-docs.mozilla.org/ source docs] is time consuming and difficult and the end result is difficult to navigate.<br />
<br />
With [https://developer.mozilla.org/en-US/ MDN] de-prioritizing build and workflow docs, we need a suitable replacement for all of Firefox's contribution and workflow documentation. The great advantage of documentation living in-tree, is that it can be updated along with the source. Unfortunately the current system to build and generate docs is difficult to write for, slow to build and generates poorly organized documentation. These factors discourage developers from creating or updating docs.<br />
<br />
This project aims to improve the documentation experience via static analysis tools (e.g hint when docs might need to be updated), enabling linters, faster build times, additional language support and well structured hierarchies. Help make documentation a bigger part of our developer's day to day workflow.<br />
|-<br />
| Improve FixMe<br />
| [http://fixme.ossn.club/ Improve FixMe], a tool for surfacing meaningful contribution opportunities to new contributors. This project started two years ago as a GSoC project and we are looking into adding more capabilities. The tool currently fetches issues only from GitHub and relays a lot into the tags project maintainers use in their repositories. We want to add gitlab support and come up with a more sophisticated way of identifying technologies and skills needed for new contributors <br />
| - Backend: Go, Buffalo, Postgresql. - Front-end: React, typescript, Redux<br />
| https://mozillians.org/en-US/u/bacharakis/<br />
| https://mozillians.org/en-US/u/bacharakis/<br />
| [https://github.com/ossn/fixme Link to] front-end source code, [https://github.com/ossn/fixme_backend link to backend] source code. [http://fixme.ossn.club/ FixMe tool in action]<br />
|-<br />
| ..your next idea here!<br />
| some details<br />
| skills/language<br />
| reporter<br />
| mentor<br />
| comments</div>Bacharakishttps://wiki.mozilla.org/index.php?title=OSSN/OpenSourceExperiments&diff=1190670OSSN/OpenSourceExperiments2018-03-19T18:19:02Z<p>Bacharakis: Survey link</p>
<hr />
<div>== Project information ==<br />
Project owner: Christos Bacharakis<br /><br />
Accountable: Lucy Harris <br /><br />
Team: Open Innovation <br /><br />
Contact: christos AT mozilla dot com<br /><br />
<br />
<br /><br />
<br />
== Intro ==<br />
As part of the [http://opensource.mozilla.community/ Open Source Student Network pilot program] we are designing a set of experiments for better understanding the user journey of University students towards their first open source project.<br />
<br />
The goal of these experiments is to '''to discover and/or validate opportunities and best practices for supporting University Tech students throughout their journey towards contributing code to Open Source Projects.'''<br />
<br />
We will closely work with the Clubs of our [http://opensource.mozilla.community OSSN network] for recruiting students who would be interested being part of the experiments. <br />
<br />
<br /><br />
<br />
== Open Source Contribution Survey ==<br />
We would like 5-10 minutes of your time for answering some simple and easy questions regarding your experience towards contributing to an Open Source project.<br />
We are looking to gather data from everyone who have tried (failed or succeeded) contributing to an open source project in the past year.<br />
Any personal data you submit as part of this survey will be handled in accordance with our Mozilla Privacy Policy.<br />
<br />
[https://www.surveygizmo.com/s3/4160758/OSSN-Contribute-to-Open-Source Survey link]<br />
<br />
<br /><br />
'''Tweet size:''' <br />
Have you ever tried to contribute (successfully or unsuccessfully) to an Open Source Project? Please help us by filling this 5' survey! We want to better understand when and why people drop off! bit.ly/FOSSCont<br />
<br />
== The problem we are trying to solve for ==<br />
Based on our recent research, there is a significant number of University students across the United States who want to contribute to Open Source projects. Most of these students drop off at some point during their journey due to various reasons.<br />
<br />
The goal of these experiments is to identify the various reasons students drop off and provide a set of recommendations.<br />
<br />
We also believe that through these experiments we will be able to identify if there is a intervention that Mozilla can do which will turn Computer Science students to Open Source contributors.<br />
<br />
<br /><br />
<br />
== Questions we are trying to answer ==<br />
{| class="wikitable"<br />
|-<br />
! Journey !! Questions<br />
|-<br />
| Discovery || <br />
* Are students more interested in projects tailored to their skill/language or to projects with a mission<br />
* Do students look for evidence of a positive community before they interact?<br />
* Do diverse students spend more time looking for a positive community than other students?<br />
* Are students interested in Major already established open source projects or to small class project<br />
|-<br />
| Engagement || <br />
* Students are more engaged with projects that meet a specific skill or with projects where they have a full stack understanding<br />
* Are projects with video introductions attract more students?<br />
* Is suggested bug matching based on what you just did works better than just exploring for new issues to work on?<br />
* Are github issues with more documentation and screenshots help students select project to work on?<br />
* Unclear or missing documentation will make it less possible for students to select and contribute to a project<br />
|-<br />
| Onboarding || <br />
* How much help should be given to students?<br />
* Does the group effect matters for getting people on board to a project? (Groups working on the same projects vs individuals to different projects<br />
* Is setting up the development environment a blocker - a process which potentially can scare people away?<br />
* Is having the maintainer getting you onboard VS a project contributor more impactful?<br />
|-<br />
| Contribution || <br />
* Solving a dummy bug VS fixing an actual bug will empower students to come back and work on another issue/bug? <br />
* What affects the retention after 1st contribution <br />
* How effective are first good bugs for longer engagement <br />
* Easy vs hard issue - solving a bug which you can reference <br />
* New feature vs fix/optimize issue <br />
|-<br />
| Retention || <br />
* Does an invitation back to the project have better results? <br />
* Suggested next projects/issues etc <br />
* Has this person contributed to an open source project after he/she graduate? <br />
* How important is the time from pushing a pull request to reviewing it. Is it an important factor for a future contribution? <br />
|-<br />
| Across the whole journey || <br />
* Does regular communication play an important role? In which sequence and form? <br />
* Which mentorship model is more effective in each step? <br />
* Are bots effective in each step of the journey? <br />
* Do suggested next steps have better results in each step of the journey than letting students explore alone? <br />
* Are students more effective when they are in a group or when they are alone? <br />
|}<br />
<br />
<br /><br />
<br />
== As a student ==<br />
The only requirement for the students is to dedicate one hour per week for taking part into our online sessions/calls. <br />
No prior experience is a certain programming language or a technology stack is needed and we invite all students regardless their skills or experiences to sign up.<br />
<br />
All the students will participate in small experiments throughout their journey towards their first code contribution.<br />
<br />
The students will have the opportunity to work on a variety of open source projects based on their interests and skills. In every step of the process, they will have experienced mentors to guide them and support them.<br />
<br />
{| class="wikitable"<br />
|-<br />
! User Journey !! What students will do<br />
|-<br />
| Discovery || The process where students will identify a project to work on<br />
|-<br />
| Engagement || There process where students will engage with a project by reading its codebase, going through the docs, issues etc<br />
|-<br />
| Onboarding || The process of setting up the development environment<br />
|-<br />
| Contributing || Identifying an issue/feature/bug, writing code and pushing it to the projects codebase<br />
|-<br />
| Retention || Identifying what to do next after the first pull request<br />
|}<br />
<br />
<br /><br />
<br />
== Timeline and participation ==<br />
<br />
The experiments are going to begin in the '''first week of February and each experiments will last four weeks'''.<br />
<br />
If you are interested being part of the experiments and you can dedicate just one hour per week for 4 weeks, '''please [http://bit.ly/Contribute2FOSS fill this form]'''.<br />
<br />
<br /><br />
<br />
== Mentors ==<br />
The students will have the opportunity to work on a variety of open source projects based on their interests and skills. In every step of the process, they will have experienced mentors to guide them and support them.<br />
<br />
As mentors you will have the opportunity to work with top students from across the US who are passionate to learn and contribute to Open Source projects.<br />
If you are mentoring, maintaining or contributing to an open source project and you are looking to mentor a small group of students for contributing to your project, please drop us a line at christos AT mozilla dot com.<br />
Requirements: As a mentor you have to dedicate the minimum of 1 hour per week for supporting your students. You can always dedicate more time but it's also up to each experiment and the different mentorship model each experiment is testing.</div>Bacharakishttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2018-03-19&diff=1190653WeeklyUpdates/2018-03-192018-03-19T16:44:00Z<p>Bacharakis: Adding OSSN topic</p>
<hr />
<div><br />
{{WeeklyUpdateNav}}<br />
* Every Monday @ 11:00am Pacific Time (19:00 UTC) <br />
* https://air.mozilla.org/channels/project-meeting/ to watch and listen<br />
* join irc.mozilla.org #airmozilla for backchannel discussion<br />
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak. <br />
{{conf|8600}}<br />
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br />
<br />
* Thanks to Tech Speakers Yuli, Andrzej, Aka and Srushtika, who gave talks/workshops to developer audiences in Spain, Poland, Ghana, and Germany in the past week. <br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
* '''[https://indiewebcamp.com/events/2018-03-20-homebrew-website-club Homebrew Website Club Meetup]''' (A HWC Tuesday exception)<br />
** 18:30-20:30 EST at Digital Harbor Foundation, '''Baltimore (<abbr title="Maryland">MD</abbr>)'''<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
* '''[https://indiewebcamp.com/events/2018-03-21-homebrew-website-club Homebrew Website Club Meetup]''' (nearly every Wednesday somewhere)<br/><strong>Be a part of the open web with your own website.</strong><br />
** '''Nürnberg (GERMANY)''', <br/>'''San Francisco''' (@[[MozSF]] commons hosted by Tantek)<br />
** 17:30-18:30 Quiet Writing Hour, finish that blog post, wiki edit, etc.!<br />
** 18:30-19:30 IndieWeb meetup, demos, & hack night <blockquote><p>Create or update your personal web site!<br/>Share what you've gotten working.</p><p>Join a community with like-minded interests. <br/>Bring friends that want a personal site!</p></blockquote> Any questions? See '''[https://indiewebcamp.com/events/2018-03-21-homebrew-website-club the wiki page for details]''' <br/>or join IRC: https://indieweb.org/discuss<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br />
<br />
=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br />
<br />
=== Next Week ===<br />
<br />
== Speakers ==<br />
<br />
The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! [https://mozillians.org/u/USERNAME Presenter]<br />
! Title<br />
! Topic<br />
! Location<br />
! Sharing<br />
! Media<br />
! More Details<br />
|-<br />
| Who Are You?<br />
| What Do You Do?<br />
| What are you going to talk about?<br />
| Where are you presenting from? (Moz Space, your house, space)<br />
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br />
| Links to slides or images you want displayed on screen<br />
| Link to where audience can find out more information<br />
|-<br />
| Jofish Kaye<br />
| Principal Research Scientist<br />
| Emerging Technologies Weekly Update<br />
| Mountain View<br />
| no<br />
| n/a<br />
| https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology<br />
|-<br />
| Michael Van Kleeck<br />
| Enterprise Solutions Architect<br />
| The Weekly MinIT! <br />
| MozPDX- The New Commons!<br />
| No<br />
| n/a<br />
| https://wiki.mozilla.org/IT/WeeklyMinIT<br />
|-<br />
| Asa Dotzler<br />
| Firefox Roadmap<br />
| Weekly Firefox Update<br />
| MTV<br />
| no<br />
| n/a<br />
| [https://wiki.mozilla.org/Firefox/Roadmap/Updates#2018-03-19 2018-03-19]<br />
|-<br />
| Christos Bacharakis<br />
| Open Source Student Network, Open Innovation team<br />
| Contributing to Open Source Survey<br />
| Mozilla Berlin<br />
| no<br />
| bit.ly/FOSSCont or https://www.surveygizmo.com/s3/4160758/OSSN-Contribute-to-Open-Source<br />
| https://wiki.mozilla.org/OSSN/OpenSourceExperiments<br />
|-<br />
|}<br />
<br />
= Welcome! =<br />
<br />
Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! ''Who is being introduced?''<br />
! ''Who are you? (the introducer)''<br />
! ''Where are you doing the introduction?''<br />
! ''Where are they from?''<br />
! ''How will they be part of Mozilla?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
| Their Name<br />
| Your Name<br />
| Intro location<br />
| Their Location<br />
| Their Role<br />
|-<br />
|}<br />
<br />
<br />
[[Category:Weekly Updates]]<br />
[[Category:Meeting Notes]]</div>Bacharakishttps://wiki.mozilla.org/index.php?title=OSSN/OpenSourceExperiments&diff=1187909OSSN/OpenSourceExperiments2018-01-30T14:10:20Z<p>Bacharakis: added owner info</p>
<hr />
<div>== Project information ==<br />
Project owner: Christos Bacharakis<br /><br />
Accountable: Lucy Harris <br /><br />
Team: Open Innovation <br /><br />
Contact: christos AT mozilla dot com<br /><br />
<br />
<br /><br />
<br />
== Intro ==<br />
As part of the [http://opensource.mozilla.community/ Open Source Student Network pilot program] we are designing a set of experiments for better understanding the user journey of University students towards their first open source project.<br />
<br />
The goal of these experiments is to '''to discover and/or validate opportunities and best practices for supporting University Tech students throughout their journey towards contributing code to Open Source Projects.'''<br />
<br />
We will closely work with the Clubs of our [http://opensource.mozilla.community OSSN network] for recruiting students who would be interested being part of the experiments. <br />
<br />
<br /><br />
<br />
== The problem we are trying to solve for ==<br />
Based on our recent research, there is a significant number of University students across the United States who want to contribute to Open Source projects. Most of these students drop off at some point during their journey due to various reasons.<br />
<br />
The goal of these experiments is to identify the various reasons students drop off and provide a set of recommendations.<br />
<br />
We also believe that through these experiments we will be able to identify if there is a intervention that Mozilla can do which will turn Computer Science students to Open Source contributors.<br />
<br />
<br /><br />
<br />
== Questions we are trying to answer ==<br />
{| class="wikitable"<br />
|-<br />
! Journey !! Questions<br />
|-<br />
| Discovery || <br />
* Are students more interested in projects tailored to their skill/language or to projects with a mission<br />
* Do students look for evidence of a positive community before they interact?<br />
* Do diverse students spend more time looking for a positive community than other students?<br />
* Are students interested in Major already established open source projects or to small class project<br />
|-<br />
| Engagement || <br />
* Students are more engaged with projects that meet a specific skill or with projects where they have a full stack understanding<br />
* Are projects with video introductions attract more students?<br />
* Is suggested bug matching based on what you just did works better than just exploring for new issues to work on?<br />
* Are github issues with more documentation and screenshots help students select project to work on?<br />
* Unclear or missing documentation will make it less possible for students to select and contribute to a project<br />
|-<br />
| Onboarding || <br />
* How much help should be given to students?<br />
* Does the group effect matters for getting people on board to a project? (Groups working on the same projects vs individuals to different projects<br />
* Is setting up the development environment a blocker - a process which potentially can scare people away?<br />
* Is having the maintainer getting you onboard VS a project contributor more impactful?<br />
|-<br />
| Contribution || <br />
* Solving a dummy bug VS fixing an actual bug will empower students to come back and work on another issue/bug? <br />
* What affects the retention after 1st contribution <br />
* How effective are first good bugs for longer engagement <br />
* Easy vs hard issue - solving a bug which you can reference <br />
* New feature vs fix/optimize issue <br />
|-<br />
| Retention || <br />
* Does an invitation back to the project have better results? <br />
* Suggested next projects/issues etc <br />
* Has this person contributed to an open source project after he/she graduate? <br />
* How important is the time from pushing a pull request to reviewing it. Is it an important factor for a future contribution? <br />
|-<br />
| Across the whole journey || <br />
* Does regular communication play an important role? In which sequence and form? <br />
* Which mentorship model is more effective in each step? <br />
* Are bots effective in each step of the journey? <br />
* Do suggested next steps have better results in each step of the journey than letting students explore alone? <br />
* Are students more effective when they are in a group or when they are alone? <br />
|}<br />
<br />
<br /><br />
<br />
== As a student ==<br />
The only requirement for the students is to dedicate one hour per week for taking part into our online sessions/calls. <br />
No prior experience is a certain programming language or a technology stack is needed and we invite all students regardless their skills or experiences to sign up.<br />
<br />
All the students will participate in small experiments throughout their journey towards their first code contribution.<br />
<br />
The students will have the opportunity to work on a variety of open source projects based on their interests and skills. In every step of the process, they will have experienced mentors to guide them and support them.<br />
<br />
{| class="wikitable"<br />
|-<br />
! User Journey !! What students will do<br />
|-<br />
| Discovery || The process where students will identify a project to work on<br />
|-<br />
| Engagement || There process where students will engage with a project by reading its codebase, going through the docs, issues etc<br />
|-<br />
| Onboarding || The process of setting up the development environment<br />
|-<br />
| Contributing || Identifying an issue/feature/bug, writing code and pushing it to the projects codebase<br />
|-<br />
| Retention || Identifying what to do next after the first pull request<br />
|}<br />
<br />
<br /><br />
<br />
== Timeline and participation ==<br />
<br />
The experiments are going to begin in the '''first week of February and each experiments will last four weeks'''.<br />
<br />
If you are interested being part of the experiments and you can dedicate just one hour per week for 4 weeks, '''please [http://bit.ly/Contribute2FOSS fill this form]'''.<br />
<br />
<br /><br />
<br />
== Mentors ==<br />
The students will have the opportunity to work on a variety of open source projects based on their interests and skills. In every step of the process, they will have experienced mentors to guide them and support them.<br />
<br />
As mentors you will have the opportunity to work with top students from across the US who are passionate to learn and contribute to Open Source projects.<br />
If you are mentoring, maintaining or contributing to an open source project and you are looking to mentor a small group of students for contributing to your project, please drop us a line at christos AT mozilla dot com.<br />
Requirements: As a mentor you have to dedicate the minimum of 1 hour per week for supporting your students. You can always dedicate more time but it's also up to each experiment and the different mentorship model each experiment is testing.</div>Bacharakishttps://wiki.mozilla.org/index.php?title=OSSN/OpenSourceExperiments&diff=1187906OSSN/OpenSourceExperiments2018-01-30T13:47:42Z<p>Bacharakis: added more info around the issues we are trying to solve for</p>
<hr />
<div>== Intro ==<br />
As part of the [http://opensource.mozilla.community/ Open Source Student Network pilot program] we are designing a set of experiments for better understanding the user journey of University students towards their first open source project.<br />
<br />
The goal of these experiments is to '''to discover and/or validate opportunities and best practices for supporting University Tech students throughout their journey for contributing code to Open Source Projects.'''<br />
<br />
We will closely work with the Clubs of our [http://opensource.mozilla.community OSSN network] for recruiting students who would be interested being part of the experiments. <br />
<br />
== The problem we are trying to solve for ==<br />
Based on our recent research, there is a significant number of University students across the United States who want to contribute to Open Source projects. Most of these students drop off at some point during their journey due to various reasons.<br />
<br />
The goal of these experiments is to identify the various reasons students drop off and provide a set of recommendations.<br />
<br />
We also believe that through these experiments we will be able to identify if there is a intervention that Mozilla can do which will turn Computer Science students to Open Source contributors.<br />
<br />
== Questions we are trying to answer ==<br />
{| class="wikitable"<br />
|-<br />
! Journey !! Questions<br />
|-<br />
| Discovery || <br />
* Are students more interested in projects tailored to their skill/language or to projects with a mission<br />
* Do students look for evidence of a positive community before they interact?<br />
* Do diverse students spend more time looking for a positive community than other students?<br />
* Are students interested in Major already established open source projects or to small class project<br />
|-<br />
| Engagement || <br />
* Students are more engaged with projects that meet a specific skill or with projects where they have a full stack understanding<br />
* Are projects with video introductions attract more students?<br />
* Is suggested bug matching based on what you just did works better than just exploring for new issues to work on?<br />
* Are github issues with more documentation and screenshots help students select project to work on?<br />
* Unclear or missing documentation will make it less possible for students to select and contribute to a project<br />
|-<br />
| Onboarding || <br />
* How much help should be given to students?<br />
* Does the group effect matters for getting people on board to a project? (Groups working on the same projects vs individuals to different projects<br />
* Is setting up the development environment a blocker - a process which potentially can scare people away?<br />
* Is having the maintainer getting you onboard VS a project contributor more impactful?<br />
|-<br />
| Contribution || <br />
* Solving a dummy bug VS fixing an actual bug will empower students to come back and work on another issue/bug? <br />
* What affects the retention after 1st contribution <br />
* How effective are first good bugs for longer engagement <br />
* Easy vs hard issue - solving a bug which you can reference <br />
* New feature vs fix/optimize issue <br />
|-<br />
| Retention || <br />
* Does an invitation back to the project have better results? <br />
* Suggested next projects/issues etc <br />
* Has this person contributed to an open source project after he/she graduate? <br />
* How important is the time from pushing a pull request to reviewing it. Is it an important factor for a future contribution? <br />
|-<br />
| Across the whole journey || <br />
* Does regular communication play an important role? In which sequence and form? <br />
* Which mentorship model is more effective in each step? <br />
* Are bots effective in each step of the journey? <br />
* Do suggested next steps have better results in each step of the journey than letting students explore alone? <br />
* Are students more effective when they are in a group or when they are alone? <br />
|}<br />
== As a student ==<br />
The only requirement for the students is to dedicate one hour per week for taking part into our online sessions/calls. <br />
No prior experience is a certain programming language or a technology stack is needed and we invite all students regardless their skills or experiences to sign up.<br />
<br />
All the students will participate in small experiments throughout their journey towards their first code contribution.<br />
<br />
The students will have the opportunity to work on a variety of open source projects based on their interests and skills. In every step of the process, they will have experienced mentors to guide them and support them.<br />
<br />
{| class="wikitable"<br />
|-<br />
! User Journey !! What students will do<br />
|-<br />
| Discovery || The process where students will identify a project to work on<br />
|-<br />
| Engagement || There process where students will engage with a project by reading its codebase, going through the docs, issues etc<br />
|-<br />
| Onboarding || The process of setting up the development environment<br />
|-<br />
| Contributing || Identifying an issue/feature/bug, writing code and pushing it to the projects codebase<br />
|-<br />
| Retention || Identifying what to do next after the first pull request<br />
|}<br />
<br />
== Timeline and call to action ==<br />
<br />
The experiments are going to begin in the '''first week of February and each experiments will last four weeks'''.<br />
<br />
If you are interested being part of the experiments and you can dedicate just one hour per week for 4 weeks, '''please [http://bit.ly/Contribute2FOSS fill this form]'''.<br />
<br />
== Mentors ==<br />
The students will have the opportunity to work on a variety of open source projects based on their interests and skills. In every step of the process, they will have experienced mentors to guide them and support them.<br />
<br />
As mentors you will have the opportunity to work with top students from across the US who are passionate to learn and contribute to Open Source projects.<br />
If you are mentoring, maintaining or contributing to an open source project and you are looking to mentor a small group of students for contributing to your project, please drop us a line at christos AT mozilla dot com.<br />
Requirements: As a mentor you have to dedicate the minimum of 1 hour per week for supporting your students. You can always dedicate more time but it's also up to each experiment and the different mentorship model each experiment is testing.</div>Bacharakishttps://wiki.mozilla.org/index.php?title=OSSN/OpenSourceExperiments&diff=1187443OSSN/OpenSourceExperiments2018-01-23T18:24:37Z<p>Bacharakis: Add format</p>
<hr />
<div>== Intro ==<br />
As part of the [http://opensource.mozilla.community/ Open Source Student Network pilot program] we are designing a set of experiments on better understanding the user journey of University students towards their first open source project.<br />
<br />
The goal of these experiments is to '''identify a set of best practices which are facilitating/driving/supporting University students to make their first code contribution to an Open Source project.'''<br />
<br />
We will closely work with the Clubs of our OSSN network for recruiting students who would be interested being part of the experiments. <br />
<br />
== Approach ==<br />
The only requirement for the students is to dedicate one hour per week for taking part into our online sessions/calls. <br />
No prior experience is a certain programming language or a technology stack is needed and we invite all students regardless their skills or experiences to sign up.<br />
<br />
All the students will participate in small experiments throughout their journey towards their first code contribution.<br />
<br />
{| class="wikitable"<br />
|-<br />
! User Journey !! What students will do<br />
|-<br />
| Discovery || The process where students will identify a project to work on<br />
|-<br />
| Engagement || There process where students will engage with a project by reading its codebase, going through the docs, issues etc<br />
|-<br />
| Onboarding || The process of setting up the development environment<br />
|-<br />
| Contributing || Identifying an issue/feature/bug, writing code and pushing it to the projects codebase<br />
|-<br />
| Retention || Identifying what to do next after the first pull request<br />
|}<br />
<br />
== Timeline and call to action ==<br />
The experiments are going to begin in the '''first week of February and each experiments will last four weeks'''.<br />
<br />
If you are interested being part of the experiments and you can dedicate just one hour per week for 4 weeks, '''please [http://bit.ly/Contribute2FOSS fill this form]'''.</div>Bacharakishttps://wiki.mozilla.org/index.php?title=OSSN/OpenSourceExperiments&diff=1187441OSSN/OpenSourceExperiments2018-01-23T18:20:31Z<p>Bacharakis: Created page with "== Intro == As part of the [http://opensource.mozilla.community/ Open Source Student Network pilot program] we are designing a set of experiments on better understanding the u..."</p>
<hr />
<div>== Intro ==<br />
As part of the [http://opensource.mozilla.community/ Open Source Student Network pilot program] we are designing a set of experiments on better understanding the user journey of University students towards their first open source project.<br />
<br />
The goal of these experiments is to '''identify a set of best practices which are facilitating/driving/supporting University students to make their first code contribution to an Open Source project.'''<br />
<br />
We will closely work with the Clubs of our OSSN network for recruiting students who would be interested being part of the experiments. <br />
<br />
== Approach ==<br />
The only requirement for the students is to dedicate one hour per week for taking part into our online sessions/calls. <br />
No prior experience is a certain programming language or a technology stack is needed and we invite all students regardless their skills or experiences to sign up.<br />
<br />
All the students will participate in small experiments throughout their journey towards their first code contribution.<br />
<br />
{| class="wikitable"<br />
|-<br />
! User Journey !! What students will do<br />
|-<br />
| Discovery || The process where students will identify a project to work on<br />
|-<br />
| Engagement || There process where students will engage with a project by reading its codebase, going through the docs, issues etc<br />
|-<br />
| Onboarding || The process of setting up the development environment<br />
|-<br />
| Contributing || Identifying an issue/feature/bug, writing code and pushing it to the projects codebase<br />
|-<br />
| Retention || Identifying what to do next after the first pull request<br />
|}<br />
<br />
== Timeline and call to action ==<br />
The experiment are going to begin in the first week of February and each experiments will last four weeks.<br />
<br />
If you are interested being part of the experiments and you can dedicate just one hour per week for 4 weeks, please [http://bit.ly/Contribute2FOSS fill this form].</div>Bacharakishttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2017-07-31&diff=1182698WeeklyUpdates/2017-07-312017-10-23T16:26:10Z<p>Bacharakis: UTC timezone was wrong!</p>
<hr />
<div><br />
{{WeeklyUpdateNav}}<br />
* Every Monday @ 11:00am Pacific Time (18:00 UTC) <br />
* https://air.mozilla.org/channels/project-meeting/ to watch and listen<br />
* join irc.mozilla.org #airmozilla for backchannel discussion<br />
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak. <br />
{{conf|8600}}<br />
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br />
* Thanks to dw-dev, Swapnesh Sahoo, Tushar Saini, and zombie for contributing to WebExtensions APIs during the month of July! You can learn more about their contributions on the [[Add-ons/Contribute/Recognition|add-ons recognition wiki]].<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
* [[Add-ons/Community/Meetings|Add-ons Community Meeting]]<br />
** 17:00 - 17:30 UTC | 10am - 10:30am Pacific; ACE Vidyo Room<br />
<br />
* [[Add-ons/Contribute/Triage#Next_Meeting|WebExtensions APIs Triage]]<br />
** 17:30 - 18:00 | 10:30am - 11am Pacific; ACE Vidyo Room<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
<br />
* '''[https://indiewebcamp.com/events/2017-08-02-homebrew-website-club Homebrew Website Club Meetup]''' (nearly every Wednesday somewhere)<br/><strong>Be a part of the open web!</strong><br />
** '''Portland (<abbr title="Oregon">OR</abbr>)''' (at DreamHost PDX)<br />
** 17:30-18:30 Quiet Writing Hour, finish that blog post, wiki edit, etc.!<br />
** 18:30-19:30 IndieWeb meetup, demos, & hack night <blockquote><p>Create or update your personal web site!<br/>Share what you've gotten working.</p><p>Join a community with like-minded interests. <br/>Bring friends that want a personal site!</p></blockquote> Any questions? See '''[https://indiewebcamp.com/events/2017-08-02-homebrew-website-club the wiki page for details]''' <br/>or join IRC: https://indieweb.org/discuss<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br />
<br />
=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br />
<br />
=== Next Week ===<br />
* Wednesday, 09 August - [https://indieweb.org/events/2017-08-09-homebrew-website-club Homebrew Website Club] in Brighton, London, Baltimore, and more cities.<br />
<br />
== Speakers ==<br />
<br />
The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! [https://mozillians.org/u/USERNAME Presenter]<br />
! Title<br />
! Topic<br />
! Location<br />
! Sharing<br />
! Media<br />
! More Details<br />
|-<br />
| Who Are You?<br />
| What Do You Do?<br />
| What are you going to talk about?<br />
| Where are you presenting from? (Moz Space, your house, space)<br />
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br />
| Links to slides or images you want displayed on screen<br />
| Link to where audience can find out more information<br />
|-<br />
| Asa Dotzler<br />
| Firefox Roadmap<br />
| Weekly Firefox Update<br />
| MTV<br />
| no<br />
| n/a<br />
| https://wiki.mozilla.org/Firefox/Roadmap/Updates#2017-07-31<br />
|-<br />
| Chris Lawrence<br />
| V.P. Leadership Network<br />
| MozFest <br />
| Brooklyn, NYC<br />
| no<br />
| <br />
| https://mozillafestival.org/<br />
|-<br />
|-<br />
| Ali Spivak<br />
| Developer Outreach <br />
| Mozilla View Source Conference<br />
| Mountain View<br />
| no<br />
| <br />
| [https://viewsourceconf.org/london-2017/ View Source website]<br />
|-<br />
| Miriam Avery<br />
| Director of Strategic Foresight<br />
| Emerging Technologies Weekly Update<br />
| Mountain View<br />
| no<br />
| n/a<br />
| https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology#July_31st.2C_2017<br />
|-<br />
| John Gruen<br />
| Test Pilot Product Manager<br />
| We're Launching New Experiments TOMORROW!<br />
| Test Pilot Flight Deck<br />
| Yes<br />
| n/a<br />
| https://testpilot.firefox.com (but not til tomorrow)<br />
|-<br />
|-<br />
| David Durst<br />
| Engineering manager, Firefox Core Engineering<br />
| Updates to the app updater in 56<br />
| remote<br />
| no<br />
| n/a<br />
| signing: https://bugzilla.mozilla.org/show_bug.cgi?id=1324498<br>compression: https://bugzilla.mozilla.org/show_bug.cgi?id=641212<br>IRC: #fce and/or #releng<br />
|-<br />
|}<br />
<br />
= Welcome! =<br />
<br />
Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! ''Who is being introduced?''<br />
! ''Who are you? (the introducer)''<br />
! ''Where are you doing the introduction?''<br />
! ''Where are they from?''<br />
! ''How will they be part of Mozilla?''<br />
|-<br />
| Trevor Smith<br />
| Lars Bergstrom<br />
| Remote (Chicago, IL)<br />
| Remote (Seattle, WA)<br />
| Augmented Reality Research Engineer<br />
|-<br />
| Ryan Gaddis<br />
| Philipp Sackl<br />
| Denver, CO<br />
| Denver, CO<br />
| Product Designer for Project Lockbox<br />
|-<br />
| Mike Conca<br />
| Kev Needham<br />
| Denver, CO<br />
| Denver, CO<br />
| Product Manager, WebExtensions<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
|}<br />
<br />
= Fireside Chat =<br />
A chance to hear from leadership at Mozilla, and have a short Q&A about a specific topic.<br />
<br />
===This Week===<br />
<br />
'''Name''', "Title"<br />
<br />
===Topics===<br />
<br />
You can submit questions in advance on the Moderator page (link), or ask them live on Air Mozilla using a Mozilla Space mic or in #airmozilla on IRC.<br />
<br />
[[Category:Weekly Updates]]<br />
[[Category:Meeting Notes]]</div>Bacharakishttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2017-04-10&diff=1167887WeeklyUpdates/2017-04-102017-04-10T12:30:24Z<p>Bacharakis: Adding US Research for Campus Clubs</p>
<hr />
<div><br />
{{WeeklyUpdateNav}}<br />
* Every Monday @ 11:00am Pacific Time (19:00 UTC) <br />
* https://air.mozilla.org/channels/project-meeting/ to watch and listen<br />
* join irc.mozilla.org #airmozilla for backchannel discussion<br />
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak. <br />
{{conf|8600}}<br />
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br />
<br />
* Big thanks to Jason Williams of the BBC for his work on Servo, making it easier for Windows users to participate - and extra props for writing about it on Mozilla Hacks! [https://hacks.mozilla.org/2017/04/hacking-contributing-to-servo-on-windows/ Hacking & Contributing to Servo on Windows]<br />
<br />
* Thanks to all the Tech Speakers who've been out and about delivering talks & workshops: Srushtika, Ram, Riccardo, Daniele, Eugenio, Andre, Bob, Yuli, Felipe, Abhiram, Viswaprasath, Miguel, Kristi, and everyone else!<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
* [https://quality.mozilla.org/event/bug-triage-day-154/ Weekly Bug Triage Day]<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
* [[Add-ons/Community/Meetings|Add-ons Community Meeting]]<br />
** 10am PT; ACE Vidyo Room<br />
*** Join the team to discuss what's going on in the add-ons community!<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
* [https://quality.mozilla.org/event/bug-verification-day-165/ Weekly Bug Verification Day]<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br />
<br />
=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br />
<br />
=== Next Week ===<br />
<br />
== Speakers ==<br />
<br />
The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! [https://mozillians.org/u/USERNAME Presenter]<br />
! Title<br />
! Topic<br />
! Location<br />
! Sharing<br />
! Media<br />
! More Details<br />
|-<br />
| Who Are You?<br />
| What Do You Do?<br />
| What are you going to talk about?<br />
| Where are you presenting from? (Moz Space, your house, space)<br />
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br />
| Links to slides or images you want displayed on screen<br />
| Link to where audience can find out more information<br />
|-<br />
| Aurelia Moser<br />
| Community Lead, Mozilla Science<br />
| Mozilla Science Fellows CFP<br />
| Home<br />
| no<br />
| https://docs.google.com/a/mozilla.com/presentation/d/1y3NXP3sLj-nVGq88BZhWhtRBPYynWltVOF4BuaUpMac/edit?usp=sharing<br />
| https://science.mozilla.org/programs/fellowships<br />
|-<br />
| Don Marti<br />
| Strategist, Open Innovation<br />
| Filterbubbler Project<br />
| Mozilla San Francisco<br />
| no<br />
| http://www.filterbubbler.org/<br />
| https://github.com/filterbubbler<br />
|-<br />
| Asa Dotzler<br />
| Firefox Roadmap<br />
| Firefox Update<br />
| MTV<br />
| no<br />
| no<br />
| https://wiki.mozilla.org/Firefox/Roadmap/Updates#2017-04-10<br />
|-<br />
| Christos Bacharakis<br />
| Project Manager at Mozilla Campus Clubs, Open Innovation<br />
| Open Source in US Universities<br />
| Home<br />
| Yes<br />
| https://docs.google.com/presentation/d/1Sc04T27847_CWYeZ-y1rXDqbEh38HNJbjHRbhEMOpqw/present#slide=id.g1dbf9b7280_0_65<br />
| https://docs.google.com/presentation/d/1Sc04T27847_CWYeZ-y1rXDqbEh38HNJbjHRbhEMOpqw/present#slide=id.g1dbf9b7280_0_65<br />
|-<br />
|}<br />
<br />
= Welcome! =<br />
<br />
Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! ''Who is being introduced?''<br />
! ''Who are you? (the introducer)''<br />
! ''Where are you doing the introduction?''<br />
! ''Where are they from?''<br />
! ''How will they be part of Mozilla?''<br />
|-<br />
! 25 New Hires<br />
! [https://mozillians.org/en-US/u/diane1/ Diane Tate]<br />
! Mozilla Mountain View<br />
! [https://docs.google.com/spreadsheets/d/1mWI0wo4il7Lw97bRGns-ri7FzCpRcjqwAeL6UqGe2Yg/edit?usp=sharing All Over]<br />
! [https://docs.google.com/presentation/d/1XgQ_9A03EF8Dc_gJSj8MSFeC28sAx9ge_GgcI2ErXoM/edit?usp=sharing all sort of ways]<br />
|-<br />
|}<br />
<br />
= Fireside Chat =<br />
A chance to hear from leadership at Mozilla, and have a short Q&A about a specific topic.<br />
<br />
===This Week===<br />
<br />
'''Name''', "Title"<br />
<br />
===Topics===<br />
<br />
You can submit questions in advance on the Moderator page (link), or ask them live on Air Mozilla using a Mozilla Space mic or in #airmozilla on IRC.<br />
<br />
[[Category:Weekly Updates]]<br />
[[Category:Meeting Notes]]</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Category:FirefoxClubs&diff=1154011Category:FirefoxClubs2016-11-08T13:45:15Z<p>Bacharakis: Adding info for transitioning FSA to Campus Clubs</p>
<hr />
<div><div style="display:block;-moz-border-radius:10px;background-color:#f5b7b1;padding:20px;margin-top:20px; border: 4px solid rgb(40, 40, 40);"><br />
<br />
<h3><span class="mw-headline">IMPORTANT NOTICE : The FSA program is now set to transition to Campus Clubs</span></h3><br />
<div style="display:block;-moz-border-radius:10px;background-color: #fadbd8 ;padding:20px;margin-top:20px;"><br />
<b>A new program is coming to campuses this September that is aligned with the existing Mozilla Clubs structure and will provide a unified model for participation on campuses around the world. <br><br />
<br />
Mozilla Campus Clubs will be replacing the FSA program and so we won’t be accepting any new Firefox Student Ambassadors. The listed FSA Activities won’t be carried any more. You can find more information about the future of the program in [https://discourse.mozilla-community.org/t/reinventing-mozilla-on-campus/8730 this post], where you can also leave your questions.<br />
<br><br><br />
Learn more about the Campus Clubs at: [https://campus.mozilla.community/ campus.mozilla.community] <br />
</b> <br />
</div><br />
<br />
</div><br />
<br />
<br />
<div style="clear:both; border: 4px solid rgb(40, 40, 40); text-align:center; padding: 2px; background: #dddddd; border-collapse: separate; -moz-border-radius: 10px; margin-top:20px;"><br />
[https://wiki.mozilla.org/StudentAmbassadors Main] | [https://wiki.mozilla.org/StudentAmbassadors/Join Join] | [https://wiki.mozilla.org/StudentAmbassadors/ProgramStructure Program Structure] | [https://wiki.mozilla.org/StudentAmbassadors/Contact Contact Us] | [https://wiki.mozilla.org/StudentAmbassadors/Activities Activities] | [https://wiki.mozilla.org/StudentAmbassadors/Toolkit Toolkit] | [https://wiki.mozilla.org/StudentAmbassadors/Recognition Recognition] | [https://wiki.mozilla.org/StudentAmbassadors/Mozilla About: Firefox and Mozilla] | [https://wiki.mozilla.org/StudentAmbassadors/FAQ FAQ]<br />
</div><br />
<br><br />
<br><br />
<br />
<br />
Firefox Clubs are the Clubs set up by Firefox Student Ambassadors. If you do see a Firefox Club for your university, please contact the Club Lead and join!<br />
<br />
To find a Club in your country, please go to https://wiki.mozilla.org/Special:SearchByProperty/ClubCountry/[insert country here] and replace [insert country here] with the name of your country.</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/Meetings/Council-2015-10-21&diff=1102761Reps/Meetings/Council-2015-10-212015-10-27T15:47:57Z<p>Bacharakis: </p>
<hr />
<div>{{RemoCouncilMeeting<br />
|date=2015/10/21 02:30:00 PM<br />
|attendees=Michael,Nuke, Bob, San James,Christos,Shahid<br />
}}<br />
Hello wonderful Reps!<br />
<br />
This week we:<br />
<br />
- Discussed on budget request SOPs and the 3 weeks rule. Going to send an update on Reps-general soon.<br />
- We are discussing with Pierros about the council elections how we should continue with this.<br />
- A letter for supporting Reps and providing any necessary information about their relation with Mozilla was drafted thanks to mentors and council.<br />
- We were contacted from Jeff of the l10n team in order to discuss this year’s Reps activities on localization and next steps for 2016. We discussed this during this week meeting and we also scheduled a meeting in Orlando with Jeff.<br />
<br />
For any further information or help, don't hesitate to contact us at reps-council@mozilla.com</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/Meetings/Council-2015-10-21&diff=1102760Reps/Meetings/Council-2015-10-212015-10-27T15:47:35Z<p>Bacharakis: Created page with "{{RemoCouncilMeeting |date=2015/10/14 02:30:00 PM |attendees=Michael,Nuke, Bob, San James,Christos,Shahid }} Hello wonderful Reps! This week we: - Discussed on budget requ..."</p>
<hr />
<div>{{RemoCouncilMeeting<br />
|date=2015/10/14 02:30:00 PM<br />
|attendees=Michael,Nuke, Bob, San James,Christos,Shahid<br />
<br />
}}<br />
Hello wonderful Reps!<br />
<br />
This week we:<br />
<br />
- Discussed on budget request SOPs and the 3 weeks rule. Going to send an update on Reps-general soon.<br />
- We are discussing with Pierros about the council elections how we should continue with this.<br />
- A letter for supporting Reps and providing any necessary information about their relation with Mozilla was drafted thanks to mentors and council.<br />
- We were contacted from Jeff of the l10n team in order to discuss this year’s Reps activities on localization and next steps for 2016. We discussed this during this week meeting and we also scheduled a meeting in Orlando with Jeff.<br />
<br />
For any further information or help, don't hesitate to contact us at reps-council@mozilla.com</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/Meetings/Council-2015-10-14&diff=1101171Reps/Meetings/Council-2015-10-142015-10-18T15:01:25Z<p>Bacharakis: added new topic</p>
<hr />
<div>{{RemoCouncilMeeting<br />
|date=2015/10/14 02:30:00 PM<br />
|attendees=Michael,Nuke,Rosana,Christos,Shahid<br />
<br />
}}<br />
===Mentor role===<br />
This week we discussed on how important is the mentor's role for having a successful Reps program. He had a discussion on how we define a “perfect” mentor and tried to identified ways and techniques on how to better empower them.<br />
<br />
===Helping out communities===<br />
We also talked on how to help new and inexperienced communities in order to close the gap between communities and individual contributors.<br />
<br />
===Reps recognition===<br />
Last but not least we brainstormed on ideas around Reps recognition but wait, this supposed to be a surprize.. Shhhh. No worries we will share more information by the end of this month.</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/Meetings/Council-2015-10-14&diff=1101170Reps/Meetings/Council-2015-10-142015-10-18T15:00:41Z<p>Bacharakis: Created page with "{{RemoCouncilMeeting |date=2015/10/14 02:30:00 PM |attendees=Michael,Nuke,Rosana,Christos,Shahid }} ===Mentor role=== This week we discussed on how important is the mentor's..."</p>
<hr />
<div>{{RemoCouncilMeeting<br />
|date=2015/10/14 02:30:00 PM<br />
|attendees=Michael,Nuke,Rosana,Christos,Shahid<br />
<br />
}}<br />
===Mentor role===<br />
This week we discussed on how important is the mentor's role for having a successful Reps program. He had a discussion on how we define a “perfect” mentor and tried to identified ways and techniques on how to better empower them.<br />
<br />
===Helping out communities===<br />
We also talked on how to help new and inexperienced communities in order to close the gap between communities and individual contributors.<br />
<br />
Reps recognition<br />
Last but not least we brainstormed on ideas around Reps recognition but wait, this supposed to be a surprize.. Shhhh. No worries we will share more information by the end of this month.</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/Meetings/Council-2015-10-07&diff=1101169Reps/Meetings/Council-2015-10-072015-10-18T14:57:57Z<p>Bacharakis: Created page with "{{RemoCouncilMeeting |date=2015/10/07 02:30:00 PM |attendees=Ankit,Shahid,Christos,Luis,Michael,Rosana }} ===Etherpad migration=== -The participation team along with the IT te..."</p>
<hr />
<div>{{RemoCouncilMeeting<br />
|date=2015/10/07 02:30:00 PM<br />
|attendees=Ankit,Shahid,Christos,Luis,Michael,Rosana<br />
}}<br />
===Etherpad migration===<br />
-The participation team along with the IT team are putting a huge effort on having a smooth transition. <br />
<br />
-There was a call to action in Reps- general from Rosana, you can help by responding to it (if necessary).<br />
<br />
===Coaching communities - the Kerala community===<br />
- council established a communication with this amazing community<br />
<br />
- they have a really promising plan and council will help them achieve it<br />
<br />
- council is always available for coaching at reps-council@mozilla.com<br />
<br />
===New Reps application Queue===<br />
- There are some delays in mentors assignment which will be solved by early next week<br />
<br />
===New council members voting period===<br />
- The process will begin soon by the module owner, Pierros</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/SOPs/Mentoring&diff=1086063Reps/SOPs/Mentoring2015-07-22T14:04:17Z<p>Bacharakis: added link to mentors selection process</p>
<hr />
<div>{{Remonav}}<br />
Mozilla Reps recognizes that our primary goals are best reached through the support, encouragement, and empowerment of community through mentorship. Mentoring is a process for the informal transmission of knowledge, made possible through regular and supportive interaction. <br />
<br />
We encourage mentors to be as open to learning from their mentees, as they are to teaching, for the benefit and growth of both individuals and the program as a whole.<br />
<br />
Being a Mozilla Reps mentor also requires a familiarity with different tools and processes that the Council has put in place to better streamline the way Mozilla Reps can document their activities, request budgets for projects, order swag and interact with other Reps. <br />
<br />
====How to Become a Mentor====<br />
Nominations are requested by council of the mentor community on an 'as needed basis'. <br />
New Mentors are nominated by existing Mentors, through one of two ways:<br />
# Direct recognition by a mentor. ie: They know someone who would make a great mentor.<br />
# Self-nomination, which is the process of proclaiming your interest to your own mentor or another mentor in the community. It will be that mentor's job to evaluate the self-nominating Rep. make recommendations to council, as to whether that self-nomination should be accepted.<br />
<br />
You can read the complete process [[ReMo/Mentors/SelectionProcess|here]]<br />
<br />
====Administrative====<br />
<br />
The mentor role comes with many administrative tasks, of which these are requirements.<br />
<br />
* Reviewing applications assigned to them on Bugzilla <br />
* Interviewing applicants to learn more about them, and tell them more about the program <br />
* Informing applicants whether or not they've been accepted to the program<br />
* Reviewing and validating their Reps with swag and budget requests<br />
* Providing feedback & suggestions to the Council<br />
* Participating in regional meetings (online and offline), notably the annual ReMo Camp. <br />
* Send Welcome Pack after Orientation Period Ends <br />
<br />
<br />
====Mentoring====<br />
<br />
The mentor role is also important in the development and success of mentees, as future leaders of the program. These are the requirements of Reps mentorship:<br />
<br />
*[[Mentor Orientation Call|Scheduling an Orientation Call]]<br />
* Regular communication, as defined in orientation call.<br />
* Assist in more complicated budgets.<br />
* Update mentees Rep Portal activities with comments, encouragement & feedback.<br />
* Read all follow-up posts on bug - blog posts & photos (share where appropriate)<br />
* Nominate mentees for Rep of the Month, for reaching or exceeding goals & expectations.<br />
* Flag opportunities for your mentees (training, events, introductions)<br />
* Publicly celebrate the success of their initiatives<br />
* Communicate recognition of emerging leaders to council<br />
<br />
'''NB: for information on first-steps of Mentors, click [[ReMo/Mentors|here]].'''<br />
<br />
<!-- === Becoming a mentor trainer ===<br />
Having hands-on experience with mentoring is an important step of your contribution path in Mozilla Reps program. The accumulated experience, best practices --><br />
<br />
== Screening Rep Applications process ==<br />
{{Admon/important |Keep bugs tidy| Please make sure that within the process the application bug is up to date with the progress and reflects the steps as noted below}}<br />
<br />
=== 1) Being assigned an applicant ===<br />
Once an applicant has submitted their application form, a bug is created on bugzilla that is triaged by Reps leadership. If this applicant has been selected for the next round, they might assign this applicant to you, by assigning you the bug. If this is the case, you will receive an email informing you of this and will be able to access it.<br />
<br />
Bug Status : '''ASSIGNED'''<br><br />
Bug Whiteboard : '''Mentor assigned'''<br />
<br />
=== 2) Screening the applicant ===<br />
The bug you've been assigned contains all the applicant submitted when applying. Read carefully through this information and decide whether or not you think this person is a good candidate to become a Mozilla Rep. [[ReMo/SOPs/Mentoring/Screening|Learn more...]]<br />
<br />
=== 3) Orientation Period ===<br />
<br />
After an applicant has been approved to join the program, he or she has a period of working closely with their mentor to get started as a rep. including an [[Mentor_Orientation_Call|Orientation Call]]. During this period (called the "Orientation Period) a mentor will help the applicant: <br />
<br />
*Take the first steps in becoming a rep, including returning a signed agreement and filling out a rep profile <br />
*Learn their responsibilities, such as completing monthly reports <br />
*Get started attending and planning events in their local area<br />
*Set personal goals<br />
<br />
The duration of the orientation period from one Rep to the next. A mentor also decides when a Rep is ready "graduated" from the orientation period. [[ReMo/SOPs/Mentoring/Orientation|Learn more...]]<br />
<br />
=== 4) Post-Orientation Period ===<br />
Mentors continue to work with their Reps even after the orientation period. Mentors are tasked to always: <br />
<br />
*Monitor their Reps' [[ReMo/SOPs/Monthly_Reports|monthly reports]] <br />
*Review and validate their Reps with swag and budget requests [[ReMo/Tools_and_Resources|(see Tools & Resources)]]<br />
*Nominate their reps for appropriate recognition and rewards <br />
*Raise the profile of emerging leaders to council<br />
*Answer any questions or help with any issues/problems their Reps may have<br />
<br />
Bug Status : '''RESOLVED'''<br><br />
Bug Whiteboard : '''Accepted/Orientation Finished'''<br />
<br />
--------------------------------------------------------------------------------<br />
=== Re-assigning mentorship to another mentor ===<br />
There are some cases when the mentor assigned to a rep can no longer fulfill his/her duties as mentor. [[ReMo/SOPs/Mentoring/Reassigning|Learn more...]]<br />
<br />
== List of Mentors ==<br />
<br />
Here, you can find the [https://reps.mozilla.org/people/#/view/grid/group/mentor/ full list of mentors].<br />
<br />
[[Category:Remosop]]</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/Mentors&diff=1086060Reps/Mentors2015-07-22T13:55:48Z<p>Bacharakis: added link to mentors selection process</p>
<hr />
<div>Mentors, together with the Council members, are the backbone of the Mozilla Reps program. They make sure things run smoothly, they ensure that Reps are supported and have what they need to be impactful in their region. This are the intial steps of mentorship with Mozilla Reps. You can find the complete mentoring process [[ReMo/Mentors/SelectionProcess |here]]. <br />
<br />
=== How to become a mentor ===<br />
<br />
Currently new mentors are selected by Council on regular basis when needed. Mentor proposals are sent by current mentors to Council for consideration.<br />
<br />
=== Next steps when becoming a mentor ===<br />
<br />
Once a Mozilla Rep has accepted to become a mentor, (s)he must follow these next steps to be ready to start mentoring:<br />
<br />
# Complete [[ReMo/SOPs/Mentoring_Training|Mentor Training]].<br />
# Carefully read through the relevant mentor SOPs:<br />
* "Mentoring" SOP : https://wiki.mozilla.org/ReMo/SOPs/Mentoring <br />
* "Swag Review" SOP: https://wiki.mozilla.org/ReMo/SOPs/Swag_Requests<br />
* "Budget Review" SOP: https://wiki.mozilla.org/ReMo/SOPs/Budget<br />
# Be subscribed to reps-mentors mailing list.<br />
<br />
=== List of current mentors ===<br />
<br />
Here, you can find the current [https://reps.mozilla.org/people/#/view/grid/group/mentor/ list of mentors here]</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/Mentors/SelectionProcess&diff=1086059Reps/Mentors/SelectionProcess2015-07-22T13:53:56Z<p>Bacharakis: Created page with "===How to become a mentor === Nominations are requested by council of the mentor community on an 'as needed basis'. New Mentors are nominated by existing Mentors or the Reps c..."</p>
<hr />
<div>===How to become a mentor ===<br />
Nominations are requested by council of the mentor community on an 'as needed basis'. New Mentors are nominated by existing Mentors or the Reps council, through one of two ways:<br />
<br />
* Direct recognition by a mentor. ie: They know someone who would make a great mentor.<br />
* Self-nomination, which is the process of proclaiming your interest to your own mentor or another mentor in the community. It will be that mentor's job to evaluate the self-nominating Rep. make recommendations to council, as to whether that self-nomination should be accepted.<br />
<br />
=== How often new mentors are selected ===<br />
New mentors are evaluated and selected normally when needed. For example when there are orphan mentees to be reassigned or when a mentor leaves.<br />
<br />
=== Mentors selection criteria ===<br />
* Fluent English<br />
* Experience in functional areas (community building, Firefox, Firefox OS, webmaker etc)<br />
* Engaged and active within the community (attending meetings, taking action)<br />
* Demonstrated good skills in Reps procedures or mentorship. <br />
* Has time to dedicate to the mentorship role.<br />
* Is willing to take on the responsibilities (if proposed by somebody else)<br />
* Quick response in Bugzilla<br />
<br />
=== Process ===<br />
* Council or mentor propose new mentors to council with an explanation on why this person thinks that this proposed Rep would be a good mentor.<br />
* Sometime Reps also step up and nominate themselves for mentor selection.<br />
* There is a communication that lists the reasons why a specific Rep has the potential to be a good mentor. It lists accomplishments, past initiatives, role in regional and local communities, impact in functional areas. <br />
* Council reviews the candidate(s) and add him/her to a tracking spreadsheet.<br />
* When there is a need for new mentors Council reviews the spreadsheet.<br />
* Council votes.<br />
* Mentors are selected.<br />
* Mentors take an on boarding [[ReMo/SOPs/Mentoring_Training|training]].<br />
* New mentors are announced and permissions granted.<br />
* Mentors can start mentoring new mentees according to the process described [[ReMo/SOPs/Mentoring |here]].</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Balkans/Events:2015/Bucharest/Thanks&diff=1076098Balkans/Events:2015/Bucharest/Thanks2015-05-23T08:10:45Z<p>Bacharakis: a huge thanks to Ioana</p>
<hr />
<div>Please feel free to add any thank to people who helped plan this event, or people you met that inspired you in some way.<br />
<br />
*[marcia] Thanks to Ioana for all her hard work planning this event and for being such a gracious host during my stay in Romania.<br />
*[marcia] Thanks to the Serbians for some great dinner conversation on Friday night.<br />
*[christos] A huge "thank you" to Ioana for organizing Ioana's meetup AKA MozBalkans. "Seriously girl?", simply AMAZING work!¡</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/Mozilla_Festival_2013&diff=737167Reps/Mozilla Festival 20132013-10-25T18:42:21Z<p>Bacharakis: </p>
<hr />
<div>===Announcement ===<br />
<br />
The Mozilla Festival (#MozFest) is an annual gathering of unconventional thinkers and inventors from around the world who meet to learn from each other and help forge the future of the web. It takes place from Oct. 25 - 27, 2013 in London, UK. <br />
<br />
Mozilla Reps are passionate people around the world who are spreading the word of Mozilla and generally the word the Open Web.<br />
As you already know Mozilla Reps is one of the driving forces of Mozilla. And Reps, especially those deeply invovled in Mozilla's Webmaker initiative, are going to be a driving force in this year's Mozilla Festival as well.<br />
<br />
Anyone is eligible to participate in the Mozilla Festival. You can register right now here: http://mzl.la/mozfest13-register<br />
However, we know that it's expensive to travel to London on your own. <br />
<br />
That's why the Reps program is offering travel stipends for Reps who have skills and experience beneficial to the Webmaker project.<br />
=== What actually happening in Mozfest - Reps during Mozfest ===<br />
<br />
So finally around 32 Reps are attending Mozfest engaging people in Mozilla's vision and mission about the Open Web.<br />
<br />
==== Friday ====<br />
The Festival is starting with a Science fair where Reps are going to run 2 booths.<br />
* Firefox OS booth: Presenting Firefox OS, new Alcatel and ZTE devices as well some cool devices that run Firefox OS. <br />
* Firefox Student Ambassadors: Our experienced Reps are going to lead the Firefox Student Ambassadors in Science fair where they are going to engage more people with this project.<br />
<br />
In general during the science fair, Mozilla Reps are going to flow around the Festival, interacting with people, represting Mozilla and engage people in Mozilla's projects, ideas and vision.<br />
<br />
==== Saturday and Sunday ==== <br />
Reps' headquarters are going to be in the 6th floor, running a booth presenting the Reps project and the impact that this has in Mozilla, maker and webmaker community.<br />
In addition Reps are going to run 2 booth during the whole weekend: <br />
Firefox OS booth: The same awesome booth is going to take place in the 1st floor along with the Mobile trac.<br />
WebDev + Reps booth: Reps are going to run a booth in the 1st floor about WebDevelopement<br />
<br />
A lot of Reps are engaged in the Guirilla Mentoring too as well in facilitating sessions and tracks.<br />
Generally Reps are deeply involved in the organization of the Festival, in running sessions, running booths and of course representing Mozilla while they engaging more people in Mozilla's mission, vision and projects.<br />
<br />
If you are a Rep you can find more information in the following [https://festival.etherpad.mozilla.org/Reps pad]<br />
<br />
===What's the role and expectation of Reps at Mozfest?===<br />
* represent Mozilla<br />
* empower people in order to participate in Mozfest and generally in to teach the web<br />
* based on their expertise, to lead some sessions in Mozfest<br />
* empower more people in order to be contributors in Mozilla's projects <br />
* have an awesome experience which will provide them a lot of useful information for their community and their future events.<br />
<br />
===What's the timeframe?===<br />
Reps should plan on arriving in London by Thursday, October 24 and departing on Monday, October 28. <br />
<br />
===What is MozFest?===<br />
<br />
It's our annual 3-day festival where many of our best ideas about creativity, learning and the web spring to life. It celebrates our mission and brings new people into our community.<br />
<br />
http://mozillafestival.org/<br />
<br />
MozFest is open to everyone. ~300 Mozillians attend MozFest each year out of 1500 total participants.<br />
<br />
===How does MozFest tie into Mozilla's products and mission?===<br />
<br />
The MozFest program is designed around themes that intersect with the web but are not exclusively linked with our community or our products. This means MozFest is a great opportunity to open our mission to new groups, to offer support for their ideas and to learn from and be inspired by them. Plus, a lot of very cool independent coders, bloggers and journalists tend to be there.<br />
<br />
===What's the difference between MozFest and the Mozilla Summit?===<br />
<br />
The Mozilla Summit is an invite-only event focused creating alignment between the core members of the Mozilla community (including you!) Mozfest is a public event open to anyone interested in helping to make the web better and more creative -- it's about bringing new talent and ideas into Mozilla. This year, MozFest is designed to build on the work of the the Summit for those people who are attending both events: MozFest will allow us to test our thinking and recruit new contributors around ideas coming out of the Summit.<br />
<br />
===What's it like?===<br />
<br />
MozFest is unlike any other tech conference you've been to because it's all about hands-on participation and collaboration. There will be some fabulous keynote speakers, but the majority of the event takes place through interactive workshops. Think: less yack, more hack.<br />
<br />
===Who pays for travel?===<br />
The Reps program is offering travel stipends for selected Mozilla Reps. Please apply! [LINK]<br />
Also, anyone who runs a MozFest session is also eligible for a travel stipends. Propose a session here. http://sessions.mozillafestival.org/ <br />
<br />
===What if I don't get sponsored in Festival?===<br />
Not getting sponsored doesn't mean that you cannot attend Mozilla Festival.<br />
Mozilla Festival is going to have a lot and interesting sessions about creativity, learning and the web spring to life where you can propose and run a session on your own. Simply follow the link: http://sessions.mozillafestival.org/ <br />
If you finally attend the Festival, your experience as a Rep is something we need and you are more than welcomed to join the awesome team of Mozfest Reps.<br />
<br />
===When and where?===<br />
<br />
MozFest 2013 will be held from October 25-27 in London, England. The festival will be hosted at Ravensbourne, a wired media and design campus located in East London next to the O2 concert arena (the same location as last year and we're delighted to be heading back). We realize this is in close proximity to the Summit and that will mean many Mozillians may not be able to attend MozFest.<br />
See transportation information and recommended hotels: http://mozillafestival.org/location</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Summit2013/Experiences/Site_Hosts&diff=700378Summit2013/Experiences/Site Hosts2013-08-28T02:30:52Z<p>Bacharakis: /* Roster of Site Hosts Santa Clara */</p>
<hr />
<div>=Summit Site Hosts=<br />
<br />
==Definition of Responsibilities==<br />
So what does it mean to be a Summit Site Host? Apart from the cool gear you'll be getting, your role will be to support and be the point of contact for a variety of tasks - the role will be similar at each venue but there may be slight differences from site to site:<br />
<br />
*Acting as an information resource for those attending the Summit<br />
*Helping to facilitate movement to the sessions<br />
*Aiding with registration and badge deployment<br />
*Manning the information desk during specified times<br />
*Helping with venue setup prior to the start of the event<br />
*Covering defined zones of the Summit in shifts during specified times<br />
*Possibly helping during social events<br />
*Possibly helping with swag questions<br />
*Greeting Mozillians at the Airport<br />
<br />
===Responsibilities during Supporting Sessions (Friday, Sunday)===<br />
<br />
*Sign-up to be the designated Site Host in the sessions you would like to attend (sign-up list to be provided by September 1st)<br />
*Arrive 15 minutes ahead of time in your rooms to ensure the facilitators have everything they need and the room is organized in the manner they've requested (if not, please reach out to a member of SHW event staff who can help support)<br />
*Introduce yourself to the session facilitators whose rooms you will be responsible for -> make sure they know you're here to help :)<br />
*Ensure that facilitators get their audience to sign their names on the session etherpad (if they are interested in learning more!)<br />
*Flag to the facilitators when they have 5 minutes left in their presentation time<br />
*Ask for help - SHW event staff will be easily identifiable and are there to support you<br />
<br />
==Time Commitment==<br />
The goal is to not interfere with your ability to participate in the Summit!<br />
<br />
* Site Host duties will be structured to allow participants to participate and fully experience the summit. <br />
* You are not necessarily signing up to work all 3 days. Some individuals may choose to help one day. But we do need Site Hosts in general throughout the event.<br />
* The work schedule will begin Thursday, October 3 right up until the Summit concludes on the evening of October 6th.<br />
<br />
===Pre-Summit Planning===<br />
*Site Host Leads will meet with each team and decide what roles everyone will play during the event<br />
<br />
===Pre-Summit Preparation - Thursday, October 3===<br />
* Meet at the Venue(s) on Thursday to pick-up your orange lanyard and familiarize yourself with the venue, location of meeting rooms, etc.<br />
<br />
===At the Summit - Live!===<br />
* Coming Soon!<br />
<br />
==Site Host Leads==<br />
We need two site host leads for each Summit location. What it means to be a Site Host Lead:<br />
<br />
*You will be responsible for helping to coordinate the efforts of the Site Hosts at each location.<br />
*You will work closely with the Event Company and their staff for supplies, and staff support at the venue<br />
*You will be the point of contact onsite for any escalations and will coordinate with points of contact for any issues<br />
*Manage the set Site Host schedule during the Summit and make changes as needed. <br />
<br />
==Roster of Site Hosts Toronto==<br />
Site Host Leads: Luciana Viana and TBD<br />
<br />
Team:<br />
*Lisa Gray<br />
*Arturo Martinez<br />
*Anthony Hughes<br />
*Matthew Claypotch<br />
*Lukas Blakk (Sunday only)<br />
*Lyre Calliope<br />
*Bob Silverberg<br />
*Kohei Yoshino (will be free everyday during the week of the Summit, also flexible in August and September for full-time or part-time help)<br />
*Santiago Hollmann<br />
*Gloria Meneses<br />
*Cori Schauer<br />
*Kevin Scannell<br />
*Bhavana Bajaj<br />
*Dumitru Gherman<br />
*Tracy Walker<br />
*Souyma Deb<br />
*Mike Hoye<br />
*Armen Zambrano<br />
*Liz Henry<br />
*Emma Irwin - Tracks<br />
*Majda Nafissa Rahal - Tracks<br />
*Clarissa Sorensen<br />
*Luis A. Sanchez a.k.a LASR21<br />
*John Jensen - Tracks<br />
*Winnie Aoieong<br />
*Alex Wafula<br />
*Vuyisile Ndlovu<br />
<br />
==Roster of Site Hosts Brussels==<br />
Site Host Leads: Ioana Chiorean and Marcia Knous<br />
<br />
Team:<br />
* Laura Forrest<br />
* Erica McClure<br />
* Delphine Lebedel<br />
* Henrik Mitsch<br />
* Dirjan Ochtman<br />
* Benoit Leseul<br />
* Reed Loden<br />
* Francesco Lodolo<br />
* Erin Lancaster<br />
* David Clarke<br />
* Jennifer Hayashi<br />
* William Reynolds<br />
* Brian King - Tracks<br />
* Patrick Finch - Tracks<br />
* Chad Weinder - Tracks<br />
* Christopher Arnold - Tracks<br />
* Irina Parievsky<br />
* Jessilyn Davis<br />
* Stephen Donner<br />
* Dietrich Ayala<br />
* Pascal Chevrel<br />
* Mohamed El-Sharnoby (Sharno)<br />
* Ibrahima Sarr<br />
* Dominik Strohmeier<br />
* Achraf Fouwad<br />
<br />
==Roster of Site Hosts Santa Clara==<br />
Site Host Leads: TBD and Co Host TBD<br />
<br />
Team:<br />
*Parul Mather<br />
*Geo Mealer<br />
*Iacopo Benesperi - tracks<br />
*Gary Kwong<br />
*Peiying Mo<br />
*Matt Wobensmith<br />
*John Hammink<br />
*Katherine Naszradi<br />
*Eusebio Barrun<br />
*Lindsay Kenzig<br />
*Benjamin Kerensa - tracks<br />
*Vineel Reddy Pindi<br />
*Galaxy Kadiyala<br />
*Rahid Hasan<br />
*Sujith Reddy<br />
*Alina Mierlus<br />
*Kengatharaiyer Sarveswaran (Sarves)<br />
*Sandraghassen Subbaraya Pillai<br />
*Saurabh Shah<br />
*Christos Bacharakis</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/Mozilla_Festival_2013&diff=692673Reps/Mozilla Festival 20132013-08-09T15:53:11Z<p>Bacharakis: </p>
<hr />
<div>===Announcement ===<br />
<br />
The Mozilla Festival (#MozFest) is an annual gathering of unconventional thinkers and inventors from around the world who meet to learn from each other and help forge the future of the web. It takes place from Oct. 25 - 27, 2013 in London, UK. <br />
<br />
Mozilla Reps are passionate people around the world who are spreading the word of Mozilla and generally the word the Open Web.<br />
As you already know Mozilla Reps is one of the driving forces of Mozilla. And Reps, especially those deeply invovled in Mozilla's Webmaker initiative, are going to be a driving force in this year's Mozilla Festival as well.<br />
<br />
Anyone is eligible to participate in the Mozilla Festival. You can register right now here: http://mzl.la/mozfest13-register<br />
However, we know that it's expensive to travel to London on your own. <br />
<br />
That's why the Reps program is offering travel stipends for Reps who have skills and experience beneficial to the Webmaker project.<br />
<br />
Have we described you in this announcement? If so:<br />
<br />
'''Apply for a travel as a sponsored Rep to the Mozilla Festival till August 18th: '''<br />
https://docs.google.com/forms/d/1l6OurLBzC_dp8qYRkKeVY3ugbO7teSa--Op8SEtjZ5s/viewform<br />
<br />
===What's the role and expectation of Reps at Mozfest?===<br />
* represent Mozilla<br />
* empower people in order to participate in Mozfest and generally in to teach the web<br />
* based on their expertise, to lead some sessions in Mozfest<br />
* empower more people in order to be contributors in Mozilla's projects <br />
* have an awesome experience which will provide them a lot of useful information for their community and their future events.<br />
<br />
===What's the timeframe?===<br />
Reps should plan on arriving in London by Thursday, October 24 and departing on Monday, October 28. <br />
<br />
===What is MozFest?===<br />
<br />
It's our annual 3-day festival where many of our best ideas about creativity, learning and the web spring to life. It celebrates our mission and brings new people into our community.<br />
<br />
http://mozillafestival.org/<br />
<br />
MozFest is open to everyone. ~300 Mozillians attend MozFest each year out of 1500 total participants.<br />
<br />
===How does MozFest tie into Mozilla's products and mission?===<br />
<br />
The MozFest program is designed around themes that intersect with the web but are not exclusively linked with our community or our products. This means MozFest is a great opportunity to open our mission to new groups, to offer support for their ideas and to learn from and be inspired by them. Plus, a lot of very cool independent coders, bloggers and journalists tend to be there.<br />
<br />
===What's the difference between MozFest and the Mozilla Summit?===<br />
<br />
The Mozilla Summit is an invite-only event focused creating alignment between the core members of the Mozilla community (including you!) Mozfest is a public event open to anyone interested in helping to make the web better and more creative -- it's about bringing new talent and ideas into Mozilla. This year, MozFest is designed to build on the work of the the Summit for those people who are attending both events: MozFest will allow us to test our thinking and recruit new contributors around ideas coming out of the Summit.<br />
<br />
===What's it like?===<br />
<br />
MozFest is unlike any other tech conference you've been to because it's all about hands-on participation and collaboration. There will be some fabulous keynote speakers, but the majority of the event takes place through interactive workshops. Think: less yack, more hack.<br />
<br />
===Who pays for travel?===<br />
The Reps program is offering travel stipends for selected Mozilla Reps. Please apply! [LINK]<br />
Also, anyone who runs a MozFest session is also eligible for a travel stipends. Propose a session here. http://sessions.mozillafestival.org/ <br />
<br />
===What if I don't get sponsored in Festival?===<br />
Not getting sponsored doesn't mean that you cannot attend Mozilla Festival.<br />
Mozilla Festival is going to have a lot and interesting sessions about creativity, learning and the web spring to life where you can propose and run a session on your own. Simply follow the link: http://sessions.mozillafestival.org/ <br />
If you finally attend the Festival, your experience as a Rep is something we need and you are more than welcomed to join the awesome team of Mozfest Reps.<br />
<br />
===When and where?===<br />
<br />
MozFest 2013 will be held from October 25-27 in London, England. The festival will be hosted at Ravensbourne, a wired media and design campus located in East London next to the O2 concert arena (the same location as last year and we're delighted to be heading back). We realize this is in close proximity to the Summit and that will mean many Mozillians may not be able to attend MozFest.<br />
See transportation information and recommended hotels: http://mozillafestival.org/location</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/Mozilla_Festival_2013&diff=692671Reps/Mozilla Festival 20132013-08-09T15:43:18Z<p>Bacharakis: </p>
<hr />
<div>===Announcement ===<br />
<br />
The Mozilla Festival (#MozFest) is an annual gathering of unconventional thinkers and inventors from around the world who meet to learn from each other and help forge the future of the web. It takes place from Oct. 25 - 27, 2013 in London, UK. <br />
<br />
Mozilla Reps are passionate people around the world who are spreading the word of Mozilla and generally the word the Open Web.<br />
As you already know Mozilla Reps is one of the driving forces of Mozilla. And Reps, especially those deeply invovled in Mozilla's Webmaker initiative, are going to be a driving force in this year's Mozilla Festival as well.<br />
<br />
Anyone is eligible to participate in the Mozilla Festival. You can register right now here: http://mzl.la/mozfest13-register<br />
However, we know that it's expensive to travel to London on your own. <br />
<br />
That's why the Reps program is offering travel stipends for Reps who have skills and experience beneficial to the Webmaker project.<br />
<br />
Have we described you in this announcement? If so:<br />
<br />
'''Apply for a travel as a sponsored Rep to the Mozilla Festival till August 18th: '''<br />
https://docs.google.com/forms/d/1l6OurLBzC_dp8qYRkKeVY3ugbO7teSa--Op8SEtjZ5s/viewform<br />
<br />
===What's the role and expectation of Reps at Mozfest?===<br />
* represent Mozilla<br />
* empower people in order to participate in Mozfest and generally in to teach the web<br />
* based on their expertise, to lead some sessions in Mozfest<br />
* empower more people in order to be contributors in Mozilla's projects <br />
* have an awesome experience which will provide them a lot of useful information for their community and their future events.<br />
<br />
===What's the timeframe?===<br />
Reps should plan on arriving in London by Thursday, October 24 and departing on Monday, October 28. <br />
<br />
===What is MozFest?===<br />
<br />
It's our annual 3-day festival where many of our best ideas about creativity, learning and the web spring to life. It celebrates our mission and brings new people into our community.<br />
<br />
http://mozillafestival.org/<br />
<br />
MozFest is open to everyone. ~300 Mozillians attend MozFest each year out of 1500 total participants.<br />
<br />
===How does MozFest tie into Mozilla's products and mission?===<br />
<br />
The MozFest program is designed around themes that intersect with the web but are not exclusively linked with our community or our products. This means MozFest is a great opportunity to open our mission to new groups, to offer support for their ideas and to learn from and be inspired by them. Plus, a lot of very cool independent coders, bloggers and journalists tend to be there.<br />
<br />
===What's the difference between MozFest and the Mozilla Summit?===<br />
<br />
The Mozilla Summit is an invite-only event focused creating alignment between the core members of the Mozilla community (including you!) Mozfest is a public event open to anyone interested in helping to make the web better and more creative -- it's about bringing new talent and ideas into Mozilla. This year, MozFest is designed to build on the work of the the Summit for those people who are attending both events: MozFest will allow us to test our thinking and recruit new contributors around ideas coming out of the Summit.<br />
<br />
===What's it like?===<br />
<br />
MozFest is unlike any other tech conference you've been to because it's all about hands-on participation and collaboration. There will be some fabulous keynote speakers, but the majority of the event takes place through interactive workshops. Think: less yack, more hack.<br />
<br />
===Who pays for travel?===<br />
The Reps program is offering travel stipends for selected Mozilla Reps. Please apply! [LINK]<br />
Also, anyone who runs a MozFest session is also eligible for a travel stipends. Propose a session here. http://sessions.mozillafestival.org/ <br />
What if I don't get sponsored in Festival?<br />
Not getting sponsored doesn't mean that you cannot attend Mozilla Festival.<br />
Mozilla Festival is going to have a lot and interesting sessions about creativity, learning and the web spring to life where you can propose and run a session on your own. Simply follow the link: http://sessions.mozillafestival.org/ <br />
If you finally attend the Festival, your experience as a Rep is something we need and you are more than welcomed to join the awesome team of Mozfest Reps.<br />
<br />
===When and where?===<br />
<br />
MozFest 2013 will be held from October 25-27 in London, England. The festival will be hosted at Ravensbourne, a wired media and design campus located in East London next to the O2 concert arena (the same location as last year and we're delighted to be heading back). We realize this is in close proximity to the Summit and that will mean many Mozillians may not be able to attend MozFest.<br />
See transportation information and recommended hotels: http://mozillafestival.org/location</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Reps/Mozilla_Festival_2013&diff=692670Reps/Mozilla Festival 20132013-08-09T15:41:11Z<p>Bacharakis: Created page with "===Announcement === The Mozilla Festival (#MozFest) is an annual gathering of unconventional thinkers and inventors from around the world who meet to learn from each other an..."</p>
<hr />
<div>===Announcement ===<br />
<br />
The Mozilla Festival (#MozFest) is an annual gathering of unconventional thinkers and inventors from around the world who meet to learn from each other and help forge the future of the web. It takes place from Oct. 25 - 27, 2013 in London, UK. <br />
<br />
Mozilla Reps are passionate people around the world who are spreading the word of Mozilla and generally the word the Open Web.<br />
As you already know Mozilla Reps is one of the driving forces of Mozilla. And Reps, especially those deeply invovled in Mozilla's <br />
<br />
Webmaker initiative, are going to be a driving force in this year's Mozilla Festival as well.<br />
<br />
Anyone is eligible to participate in the Mozilla Festival. You can register right now here: http://mzl.la/mozfest13-register<br />
However, we know that it's expensive to travel to London on your own. <br />
<br />
That's why the Reps program is offering travel stipends for Reps who have skills and experience beneficial to the Webmaker project.<br />
<br />
Have we described you in this announcement? If so:<br />
<br />
'''Apply for a travel as a sponsored Rep to the Mozilla Festival till August 18th: '''<br />
https://docs.google.com/forms/d/1l6OurLBzC_dp8qYRkKeVY3ugbO7teSa--Op8SEtjZ5s/viewform<br />
<br />
===What's the role and expectation of Reps at Mozfest?===<br />
* represent Mozilla<br />
* empower people in order to participate in Mozfest and generally in to teach the web<br />
* based on their expertise, to lead some sessions in Mozfest<br />
* empower more people in order to be contributors in Mozilla's projects <br />
* have an awesome experience which will provide them a lot of useful information for their community and their future events.<br />
<br />
===What's the timeframe?===<br />
Reps should plan on arriving in London by Thursday, October 24 and departing on Monday, October 28. <br />
<br />
===What is MozFest?===<br />
<br />
It's our annual 3-day festival where many of our best ideas about creativity, learning and the web spring to life. It celebrates our mission and brings new people into our community.<br />
<br />
http://mozillafestival.org/<br />
<br />
MozFest is open to everyone. ~300 Mozillians attend MozFest each year out of 1500 total participants.<br />
<br />
===How does MozFest tie into Mozilla's products and mission?===<br />
<br />
The MozFest program is designed around themes that intersect with the web but are not exclusively linked with our community or our products. This means MozFest is a great opportunity to open our mission to new groups, to offer support for their ideas and to learn from and be inspired by them. Plus, a lot of very cool independent coders, bloggers and journalists tend to be there.<br />
<br />
===What's the difference between MozFest and the Mozilla Summit?===<br />
<br />
The Mozilla Summit is an invite-only event focused creating alignment between the core members of the Mozilla community (including you!) Mozfest is a public event open to anyone interested in helping to make the web better and more creative -- it's about bringing new talent and ideas into Mozilla. This year, MozFest is designed to build on the work of the the Summit for those people who are attending both events: MozFest will allow us to test our thinking and recruit new contributors around ideas coming out of the Summit.<br />
<br />
===What's it like?===<br />
<br />
MozFest is unlike any other tech conference you've been to because it's all about hands-on participation and collaboration. There will be some fabulous keynote speakers, but the majority of the event takes place through interactive workshops. Think: less yack, more hack.<br />
<br />
===Who pays for travel?===<br />
The Reps program is offering travel stipends for selected Mozilla Reps. Please apply! [LINK]<br />
Also, anyone who runs a MozFest session is also eligible for a travel stipends. Propose a session here. http://sessions.mozillafestival.org/ <br />
What if I don't get sponsored in Festival?<br />
Not getting sponsored doesn't mean that you cannot attend Mozilla Festival.<br />
Mozilla Festival is going to have a lot and interesting sessions about creativity, learning and the web spring to life where you can propose and run a session on your own. Simply follow the link: http://sessions.mozillafestival.org/ <br />
If you finally attend the Festival, your experience as a Rep is something we need and you are more than welcomed to join the awesome team of Mozfest Reps.<br />
<br />
===When and where?===<br />
<br />
MozFest 2013 will be held from October 25-27 in London, England. The festival will be hosted at Ravensbourne, a wired media and design campus located in East London next to the O2 concert arena (the same location as last year and we're delighted to be heading back). We realize this is in close proximity to the Summit and that will mean many Mozillians may not be able to attend MozFest.<br />
See transportation information and recommended hotels: http://mozillafestival.org/location</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Firefox_OS/Community/Mystery_Checks_Spanish&diff=677424Firefox OS/Community/Mystery Checks Spanish2013-07-17T18:56:35Z<p>Bacharakis: Created page with "= Mystery Checks = == Mystery shopper == === Call and Role === Los teléfonos con Firefox OS ya están en las tiendas de tu región y estamos listos para escribir la histori..."</p>
<hr />
<div>= Mystery Checks =<br />
<br />
== Mystery shopper ==<br />
=== Call and Role ===<br />
<br />
Los teléfonos con Firefox OS ya están en las tiendas de tu región y estamos listos para escribir la historia una vez más.<br />
<br />
Una vez los teléfonos estén disponibles en las tiendas, nosotros como Mozilleros podemos proveer información valiosa sobre cómo se exibe, comercializa y promueve Firefox OS en las tiendas locales. Por este motivo se creó el programa "revisor misterioso", y nos encantaría invitarte a convertirte en un "comprador misterioso".<br />
<br />
Los compradores misteriosos son selectos mozilleros que trabajan encubiertos, escuchando el desempeño de Firefox OS en el campo de batalla. Sus tareas básicas son visitar las tiendas, haciéndose pasar por compradores que quieren información sobre terminales móviles y sus tarifas. Su rol consiste en obtener respuestas basadas en un cuestionario compilado como parte de escenarios predefinidos.<br />
<br />
=== Code of Operations ===<br />
<br />
* '''Stay under cover'''<br />
** It is real important NOT to be identified as a mystery shopper but as a normal customer. <br />
** While providing feedback - filling up the Questionnaire you have to be in a safe place, far from the mobile store. DO NOT start filling up the Questionnaire the moment you get out from the shop.<br />
* '''Stay informed'''<br />
** Read and understand all the questions<br />
** Before you enter a mobile store you have to think and build a strong story. <br />
* '''Stay calm'''<br />
** Be creative and try to create your own questions answering the questions on the Questionnaire.<br />
** DO NOT read the questions directly from the questionnaire.<br />
* '''Stay Mozillian'''<br />
** Provide feedback, based on your experience on the ground<br />
** Being part of the program you are an important part of our FirefoxOS launches!<br />
<br />
=== Tools ===<br />
You are going to be provided with the Questionnaire and a list with all the stores you are going to visit.<br />
The coordination of each local team will happen within a Teambox instance created specially for that (more info soon)<br />
=== Commitment ===<br />
The commitment needed will be aprox ~5 hours per week in order to visit the shops assigned to you. Its up to you to maximize or minimize the time needed but the optimal time per visit is ~10-15' talking with the sales person + 7' checking the store (marketing materials, labels, etc).<br />
<br />
=== Signup ===<br />
TBA<br />
<br />
== Tier one deployment ==<br />
* Schedule<br />
** http://publish.smartsheet.com/a49a54951fdb4fd0bc3587e248ab93c5<br />
* Signup <br />
** https://docs.google.com/a/mozilla.com/forms/d/1tv6uTCc9yNQVUKNquyNam5INzADDxtj61mz9wVjPX9E/viewform<br />
* Communications<br />
* Questionnaire<br />
** https://etherpad.mozilla.org/mysteryquestions<br />
* Tools<br />
** TBA</div>Bacharakishttps://wiki.mozilla.org/index.php?title=Firefox_OS/Community/Mystery_Checks&diff=677423Firefox OS/Community/Mystery Checks2013-07-17T18:55:13Z<p>Bacharakis: </p>
<hr />
<div>= Mystery Checks =<br />
<br />
== Mystery shopper ==<br />
=== Call and Role ===<br />
FirefoxOS phone are hitting the stores in your region and we are ready to write history for one more time!<br />
<br />
As phones will be available to stores, we as Mozillians can provide valuable feedback from our local stores on how FirefoxOS is displayed, marketed and promoted. That's why we created the "Mystery Checks" program, and we would like to invite you to become Mystery Shoppers!<br />
<br />
Mystery shoppers are selected Mozillians, that serve in silence, listening to the pulse of FirefoxOS on the ground. They are tasked with monthly basis visits to mobile stores posing as customers who want information on mobile phones and/or on mobile contracts. Their role is to get answers based on questionnaires compiled as part of pre-defined scenarios.<br />
<br />
=== Code of Operations ===<br />
<br />
* '''Stay under cover'''<br />
** It is real important NOT to be identified as a mystery shopper but as a normal customer. <br />
** While providing feedback - filling up the Questionnaire you have to be in a safe place, far from the mobile store. DO NOT start filling up the Questionnaire the moment you get out from the shop.<br />
* '''Stay informed'''<br />
** Read and understand all the questions<br />
** Before you enter a mobile store you have to think and build a strong story. <br />
* '''Stay calm'''<br />
** Be creative and try to create your own questions answering the questions on the Questionnaire.<br />
** DO NOT read the questions directly from the questionnaire.<br />
* '''Stay Mozillian'''<br />
** Provide feedback, based on your experience on the ground<br />
** Being part of the program you are an important part of our FirefoxOS launches!<br />
<br />
=== Tools ===<br />
You are going to be provided with the Questionnaire and a list with all the stores you are going to visit.<br />
The coordination of each local team will happen within a Teambox instance created specially for that (more info soon)<br />
=== Commitment ===<br />
The commitment needed will be aprox ~5 hours per week in order to visit the shops assigned to you. Its up to you to maximize or minimize the time needed but the optimal time per visit is ~10-15' talking with the sales person + 7' checking the store (marketing materials, labels, etc).<br />
<br />
=== Signup ===<br />
TBA<br />
<br />
== Tier one deployment ==<br />
* Schedule<br />
** http://publish.smartsheet.com/a49a54951fdb4fd0bc3587e248ab93c5<br />
* Signup <br />
** https://docs.google.com/a/mozilla.com/forms/d/1tv6uTCc9yNQVUKNquyNam5INzADDxtj61mz9wVjPX9E/viewform<br />
* Communications<br />
* Questionnaire<br />
** https://etherpad.mozilla.org/mysteryquestions<br />
* Tools<br />
** TBA</div>Bacharakishttps://wiki.mozilla.org/index.php?title=MozCampEU2012/TheRecord&diff=481195MozCampEU2012/TheRecord2012-10-19T00:42:23Z<p>Bacharakis: /* Photos */</p>
<hr />
<div>= The Record of MozCamp EU 2012 =<br />
<br />
If you have blog posts, pictures, videos, or comments on on MozCamp EU 2012 in Warsaw, please add them here.<br />
<br />
== Blog Posts ==<br />
<br />
Tag your videos with ''mozcamp'' and ''mozcampeu2012''.<br />
<br />
* Oskar Ivanić: [https://gingerzillian.wordpress.com/2012/09/13/mozillians-at-warsaw-mozcamp/ Mozillians at Warsaw (MozCamp)]<br />
* Ludovic Hirlimann [http://sietch-tabr.tumblr.com/post/31270244886/my-mozcamp-warsaw-2012-recap My m0zcamp warsaw 2012 recap]<br />
* Taras Glek: [https://blog.mozilla.org/tglek/2012/09/18/moacamp-eu-in-warsaw/ MozCamp.EU in Warsaw]<br />
* Lawrence Mandel: [http://lawrencemandel.com/2012/09/21/mozcamp-eu-2012-in-a-word-passion/ MozCamp EU 2012 in a word: Passion]<br />
* Ibrahima Sarr: [http://i-sarr.ibrahima-sarr.com/?p=75#more-75/ MOZCAMP Europe 2012: A weekend to remember!]<br />
* Anant Narayanan: [http://kix.in/2012/09/16/mozcamp-eu-2012-mobilize-mozilla/ MozCampEU 2012: Mobilize Mozilla]<br />
* Amy Tsay: [https://blog.mozilla.org/addons/2012/09/17/mozcamp-2012-wrap-up/ MozCamp 2012 Wrap-up]<br />
<br />
== Photos ==<br />
<br />
Tag your photos with ''mozcamp'' and ''mozcampeu2012''.<br />
<br />
* [http://www.flickr.com/photos/king-molan/sets/72157631500382506/ Brian King's Flickr Set]<br />
* [http://www.flickr.com/photos/lhirlimann/sets/72157631431599232/ Ludovic Hirlimann's Flickr Set]<br />
* [http://www.flickr.com/photos/flore_frmoz/sets/72157631500309862/ Flore Allemandou's Flickr Set]<br />
* [http://www.flickr.com/photos/83973540@N02/sets/72157631512237089/ Lawrence Mandel's Flickr Set]<br />
* [https://www.dropbox.com/sh/j0pn6oc8eauwk9i/nQv5p3o_xP Elad Alfassa's DropBox folder]<br />
* [http://www.flickr.com/photos/barzogh/ Achraf Fouwad's Flickr Set]<br />
* [http://www.flickr.com/photos/hubertgajewski/sets/72157631511867726/ Hubert Gajewski's Flickr Set]<br />
* [http://www.flickr.com/photos/catchingamy/sets/72157631623283494/ Amy Tsay's Flickr Set]<br />
* [http://www.flickr.com/photos/mozamoteam/sets/72157631475156000/ AMO Team's Flickr Set]<br />
* [https://picasaweb.google.com/105770476640273513358/MozCampEurope2012 Christos Bacharakis' Picasa Set]<br />
<br />
== Videos ==<br />
<br />
Tag your videos with ''mozcamp'' and ''mozcampeu2012''.<br />
<br />
* [http://vimeo.com/49453681 Firefox closing dance]<br />
* [https://www.youtube.com/watch?v=1nj0cTKAzaI The firefox costume]<br />
* [https://www.youtube.com/watch?v=z1pUiUrGaUI Firefox closing dance 2]<br />
* [https://www.youtube.com/watch?v=_HRiLIkzvFQ BananaBread demo]<br />
<br />
== Testimonials ==<br />
<br />
* "The Best Yet!" - Brian King<br />
* "it was my first Mozcabmp and it was AWESOME, met fantastic mozillians, my buddy Chris Heillman which is a genius, the sumo team gave me the motivation to settle soon a firefox-clinic ( i'll make a public annoucement about this very soon ).. i'm still nostalgic !* - Achraf Fouwad</div>Bacharakishttps://wiki.mozilla.org/index.php?title=MozCampEU2012/Buddyprogram/ChristosBacharakis&diff=467685MozCampEU2012/Buddyprogram/ChristosBacharakis2012-09-04T22:55:13Z<p>Bacharakis: </p>
<hr />
<div><h1>Name</h1><br />
Christos Bacharakis<br />
<h1>Link to My Mozillians/Reps/Twitter Accounts</h1><br />
[https://reps.mozilla.org/u/bacharakis/ Bacharakis in reps ]<br />
[http://twitter.com/bacharakis - and twitter too @bacharakis]<br />
<h2>What is the overall goal I want to accomplish by attending MozCamp Europe</h2><br />
I want to get in touch with all these interesting and intelligence Mozillians but specially get in touch with a Boot to Gecko developer and a HTML5 guru!<br />
<h2>What I want to achieve by Sunday (September 9th)</h2><br />
I am following this project from it's early step and I want to involve more in Gaia project first and next in Gecko. I want to meet a person who is going to solve all my questions and help me archive my goal. <br />
Secondly I am really interested in Web Applications and I would like to meet a person to share my personal toughs and ideas and provide me a feedback.<br />
<h3>What I will achieve by September 23rd</h3><br />
Join the Gaia developers community and maybe launch a Web Application I am working on by the help of the Community.<br />
<h3>What I will achieve by October 7th</h3><br />
Be a rock star!<br />
<br />
[[Category:MozCampEU2012Buddy|{{SUBPAGENAME}}]]</div>Bacharakishttps://wiki.mozilla.org/index.php?title=MozCampEU2012/Buddyprogram/ChristosBacharakis&diff=467682MozCampEU2012/Buddyprogram/ChristosBacharakis2012-09-04T22:52:14Z<p>Bacharakis: </p>
<hr />
<div><h1>Christos Bacharakis</h1><br />
<h1>My rep and twitter handle is @Bacharakis</h1><br />
<h2>What is the overall goal I want to accomplish by attending MozCamp Europe</h2><br />
I want to get in touch with all these interesting and intelligence Mozillians but specially get in touch with a Boot to Gecko developer and a HTML5 guru!<br />
<h2>What I want to achieve by Sunday (September 9th)</h2><br />
I am following this project from it's early step and I want to involve more in Gaia project first and next in Gecko. I want to meet a person who is going to solve all my questions and help me archive my goal. <br />
Secondly I am really interested in Web Applications and I would like to meet a person to share my personal toughs and ideas and provide me a feedback.<br />
<h3>What I will achieve by September 23rd</h3><br />
Join the Gaia developers community and maybe launch a Web Application I am working on by the help of the Community.<br />
<h3>What I will achieve by October 7th</h3><br />
Be a rock star!<br />
<br />
[[Category:MozCampEU2012Buddy|{{SUBPAGENAME}}]]</div>Bacharakishttps://wiki.mozilla.org/index.php?title=MozCampEU2012/Buddyprogram/ChristosBacharakis&diff=467680MozCampEU2012/Buddyprogram/ChristosBacharakis2012-09-04T22:50:43Z<p>Bacharakis: Created page with "<h1>Christos Bacharakis</h1> <h1>My rep and twitter handle is @Bacharakis</h1> <h2>I want to get in touch with all these interesting and intelligence Mozillians but specially get..."</p>
<hr />
<div><h1>Christos Bacharakis</h1><br />
<h1>My rep and twitter handle is @Bacharakis</h1><br />
<h2>I want to get in touch with all these interesting and intelligence Mozillians but specially get in touch with a Boot to Gecko developer and a HTML5 guru!<br />
</h2><br />
<h2>I am following this project from it's early step and I want to involve more in Gaia project first and next in Gecko. I want to meet a person who is going to solve all my questions and help me archive my goal. <br />
Secondly I am really interested in Web Applications and I would like to meet a person to share my personal toughs and ideas and provide me a feedback.</h2><br />
<h3>Join the Gaia developers community and maybe launch a Web Application I am working on by the help of the Community.</h3><br />
<h3>Be a rock star!</h3><br />
<br />
[[Category:MozCampEU2012Buddy|{{SUBPAGENAME}}]]</div>Bacharakishttps://wiki.mozilla.org/index.php?title=OpenSuseCollaborationCamp2012&diff=466528OpenSuseCollaborationCamp20122012-09-01T00:37:41Z<p>Bacharakis: http://bacharakis.com/?p=430</p>
<hr />
<div>{{Remoevents<br />
|eventname=OpenSuse Collaboration Camp 2012<br />
|eventdescription=OpenSuse Collaboration Camp 2012 is going to be a summer and fresh event with speakers around the globe and Greek re presenters from a large amount of FOSS projects.<br />
<br />
Review:<br />
http://bacharakis.com/?p=430<br />
<br />
|eventowner=Bacharakis<br />
|eventwebsite=http://www.os-el.gr/summercamp/en/<br />
|eventstartdate=32202/01/01 04:00:00 PM<br />
|eventenddate=32202/01/01 04:00:00 PM<br />
|city=Katerini<br />
|country=Greece<br />
|eventlocation=Grand Platon Hotel<br />
|eventregion=EMEA<br />
|eventattendance=50-100<br />
|eventswag=772018<br />
}}<br />
I am going to run a presentation regarding Mozilla Boot to Gecko where I am going to present a live demo of B2G running on Samsung Nexus S.<br />
Additionally I will run a second presentation/workshop where the attendance will have the chance to learn the advances of web applications and how to create one in easy steps.</div>Bacharakishttps://wiki.mozilla.org/index.php?title=OpenSuseCollaborationCamp2012&diff=448586OpenSuseCollaborationCamp20122012-07-09T12:05:25Z<p>Bacharakis: </p>
<hr />
<div>{{Remoevents<br />
|eventname=OpenSuse Collaboration Camp 2012<br />
|eventdescription=OpenSuse Collaboration Camp 2012 is going to be a summer and fresh event with speakers around the globe and Greek re presenters from a large amount of FOSS projects.<br />
|eventowner=Bacharakis<br />
|eventwebsite=http://www.os-el.gr/summercamp/en/<br />
|eventstartdate=2012/07/20 18:00:00 PM<br />
|eventenddate=2012/07/22 19:00:00 PM<br />
|city=Katerini<br />
|country=Greece<br />
|eventlocation=Grand Platon Hotel<br />
|eventregion=EMEA<br />
|eventattendance=50-100<br />
|eventswag=772018<br />
}}<br />
I am going to run a presentation regarding Mozilla Boot to Gecko where I am going to present a live demo of B2G running on Samsung Nexus S.<br />
Additionally I will run a second presentation/workshop where the attendance will have the chance to learn the advances of web applications and how to create one in easy steps.</div>Bacharakishttps://wiki.mozilla.org/index.php?title=OpenSuseCollaborationCamp2012&diff=448581OpenSuseCollaborationCamp20122012-07-09T11:35:07Z<p>Bacharakis: We are going to rock!</p>
<hr />
<div>{{Remoevents<br />
|eventname=OpenSuse Collaboration Camp 2012<br />
|eventdescription=OpenSuse Collaboration Camp 2012 is going to be a summer and fresh event with speakers around the globe and Greek re presenters from a large amount of FOSS projects. <br />
|eventowner=Bacharakis<br />
|eventwebsite=http://www.os-el.gr/summercamp/en/<br />
|city=Katerini<br />
|country=Greece<br />
|eventlocation=Grand Platon Hotel<br />
|eventregion=EMEA<br />
|eventattendance=50-100<br />
}}<br />
I am going to run a presentation regarding Mozilla Boot to Gecko where I am going to present a live demo of B2G running on Samsung Nexus S.<br />
Additionally I will run a second presentation/workshop where the attendance will have the chance to learn the advances of web applications and how to create one in easy steps.</div>Bacharakis