MozillaWiki - User contributions [en]

ScienceLab

2020-03-04T19:35:11Z

Abby: /* Publications & Communications */

__NOTOC__
<section begin=summary />{{RoadmapSummary
|icon=Mozilla_science_lab_logo-icon.jpg‎
|pagelocation=ScienceLab
|pagetitle=Mozilla Science Lab
|updated=Jan 19, 2016
|owner=Stephanie Wright
|description=The Mozilla Science Lab was an initiative of the Mozilla Foundation from 2013 - 2018. We explored how the power of open source could change the way science was done on the web. We operated under the belief that a community of peers that work, learn and build together could make research thrive on the open web. We did this through sprints, participatory learning, and prototyping with the research community to make science more like the web: open, collaborative and efficient. If you’re interested in Mozilla’s continuing efforts around open science, please visit the Mozilla Festival website at [https://www.mozillafestival.org/?utm_source=sunset mozillafestival.org].
}}<section end=summary />

=== PROGRAM RESOURCES ===
== Global Sprint ==
Mozilla’s Global Sprint was an annual fun, two-day collaborative global hackathon. A diverse network of educators, engineers, artists, scientists, and many others come together in person and online to build projects for a healthy Internet. [https://twitter.com/hashtag/mozsprint #MozSprint]

* [https://mozilla.github.io/global-sprint/participants-guide/ Participant Guide]
* [https://mozilla.github.io/global-sprint/project-lead-guide/ Project Lead Guide]
* [https://mozilla.github.io/global-sprint/site-hosts-guide/ Site Host Guide]

== Open Data Guides ==
The primers were designed to for you to read at your own pace and pick and choose the topics you want to read concerning open data. The Instructor guides are a resource for train-the-trainer type materials on Open Data. They are meant to provide a series of approachable, fun, collaborative workshops where each of the modules is interactive and customizable to meet a variety of audiences.

* [https://mozillascience.github.io/open-data-primers/ Primers]
* [https://mozillascience.github.io/open-data-guides/#teach Instructor Guides]

== Open Leadership ==
Resources on working openly and leading openly (#WOLO)

* [https://mozillascience.github.io/leadership-training/| Working Open Workshop]
* [https://mozilla.teachable.com/p/open-leadership-101| Open Leadership 101]
* [https://mzl.la/openleaders| Mozilla Open Leaders]
* [https://mzl.la/open-leadership| Open Leadership Training Series]

== Study Groups ==
[https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-mozilla-science-study-groups/ Study Groups were started in 2015] as a way for folks to hold informal spaces to hangout and learn from each other about coding in the lab.

* [https://github.com/mozillascience/studyGroup Template]
* [https://github.com/mozillascience/studyGroupLessons Lessons Bank]
* [https://mozillascience.github.io/studyGroupHandbook/lessons.html Handbook]

== Publications & Communications ==
* [https://github.com/mozillascience/Reports Annual Reports]
* [https://github.com/mozillascience/Reports/blob/master/MSLEvaluationFINAL_20181001.pdf Impact Evaluation (pdf)]
* [https://blog.mozilla.org/foundation-archive/category/mozilla-science/ Blog]
* [https://www.flickr.com/photos/139954518@N06/ Flickr]
* [https://twitter.com/MozillaScience Twitter]
* [https://github.com/mozillascience/ GitHub]

=== PROGRAM TIMELINE ===

'''14 June 2013''' - [https://kaythaney.com/2013/06/14/announcing-the-mozilla-science-lab/ The Mozilla Science Lab (MSL)] is open for business!

'''Aug 2013''' - MSL starts up the [https://kaythaney.com/2013/08/08/experiment-exploring-code-review-for-science/ Code Review pilot] with PLOS Computational Biology

'''Nov 2013''' - The Lab begins [https://blog.mozilla.org/foundation-archive/mozilla-science/join-our-next-community-call-december-12-11-et/ Community Calls] and participates in its first [https://www.mozillafestival.org/ Mozilla Festival]

'''Dec 2013''' - MSL [https://blog.mozilla.org/foundation-archive/mozilla-science/code-as-a-research-object-a-new-project/MSL partners with GitHub and figshare] to launch "[http://mozillascience.github.io/code-research-object/ Code as a Research Object]".

'''May 2014''' - The [https://blog.mozilla.org/foundation-archive/mozilla-science/our-first-data-carpentry-workshop/ first Data Carpentry workshop] takes place.

'''July 2014''' - The Science Lab runs its [https://blog.mozilla.org/foundation-archive/mozilla-science/the-mozsprint-heard-round-the-world/ first annual Global Sprint].

'''Oct 2014''' - Software Carpentry leaves the Mozilla Science Lab to become the [https://software-carpentry.org/blog/2014/10/announcing-the-creation-of-the-software-carpentry-foundational.html Software Carpentry Foundation].

'''Nov 2014''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/contributorship-badges-a-new-project/ Contributorship Badges project takes off].

'''Mar 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/collaborate-open-for-submissions/ MSL releases Collaborate], a community portal for open science projects.

'''Apr 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-mozilla-science-study-groups/ Mozilla Science Study Groups are introduced].

'''Jun 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/apply-today-to-become-a-mozilla-fellow-for-science/ Applications open] for the first cohort of Mozilla Fellows for Open Science.

'''Sep 2015''' - The Lab holds the [https://blog.mozilla.org/foundation-archive/mozilla-science/teaching-leadership-like-mozilla/ Open Science Leadership Summit] at the Mozilla Toronto office.

'''Nov 2015''' - MSL adds to its regular monthly community calls with [https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-the-monthly-mozilla-science-project-call/ Project Calls]

'''Feb 2016''' - The [http://mozillascience.github.io/working-open-workshop/ first Working Open Workshop] is held in Berlin and the start of our first [https://mozilla.github.io/leadership-training/ Open Leadership Training Cohort].

'''Oct 2016''' - The [https://blog.mozilla.org/foundation-archive/category/mozilla-science/page/7/ Mozilla Science Lab Book Club] is formed.

'''Mar 2017''' - MSL opens enrollment to [https://mozilla.teachable.com/p/open-leadership-101 Open Leadership 101].

'''May 2017''' - The Lab opens the call for proposals for the [https://blog.mozilla.org/foundation-archive/mozilla-science/mini-grant-cfp/ Mozilla Science Mini Grants program].

'''Jul 2018''' - The Science Lab publishes the [https://mozillascience.github.io/open-data-guides/ Open Data Instructor Guides and Open Data Primers].

'''Sep 2018''' - The [https://blog.mozilla.org/foundation-archive/mozilla-science/news-from-mozilla-science-lab/ Mozilla Science Lab program is sunsetted] and its programs are folded into other [https://foundation.mozilla.org/en/ Foundation programs] and partner organizations.

=== SUPPORT ===

The Mozilla Science Lab was supported over the years by the [http://www.sloan.org Alfred P. Sloan Foundation], the [http://www.helmsleytrust.org Helmsley Charitable Trust], and the [https://www.siegelendowment.org/ Siegel Family Endowment].

=== LICENSE ===
https://i.creativecommons.org/l/by/4.0/88x31.png

This work by the Mozilla Science Lab is licensed under a [http://creativecommons.org/licenses/by/4.0/ Creative Commons Attribution 4.0 International License].

ScienceLab

2020-03-04T16:08:52Z

Abby: /* Open Leadership */

__NOTOC__
<section begin=summary />{{RoadmapSummary
|icon=Mozilla_science_lab_logo-icon.jpg‎
|pagelocation=ScienceLab
|pagetitle=Mozilla Science Lab
|updated=Jan 19, 2016
|owner=Stephanie Wright
|description=The Mozilla Science Lab was an initiative of the Mozilla Foundation from 2013 - 2018. We explored how the power of open source could change the way science was done on the web. We operated under the belief that a community of peers that work, learn and build together could make research thrive on the open web. We did this through sprints, participatory learning, and prototyping with the research community to make science more like the web: open, collaborative and efficient. If you’re interested in Mozilla’s continuing efforts around open science, please visit the Mozilla Festival website at [https://www.mozillafestival.org/?utm_source=sunset mozillafestival.org].
}}<section end=summary />

=== Timeline ===

'''14 June 2013''' - [https://kaythaney.com/2013/06/14/announcing-the-mozilla-science-lab/ The Mozilla Science Lab (MSL)] is open for business!

'''Aug 2013''' - MSL starts up the [https://kaythaney.com/2013/08/08/experiment-exploring-code-review-for-science/ Code Review pilot] with PLOS Computational Biology

'''Nov 2013''' - The Lab begins [https://blog.mozilla.org/foundation-archive/mozilla-science/join-our-next-community-call-december-12-11-et/ Community Calls] and participates in its first [https://www.mozillafestival.org/ Mozilla Festival]

'''Dec 2013''' - MSL [https://blog.mozilla.org/foundation-archive/mozilla-science/code-as-a-research-object-a-new-project/MSL partners with GitHub and figshare] to launch "[http://mozillascience.github.io/code-research-object/ Code as a Research Object]".

'''May 2014''' - The [https://blog.mozilla.org/foundation-archive/mozilla-science/our-first-data-carpentry-workshop/ first Data Carpentry workshop] takes place.

'''July 2014''' - The Science Lab runs its [https://blog.mozilla.org/foundation-archive/mozilla-science/the-mozsprint-heard-round-the-world/ first Global Sprint].

'''Oct 2014''' - Software Carpentry leaves the Mozilla Science Lab to become the [https://software-carpentry.org/blog/2014/10/announcing-the-creation-of-the-software-carpentry-foundational.html Software Carpentry Foundation].

'''Nov 2014''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/contributorship-badges-a-new-project/ Contributorship Badges project takes off].

'''Mar 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/collaborate-open-for-submissions/ MSL releases Collaborate], a community portal for open science projects.

'''Apr 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-mozilla-science-study-groups/ Mozilla Science Study Groups are introduced].

'''Jun 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/apply-today-to-become-a-mozilla-fellow-for-science/ Applications open] for the first cohort of Mozilla Fellows for Open Science.

'''Sep 2015''' - The Lab holds the [https://blog.mozilla.org/foundation-archive/mozilla-science/teaching-leadership-like-mozilla/ Open Science Leadership Summit] at the Mozilla Toronto office.

'''Nov 2015''' - MSL adds to its regular monthly community calls with [https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-the-monthly-mozilla-science-project-call/ Project Calls]

'''Feb 2016''' - The [http://mozillascience.github.io/working-open-workshop/ first Working Open Workshop] is held in Berlin and the start of our first [https://mozilla.github.io/leadership-training/ Open Leadership Training Cohort].

'''Oct 2016''' - The [https://blog.mozilla.org/foundation-archive/category/mozilla-science/page/7/ Mozilla Science Lab Book Club] is formed.

'''Mar 2017''' - MSL opens enrollment to [https://mozilla.teachable.com/p/open-leadership-101 Open Leadership 101].

'''May 2017''' - The Lab opens the call for proposals for the [https://blog.mozilla.org/foundation-archive/mozilla-science/mini-grant-cfp/ Mozilla Science Mini Grants program].

'''Jul 2018''' - The Science Lab publishes the [https://mozillascience.github.io/open-data-guides/ Open Data Instructor Guides and Open Data Primers].

'''Sep 2018''' - The [https://blog.mozilla.org/foundation-archive/mozilla-science/news-from-mozilla-science-lab/ Mozilla Science Lab program is sunsetted] and its programs are folded into other [https://foundation.mozilla.org/en/ Foundation programs] and partner organizations.

=== Study Groups ===
[https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-mozilla-science-study-groups/ Study Groups were started in 2015] as a way for folks to hold informal spaces to hangout and learn from each other about coding in the lab.

* [https://github.com/mozillascience/studyGroup Template]
* [https://github.com/mozillascience/studyGroupLessons Lessons Bank]
* [https://mozillascience.github.io/studyGroupHandbook/lessons.html Handbook]

=== Open Leadership ===
Resources on working openly and leading openly (#WOLO)

* [https://mozillascience.github.io/leadership-training/| Working Open Workshop]
* [https://mozilla.teachable.com/p/open-leadership-101| Open Leadership 101]
* [https://mzl.la/openleaders| Mozilla Open Leaders]
* [https://mzl.la/open-leadership| Open Leadership Training Series]

=== Open Data Guides ===
The primers were designed to for you to read at your own pace and pick and choose the topics you want to read concerning open data. The Instructor guides are a resource for train-the-trainer type materials on Open Data. They are meant to provide a series of approachable, fun, collaborative workshops where each of the modules is interactive and customizable to meet a variety of audiences.

* [https://mozillascience.github.io/open-data-primers/ Primers]
* [https://mozillascience.github.io/open-data-guides/#teach Instructor Guides]

=== Publications ===
Annual Reports
Assessment
Other Pubs

== Support ==

The Mozilla Science Lab was supported over the years by the [http://www.sloan.org Alfred P. Sloan Foundation], the [http://www.helmsleytrust.org Helmsley Charitable Trust], and the [https://www.siegelendowment.org/ Siegel Family Endowment].

==License==
https://i.creativecommons.org/l/by/4.0/88x31.png

This work by the Mozilla Science Lab is licensed under a [http://creativecommons.org/licenses/by/4.0/ Creative Commons Attribution 4.0 International License].

ScienceLab

2020-03-04T16:08:10Z

Abby: /* Open Leadership */

__NOTOC__
<section begin=summary />{{RoadmapSummary
|icon=Mozilla_science_lab_logo-icon.jpg‎
|pagelocation=ScienceLab
|pagetitle=Mozilla Science Lab
|updated=Jan 19, 2016
|owner=Stephanie Wright
|description=The Mozilla Science Lab was an initiative of the Mozilla Foundation from 2013 - 2018. We explored how the power of open source could change the way science was done on the web. We operated under the belief that a community of peers that work, learn and build together could make research thrive on the open web. We did this through sprints, participatory learning, and prototyping with the research community to make science more like the web: open, collaborative and efficient. If you’re interested in Mozilla’s continuing efforts around open science, please visit the Mozilla Festival website at [https://www.mozillafestival.org/?utm_source=sunset mozillafestival.org].
}}<section end=summary />

=== Timeline ===

'''14 June 2013''' - [https://kaythaney.com/2013/06/14/announcing-the-mozilla-science-lab/ The Mozilla Science Lab (MSL)] is open for business!

'''Aug 2013''' - MSL starts up the [https://kaythaney.com/2013/08/08/experiment-exploring-code-review-for-science/ Code Review pilot] with PLOS Computational Biology

'''Nov 2013''' - The Lab begins [https://blog.mozilla.org/foundation-archive/mozilla-science/join-our-next-community-call-december-12-11-et/ Community Calls] and participates in its first [https://www.mozillafestival.org/ Mozilla Festival]

'''Dec 2013''' - MSL [https://blog.mozilla.org/foundation-archive/mozilla-science/code-as-a-research-object-a-new-project/MSL partners with GitHub and figshare] to launch "[http://mozillascience.github.io/code-research-object/ Code as a Research Object]".

'''May 2014''' - The [https://blog.mozilla.org/foundation-archive/mozilla-science/our-first-data-carpentry-workshop/ first Data Carpentry workshop] takes place.

'''July 2014''' - The Science Lab runs its [https://blog.mozilla.org/foundation-archive/mozilla-science/the-mozsprint-heard-round-the-world/ first Global Sprint].

'''Oct 2014''' - Software Carpentry leaves the Mozilla Science Lab to become the [https://software-carpentry.org/blog/2014/10/announcing-the-creation-of-the-software-carpentry-foundational.html Software Carpentry Foundation].

'''Nov 2014''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/contributorship-badges-a-new-project/ Contributorship Badges project takes off].

'''Mar 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/collaborate-open-for-submissions/ MSL releases Collaborate], a community portal for open science projects.

'''Apr 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-mozilla-science-study-groups/ Mozilla Science Study Groups are introduced].

'''Jun 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/apply-today-to-become-a-mozilla-fellow-for-science/ Applications open] for the first cohort of Mozilla Fellows for Open Science.

'''Sep 2015''' - The Lab holds the [https://blog.mozilla.org/foundation-archive/mozilla-science/teaching-leadership-like-mozilla/ Open Science Leadership Summit] at the Mozilla Toronto office.

'''Nov 2015''' - MSL adds to its regular monthly community calls with [https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-the-monthly-mozilla-science-project-call/ Project Calls]

'''Feb 2016''' - The [http://mozillascience.github.io/working-open-workshop/ first Working Open Workshop] is held in Berlin and the start of our first [https://mozilla.github.io/leadership-training/ Open Leadership Training Cohort].

'''Oct 2016''' - The [https://blog.mozilla.org/foundation-archive/category/mozilla-science/page/7/ Mozilla Science Lab Book Club] is formed.

'''Mar 2017''' - MSL opens enrollment to [https://mozilla.teachable.com/p/open-leadership-101 Open Leadership 101].

'''May 2017''' - The Lab opens the call for proposals for the [https://blog.mozilla.org/foundation-archive/mozilla-science/mini-grant-cfp/ Mozilla Science Mini Grants program].

'''Jul 2018''' - The Science Lab publishes the [https://mozillascience.github.io/open-data-guides/ Open Data Instructor Guides and Open Data Primers].

'''Sep 2018''' - The [https://blog.mozilla.org/foundation-archive/mozilla-science/news-from-mozilla-science-lab/ Mozilla Science Lab program is sunsetted] and its programs are folded into other [https://foundation.mozilla.org/en/ Foundation programs] and partner organizations.

=== Study Groups ===
[https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-mozilla-science-study-groups/ Study Groups were started in 2015] as a way for folks to hold informal spaces to hangout and learn from each other about coding in the lab.

* [https://github.com/mozillascience/studyGroup Template]
* [https://github.com/mozillascience/studyGroupLessons Lessons Bank]
* [https://mozillascience.github.io/studyGroupHandbook/lessons.html Handbook]

=== Open Leadership ===
Resources on working openly and leading openly (#WOLO)

* [[https://mozillascience.github.io/leadership-training/|Working Open Workshop]]
* [[https://mozilla.teachable.com/p/open-leadership-101|Open Leadership 101]]
* [[https://mzl.la/openleaders|Mozilla Open Leaders]]
* [[https://mzl.la/open-leadership|Open Leadership Training Series]]

=== Open Data Guides ===
The primers were designed to for you to read at your own pace and pick and choose the topics you want to read concerning open data. The Instructor guides are a resource for train-the-trainer type materials on Open Data. They are meant to provide a series of approachable, fun, collaborative workshops where each of the modules is interactive and customizable to meet a variety of audiences.

* [https://mozillascience.github.io/open-data-primers/ Primers]
* [https://mozillascience.github.io/open-data-guides/#teach Instructor Guides]

=== Publications ===
Annual Reports
Assessment
Other Pubs

== Support ==

The Mozilla Science Lab was supported over the years by the [http://www.sloan.org Alfred P. Sloan Foundation], the [http://www.helmsleytrust.org Helmsley Charitable Trust], and the [https://www.siegelendowment.org/ Siegel Family Endowment].

==License==
https://i.creativecommons.org/l/by/4.0/88x31.png

This work by the Mozilla Science Lab is licensed under a [http://creativecommons.org/licenses/by/4.0/ Creative Commons Attribution 4.0 International License].

ScienceLab

2020-03-04T16:07:34Z

Abby: /* Open Leadership */

__NOTOC__
<section begin=summary />{{RoadmapSummary
|icon=Mozilla_science_lab_logo-icon.jpg‎
|pagelocation=ScienceLab
|pagetitle=Mozilla Science Lab
|updated=Jan 19, 2016
|owner=Stephanie Wright
|description=The Mozilla Science Lab was an initiative of the Mozilla Foundation from 2013 - 2018. We explored how the power of open source could change the way science was done on the web. We operated under the belief that a community of peers that work, learn and build together could make research thrive on the open web. We did this through sprints, participatory learning, and prototyping with the research community to make science more like the web: open, collaborative and efficient. If you’re interested in Mozilla’s continuing efforts around open science, please visit the Mozilla Festival website at [https://www.mozillafestival.org/?utm_source=sunset mozillafestival.org].
}}<section end=summary />

=== Timeline ===

'''14 June 2013''' - [https://kaythaney.com/2013/06/14/announcing-the-mozilla-science-lab/ The Mozilla Science Lab (MSL)] is open for business!

'''Aug 2013''' - MSL starts up the [https://kaythaney.com/2013/08/08/experiment-exploring-code-review-for-science/ Code Review pilot] with PLOS Computational Biology

'''Nov 2013''' - The Lab begins [https://blog.mozilla.org/foundation-archive/mozilla-science/join-our-next-community-call-december-12-11-et/ Community Calls] and participates in its first [https://www.mozillafestival.org/ Mozilla Festival]

'''Dec 2013''' - MSL [https://blog.mozilla.org/foundation-archive/mozilla-science/code-as-a-research-object-a-new-project/MSL partners with GitHub and figshare] to launch "[http://mozillascience.github.io/code-research-object/ Code as a Research Object]".

'''May 2014''' - The [https://blog.mozilla.org/foundation-archive/mozilla-science/our-first-data-carpentry-workshop/ first Data Carpentry workshop] takes place.

'''July 2014''' - The Science Lab runs its [https://blog.mozilla.org/foundation-archive/mozilla-science/the-mozsprint-heard-round-the-world/ first Global Sprint].

'''Oct 2014''' - Software Carpentry leaves the Mozilla Science Lab to become the [https://software-carpentry.org/blog/2014/10/announcing-the-creation-of-the-software-carpentry-foundational.html Software Carpentry Foundation].

'''Nov 2014''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/contributorship-badges-a-new-project/ Contributorship Badges project takes off].

'''Mar 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/collaborate-open-for-submissions/ MSL releases Collaborate], a community portal for open science projects.

'''Apr 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-mozilla-science-study-groups/ Mozilla Science Study Groups are introduced].

'''Jun 2015''' - [https://blog.mozilla.org/foundation-archive/mozilla-science/apply-today-to-become-a-mozilla-fellow-for-science/ Applications open] for the first cohort of Mozilla Fellows for Open Science.

'''Sep 2015''' - The Lab holds the [https://blog.mozilla.org/foundation-archive/mozilla-science/teaching-leadership-like-mozilla/ Open Science Leadership Summit] at the Mozilla Toronto office.

'''Nov 2015''' - MSL adds to its regular monthly community calls with [https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-the-monthly-mozilla-science-project-call/ Project Calls]

'''Feb 2016''' - The [http://mozillascience.github.io/working-open-workshop/ first Working Open Workshop] is held in Berlin and the start of our first [https://mozilla.github.io/leadership-training/ Open Leadership Training Cohort].

'''Oct 2016''' - The [https://blog.mozilla.org/foundation-archive/category/mozilla-science/page/7/ Mozilla Science Lab Book Club] is formed.

'''Mar 2017''' - MSL opens enrollment to [https://mozilla.teachable.com/p/open-leadership-101 Open Leadership 101].

'''May 2017''' - The Lab opens the call for proposals for the [https://blog.mozilla.org/foundation-archive/mozilla-science/mini-grant-cfp/ Mozilla Science Mini Grants program].

'''Jul 2018''' - The Science Lab publishes the [https://mozillascience.github.io/open-data-guides/ Open Data Instructor Guides and Open Data Primers].

'''Sep 2018''' - The [https://blog.mozilla.org/foundation-archive/mozilla-science/news-from-mozilla-science-lab/ Mozilla Science Lab program is sunsetted] and its programs are folded into other [https://foundation.mozilla.org/en/ Foundation programs] and partner organizations.

=== Study Groups ===
[https://blog.mozilla.org/foundation-archive/mozilla-science/introducing-mozilla-science-study-groups/ Study Groups were started in 2015] as a way for folks to hold informal spaces to hangout and learn from each other about coding in the lab.

* [https://github.com/mozillascience/studyGroup Template]
* [https://github.com/mozillascience/studyGroupLessons Lessons Bank]
* [https://mozillascience.github.io/studyGroupHandbook/lessons.html Handbook]

=== Open Leadership ===
Resources on working openly and leading openly (#WOLO)

* [[mozillascience.github.io/leadership-training/|Working Open Workshop]]
* [[https://mozilla.teachable.com/p/open-leadership-101|Open Leadership 101]]
* [[https://mzl.la/openleaders|Mozilla Open Leaders]]
* [[https://mzl.la/open-leadership|Open Leadership Training Series]]

=== Open Data Guides ===
The primers were designed to for you to read at your own pace and pick and choose the topics you want to read concerning open data. The Instructor guides are a resource for train-the-trainer type materials on Open Data. They are meant to provide a series of approachable, fun, collaborative workshops where each of the modules is interactive and customizable to meet a variety of audiences.

* [https://mozillascience.github.io/open-data-primers/ Primers]
* [https://mozillascience.github.io/open-data-guides/#teach Instructor Guides]

=== Publications ===
Annual Reports
Assessment
Other Pubs

== Support ==

The Mozilla Science Lab was supported over the years by the [http://www.sloan.org Alfred P. Sloan Foundation], the [http://www.helmsleytrust.org Helmsley Charitable Trust], and the [https://www.siegelendowment.org/ Siegel Family Endowment].

==License==
https://i.creativecommons.org/l/by/4.0/88x31.png

This work by the Mozilla Science Lab is licensed under a [http://creativecommons.org/licenses/by/4.0/ Creative Commons Attribution 4.0 International License].

Foundation/AI/FLEX/Projects/OKRGenerator

2019-08-20T15:49:03Z

Abby: /* Learnings, Outcomes, Next Steps */

= MoFo OKR Generator =
MoFo FLEX 2019 - Project Proposal

== Overview ==
'''Project Lead:''' Abby 
'''Area of Focus:''' Misinformation, Openness 
'''Knowledge Level Required:''' Beginner, Intermediate, Expert 

Interested? Want to chat / keep up to date? Join our Slack channel [https://mozilla.slack.com/messages/CJ1FRPEQP/ #mofoflex-okrgenerator]

== Project Information ==
==== Project Description: ====
Need to come up with an OKR? Use the MoFo OKR generator!

We'll use mofo's past and current okrs as the training data. We may have to supplement with text from reports / meetings / etc.

==== Expected Outcomes: ====
Learning how to implement a text generator

==== Help Required: ====
Anyone: Gathering OKRs & other text

Design: UI/UX of the site

Engineering: front & back-end

==== Required Time Commitments ====
The project will take place over 3 months. The Project Lead will spend 3 hours working on the project and contributors would need to allow for 3 hours per week to fully get involved.

== Project Updates ==
Slack channel created [https://mozilla.slack.com/messages/CJ1FRPEQP/ #mofoflex-okrgenerator]

Meeting notes: https://docs.google.com/document/d/1wU11oQmGnHpa2ZBfjqBcqIUuEFTuSQzE0V4Og5BbUrA/edit#

Kick-off call is Thursday May 2, 1:30pm ET

Join our meetings: https://calendar.google.com/event?action=TEMPLATE&tmeid=MXRwaTVzMGk1dDg1NDA4ZmE1OGJ1aGpxaDZfMjAxOTA1MTZUMTczMDAwWiBhYmlnYWlsQG1vemlsbGFmb3VuZGF0aW9uLm9yZw&tmsrc=abigail%40mozillafoundation.org&scp=ALL

== Learnings, Outcomes, Next Steps ==

[[File:Okr generator zine cover.png|thumb|Cover image of the OKR Generator zine. Made by Sam Burton]]

Here's what we made!

If you're looking for an overview, here's a zine documenting our journey on the OKR Generator project! [[File:OKRGenerator Zine.pdf|thumb|okr generator, the zine]] In the zine, you can see our process and read our learnings after the project.

We wrote lots of code. Here are the GitHub repositories for the [https://github.com/acabunoc/okrgenerator text generator] and the [https://github.com/cadecairos/okr-classifier classifier]

We generated some text after training the neural network on the Internet Health Report:
<pre>the internet in the world in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the int</pre>

File:OKRGenerator Zine.pdf

2019-08-20T15:48:07Z

Abby:

OKR Generator, the Zine

Foundation/AI/FLEX/Projects/OKRGenerator

2019-08-09T19:50:18Z

Abby: update for outcomes / learnings. Remove call for participants.

= MoFo OKR Generator =
MoFo FLEX 2019 - Project Proposal

== Overview ==
'''Project Lead:''' Abby 
'''Area of Focus:''' Misinformation, Openness 
'''Knowledge Level Required:''' Beginner, Intermediate, Expert 

Interested? Want to chat / keep up to date? Join our Slack channel [https://mozilla.slack.com/messages/CJ1FRPEQP/ #mofoflex-okrgenerator]

== Project Information ==
==== Project Description: ====
Need to come up with an OKR? Use the MoFo OKR generator!

We'll use mofo's past and current okrs as the training data. We may have to supplement with text from reports / meetings / etc.

==== Expected Outcomes: ====
Learning how to implement a text generator

==== Help Required: ====
Anyone: Gathering OKRs & other text

Design: UI/UX of the site

Engineering: front & back-end

==== Required Time Commitments ====
The project will take place over 3 months. The Project Lead will spend 3 hours working on the project and contributors would need to allow for 3 hours per week to fully get involved.

== Project Updates ==
Slack channel created [https://mozilla.slack.com/messages/CJ1FRPEQP/ #mofoflex-okrgenerator]

Meeting notes: https://docs.google.com/document/d/1wU11oQmGnHpa2ZBfjqBcqIUuEFTuSQzE0V4Og5BbUrA/edit#

Kick-off call is Thursday May 2, 1:30pm ET

Join our meetings: https://calendar.google.com/event?action=TEMPLATE&tmeid=MXRwaTVzMGk1dDg1NDA4ZmE1OGJ1aGpxaDZfMjAxOTA1MTZUMTczMDAwWiBhYmlnYWlsQG1vemlsbGFmb3VuZGF0aW9uLm9yZw&tmsrc=abigail%40mozillafoundation.org&scp=ALL

== Learnings, Outcomes, Next Steps ==

[[File:Okr generator zine cover.png|thumb|Cover image of the OKR Generator zine. Made by Sam Burton]]

Here's what we made!

If you're looking for an overview, here's a zine documenting our journey on the OKR Generator project!
[https://docs.google.com/document/d/17A6g3KSpCwVbP0sx7oLMmcYH8U6fSQzWoMkB7ttXDeE/edit OKR Generator, The Zine] In the zine, you can see our process and read our learnings after the project.

We wrote lots of code. Here are the GitHub repositories for the [https://github.com/acabunoc/okrgenerator text generator] and the [https://github.com/cadecairos/okr-classifier classifier]

We generated some text after training the neural network on the Internet Health Report:
<pre>the internet in the world in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the internet in the internet in the world are also sechnology in the united states and security of the internet hn the internet in the internet in the int</pre>

File:Okr generator zine cover.png

2019-08-09T19:46:51Z

Abby:

Robot with the label, OKR Generator. This is the cover of the OKR Generator zine. Image made by Sam Burton.

Foundation/Weekly Priorities/2019-07-08

2019-07-08T19:03:53Z

Abby: /* Key Dates (Upcoming) */

== Mozilla Foundation Weekly Priorities: July 8th, 2019 ==

=== Key Dates (Upcoming) ===
* July 8 - Science Mini Grant Public Announcement (Kevin, Lindsey)
* July 9-10 - Board retreat (Berlin)
* July 11-12 - Executive team meeting (Berlin)
* July 12 - Deadline for MoFo Engagement Survey
* July 16 - Responsible Computer Science Challenge Awardees - In-Person Orientation/Kick Off Meeting @ SF office
* July 24 - MoFo Monthly Call
* August 1 - MozFest Call for Proposals closes
* August 1 - OLX Applications close
* September TBD - Strategy Retreat

=== What's Moving This Week (and who to contact with questions) ===
* Finalizing team OKRs (all)
* AI Convening over the next two days in Berlin with external partners and board members (Mark)
* Prep for MoFo monthly call, OKR 3 call, and MozFest press event (Communications team)
* MozFest book (Kristina, Kevin, and Sarah)
* MozFest tech spec (Marc)
* OLX curriculum scoping (Abby and Chad)
* Finalizing the OLX application and review process in Fluxx (Kalpana)
* PNI reminder email, donate stack progress, site CMS & content tweaks (Engagement)
* Preparing for the next mini-campaign and finishing up grant proposals (Partnerships)
* Finalizing single audit samples, updating grants and fellow expenses with May actuals (Ruzanna)

===Notes from the last Executive Team weekly meeting ===
* Board prep - Discussed board materials and building a narrative around impactful work in H2 to drive towards helping us achieve our org-wide OKRs.
* Monthly OKR calls - Decided to move to every other month calls for our org-wide OKRs in H2, and discussed potential case studies to feature on July calls. We’ll still provide top-level updates on the monthly MoFo call and complete monthly reporting in the OKR dashboard.

===Job Openings===
* Currently in case study stage for the following roles:
** VP, Leadership
** Director, Leadership Programs
** Director of Operations

////[[Foundation/Weekly_Priorities/#Mozilla_Foundation_Weekly_Priorities|MoFo Weekly Priorities Archives]]

[[Category: Weekly Priorities]]

Foundation/AI/FLEX/Projects/OKRGenerator

2019-05-03T14:14:43Z

Abby: /* Project Updates */

Foundation/AI/FLEX/Projects/OKRGenerator

2019-05-02T17:28:19Z

Abby: add update

Foundation/AI/FLEX/Projects/OKRGenerator

2019-04-22T14:58:01Z

Abby: add slack update

Foundation/AI/FLEX/Projects/OKRGenerator

2019-04-17T19:10:48Z

Abby: /* Help Required: */ break out help

Foundation/AI/FLEX/Projects/OKRGenerator

2019-04-16T18:16:28Z

Abby: added slack

Foundation/Strategy Retreat

2019-04-03T17:19:32Z

Abby: typo in my name

== Mozilla Foundation Strategy Retreat FAQ ==

==== What are MoFo Strategy Retreats? ====

MoFo Strategy Retreats are 2-day sprints that aim to help us create forward momentum towards our strategy and address a high-impact challenge.
In addition, they serve to:
* Keep us focused on how we can advance our external impact
* Create organizational elegance by aligning outcomes of Strategy Retreats with ongoing planning, All-Hands, Board conversations and other programs where helpful.
* Build more participation and familiarity with the strategic planning process across the organization.

==== Why did we decide on this approach? ====

The MoFo executive team (Mark Surman, Angela Plohman, Ashley Boyd) has been exploring ways to help advance the strategy through cross-functional, collaborative thinking around impact. The retreats started in 2017 to provide an opportunity for people at different levels to engage in strategy, and to practice together how we solve specific challenges.

==== How do Strategy Retreats fit into our regular planning cycle? ====

We host Strategy Retreats twice per year. The first retreat will take place in the spring, early enough in the year for us to examine where we may need extra focus and attention. The second retreat will happen in the fall, where we’ll focus on the next year’s planning cycle.

Strategy Retreats take place as part of a larger sequence of strategic planning processes at MoFo. The outcomes of the retreat link to and flow into preparation for board meetings, All Hands, team-level planning, etc.

==== How are the themes and attendees decided? ====

The MoFo executive team will define the theme and outcomes, and select participants for each retreat. Themes will be selected that can be advanced in a few days between the executives, MoFo staff and external parties.

Attendees for each retreat will vary depending on the theme, to bring a diversity of insight and expertise from across the organization. They will include MoFo staff to represent a cross-section of the organization, varying tenures at MoFo, office and remote workers, and various professional backgrounds and areas of expertise. External participants may also be invited.

==== Who is designing/facilitating the Strategy Retreats? ====

Stephanie Ryan from The Coaching Studio will design and facilitate the retreats. She has been working with the executive team for several years and has attended several All-Hands. The Coaching Studio will continue working to support the Executive Team and the organization as a whole through strategic planning.

==== What is the expectation of participants after the retreat? ====

Participants in the strategy retreats are not cohorts. They are invited based on their expertise and opinions as it relates to the theme of the retreat. They may continue to consult or work on the outputs of the retreat after the fact, however that is usually determined on a case-by-case basis.

There are some expectations for work that participants will engage in both before and after the retreat.
* Before
** Complete any pre-reading/viewing/assignments in advance of the retreat
* After
** Share back the experience and takeaways with their teams, and also perhaps during a staff call
** Participate in a 1:1 feedback discussion about the retreat

== Strategy Retreat Details ==

==== April 2019 ====

'''Theme:''' The theme for the April 2019 Strategy Retreat is working like a movement. We’ll explore how we can build strength through massive collaboration and engagement with the movement for internet health. We’ll focus on how–across existing MoFo programs–we can get to the next level of growth and impact through our collaboration with, and promotion, of our movement partners. We’ll draw on ideas and inspiration about how to introduce and scale this approach within our work from each other and external sources.

'''Outputs:''' The aim of the retreat is to develop or refine strategic movement building plans for three initiatives already underway at Mozilla. These include:

* EU misinformation and related campaigns working with partners following the election (Theme/Revenue/Reach OKR)
* Collaboration with and among fellows on defining an AI agenda for the internet health movement (Theme/Reach OKR)
* Responsible CS Challenge - weaving winners, finalists and judges into the movement, accelerating ethics in CS/AI (Theme OKR)
* We’ll also brainstorm additional places where we can build on this thinking with cross-org support

By the end of the retreat, teams working on the initiatives above will have a clear plan about how to use our programmatic tools/platforms/resources to expand collaboration and participation across the movement. All participants will have new skills that will allow them to ‘work like a movement’ as individuals, as teams and with our community. These skills will allow them to develop further collaborations beyond those designed at the retreat.

'''April 2019 Participants'''
The executive team, in consultation with some directors, invites staff and partners that bring diverse thinking and expertise in relation to the theme. For the April retreat, this group represents staff across teams, roles, geographies, tenures and professional backgrounds--key stakeholders in the initiatives listed above, as well as core supports for public messaging/promotion/partnerships based on these efforts.

{| class="wikitable"
|-
| Abby Cabunoc Mayes || Practice Lead, Working Open
|-
| Angela Plohman || EVP, Strategic Operations
|-
| Anil Kanji || Director, Digital Engagement
|-
| Ashley Boyd || VP, Advocacy & Engagement
|-
| Brandi Guerkink || EU Campaigner
|-
| Chad Sansing || Open Culture Lead
|-
| Gabi Ivens || Fellow
|-
| Janice Wait || Portfolio Manager
|-
| Jenn Beard || Program Officer
|-
| Jesse Ward || Major Gifts Officer
|-
| Juan Barajas || Director, Partnerships
|-
| Kevin Zawacki || Editorial Lead
|-
| Lainie DeCoursy || Senior Program Manager, Strategic Operations
|-
| Lindsey Dodson || Senior Program Officer
|-
| Lotta Rao || Director, Communications
|-
| Mark Surman || Executive Director
|-
| Melissa Huerta || Senior Program Officer
|-
| Michelle Thorne || Program Lead, Open Internet of Things
|-
| Miriam Avery || Director, Strategy Foresight, MoCo
|-
| Rizwan Tufail || Director, Fellowships & Awards
|-
| Sarah Allen || Director, Events and Training
|-
| Theo Chevalier ||Localization Project Manager
|-
|}

[https://ainowinstitute.org/people/rashida-richardson.html Rashida Richardson] from AI Now and [https://www.astraeafoundation.org/team/j-bob-alotta/ J. Bob Alotta] from Astraea Foundation will be joining as guests for portions of the retreat.

==== September 2018 ====

'''Theme:''' The September Strategy Retreat is a key component of our strategic planning process, where we’ll be focused on on answering the following question: “What concrete improvements to the health of the internet do we want to make over the next 3-5 years?” Together, we’ll explore how we might use our core programs - shaping the agenda, connecting leaders and rallying citizens - to set our sights on a specific, compelling impact goal that builds on the ‘your data and you’ theme used in 2018. As a step in the development of this statement, together, we will be exploring, clarifying, and narrowing our list of potential impact statements to undergo further analysis. The outcome of this retreat will link directly to and flow into the preparation for the November board meeting.

Specific goals:
* Hone draft impact goals that describe concrete 'wins' on internet health over the coming years
* Review these goals against a set of criteria related to Mozilla's mission, community and likelihood of success -- narrow the number of goals under consideration
* Create a list of questions that need to be answered and evidence that needs to be gathered to further test the goals against the criteria
* Develop a plan to engage staff, fellows and key allies from across the movement in further fleshing out and testing the thinking on the narrower list of goals
* Overall, deepen engagement in strategic planning and improve our ability to do analysis and make decisions as a group

By the end of the retreat, participants will have a clearer understanding of each of the impact statements, as well as be able to connect their team’s work to those statements. Tangibly, we’ll expect to have honed and refined versions of our draft impact statements, alignment on the criteria by which they’ll be reviewed, details to help us build out out deeper analyses (questions to answer, evidence to gather) and next steps on broader engagement.

'''September 2018 Participant [https://docs.google.com/document/d/13BJEzshvZNe5K96AtxYOR1WW61l2DO8EsRi8yVLN1GU/edit#heading=h.6ts3q2mfymou bios]'''
{| class="wikitable"
|-
| Angela Plohman || Mark Surman
|-
| Ashley Boyd || Mehan Jayasuriya
|-
| Chris Riley (MoCo) || Michael Auckland
|-
| Jesse Von Doom || Paul Zenke
|-
| Josh Wolf || Rizwan Tufail
|-
| Jon Lloyd || Sam Burton
|-
| Juan Barajas || Sara Haghoodsti
|-
| Kristina Shu || Sarah Allen
|-
| Lainie DeCoursy || Sunil Abraham
|-
| Lotta Rao ||
|}

==== May 2018 ====

'''Theme:''' During this Strategy Retreat, we will explore how MoFo can thrive in the long-term and build on our success to date for greater impact in the world. Starting with a review of our current programs, we will work to explore how we can build excellence as we maximize impact, expand global reach and foster long-term sustainability. We will use the interim MoFo program evaluation report as our core document and will draw insight, ideas and inspiration from each other and external sources.

This retreat was rooted in finding inspiration from others doing social change and movement building work. Participants all played key roles in taking the discussions and learnings from the retreat back to their teams, and also facilitated activities and break-out groups on the same themes at Toronto All Hands.

'''May 2018 Participant [https://docs.google.com/document/d/19AwXDztwgMCzlAPO52wm3YKfePxkyKYi76teBZCW3S0/edit bios]'''

{| class="wikitable"
|-
| Amira Dhalla || Lainie DeCoursy
|-
| Angela Plohman || Mark Surman
|-
| Ashley Boyd || Melissa Romaine
|-
| Jairus Khan || Sara Haghdoosti
|-
| Josh Wolf || Sarah Watson
|-
| Juan Barajas ||
|}

External participants:
* Chris Stone, Fmr Pres, Open Society Foundations
* Marc Solomon, Freedom to Marry
* Rashad Robinson, Color of Change

==== August 2017 ====

'''Theme:''' During this Strategy Retreat, we’ll look towards where we want the Internet health movement to be five years from now, and we’ll examine in detail why this work is important now, what to focus resources on in the final year of our 3-year strategy, and how we can increase our external impact, with an eye towards our future ambitions for the movement.

We’re not changing the strategy or programs for 2018. We are, however, taking a stance on focus and simplicity for the initiatives within in each program area.
* Shape the agenda = Internet Health Report and related research/initiatives
* Connect leaders = $ to support leaders and their work in the movement
* Rally citizens = campaigns to educate and motivate people to take action; asking companies and governments to pay attention to internet health

We’ll also explore initiatives that support the above programs - including MozFest and a digital engagement strategy. Also key will be connecting these initiatives to each other and to the overall movement.

This retreat helped kick-off our planning for 2018. We were able to step back and dig in on deeper levels around WHY our work matters and is urgent, while also generating concrete ideas for how we might take this work forward in the next 18 months. Outcomes included draft objectives for 2018 and plenty of content that now lives in our [https://drive.google.com/file/d/1Bl-h9d1IrhBXOskacm8eYkPteNMdxlN2/view strategy brief].

'''August 2017 participants''' [https://docs.google.com/document/d/13OOAqKlogCNvDqlX5soG5PNhYJpRkTQAObK0rBEpQng/edit# bios]

{| class="wikitable"
|-
| Amy Schapiro || Juan Barajas || Paul Johnson
|-
| Angela Plohman || Kasia Odrozek || Rizwan Tufail
|-
| Ashley Boyd || Lainie DeCoursy || Sam Burton
|-
| Chris Lawrence || Lindsey Frost || Sarah Allen
|-
| Cori Zarek || Lotta Rao || VojtechSedlak
|-
| Hana Sun || Mark Surman || Will Easton
|-
| Jesse Von Doom || Michael Auckland ||
|}

External participants:
* Betsy Hoover, Partner and Co-Founder of Higher Ground Labs & 270 Strategies
* Kirstie Whittaker, Mozilla Fellow for Science Alumna
* Tom Liacas, Senior Strategist, NetChange Consulting

==== April 2017 ====

'''Theme:''' Increase impact and momentum around implementation of how MoFo drives public demand for better privacy and security. We want to create a space in which our combined issue, messaging, campaign and network expertise will strengthen our existing plans for raising public understanding of–and action in support of–better Internet privacy and security.

Core questions include:
* What are core privacy and security issues emerging globally in which MoFo can make a unique and important impact in 2017?
* How do we use the Mozilla Network for these themes and campaigns?
* What other existing resources can we leverage to develop the most impactful results in these areas and how?
* What new resources / approaches / actions do we need to cultivate in order to create the most impact in this area in 2017 and how?

The outputs from this retreat heavily influenced planning around our mass market education “Privacy by Default” campaign, as well as furthered thinking around our grantmaking strategy related to privacy and security themes/projects/etc.

'''April 2017 Participants'''
{| class="wikitable"
|-
| Angela Plohman || Jen Caltrider
|-
| Ashley Boyd || Lainie DeCoursy
|-
| Brett Gaylor || Lotta Rao
|-
| Chris Lawrence || Mark Surman
|-
| Chrystian Rodriguez || Meghan McDermott
|}

External participants:
* Camille Fischer - Former Obama Administration Policy Advisor, White House National Economic Council
* Josh Levy - Campaign strategist and digital rights advocate
* Sarah Aoun - Digital Security Trainer with Research Action Design (RAD)

Community:SummerOfCode17

2017-03-28T18:09:01Z

Abby: Update thimble projects for Gideon

This is Mozilla's list of green-lit project proposals for the 2017 Google Summer of Code.

Are you a student looking to apply to GSoC with Mozilla? You're in the right place. This page lists all the confirmed [[SummerOfCode|Google Summer of Code]] projects. New suggestions can be made on [[Community:SummerOfCode17:Brainstorming|the Brainstorming page]]. Do not edit this page yourself; contact Mike Hoye or Florian for edits.

If you're interested in participating in Mozilla's GSoC program, you can choose from the list below, '''but you do not have to'''. You can submit a proposal for your own idea. You should look at the [[Community:SummerOfCode17:Brainstorming|guidelines]], though, and discuss your ideas or application in the #introduction channel on IRC.Mozilla.org. This is important, as GSoC projects '''must have''' a supporting member of the Mozilla community to evaluate and mentor them, named in the application.

===Application Advice===

You should do the following:

* Talk to the mentor. Contact details are on this page; if all you have is a nickname, reach out to them on IRC.
* Read the [https://flossmanuals.net/GSoCStudentGuide/ GSoC Student Guide] and follow its advice.
* Read [http://blog.gerv.net/2006/05/how_not_to_apply_for_summer_of/ How Not To Apply For Summer Of Code] and avoid doing the things listed there.
* Read our examples of good applications: [[SummerOfCode/SampleApplications/1|1]], [[SummerOfCode/SampleApplications/2|2]], [[SummerOfCode/SampleApplications/3|3]].
* Apply on [https://summerofcode.withgoogle.com/ the GSoC site] (note that we have an [[SummerOfCode/ApplicationTemplate|application template]]).
* It is entirely acceptable to apply for 2 or 3 projects, if more than one catches your eye; if the applications are high quality, that can improve your chances. Applying to more than that will seem like spam.

Questions about individual projects are best addressed to the potential mentor of that project. These should be listed in the table below. If you want to contact a mentor and contact details are not here, ask people in the #introduction channel on IRC: irc://irc.mozilla.org/#introduction. If you have questions of any other sort, send mail to [mailto:mhoye@mozilla.com Mike Hoye]. He will try and respond promptly and direct your questions to the right person.

===Project List===

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| TaskCluster JSON Parameterization
| Build a powerful JSON parameterization system and use it everywhere
| JavaScript, Python
| [https://mozillians.org/en-US/u/dustin/ :dustin]
| [https://mozillians.org/en-US/u/dustin/ :dustin]
| The json-e language supports complex transformations of JSON data. The project involves completing the specification, implementation (in two languages), and documentation of this language, then using it to support Gecko action and decision task and users of taskcluster-github and taskcluster-hooks. Success here means that the language is complete and in active use in at least one of the listed contexts.
|-
| Livelog Proxy
| Write a server that privileged-clients can open a HTTPS connection to in-order to expose a webhook that http-clients can call.
When normal http-clients access the exposed webhooks the connection will be reverse proxied to the
privileged-clients over their out-going connection.
| golang, github, http, web sockets, node.js
| :jonasfj
| :jonasfj
| This is like to ngrok and localtunnel.me, read up on those. For performance reasons server should be written in golang, with client libraries in golang and node.js.
|
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| about:telemetry redesign
| about:telemetry is present on all builds of Firefox as a way for users to view the data being stored and sent via Telemetry. It was built before Firefox had multi-process Telemetry and without a clear design. This has resulted in a confusing HTML UI and barely-comprehensible JS.
| webtech (HTML+CSS+JS) and Design
| :chutten
| chutten@mozilla.com
| [[Telemetry/GSoC17:AboutTelemetry|Some information]]
|-
| Boost Session Restore performance
| Session (Re)store is important as a key feature of Firefox. Many people rely on it to re-open a tab from the past or recover from an unfortunate power outage. But making it blazing fast has not been our primary focus, until now. Your goal will be to help us make restoring any session snappy and blazing fast. Expect to learn a lot about the Firefox internals and interact with many core engineers during the SoC course.
| JavaScript
| :mikedeboer
| :mikedeboer, :dao
|
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Developer Tools for Designers
| In Firefox Developer Tools, we're aiming to implement visual tools that will help developers and designers edit CSS properties visually. Since CSS is very declarative by nature, we can provide tools that are commonly found in designer tools in order to bridge the learning gap of new developers and designers learning CSS and allow them to edit complex CSS features such as CSS filters, blend, clip-path, layout, etc without knowing what the properties are. Going beyond editing CSS, we also need to think about how we can visually inspect the CSS style transformations that can impact the layout. Finally, we are looking for ways to better export and see the changes made in the Inspector tool so that we can take the work we have done in the Developer Tools and apply that to your local source files.
| JavaScript, HTML, CSS, React, Redux
| [[User:Gl|:gl]]
| [[User:Gl|:gl]]
| Starting meta bug for inspiration [https://bugzilla.mozilla.org/show_bug.cgi?id=1258390 Bug 1258390]
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| [[Community:SummerOfCode17/AndroidWebExtensions|Implement WebExtension APIs]]
| [https://developer.mozilla.org/en-US/Add-ons/WebExtensions WebExtensions] are a cross-browser system for developing browser add-ons. [http://arewewebextensionsyet.com/ Not all APIs are supported] by Firefox for Android yet.
The goal of this project is to:
* Implement some of the missing APIs ([https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/contextMenus contextMenus], [https://developer.chrome.com/extensions/browsingData browsingData], [identity?], [proxy?])
* Add automated test for those APIs
* Improve the tooling for building WebExtensions for Firefox for Android.
[[Community:SummerOfCode17/AndroidWebExtensions|Lear more about this project]]
| Java, JavaScript, Android
| [https://mozillians.org/en-US/u/sebastian.kaspari/ :sebastian]
| [https://mozillians.org/en-US/u/sebastian.kaspari/ :sebastian]
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
! JS static analysis
! Bring some static analysis in our Firefox Javascript code
! Javascript experience, FLOW(?)
! [mailto:s@mozilla.com Sylvestre]
! [mailto:s@mozilla.com Sylvestre]
! This project aims to evaluate and integrate more static analysis for Javascript code into some key sections of the Firefox code. We will focus on deploying [https://github.com/facebook/flow FLOW] on some part of the code as a proof of concept. Depending on the results, this will be extended to more components and/or integration in the developer workflow.
|-
! C++ static analysis
! Add new checkers specific to our base code
! Strong C++ experience, clang
! [mailto:s@mozilla.com Sylvestre]
! [mailto:andi@mozilla.com Andi]
! In order to tackle issues during the development phase, Mozilla wrote a [https://hg.mozilla.org/mozilla-central/file/tip/build/clang-plugin bunch of static analyzers checkers] based on [http://clang.llvm.org/extra/clang-tidy/ clang-tidy]. In this project, we will focus on writing more checkers (either generic to C/C++ or specific to Gecko programming patterns).
|-
! JSON in Sqlite
! Query JSON Documents stored in Sqlite
! Database, SQL, Python
! [mailto:klahnakoski@mozilla.com Kyle Lahnakoski]
! [mailto:klahnakoski@mozilla.com Kyle Lahnakoski]
! [https://github.com/klahnakoski/JSONQueryExpressionTests/blob/master/docs/GSOC%20Proposal.md Details]
|-
! Regression localization from stack traces
! Tool to blame a patch for causing a newly introduced crash.
! C++, Python
! [mailto:marco@mozilla.com Marco]
! [mailto:calixte@mozilla.com Calixte]
! The project would involve creating a tool that analyzes a set of stack traces, performing the intersection with the Firefox call graph (which can be generated using Clang) and a set of recently committed patches.
|-
! Improvements for crash clustering
! Build a tool to improve crash clustering, currently based on the top method of the stack trace.
! Python, C++
! [mailto:marco@mozilla.com Marco]
! [mailto:marco@mozilla.com Marco]
! The project would involve finalizing https://github.com/marco-c/crashsimilarity; testing it more thoroughly; putting it in production.
|-
! Improve Reliability of Automated tests
! Add a --test-lint mode to all harnesses which will ensure the test is more stable and check for common mistakes.
! Python, Javascript
! [mailto:jmaher@mozilla.com Joel (:jmaher)]
! [mailto:jmaher@mozilla.com Joel (:jmaher)] [mailto:gbrown@mozilla.com Geoff (:gbrown)]
! Mozilla's developers write dozens of new tests every week. We would like to provide a way to ensure these new tests are stable and reliable. This will be done by implementing a test-lint mode in all of our test harnesses which will run the tests by themselves as well as repeat them 10 times each. more details here: https://public.etherpad-mozilla.org/p/9u9OijDCKn
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| MDN Documentation Tester WebExtension
| Rewrite the [https://github.com/Elchi3/mdn-doc-tests MDN doc tester add-on] as a (well-tested, modern, documented) WebExtension that runs in Firefox, Chrome, Opera, and possibly Edge. Ideally reach feature parity with the existing Add-on SDK add-on and if time allows work on new test ideas that run against the MDN documentation.
| Add-On/WebExtension experience (JavaScript, HTML, CSS)
| Florian Scholz (fscholz@mozilla.com)
| Florian Scholz (fscholz@mozilla.com)
|}

== PDF.js ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Streams API in PDF.js
| Streams API with PDF.js, makes it more faster and memory efficient. Passing data incrementally from worker to main thread increases the speed of processing. Using Streams API instead of xhr in networking reduces the memory usage. Since Streams API is a new technology, using it in PDF.js test Firefox's implementation.
| ECMAScript 2015, Web APIs
| [mailto:ydelendik@mozilla.com Yury Delendik (:yury)]
| [mailto:ydelendik@mozilla.com Yury Delendik (:yury)]
| Proposal: https://docs.google.com/document/d/1yTPvPBhGkFn7XUntAt8wdVPckxHovYylNAIJOGnGRXc/edit?usp=sharing
Firefox implementation: https://bugzilla.mozilla.org/show_bug.cgi?id=1128959
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Improve Balrog's Admin API
| Make Balrog's Admin API simpler and easier for clients to work with by moving to a [http://swagger.io/ Swagger]-based approach.
| python,rest apis
| Ben Hearsum (bhearsum@mozilla.com)
| Ben Hearsum (bhearsum@mozilla.com)
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
! Rust Language Server (RLS)
! The RLS is a service for providing information about Rust programs from the Rust compiler to IDEs and other tools. It will be at the core of the IDE experience for Rust programmers. By the summer, we should have just had the first release of the RLS, and there is lots still to do. Exactly what would depend on what YOU want from the project. Some ideas for projects directly on the RLS are [https://github.com/rust-lang-nursery/rls/issues/142 here]. You could also work on either rustw - a web frontend for the RLS - or our Visual Studio Code plugin; in either case, providing new functionality directly to users.
! Rust, and ideally either: web development, or Javascript (e.g., Electron, node.js), or IDE internals.
! [https://github.com/brson/ brson]
! [https://github.com/nrc/ nrc]
! [https://github.com/rust-lang-nursery/rls RLS repo] [http://www.jonathanturner.org/2017/01/rls-alpha-release.html RLS description]
|-
! Rust + WebAssembly showcase
! (this project has many applicants and is not considering new candidates. please look elsewhere) Rust and WebAssembly are going to be a great pair. Design and implement a simple and attractive web application, in Rust, that demonstrates the power of Rust on the web. Make fixes to upstream projects as necessary. Write a blog post about it.
! Rust, web development
! [https://github.com/brson/ brson]
! [https://github.com/brson/ brson], [https://github.com/badboy badboy]
! cc https://users.rust-lang.org/t/compiling-to-the-web-with-rust-and-emscripten/7627. Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-1-md
|-
! Rust dashboard updates
! (this project has many applicants and is not considering new candidates. please look elsewhere) Update rusty-dash.com to include additional metrics important to the project. This tool is vital to the day-to-day management of Rust, but it needs some dedicated attention to fulfill its promise.
! Rust
! [https://github.com/brson/ brson]
! [https://github.com/brson/ brson]
! Follow on work to https://internals.rust-lang.org/t/the-rust-project-needs-much-better-visibility-into-important-metrics/3367
|-
! Rust reproducible builds
! (this project has many applicants and is not considering new candidates. please look elsewhere) Make the Rust build process produce the identical binaries when run with identical configurations. This improves the security of the Rust ecosystem by allowing others to
double-check the official Rust builds
! Rust, compilers, systems programming
! [https://github.com/brson/ brson]
! [https://github.com/brson/ brson], [https://github.com/michaelwoerister mw]
! https://internals.rust-lang.org/t/verifying-rustc-releases-with-reproducible-builds/4502. Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-2-md
|-
! Abstract the Rust standard library
! (this project has many applicants and is not considering new candidates. please look elsewhere) The Rust standard library is very portable, but can be very, very portable. Refactor the
standard library to pull out a platform abstraction layer.
! Moderate Rust experience
! [https://github.com/brson/ brson]
! [https://github.com/brson/ brson]
! https://internals.rust-lang.org/t/refactoring-std-for-ultimate-portability/4301
|-
! Rust cross-platform showcase project
! (this project has many applicants and is not considering new candidates. please look elsewhere) Rust is very portable. Create a single showcase demo project that compiles for Windows, OS X, Linux, Android, iOS, wasm, and microcontrollers. Use real crates to accomplish some real task. Set up CI for all platforms on Travis. To be used as a teaching tool and for regression testing. Write a blog post.
! Moderate Rust experience
! [https://github.com/brson/ brson]
! [https://github.com/brson/ brson]
!
|-
! rustc micro-optimization bonanza
! (this project has many applicants and is not considering new candidates. please look elsewhere) Just go hog wild finding microoptimizations in rustc. Write a blog post bragging about it.
! Performance optimization
! [https://github.com/brson/ brson]
! [https://github.com/brson/ brson]
!
|-
! Rust-specific benchmark suite
! (this project has many applicants and is not considering new candidates. please look elsewhere) Today Rust uses perf.rust-lang.org to track _compile time_ performance, but nothing to track _runtime_ performance. Work with the Rust developers to create a benchmark suite specific to Rust.
! Programming
! [https://github.com/brson/ brson]
! [https://github.com/brson/ brson]
!
|-
! Rust crate semver compatibility tool
! (this project has many applicants and is not considering new candidates. please look elsewhere) Rust libraries follow the semver spec for indicating API compatibility, but conformance to semver is not enforced in any way - it is up to crate authors to guarantee their crates can be upgraded correctly. With Rust's strong type system it should be possible to mechanically check whether crates
are obeying semver. This would be a huge boon to the stability of the Rust ecosystem.
! Static analysis
! [https://github.com/brson/ brson]
! [https://github.com/brson/ brson], [https://github.com/badboy/ badboy]
! https://users.rust-lang.org/t/warnings-for-breaking-semver/1415 https://users.rust-lang.org/t/signature-based-api-comparison/2377 . Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-3-md
|-
! Reconstruct the Rust bootstrap chain
! (this project has many applicants and is not considering new candidates. please look elsewhere) Rust is a self-hosted compiler, originally bootstrapped from OCaml, then self-bootstrapped several hundred times over the years. Today there is only one Rust 'lineage' of any note, the official compiler, but with compilers diversity of implementation is a security issue. If another party could replicate the
Rust compiler it would provide assurance that the official isn't compromised by, or can recover from, a "trusting trust" attack. Although the historical information needed to rebootstrap Rust is mostly complete, it is not trivial to do. Construct a script that can reconstruct the modern Rust compiler from the original OCaml implementation, run it to completion, write a blog post.
! Scripting, build systems
! [https://github.com/brson/ brson]
! [https://github.com/alexcrichton/ acrichto]
!
|-
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Off-main thread HTML parsing
| [https://github.com/servo/servo/wiki/Off-main-thread-HTML-parsing-project Project page]
| Enthusiasm to learn Rust, comfortable reading/writing JavaScript
| [https://mozillians.org/en-US/u/jdm/ jdm]
| [mailto:aramine@mozilla.com Anthony Ramine (nox)]
|
|-
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| StopTrackware.org
| Create a clearinghouse of trackware lists like StopBadware.org, by creating a Track-the-trackers add-on that uses data [http://www2016.net/proceedings/proceedings/p121.pdf "safeness" approach like Cliqz]
| Add-On creation experience (JavaScript, HTML, CSS, Networking), Cloud Service experience (python or node.js)
| Luke Crouch
| Luke Crouch
|
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Design screenshot-based localization interface in [https://pontoon.mozilla.org/ Pontoon]
| We'd like to explore the feasibility of screenshot-based localization process in [https://pontoon.mozilla.org/ Pontoon] - Mozilla's translation tool. To provide more translation context, each string will be accompanied by a screenshot showing how the string is used in the application. Additionally, localizers will have the ability to navigate and filter strings by screenshots, as well as preview their translations in the localized screenshots.
| JavaScript, HTML, CSS and Design. Django is a plus.
| [[User:Mathjazz|:mathjazz]]
| [[User:Mathjazz|:mathjazz]]
|
|}

== Security Assurance ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|
TLS 1.3 scanning in Mozilla TLS Observatory
|
[https://github.com/mozilla/tls-observatory Mozilla TLS Observatory] is a hosted service that provides hindsight and compliance checking on the configuration of HTTPS servers. The goal of this project is to improve the service to support scanning TLS 1.3 enabled endpoints, either by improving the [https://github.com/mozilla/cipherscan existing scanner] or writing an entirely new scanner.
|
Programming skills in C, Bash and Go. Strong understanding of TLS and micro-services architectures.
|
Julien Vehent
|
Julien Vehent
|
None
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| science.mozilla.org phase 2
| Start phase 2 of the Mozilla Science Lab website by implementing
* [https://github.com/mozilla/science.mozilla.org/issues/135 github authentication],
* [https://github.com/mozilla/science.mozilla.org/issues/311 members homepage],
* [https://github.com/mozilla/science.mozilla.org/issues/536 improve blog post readability], and add the
* [https://github.com/mozilla/science.mozilla.org/issues/518 ability to join projects]
| js, html, css, react, django, python
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| [https://mozillians.org/en-US/u/alanmoo/ alanmoo]
| Detailed list and breakdown of all phase 2 work (only the tasks mentioned in details are expected to be completed by the student):
* Phase 2.1 https://github.com/mozilla/science.mozilla.org/milestone/11
* Phase 2.2 https://github.com/mozilla/science.mozilla.org/milestone/12
|-
| Paper Badger - badgr migration & publisher integration
| * Issuing badges to credit authors for their work on academic papers.
* In the final steps of our badgekit to Badgr migration, add tests to make sure we have feature parity and make the switch to Badgr in production.
* Implement a [https://github.com/mozillascience/PaperBadger/issues/160 journal submission system integration] with paper badger. This way, journals won't have to manually enter new badges in our system.
| js, Badgr, APIs, authentication, node.js, react
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| github: https://github.com/mozillascience/paperbadger
|-
| Study Group participation visualization
| [https://github.com/mozillascience/studyGroup study groups] meet all over the world, running regular events share skills, co-work and create community around open science. Right now there's no easy way to see all the study group events.
* Write a script to collect data for all study group events happening world wide. Each study group is a [https://github.com/mozillascience/studyGroup fork of this template repo]. Each event is an issue in the repo ([https://github.com/UofTCoders/Events/issues example of events as issues]). [https://github.com/mozillascience/studyGroup/blob/gh-pages/scripts/updateCalendar.py here is a script] that collects all events for a specific repo. Please update this to collect data from all forks.
* Visualize this data in a way that shows study group activity all around the world! viz: calendar, map
| js, html, css, python (or another scripting language), data visualization
| [https://mozillians.org/en-US/u/zannah/ Zannah]
| [https://mozillians.org/en-US/u/aurelia/ Aurelia]
| main study group repo: https://github.com/mozillascience/studyGroup
|}

== Thimble ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Address stability issues within Thimble
| Main task: Get Thimble to write directly to AWS instead of writing to a database first.
| js, html, css
| [https://mozillians.org/en-US/u/gideon/ gideon]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| Full list of issues affecting thimble's stability: https://github.com/mozilla/thimble.mozilla.org/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3A%22good%20first%20bug%22%20-label%3A%22assigned%20to%20contributor%22
|-
| Thimble with Collaboration
| Goal: Use together.js to enable a multi-user environment on Thimble that is tailored to work as a virtual teaching environment for HTML/CSS/JS
Details:
* Fixing issues in together.js to make it functional
* working on ways to sync state between Thimble's editor and the remote Thimble editor(s
* Syncing filesystems across Thimble editors with WebRTC
| js, html, css
| [https://mozillians.org/en-US/u/gideon/ gideon]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| thimble repo: https://github.com/mozilla/thimble.mozilla.org
|}

== Open Innovation (Open Source Student Clubs) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Measuring the Development of an Open Source Contributor
| We are looking for a passionate developer to work with the GitHub API to build a platform for measuring contributors performance/engagement across multiple open source projects over an extended time period.
| Javascript, javascript framework, a sequel database, HTML, GitHub API
| [https://mozillians.org/en-US/u/lucyeoh/ :Lucy]
| [https://mozillians.org/en-US/u/bacharakis/ :Christos]
| For questions about this project please leave a comment in [https://github.com/mozilla/Campus-Program/issues/363 this issue]
|-
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
| Matrix protocol support
| [http://matrix.org/ Matrix] is an open, decentralized protocol for instant messaging (and more!) It has bridges to many other networks and protocol, e.g. IRC, Slack, and more. Initial support for Matrix was added in {{bug|1199855}}, but there's a lot to do still:

* Support more features from the Matrix SDK (room topics, typing notifications, read receipts, etc.)
* Support one-on-one conversations.
* Add tests specific to Matrix.
* Improve the Matrix JS-SDK that Instantbird and Thunderbird depend on.
* Improving and expanding shared code and APIs used by all JavaScript protocol plugins (IRC, XMPP, Yahoo and Twitter).
* Improving documentation of the process for adding a protocol to Instantbird/Thunderbird.
* Using the Matrix protocol on a day-to-day basis to dog-food the code and see what else is missing.
| JavaScript, XPCOM, experience using HTTP APIs
| Patrick Cloke [:clokep]
| [mailto:clokep@gmail.com clokep]
| If you're interested in supporting a different protocol, please come talk to us. Protocols we're interested in: Matrix, Google Hangouts, Facebook, Bonjour, TextSecure/Signal, Telegram, or others!
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Introducing Calendar Accounts
| Traditionally our calendar extension is organized into a list of calendars, each calendar being implemented by a “provider”, for example local storage or using the CalDAV protocol. The service to manage these calendars maintains a simple list, the entries have no connection to each other.
Some calendar providers would greatly benefit from being able to group calendars into accounts, for example free-busy lookups are usually per-server operations and not per-calendar. It would also open the door for some great new features that have been postponed because they can be implemented cleaner with the notion of accounts.
| XUL, CSS, JavaScript
| [mailto:mozilla@kewis.ch Fallen]
| [mailto:mozilla@kewis.ch Fallen]
| [[Media:Calendar-gsoc2015-calmgr.pdf|Click here for a detailed project description]]
|-
| Resource Booking Improvements
| The Lightning extension has a dialog for inviting attendees to an event, which also shows availability information. Albeit not very obvious, it also allows booking resources and rooms. To improve this experience we would like users to be able to pick rooms and resources in a way that they don't need to remember the room address and quickly see which rooms and resources exist and are available around the proposed time of the event.
| XUL, CSS, JavaScript
| [mailto:mozilla@kewis.ch Fallen]
| [mailto:mozilla@kewis.ch Fallen]
| [[Media:Calendar-gsoc2015-resourcebooking.pdf|Click here for a detailed project description]]
|-
| Advanced Preferences System
| Today, Lightning preferences can mostly only be set on global level. A different, but smaller set of preferences is available on calendar level, whereas several preferences are currently only available from within the config editor. The goal of this project is to create a preference system like Thunderbird uses it - making most of the preferences available on calendar level with an option to fall back to corresponding globally configured preferences.

This is mainly a JavaScript project, but to a smaller extent some UI extensions are required. The emphasis is on the functional part here.

| XUL, HTML, CSS, JavaScript
| MakeMyDay
| [mailto:mozilla@kewis.ch Fallen] / MakeMyDay
|
|-
| Convert from XUL to HTML
| Lightning has traditionally been using XUL for its user interface. To modernize, we would like to convert dialogs, tab content and other parts of the user interface to HTML. The new components should use web standards as much as possible, avoiding extensive use of third party libraries.

This is a fairly open ended proposal, which requires the applicant to first identify parts of the user interface that would make sense to convert to HTML and put up a timeline how long to spend on each component. Focus should be on the quality of the conversion, not the quantity of components changed.
| HTML, CSS, JavaScript
| [mailto:mozilla@kewis.ch Fallen]
| [mailto:mozilla@kewis.ch Fallen]
|}

Community:SummerOfCode17:Brainstorming

2017-02-08T17:51:30Z

Abby: update skills for study group project -- django not needed!

Mozilla community members - submit proposals here for 2017 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode17|official list]].) '''The''' absolute last '''deadline for submitting ideas''' in time to help us get accepted by Google '''is February 9th'''.

Are you a student looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode17|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - 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 can, 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.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''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.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''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.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| TaskCluster JSON Parameterization
| Build a powerful JSON parameterization system and use it everywhere
| JavaScript, Python
| :dustin
| :dustin
| The json-e language supports complex transformations of JSON data. The project involves completing the specification, implementation (in two languages), and documentation of this language, then using it to support Gecko action and decision task and users of taskcluster-github and taskcluster-hooks. Success here means that the language is complete and in active use in at least one of the listed contexts.
|-
| Livelog Proxy
| Write a server that privileged-clients can open a HTTPS connection to in-order to expose a webhook that http-clients can call.
When normal http-clients access the exposed webhooks the connection will be reverse proxied to the
privileged-clients over their out-going connection.
| golang, github, http, web sockets, node.js
| :jonasfj
| :jonasfj
| This is like to ngrok and localtunnel.me, read up on those. For performance reasons server should be written in golang, with client libraries in golang and node.js.
|
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| about:telemetry redesign
| about:telemetry is present on all builds of Firefox as a way for users to view the data being stored and sent via Telemetry. It was built before Firefox had multi-process Telemetry and without a clear design. This has resulted in a confusing HTML UI and barely-comprehensible JS.
| webtech (HTML+CSS+JS) and Design
| :chutten
| :chutten
|
|-
| Boost Session Restore performance
| Session (Re)store is important as a key feature of Firefox. Many people rely on it to re-open a tab from the past or recover from an unfortunate power outage. But making it blazing fast has not been our primary focus, until now. Your goal will be to help us make restoring any session snappy and blazing fast. Expect to learn a lot about the Firefox internals and interact with many core engineers during the SoC course.
| JavaScript
| :mikedeboer
| :mikedeboer, :dao
|
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Implement WebExtension APIs
| [https://developer.mozilla.org/en-US/Add-ons/WebExtensions WebExtensions] are a cross-browser system for developing browser add-ons. [http://arewewebextensionsyet.com/ Not all APIs are supported] by Firefox for Android yet.
The goal of this project is to:
* Implement some of the missing APIs ([https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/contextMenus contextMenus], [https://developer.chrome.com/extensions/browsingData browsingData], [identity?], [proxy?])
* Add automated test for those APIs
* Improve the tooling for building WebExtensions for Firefox for Android.
| Java, JavaScript, Android
| [https://mozillians.org/en-US/u/sebastian.kaspari/ :sebastian]
| [https://mozillians.org/en-US/u/sebastian.kaspari/ :sebastian]
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
! JS static analysis
! Bring some static analysis in our Firefox Javascript code
! Javascript experience, FLOW(?)
! Sylvestre
! same
! This project aims to evaluate and integrate more static analysis for Javascript code into some key sections of the Firefox code. We will focus on deploying [https://github.com/facebook/flow FLOW] on some part of the code as a proof of concept. Depending on the results, this will be extended to more components and/or integration in the developer workflow.
|-
! C++ static analysis
! Add new checkers specific to our base code
! Strong C++ experience, clang
! Sylvestre
! Andi
! In order to tackle issues during the development phase, Mozilla wrote a [https://hg.mozilla.org/mozilla-central/file/tip/build/clang-plugin bunch of static analyzers checkers] based on [http://clang.llvm.org/extra/clang-tidy/ clang-tidy]. In this project, we will focus on writing more checkers (either generic to C/C++ or specific to Gecko programming patterns).
|-
! JSON in Sqlite
! Query JSON Documents stored in Sqlite
! Database, SQL, Python
! Kyle Lahnakoski
! Kyle Lahnakoski
! [https://github.com/klahnakoski/JSONQueryExpressionTests/blob/master/docs/GSOC%20Proposal.md Details]
|-
! View details of performance test results
! At the moment, Perfherder provides summarized views of results of Talos tests and others, but not the individual test results, athough the supporting data exists. This project will be about creating an easy-to-use web interface for visualizing this data that integrates well with the existing Perfherder views
! HTML, CSS, JS, AngularJS
! Will Lachance (:wlach)
! Will Lachance (:wlach), Robert Wood (:rwood)
! [https://wiki.mozilla.org/Auto-tools/Projects/Perfherder Perfherder wiki] / [https://bugzilla.mozilla.org/show_bug.cgi?id=1164891 bug] (don't be fooled by the fact that there is just one bug, there is easily enough work here to fill a gsoc project)
|-
! Regression localization from stack traces
! Tool to blame a patch for causing a newly introduced crash.
! C++, Python
! Marco
! Marco
! The project would involve creating a tool that analyzes a set of stack traces, performing the intersection with the Firefox call graph (which can be generated using Clang) and a set of recently committed patches.
|-
! Improvements for crash clustering
! Build a tool to improve crash clustering, currently based on the top method of the stack trace.
! Python, C++
! Marco
! Marco
! The project would involve finalizing https://github.com/marco-c/crashsimilarity; testing it more thoroughly; putting it in production.
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| MDN Documentation Tester WebExtension
| Rewrite the [https://github.com/Elchi3/mdn-doc-tests MDN doc tester add-on] as a (well-tested, modern, documented) WebExtension that runs in Firefox, Chrome, Opera, and possibly Edge. Ideally reach feature parity with the existing Add-on SDK add-on and if time allows work on new test ideas that run against the MDN documentation.
| Add-On/WebExtension experience (JavaScript, HTML, CSS)
| Florian Scholz
| Florian Scholz
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Curriculum database for Learning site
| Curriculum is currently accessed via the Teaching Activities page of the learning site (https://learning.mozilla.org/en-US/activities ). It's a pretty static experience. Users can browse through a list of modules, but there is no search capability. We have a prototype for a more interactive UX that allows users to search and filter curriculum modules and activities: https://flukeout.github.io/curriculum-search-react/. This project would require implementing the front-end, as well as wiring up the backend database (for which the model has been defined, but the data has not been migrated).
| js, html, css, django, python
| [https://mozillians.org/en-US/u/hannah/ hannah]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| This would be a big win for the curriculum team and for the community members who make good use of our learning/teaching materials. The database could eventually be extended beyond the learning site and support other parts of the network as well.
|}

== OpenArt ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Improve Balrog's Admin API
| Make Balrog's Admin API simpler and easier for clients to work with by moving to a [http://swagger.io/ Swagger]-based approach.
| python,rest apis
| Ben Hearsum
| Ben Hearsum
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
! Rust + WebAssembly showcase
! Rust and WebAssembly are going to be a great pair. Design and implement a simple and attractive web application, in Rust, that demonstrates the power of Rust on the web. Make fixes to upstream projects as necessary. Write a blog post about it.
! Rust, web development
! brson
! brson, badboy
! cc https://users.rust-lang.org/t/compiling-to-the-web-with-rust-and-emscripten/7627. Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-1-md
|-
! Rust dashboard updates
! Update rusty-dash.com to include additional metrics important to the project. This tool is vital to the day-to-day management of Rust, but it needs some dedicated attention to fulfill its promise.
! Rust
! brson
! brson, aturon?, dikaiosune?
! Follow on work to https://internals.rust-lang.org/t/the-rust-project-needs-much-better-visibility-into-important-metrics/3367
|-
! Rust reproducible builds
! Make the Rust build process produce the identical binaries when run with identical configurations. This improves the security of the Rust ecosystem by allowing others to
double-check the official Rust builds
! Rust, compilers, systems programming
! brson
! brson, mw, Manishearth
! https://internals.rust-lang.org/t/verifying-rustc-releases-with-reproducible-builds/4502. Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-2-md
|-
! Abstract the Rust standard library
! The Rust standard library is very portable, but can be very, very portable. Refactor the
standard library to pull out a platform abstraction layer.
! Moderate Rust experience
! brson
! brson
! https://internals.rust-lang.org/t/refactoring-std-for-ultimate-portability/4301
|-
! Rust cross-platform showcase project
! Rust is very portable. Create a single showcase demo project that compiles for Windows, OS X, Linux, Android, iOS, wasm, and microcontrollers. Use real crates to accomplish some real task. Set up CI for all platforms on Travis. To be used as a teaching tool and for regression testing. Write a blog post.
! Moderate Rust experience
! brson
! brson
!
|-
! rustc micro-optimization bonanza
! Just go hog wild finding microoptimizations in rustc. Write a blog post bragging about it.
! Performance optimization
! brson
! brson, nnethercote?
!
|-
! Rust-specific benchmark suite
! Today Rust uses perf.rust-lang.org to track _compile time_ performance, but nothing to track _runtime_ performance. Work with the Rust developers to create a benchmark suite specific to Rust.
! Programming
! brson
! brson
!
|-
! Rust crate semver compatibility tool
! Rust libraries follow the semver spec for indicating API compatibility, but conformance to semver is not enforced in any way - it is up to crate authors to guarantee their crates can be upgraded correctly. With Rust's strong type system it should be possible to mechanically check whether crates
are obeying semver. This would be a huge boon to the stability of the Rust ecosystem.
! Static analysis
! brson
! brson, badboy
! https://users.rust-lang.org/t/warnings-for-breaking-semver/1415 https://users.rust-lang.org/t/signature-based-api-comparison/2377 . Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-3-md
|-
! Reconstruct the Rust bootstrap chain
! Rust is a self-hosted compiler, originally bootstrapped from OCaml, then self-bootstrapped several hundred times over the years. Today there is only one Rust 'lineage' of any note, the official compiler, but with compilers diversity of implementation is a security issue. If another party could replicate the
Rust compiler it would provide assurance that the official isn't compromised by, or can recover from, a "trusting trust" attack. Although the historical information needed to rebootstrap Rust is mostly complete, it is not trivial to do. Construct a script that can reconstruct the modern Rust compiler from the original OCaml implementation, run it to completion, write a blog post.
! Scripting, build systems
! brson
! acrichto
!
|-
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Off-main thread HTML parsing
| [https://github.com/servo/servo/wiki/Off-main-thread-HTML-parsing-project Project page]
| Enthusiasm to learn Rust, comfortable reading/writing JavaScript
| [https://mozillians.org/en-US/u/jdm/ jdm]
| Anthony Ramine (nox)
|
|-
| Extend ServiceWorker implementation
| [https://github.com/servo/servo/wiki/More-ServiceWorker-support-project Project page]
| Enthusiasm to learn Rust, comfortable reading/writing JavaScript
| [https://mozillians.org/en-US/u/jdm/ jdm]
| [https://mozillians.org/en-US/u/jdm/ jdm]
|
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Tor Experiment
| Create a an experimental extension that bundles and launches Tor. Benchmark and report the amount of data transferred, time-to-first-byte, bandwidth differentials.
| Add-On creation experience, Programming in C/Javascript.
| Tom Ritter
| Tom Ritter
|-
| StopTrackware.org
| Create a clearinghouse of trackware lists like StopBadware.org, by creating a Track-the-trackers add-on that uses data [http://www2016.net/proceedings/proceedings/p121.pdf "safeness" approach like Cliqz]
| Add-On creation experience (JavaScript, HTML, CSS, Networking), Cloud Service experience (python or node.js)
| Luke Crouch
| Luke Crouch
|
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Design screenshot-based localization interface in [https://pontoon.mozilla.org/ Pontoon]
| We'd like to explore the feasibility of screenshot-based localization process in [https://pontoon.mozilla.org/ Pontoon] - Mozilla's translation tool. To provide more translation context, each string will be accompanied by a screenshot showing how the string is used in the application. Additionally, localizers will have the ability to navigate and filter strings by screenshots, as well as preview their translations in the localized screenshots.
| Web standards and Design. Django is a plus.
| [[User:Mathjazz|:mathjazz]]
| [[User:Mathjazz|:mathjazz]]
|
|}

== Build system ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Assurance ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|
TLS 1.3 scanning in Mozilla TLS Observatory
|
[https://github.com/mozilla/tls-observatory Mozilla TLS Observatory] is a hosted service that provides hindsight and compliance checking on the configuration of HTTPS servers. The goal of this project is to improve the service to support scanning TLS 1.3 enabled endpoints, either by improving the [https://github.com/mozilla/cipherscan existing scanner] or writing an entirely new scanner.
|
Programming skills in C, Bash and Go. Strong understanding of TLS and micro-services architectures.
|
Julien Vehent
|
Julien Vehent
|
None
|}

== WADI ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| science.mozilla.org phase 2
| Start phase 2 of the Mozilla Science Lab website by implementing
* [https://github.com/mozilla/science.mozilla.org/issues/135 github authentication],
* [https://github.com/mozilla/science.mozilla.org/issues/311 members homepage],
* [https://github.com/mozilla/science.mozilla.org/issues/536 improve blog post readability], and add the
* [https://github.com/mozilla/science.mozilla.org/issues/518 ability to join projects]
| js, html, css, react, django, python
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| [https://mozillians.org/en-US/u/alanmoo/ alanmoo]
| Detailed list and breakdown of all phase 2 work (only the tasks mentioned in details are expected to be completed by the student):
* Phase 2.1 https://github.com/mozilla/science.mozilla.org/milestone/11
* Phase 2.2 https://github.com/mozilla/science.mozilla.org/milestone/12
|-
| Paper Badger - badgr migration & publisher integration
| * Issuing badges to credit authors for their work on academic papers.
* In the final steps of our badgekit to Badgr migration, add tests to make sure we have feature parity and make the switch to Badgr in production.
* Implement a [https://github.com/mozillascience/PaperBadger/issues/160 journal submission system integration] with paper badger. This way, journals won't have to manually enter new badges in our system.
| js, Badgr, APIs, authentication, node.js, react
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| github: https://github.com/mozillascience/paperbadger
|-
| Study Group participation visualization
| [https://github.com/mozillascience/studyGroup study groups] meet all over the world, running regular events share skills, co-work and create community around open science. Right now there's no easy way to see all the study group events.
* Write a script to collect data for all study group events happening world wide. Each study group is a [https://github.com/mozillascience/studyGroup fork of this template repo]. Each event is an issue in the repo ([https://github.com/UofTCoders/Events/issues example of events as issues]). [https://github.com/mozillascience/studyGroup/blob/gh-pages/scripts/updateCalendar.py here is a script] that collects all events for a specific repo. Please update this to collect data from all forks.
* Visualize this data in a way that shows study group activity all around the world! viz: calendar, map
| js, html, css, python (or another scripting language), data visualization
| [https://mozillians.org/en-US/u/zannah/ Zannah]
| [https://mozillians.org/en-US/u/aurelia/ Aurelia]
| main study group repo: https://github.com/mozillascience/studyGroup
|}

== MozVR ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Reporter
! Mentor(s)
! Comments
|-
|}

== Connected Devices ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Reporter
! Mentor(s)
! Comments
|-
|}

== Thimble ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Address stability issues within Thimble
| Main task: Get Thimble to write directly to AWS instead of writing to a database first.
| js, html, css
| [https://mozillians.org/en-US/u/gideon/ gideon]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| Full list of issues affecting thimble's stability: https://github.com/mozilla/thimble.mozilla.org/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3A%22good%20first%20bug%22%20-label%3A%22assigned%20to%20contributor%22
|-
| Integrating VR capabilities into Thimble
| Goal: Thimble makes it easy to create multi user VR experiences, allowing the whole classroom to take virtual field trips through student projects.
This is made possible by doing any of these:
* Integration of the A-frame visual inspector, which gives the user lots of control over an object properties in a custom UI
* Custom Quick-Edit UI for different types of objects
* Develop large, visual menu of 3D objects make it easy to build interesting scenes quickly
* A wide range of starter projects
| js, html, css
| [https://mozillians.org/en-US/u/gideon/ gideon]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| This work would be done in parallel with work done by [https://cdot.senecacollege.ca/ CDOT] on making Thimble a VR experience building tool
thimble repo: https://github.com/mozilla/thimble.mozilla.org
|-
| Thimble and Remote Mentorship
| Goal: Use together.js to enable a multi-user environment on Thimble that is tailored to work as a virtual teaching environment for HTML/CSS/JS
Details:
* Fixing issues in together.js to make it functional
* working on ways to sync state between Thimble's editor and the remote Thimble editor(s
* Syncing filesystems across Thimble editors with WebRTC
| js, html, css
| [https://mozillians.org/en-US/u/gideon/ gideon]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| thimble repo: https://github.com/mozilla/thimble.mozilla.org
|}

Community:SummerOfCode17:Brainstorming

2017-02-07T21:27:56Z

Abby: change mentor abbycabs -> alanmoo

Mozilla community members - submit proposals here for 2017 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode17|official list]].) '''The''' absolute last '''deadline for submitting ideas''' in time to help us get accepted by Google '''is February 9th'''.

Are you a student looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode17|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - 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 can, 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.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''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.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''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.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| TaskCluster JSON Parameterization
| Build a powerful JSON parameterization system and use it everywhere
| JavaScript, Python
| :dustin
| :dustin
| The json-e language supports complex transformations of JSON data. The project involves completing the specification, implementation (in two languages), and documentation of this language, then using it to support Gecko action and decision task and users of taskcluster-github and taskcluster-hooks. Success here means that the language is complete and in active use in at least one of the listed contexts.
|-
| Livelog Proxy
| Write a server that privileged-clients can open a HTTPS connection to in-order to expose a webhook that http-clients can call.
When normal http-clients access the exposed webhooks the connection will be reverse proxied to the
privileged-clients over their out-going connection.
| golang, github, http, web sockets, node.js
| :jonasfj
| :jonasfj
| This is like to ngrok and localtunnel.me, read up on those. For performance reasons server should be written in golang, with client libraries in golang and node.js.
|
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| about:telemetry redesign
| about:telemetry is present on all builds of Firefox as a way for users to view the data being stored and sent via Telemetry. It was built before Firefox had multi-process Telemetry and without a clear design. This has resulted in a confusing HTML UI and barely-comprehensible JS.
| webtech (HTML+CSS+JS) and Design
| :chutten
| :chutten
|
|-
| Boost Session Restore performance
| Session (Re)store is important as a key feature of Firefox. Many people rely on it to re-open a tab from the past or recover from an unfortunate power outage. But making it blazing fast has not been our primary focus, until now. Your goal will be to help us make restoring any session snappy and blazing fast. Expect to learn a lot about the Firefox internals and interact with many core engineers during the SoC course.
| JavaScript
| :mikedeboer
| :mikedeboer, :dao
|
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Implement WebExtension APIs
| [https://developer.mozilla.org/en-US/Add-ons/WebExtensions WebExtensions] are a cross-browser system for developing browser add-ons. [http://arewewebextensionsyet.com/ Not all APIs are supported] by Firefox for Android yet.
The goal of this project is to:
* Implement some of the missing APIs ([https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/contextMenus contextMenus], [https://developer.chrome.com/extensions/browsingData browsingData], [identity?], [proxy?])
* Add automated test for those APIs
* Improve the tooling for building WebExtensions for Firefox for Android.
| Java, JavaScript, Android
| [https://mozillians.org/en-US/u/sebastian.kaspari/ :sebastian]
| [https://mozillians.org/en-US/u/sebastian.kaspari/ :sebastian]
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
! JS static analysis
! Bring some static analysis in our Firefox Javascript code
! Javascript experience, FLOW(?)
! Sylvestre
! same
!
|-
! C++ static analysis
! Add new checkers specific to our base code
! Strong C++ experience, clang
! Sylvestre
! Andi
!
|-
! JSON in Sqlite
! Query JSON Documents stored in Sqlite
! Database, SQL, Python
! Kyle Lahnakoski
! Kyle Lahnakoski
! [https://github.com/klahnakoski/JSONQueryExpressionTests/blob/master/docs/GSOC%20Proposal.md Details]
|-
! View details of performance test results
! At the moment, Perfherder provides summarized views of results of Talos tests and others, but not the individual test results, athough the supporting data exists. This project will be about creating an easy-to-use web interface for visualizing this data that integrates well with the existing Perfherder views
! HTML, CSS, JS, AngularJS
! Will Lachance (:wlach)
! Will Lachance (:wlach), Robert Wood (:rwood)
! [https://wiki.mozilla.org/Auto-tools/Projects/Perfherder Perfherder wiki] / [https://bugzilla.mozilla.org/show_bug.cgi?id=1164891 bug] (don't be fooled by the fact that there is just one bug, there is easily enough work here to fill a gsoc project)
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| MDN Documentation Tester WebExtension
| Rewrite the [https://github.com/Elchi3/mdn-doc-tests MDN doc tester add-on] as a (well-tested, modern, documented) WebExtension that runs in Firefox, Chrome, Opera, and possibly Edge. Ideally reach feature parity with the existing Add-on SDK add-on and if time allows work on new test ideas that run against the MDN documentation.
| Add-On/WebExtension experience (JavaScript, HTML, CSS)
| Florian Scholz
| Florian Scholz
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Curriculum database for Learning site
| Curriculum is currently accessed via the Teaching Activities page of the learning site (https://learning.mozilla.org/en-US/activities ). It's a pretty static experience. Users can browse through a list of modules, but there is no search capability. We have a prototype for a more interactive UX that allows users to search and filter curriculum modules and activities: https://flukeout.github.io/curriculum-search-react/. This project would require implementing the front-end, as well as wiring up the backend database (for which the model has been defined, but the data has not been migrated).
| js, html, css, django, python
| [https://mozillians.org/en-US/u/hannah/ hannah]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| This would be a big win for the curriculum team and for the community members who make good use of our learning/teaching materials. The database could eventually be extended beyond the learning site and support other parts of the network as well.
|}

== OpenArt ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Improve Balrog's Admin API
| Make Balrog's Admin API simpler and easier for clients to work with by moving to a [http://swagger.io/ Swagger]-based approach.
| python,rest apis
| Ben Hearsum
| Ben Hearsum
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
! Rust + WebAssembly showcase
! Rust and WebAssembly are going to be a great pair. Design and implement a simple and attractive web application, in Rust, that demonstrates the power of Rust on the web. Make fixes to upstream projects as necessary. Write a blog post about it.
! Rust, web development
! brson
! brson, badboy
! cc https://users.rust-lang.org/t/compiling-to-the-web-with-rust-and-emscripten/7627. Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-1-md
|-
! Rust dashboard updates
! Update rusty-dash.com to include additional metrics important to the project. This tool is vital to the day-to-day management of Rust, but it needs some dedicated attention to fulfill its promise.
! Rust
! brson
! brson, aturon?, dikaiosune?
! Follow on work to https://internals.rust-lang.org/t/the-rust-project-needs-much-better-visibility-into-important-metrics/3367
|-
! Rust reproducible builds
! Make the Rust build process produce the identical binaries when run with identical configurations. This improves the security of the Rust ecosystem by allowing others to
double-check the official Rust builds
! Rust, compilers, systems programming
! brson
! brson, mw, Manishearth
! https://internals.rust-lang.org/t/verifying-rustc-releases-with-reproducible-builds/4502. Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-2-md
|-
! Abstract the Rust standard library
! The Rust standard library is very portable, but can be very, very portable. Refactor the
standard library to pull out a platform abstraction layer.
! Moderate Rust experience
! brson
! brson
! https://internals.rust-lang.org/t/refactoring-std-for-ultimate-portability/4301
|-
! Rust cross-platform showcase project
! Rust is very portable. Create a single showcase demo project that compiles for Windows, OS X, Linux, Android, iOS, wasm, and microcontrollers. Use real crates to accomplish some real task. Set up CI for all platforms on Travis. To be used as a teaching tool and for regression testing. Write a blog post.
! Moderate Rust experience
! brson
! brson
!
|-
! rustc micro-optimization bonanza
! Just go hog wild finding microoptimizations in rustc. Write a blog post bragging about it.
! Performance optimization
! brson
! brson, nnethercote?
!
|-
! Rust-specific benchmark suite
! Today Rust uses perf.rust-lang.org to track _compile time_ performance, but nothing to track _runtime_ performance. Work with the Rust developers to create a benchmark suite specific to Rust.
! Programming
! brson
! brson
!
|-
! Rust crate semver compatibility tool
! Rust libraries follow the semver spec for indicating API compatibility, but conformance to semver is not enforced in any way - it is up to crate authors to guarantee their crates can be upgraded correctly. With Rust's strong type system it should be possible to mechanically check whether crates
are obeying semver. This would be a huge boon to the stability of the Rust ecosystem.
! Static analysis
! brson
! brson, badboy
! https://users.rust-lang.org/t/warnings-for-breaking-semver/1415 https://users.rust-lang.org/t/signature-based-api-comparison/2377 . Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-3-md
|-
! Reconstruct the Rust bootstrap chain
! Rust is a self-hosted compiler, originally bootstrapped from OCaml, then self-bootstrapped several hundred times over the years. Today there is only one Rust 'lineage' of any note, the official compiler, but with compilers diversity of implementation is a security issue. If another party could replicate the
Rust compiler it would provide assurance that the official isn't compromised by, or can recover from, a "trusting trust" attack. Although the historical information needed to rebootstrap Rust is mostly complete, it is not trivial to do. Construct a script that can reconstruct the modern Rust compiler from the original OCaml implementation, run it to completion, write a blog post.
! Scripting, build systems
! brson
! acrichto
!
|-
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Off-main thread HTML parsing
| [https://github.com/servo/servo/wiki/Off-main-thread-HTML-parsing-project Project page]
| Enthusiasm to learn Rust, comfortable reading/writing JavaScript
| [https://mozillians.org/en-US/u/jdm/ jdm]
| Anthony Ramine (nox)
|
|-
| Extend ServiceWorker implementation
| [https://github.com/servo/servo/wiki/More-ServiceWorker-support-project Project page]
| Enthusiasm to learn Rust, comfortable reading/writing JavaScript
| [https://mozillians.org/en-US/u/jdm/ jdm]
| [https://mozillians.org/en-US/u/jdm/ jdm]
|
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Tor Experiment
| Create a an experimental extension that bundles and launches Tor. Benchmark and report the amount of data transferred, time-to-first-byte, bandwidth differentials.
| Add-On creation experience, Programming in C/Javascript.
| Tom Ritter
| Tom Ritter
|-
| StopTrackware.org
| Create a clearinghouse of trackware lists like StopBadware.org, by creating a Track-the-trackers add-on that uses data [http://www2016.net/proceedings/proceedings/p121.pdf "safeness" approach like Cliqz]
| Add-On creation experience (JavaScript, HTML, CSS, Networking), Cloud Service experience (python or node.js)
| Luke Crouch
| Luke Crouch
|
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Design screenshot-based localization interface in [https://pontoon.mozilla.org/ Pontoon]
| We'd like to explore the feasibility of screenshot-based localization process in [https://pontoon.mozilla.org/ Pontoon] - Mozilla's translation tool. To provide more translation context, each string will be accompanied by a screenshot showing how the string is used in the application. Additionally, localizers will have the ability to navigate and filter strings by screenshots, as well as preview their translations in the localized screenshots.
| Web standards and Design. Django is a plus.
| [[User:Mathjazz|:mathjazz]]
| [[User:Mathjazz|:mathjazz]]
|
|}

== Build system ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Assurance ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|
TLS 1.3 scanning in Mozilla TLS Observatory
|
[https://github.com/mozilla/tls-observatory Mozilla TLS Observatory] is a hosted service that provides hindsight and compliance checking on the configuration of HTTPS servers. The goal of this project is to improve the service to support scanning TLS 1.3 enabled endpoints, either by improving the [https://github.com/mozilla/cipherscan existing scanner] or writing an entirely new scanner.
|
Programming skills in C, Bash and Go. Strong understanding of TLS and micro-services architectures.
|
Julien Vehent
|
Julien Vehent
|
None
|}

== WADI ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| science.mozilla.org phase 2
| Start phase 2 of the Mozilla Science Lab website by implementing
* [https://github.com/mozilla/science.mozilla.org/issues/135 github authentication],
* [https://github.com/mozilla/science.mozilla.org/issues/311 members homepage],
* [https://github.com/mozilla/science.mozilla.org/issues/536 improve blog post readability], and add the
* [https://github.com/mozilla/science.mozilla.org/issues/518 ability to join projects]
| js, html, css, react, django, python
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| [https://mozillians.org/en-US/u/alanmoo/ alanmoo]
| Detailed list and breakdown of all phase 2 work (only the tasks mentioned in details are expected to be completed by the student):
* Phase 2.1 https://github.com/mozilla/science.mozilla.org/milestone/11
* Phase 2.2 https://github.com/mozilla/science.mozilla.org/milestone/12
|-
| Paper Badger - badgr migration & publisher integration
| * Issuing badges to credit authors for their work on academic papers.
* In the final steps of our badgekit to Badgr migration, add tests to make sure we have feature parity and make the switch to Badgr in production.
* Implement a [https://github.com/mozillascience/PaperBadger/issues/160 journal submission system integration] with paper badger. This way, journals won't have to manually enter new badges in our system.
| js, Badgr, APIs, authentication, node.js, react
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| github: https://github.com/mozillascience/paperbadger
|-
| Study Group participation visualization
| [https://github.com/mozillascience/studyGroup study groups] meet all over the world, running regular events share skills, co-work and create community around open science. Right now there's no easy way to see all the study group events.
* Write a script to collect data for all study group events happening world wide. Each study group is a [https://github.com/mozillascience/studyGroup fork of this template repo]. Each event is an issue in the repo ([https://github.com/UofTCoders/Events/issues example of events as issues]). [https://github.com/mozillascience/studyGroup/blob/gh-pages/scripts/updateCalendar.py here is a script] that collects all events for a specific repo. Please update this to collect data from all forks.
* Visualize this data in a way that shows study group activity all around the world! viz: calendar, map
| js, html, css, react, django, python
| [https://mozillians.org/en-US/u/zannah/ Zannah]
| [https://mozillians.org/en-US/u/aurelia/ Aurelia]
| main study group repo: https://github.com/mozillascience/studyGroup
|}

== MozVR ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Reporter
! Mentor(s)
! Comments
|-
|}

== Connected Devices ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Reporter
! Mentor(s)
! Comments
|-
|}

== Thimble ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Address stability issues within Thimble
| Main task: Get Thimble to write directly to AWS instead of writing to a database first.
| js, html, css
| [https://mozillians.org/en-US/u/gideon/ gideon]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| Full list of issues affecting thimble's stability: https://github.com/mozilla/thimble.mozilla.org/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3A%22good%20first%20bug%22%20-label%3A%22assigned%20to%20contributor%22
|-
| Integrating VR capabilities into Thimble
| Goal: Thimble makes it easy to create multi user VR experiences, allowing the whole classroom to take virtual field trips through student projects.
This is made possible by doing any of these:
* Integration of the A-frame visual inspector, which gives the user lots of control over an object properties in a custom UI
* Custom Quick-Edit UI for different types of objects
* Develop large, visual menu of 3D objects make it easy to build interesting scenes quickly
* A wide range of starter projects
| js, html, css
| [https://mozillians.org/en-US/u/gideon/ gideon]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| This work would be done in parallel with work done by [https://cdot.senecacollege.ca/ CDOT] on making Thimble a VR experience building tool
thimble repo: https://github.com/mozilla/thimble.mozilla.org
|-
| Thimble and Remote Mentorship
| Goal: Use together.js to enable a multi-user environment on Thimble that is tailored to work as a virtual teaching environment for HTML/CSS/JS
Details:
* Fixing issues in together.js to make it functional
* working on ways to sync state between Thimble's editor and the remote Thimble editor(s
* Syncing filesystems across Thimble editors with WebRTC
| js, html, css
| [https://mozillians.org/en-US/u/gideon/ gideon]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| thimble repo: https://github.com/mozilla/thimble.mozilla.org
|}

Community:SummerOfCode17:Brainstorming

2017-02-07T02:59:21Z

Abby: Added Foundation, Science Lab and Thimble projects

Mozilla community members - submit proposals here for 2017 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode17|official list]].) '''The''' absolute last '''deadline for submitting ideas''' in time to help us get accepted by Google '''is February 9th'''.

Are you a student looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode17|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - 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 can, 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.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''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.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''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.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| TaskCluster JSON Parameterization
| Build a powerful JSON parameterization system and use it everywhere
| JavaScript, Python
| :dustin
| :dustin
| The json-e language supports complex transformations of JSON data. The project involves completing the specification, implementation (in two languages), and documentation of this language, then using it to support Gecko action and decision task and users of taskcluster-github and taskcluster-hooks. Success here means that the language is complete and in active use in at least one of the listed contexts.
|-
| Livelog Proxy
| Write a server that privileged-clients can open a HTTPS connection to in-order to expose a webhook that http-clients can call.
When normal http-clients access the exposed webhooks the connection will be reverse proxied to the
privileged-clients over their out-going connection.
| golang, github, http, web sockets, node.js
| :jonasfj
| :jonasfj
| This is like to ngrok and localtunnel.me, read up on those. For performance reasons server should be written in golang, with client libraries in golang and node.js.
|
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| about:telemetry redesign
| about:telemetry is present on all builds of Firefox as a way for users to view the data being stored and sent via Telemetry. It was built before Firefox had multi-process Telemetry and without a clear design. This has resulted in a confusing HTML UI and barely-comprehensible JS.
| webtech (HTML+CSS+JS) and Design
| :chutten
| :chutten
|
|-
| Boost Session Restore performance
| Session (Re)store is important as a key feature of Firefox. Many people rely on it to re-open a tab from the past or recover from an unfortunate power outage. But making it blazing fast has not been our primary focus, until now. Your goal will be to help us make restoring any session snappy and blazing fast. Expect to learn a lot about the Firefox internals and interact with many core engineers during the SoC course.
| JavaScript
| :mikedeboer
| :mikedeboer, :dao
|
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Implement WebExtension APIs
| [https://developer.mozilla.org/en-US/Add-ons/WebExtensions WebExtensions] are a cross-browser system for developing browser add-ons. [http://arewewebextensionsyet.com/ Not all APIs are supported] by Firefox for Android yet.
The goal of this project is to:
* Implement some of the missing APIs ([https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/contextMenus contextMenus], [https://developer.chrome.com/extensions/browsingData browsingData], [identity?], [proxy?])
* Add automated test for those APIs
* Improve the tooling for building WebExtensions for Firefox for Android.
| Java, JavaScript, Android
| [https://mozillians.org/en-US/u/sebastian.kaspari/ :sebastian]
| [https://mozillians.org/en-US/u/sebastian.kaspari/ :sebastian]
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
! JS static analysis
! Bring some static analysis in our Firefox Javascript code
! Javascript experience, FLOW(?)
! Sylvestre
! same
!
|-
! C++ static analysis
! Add new checkers specific to our base code
! Strong C++ experience, clang
! Sylvestre
! Andi
!
|-
! JSON in Sqlite
! Query JSON Documents stored in Sqlite
! Database, SQL, Python
! Kyle Lahnakoski
! Kyle Lahnakoski
! [https://github.com/klahnakoski/JSONQueryExpressionTests/blob/master/docs/GSOC%20Proposal.md Details]
|-
! View details of performance test results
! At the moment, Perfherder provides summarized views of results of Talos tests and others, but not the individual test results, athough the supporting data exists. This project will be about creating an easy-to-use web interface for visualizing this data that integrates well with the existing Perfherder views
! HTML, CSS, JS, AngularJS
! Will Lachance (:wlach)
! Will Lachance (:wlach), Robert Wood (:rwood)
! [https://wiki.mozilla.org/Auto-tools/Projects/Perfherder Perfherder wiki] / [https://bugzilla.mozilla.org/show_bug.cgi?id=1164891 bug] (don't be fooled by the fact that there is just one bug, there is easily enough work here to fill a gsoc project)
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Curriculum database for Learning site
| Curriculum is currently accessed via the Teaching Activities page of the learning site (https://learning.mozilla.org/en-US/activities ). It's a pretty static experience. Users can browse through a list of modules, but there is no search capability. We have a prototype for a more interactive UX that allows users to search and filter curriculum modules and activities: https://flukeout.github.io/curriculum-search-react/. This project would require implementing the front-end, as well as wiring up the backend database (for which the model has been defined, but the data has not been migrated).
| js, html, css, django, python
| [https://mozillians.org/en-US/u/hannah/ hannah]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| This would be a big win for the curriculum team and for the community members who make good use of our learning/teaching materials. The database could eventually be extended beyond the learning site and support other parts of the network as well.
|}

== OpenArt ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Improve Balrog's Admin API
| Make Balrog's Admin API simpler and easier for clients to work with by moving to a [http://swagger.io/ Swagger]-based approach.
| python,rest apis
| Ben Hearsum
| Ben Hearsum
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
! Rust + WebAssembly showcase
! Rust and WebAssembly are going to be a great pair. Design and implement a simple and attractive web application, in Rust, that demonstrates the power of Rust on the web. Make fixes to upstream projects as necessary. Write a blog post about it.
! Rust, web development
! brson
! brson, badboy
! cc https://users.rust-lang.org/t/compiling-to-the-web-with-rust-and-emscripten/7627. Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-1-md
|-
! Rust dashboard updates
! Update rusty-dash.com to include additional metrics important to the project. This tool is vital to the day-to-day management of Rust, but it needs some dedicated attention to fulfill its promise.
! Rust
! brson
! brson, aturon?, dikaiosune?
! Follow on work to https://internals.rust-lang.org/t/the-rust-project-needs-much-better-visibility-into-important-metrics/3367
|-
! Rust reproducible builds
! Make the Rust build process produce the identical binaries when run with identical configurations. This improves the security of the Rust ecosystem by allowing others to
double-check the official Rust builds
! Rust, compilers, systems programming
! brson
! brson, mw, Manishearth
! https://internals.rust-lang.org/t/verifying-rustc-releases-with-reproducible-builds/4502. Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-2-md
|-
! Abstract the Rust standard library
! The Rust standard library is very portable, but can be very, very portable. Refactor the
standard library to pull out a platform abstraction layer.
! Moderate Rust experience
! brson
! brson
! https://internals.rust-lang.org/t/refactoring-std-for-ultimate-portability/4301
|-
! Rust cross-platform showcase project
! Rust is very portable. Create a single showcase demo project that compiles for Windows, OS X, Linux, Android, iOS, wasm, and microcontrollers. Use real crates to accomplish some real task. Set up CI for all platforms on Travis. To be used as a teaching tool and for regression testing. Write a blog post.
! Moderate Rust experience
! brson
! brson
!
|-
! rustc micro-optimization bonanza
! Just go hog wild finding microoptimizations in rustc. Write a blog post bragging about it.
! Performance optimization
! brson
! brson, nnethercote?
!
|-
! Rust-specific benchmark suite
! Today Rust uses perf.rust-lang.org to track _compile time_ performance, but nothing to track _runtime_ performance. Work with the Rust developers to create a benchmark suite specific to Rust.
! Programming
! brson
! brson
!
|-
! Rust crate semver compatibility tool
! Rust libraries follow the semver spec for indicating API compatibility, but conformance to semver is not enforced in any way - it is up to crate authors to guarantee their crates can be upgraded correctly. With Rust's strong type system it should be possible to mechanically check whether crates
are obeying semver. This would be a huge boon to the stability of the Rust ecosystem.
! Static analysis
! brson
! brson, badboy
! https://users.rust-lang.org/t/warnings-for-breaking-semver/1415 https://users.rust-lang.org/t/signature-based-api-comparison/2377 . Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-3-md
|-
! Reconstruct the Rust bootstrap chain
! Rust is a self-hosted compiler, originally bootstrapped from OCaml, then self-bootstrapped several hundred times over the years. Today there is only one Rust 'lineage' of any note, the official compiler, but with compilers diversity of implementation is a security issue. If another party could replicate the
Rust compiler it would provide assurance that the official isn't compromised by, or can recover from, a "trusting trust" attack. Although the historical information needed to rebootstrap Rust is mostly complete, it is not trivial to do. Construct a script that can reconstruct the modern Rust compiler from the original OCaml implementation, run it to completion, write a blog post.
! Scripting, build systems
! brson
! acrichto
!
|-
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Off-main thread HTML parsing
| [https://github.com/servo/servo/wiki/Off-main-thread-HTML-parsing-project Project page]
| Enthusiasm to learn Rust, comfortable reading/writing JavaScript
| [https://mozillians.org/en-US/u/jdm/ jdm]
| Anthony Ramine (nox)
|
|-
| Extend ServiceWorker implementation
| [https://github.com/servo/servo/wiki/More-ServiceWorker-support-project Project page]
| Enthusiasm to learn Rust, comfortable reading/writing JavaScript
| [https://mozillians.org/en-US/u/jdm/ jdm]
| [https://mozillians.org/en-US/u/jdm/ jdm]
|
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Tor Experiment
| Create a an experimental extension that bundles and launches Tor. Benchmark and report the amount of data transferred, time-to-first-byte, bandwidth differentials.
| Add-On creation experience, Programming in C/Javascript.
| Tom Ritter
| Tom Ritter
|-
| StopTrackware.org
| Create a clearinghouse of trackware lists like StopBadware.org, by creating a Track-the-trackers add-on that uses data [http://www2016.net/proceedings/proceedings/p121.pdf "safeness" approach like Cliqz]
| Add-On creation experience (JavaScript, HTML, CSS, Networking), Cloud Service experience (python or node.js)
| Luke Crouch
| Luke Crouch
|
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Design screenshot-based localization interface in [https://pontoon.mozilla.org/ Pontoon]
| We'd like to explore the feasibility of screenshot-based localization process in [https://pontoon.mozilla.org/ Pontoon] - Mozilla's translation tool. To provide more translation context, each string will be accompanied by a screenshot showing how the string is used in the application. Additionally, localizers will have the ability to navigate and filter strings by screenshots, as well as preview their translations in the localized screenshots.
| Web standards and Design. Django is a plus.
| [[User:Mathjazz|:mathjazz]]
| [[User:Mathjazz|:mathjazz]]
|
|}

== Build system ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Assurance ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|
TLS 1.3 scanning in Mozilla TLS Observatory
|
[https://github.com/mozilla/tls-observatory Mozilla TLS Observatory] is a hosted service that provides hindsight and compliance checking on the configuration of HTTPS servers. The goal of this project is to improve the service to support scanning TLS 1.3 enabled endpoints, either by improving the [https://github.com/mozilla/cipherscan existing scanner] or writing an entirely new scanner.
|
Programming skills in C, Bash and Go. Strong understanding of TLS and micro-services architectures.
|
Julien Vehent
|
Julien Vehent
|
None
|}

== WADI ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| science.mozilla.org phase 2
| Start phase 2 of the Mozilla Science Lab website by implementing
* [https://github.com/mozilla/science.mozilla.org/issues/135 github authentication],
* [https://github.com/mozilla/science.mozilla.org/issues/311 members homepage],
* [https://github.com/mozilla/science.mozilla.org/issues/536 improve blog post readability], and add the
* [https://github.com/mozilla/science.mozilla.org/issues/518 ability to join projects]
| js, html, css, react, django, python
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| Detailed list and breakdown of all phase 2 work (only the tasks mentioned in details are expected to be completed by the student):
* Phase 2.1 https://github.com/mozilla/science.mozilla.org/milestone/11
* Phase 2.2 https://github.com/mozilla/science.mozilla.org/milestone/12
|-
| Paper Badger - badgr migration & publisher integration
| * Issuing badges to credit authors for their work on academic papers.
* In the final steps of our badgekit to Badgr migration, add tests to make sure we have feature parity and make the switch to Badgr in production.
* Implement a [https://github.com/mozillascience/PaperBadger/issues/160 journal submission system integration] with paper badger. This way, journals won't have to manually enter new badges in our system.
| js, Badgr, APIs, authentication, node.js, react
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| [https://mozillians.org/en-US/u/Abby/ abbycabs]
| github: https://github.com/mozillascience/paperbadger
|-
| Study Group participation visualization
| [https://github.com/mozillascience/studyGroup study groups] meet all over the world, running regular events share skills, co-work and create community around open science. Right now there's no easy way to see all the study group events.
* Write a script to collect data for all study group events happening world wide. Each study group is a [https://github.com/mozillascience/studyGroup fork of this template repo]. Each event is an issue in the repo ([https://github.com/UofTCoders/Events/issues example of events as issues]). [https://github.com/mozillascience/studyGroup/blob/gh-pages/scripts/updateCalendar.py here is a script] that collects all events for a specific repo. Please update this to collect data from all forks.
* Visualize this data in a way that shows study group activity all around the world! viz: calendar, map
| js, html, css, react, django, python
| [https://mozillians.org/en-US/u/zannah/ Zannah]
| [https://mozillians.org/en-US/u/aurelia/ Aurelia]
| main study group repo: https://github.com/mozillascience/studyGroup
|}

== MozVR ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Reporter
! Mentor(s)
! Comments
|-
|}

== Connected Devices ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Reporter
! Mentor(s)
! Comments
|-
|}

== Thimble ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Address stability issues within Thimble
| Main task: Get Thimble to write directly to AWS instead of writing to a database first.
| js, html, css
| [https://mozillians.org/en-US/u/gideon/ gideon]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| Full list of issues affecting thimble's stability: https://github.com/mozilla/thimble.mozilla.org/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3A%22good%20first%20bug%22%20-label%3A%22assigned%20to%20contributor%22
|-
| Integrating VR capabilities into Thimble
| Goal: Thimble makes it easy to create multi user VR experiences, allowing the whole classroom to take virtual field trips through student projects.
This is made possible by doing any of these:
* Integration of the A-frame visual inspector, which gives the user lots of control over an object properties in a custom UI
* Custom Quick-Edit UI for different types of objects
* Develop large, visual menu of 3D objects make it easy to build interesting scenes quickly
* A wide range of starter projects
| js, html, css
| [https://mozillians.org/en-US/u/gideon/ gideon]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| This work would be done in parallel with work done by [https://cdot.senecacollege.ca/ CDOT] on making Thimble a VR experience building tool
thimble repo: https://github.com/mozilla/thimble.mozilla.org
|-
| Thimble and Remote Mentorship
| Goal: Use together.js to enable a multi-user environment on Thimble that is tailored to work as a virtual teaching environment for HTML/CSS/JS
Details:
* Fixing issues in together.js to make it functional
* working on ways to sync state between Thimble's editor and the remote Thimble editor(s
* Syncing filesystems across Thimble editors with WebRTC
| js, html, css
| [https://mozillians.org/en-US/u/gideon/ gideon]
| [https://mozillians.org/en-US/u/gideon/ gideon]
| thimble repo: https://github.com/mozilla/thimble.mozilla.org
|}

GitHub

2016-08-11T20:35:02Z

Abby: add mozilla science lab github org

This page is specifically about [https://github.com/mozilla the "mozilla" organization on github]. There are several other github organizations you may be interested in, cf. the incomplete list [[#other_github|below]].
<div id="contact">
{| class="wikitable"
|-
! [[File:Red_question_mark.png|144px|Send us an email!|link=]] Got a question?
|-
| Email {{emailentry|github-owners|mozilla.org|at=is}} 
Bugzilla [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& mozilla.org :: Github: Administration] 
irc #github on [[IRC|moznet]]
|}

== News ==
* As of June 20, 2016, all members [https://groups.google.com/forum/#!topic/mozilla.dev.platform/UmHOOh3qtiM must have 2FA enabled]. You have been notified if this impacts you.

== Recommendations and FAQ ==

=== Where should I ask additional questions? ===
* Send an email to '''{{emailentry|github-owners|mozilla.org|at=is}}''' and we'll respond right away! We're also available on #github on irc.

=== How do I hook up a new 3rd party application to a repository in the mozilla org? ===
3rd party applications can easily impact many other repositories than the initial one. For that reason, the following steps are strongly encouraged:
# Create yourself a new github user for this repository.
# Make them an admin of the repository(s) temporarily.
# Sign in as the new github user and setup the 3rd party application.
# Log back into your normal account.
# Try to reduce access of that user from an admin of the repository(s) to read only access.
# If (5) doesn't work, at least the 3rd party application will not have access to all of your normal github account's (including private repositories).

* Authorizing an application to work with GitHub utilizes the permissions your account has -- so, any repositories you have access to the application will have access to as well (including private ones). If you want to grant access to an application that no one else has used with the Mozilla organization yet you'll see a "Request access" button during the set up flow. You'll need to click that button to request approval. See below for an example:

[[File:github_approval.png]]

* In some cases, the application does not need to be "approved" to function correctly, as it has read only access to any public repository. (Some applications only want write access to help you configure the application first time.)

* In other cases, the application does need write permission, and/or permission to read a private repository. In these cases, it is helpful to send the details to the owner's team, either by [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& opening a bug] or [[#contact|email]].

=== Reviewing owners and permissions ===
As an owner or repository admin you're responsible for maintaining the list of people with access to your projects. Please be active and prudent about maintaining this list.

=== Can I be an Owner of the Mozilla Organization? ===
The Owners group on github has complete administrative power and will be limited to a minimal number of people and reviewed regularly. If a person is an owner they are expected to actively participate in the group and assist others as requested. Owners will be added as a need arises (for example, support in another timezone) as determined by the current owners.

All owners '''must''' have 2FA enabled for their GitHub login. (Everyone else ''should''.)

=== Can I be a Member of the Mozilla Organization? ===
With recent github enhancements (2015), we encourage the following (rough) guidelines, which strongly prefers using github teams. As a reminder, all members of the [https://github.com/mozilla/ Mozilla organization on github] agree to be bound by [https://www.mozilla.org/en-US/about/governance/policies/commit/requirements/ Mozilla's Commit Access Requirements], and should follow the intent of the [https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/ Mozilla's Commit Access Policy] as much as practical.
* "Outside Collaborator": repository admins can grant outside collaborator to any github account. "Outside Collaborator" is roughly analogous to "Level 1a" access to Mozilla hosted repositories.
* "Team Member": team maintainers can add github users to a team, if they are already a member of the organization. If you are not yet a member of the organization, the team maintainer should [[#contact|request your addition]] to their team, as a form of vouching. "Team Member" is roughly analogous to "Level 2" or "Level 3", with the distinction being the content of the repositories managed by the team.

{{note| As of June 30, 2016, all members of the Mozilla organization on github '''MUST''' have [https://help.github.com/articles/about-two-factor-authentication/ 2FA enabled].|reminder}}

{{note| Automation accounts are also required to have 2FA enabled. Scripts should use [https://help.github.com/articles/creating-an-access-token-for-command-line-use/ access tokens] with minimum permissions to accomplish the task.}}

Some people are interested in being members of the Mozilla organization on github as a way to highlight their contributions to the Mozilla Project. Thanks for your help! And there is a [https://www.mozilla.org/credits/ better place] to highlight your work. Please refer to the [https://www.mozilla.org/credits/FAQ FAQ] for that process.

=== Should I make a separate github organization or just create a repository in an existing one? ===
This is a personal preference. If you have a large enough project or organization feel free. We suggest you use the strategies and recommendations here as a model to manage the details.

=== Forking vs Transferring ===
'''Do not "fork" a repository into a Mozilla organization.''' Doing so gives ''every team in the org'' rights to it.

If you have created a repo on your own account (for example, myuser/myrepo) and it should live under the Mozilla organization, here are the steps:

{{note|As soon as you transfer, your repository will be in "limbo" (only you will have write access) until you get the assistance of an [[#contact|org admin]] who can make the changes. Please plan in advance if timing is critical.}}

# If you're not a member of any team, talk to an [[#contact|org admin]].
# Under the repo admin, transfer ownership to the Mozilla organization. If you don't see this option, return to step 1.
# Choose which teams should be given access. All chosen teams will have only 'read' access at this point.
# Ask an [[#contact|org admin]] to grant team permissions higher than read ('write' and 'admin' are the other choices). (Team maintainers do not have the ability to change a repositories status.)
# Fork the repo from Mozilla (mozilla/myrepo) back to your account (recreating myuser/myrepo). While the transferred repo becomes the root of the network on Github (e.g. all forks are now forks of mozilla/myrepo) other users may be pointing to your repo by URL. (Optional, github will redirect old URLs for transfers, but you probably want a local repo if you use the PR workflow.)

=== Do I need to be an owner to create repositories? ===
No. If a person has read/write access to another repository in that organization they can make more repositories in that organization. However, it's preferred that you create repositories in the context of a team.

=== Are there requirements for when or how I should create a new team? ===
No. When requirements were proposed they all seemed too rigid and time consuming. Instead we recommend staying flexible and using good naming and documentation for projects (similar to naming CSS classes or variables).

On large teams we recommend you separate teams for read/write and repository administration.

<div id="other_github"></div>
=== Is "mozilla" the only github "organization" related to Mozilla? ===
No, there are plenty of Mozilla-related "organizations" on github. As a rule of thumb, initiatives that create a large number of sub-repositories will create their own "organization". Here is a (probably incomplete) list of them:
{| class="wikitable sortable"
|-
! Organization !! Description !! Contact Owner
|-
| [https://github.com/mozilla-it mozilla-it] || Mozilla IT's repositories || ?
|-
| [https://github.com/bugzilla bugzilla] || Bugzilla (the product) || #bteam
|-
| [https://github.com/drumbeat-badge-sprint drumbeat-badge-sprint] || Drumbeat Badge Lab || ?
|-
| [https://github.com/hackasaurus hackasaurus] || Hackasaurus || ?
|-
| [https://github.com/jetpack-labs jetpack-labs] || Jetpack Labs || ?
|-
| [https://github.com/mdn mdn] || Mozilla Developer Network || {{Mozillian|groovecoder|Luke Crouch}}
|-
| [https://github.com/mozbrick mozbrick] || Mozilla Brick (web components library) || ?
|-
| [https://github.com/mozilla-appmaker mozilla-appmaker] || Mozilla Appmaker || ?
|-
| [https://github.com/mozilla-b2g mozilla-b2g] || Mozilla Boot2Gecko / Firefox OS || ?
|-
| [https://github.com/mozilla-cit mozilla-cit] || Mozilla Community Ops || {{Mozillians|tanner|Tanner Filip}} or {{Mozillians|yalam96|Yousef Alam}}
|-
| [https://github.com/mozilla-comm mozilla-comm] || Calendaring and Messaging related projects || ?
|-
| [https://github.com/mozilla-cordova mozilla-cordova] || Firefox OS Support for Apache Cordova || ?
|-
| [https://github.com/mozilla-metrics mozilla-metrics] || Mozilla Metrics || ?
|-
| [https://github.com/mozilla-raptor mozilla-raptor] || Mozilla Raptor / Firefox OS Performance || {{Mozillian|eliperelman|Eli Perelman}}, {{Mozillian|rwood|Rob Wood}}
|-
| [https://github.com/mozilla-releng mozilla-releng] || Mozilla Release Engineering || #releng
|-
| [https://github.com/mozilla-services mozilla-services] || Mozilla Services || [https://github.com/orgs/mozilla-services/people?utf8=%E2%9C%93&query=role%3Aowner mozilla-services owners]
|-
| [https://github.com/mozilla-svcops mozilla-svcops] || Mozilla Cloud Services Ops || {{Mozillian|relud|Daniel Thornton}}
|-
| [https://github.com/MozillaTW MozillaTW] || Mozilla Taiwan || ?
|-
| [https://github.com/Mozilla-TWQA Mozilla-TWQA] || Mozilla Taiwan QA || ?
|-
| [https://github.com/mozillahispano mozillahispano] || Mozilla Hispano || ?
|-
| [https://github.com/MozillaScience MozillaScience] || Mozilla Science Lab || ?
|-
| [https://github.com/MozillaSecurity MozillaSecurity] || Mozilla Platform Fuzzing Team master repo with many fuzzing tools under it. || ?
|-
| [https://github.com/MozillaWiki MozillaWiki] || MozillaWiki (wiki.mozilla.org) || {{Mozillian|ckoehler|Christie Koehler}}, {{Mozillian|gphemsley|Gordon P. Hemsley}}
|-
| [https://github.com/mozillayvr mozillayvr] || Mozilla Vancouver @MozillaYVR || {{Mozillian|bclark|Brian Clark}}, {{Mozillian|shobson|Stephanie Hobson}}
|-
| [https://github.com/mozfr mozfr] || Mozilla Francophone || Pascal Chevrel https://mozillians.org/fr/u/pascalc/
|-
| [https://github.com/opennews opennews] || Knight-Mozilla OpenNews || ?
|-
| [https://github.com/rust-lang rust-lang] || The Rust Programming Language || {{Mozillian|aturon|Aaron Turon}}
|-
| [https://github.com/servo servo] || Servo (browser engine written in Rust) || {{Mozillian|larsberg|Lars Bergstrom}}, Jack Moffitt
|-
| [https://github.com/tabulapdf tabulapdf] || Tabula project (extract data from PDF files) || ?
|-
| [https://github.com/webcompat webcompat] || Web Compatibility Team || {{Mozillian|miketaylr|Mike Taylor}}
|-
| [https://github.com/mozilla-l10n mozilla-l10n] || Mozilla l10n-drivers team || Pascal Chevrel https://mozillians.org/fr/u/pascalc/
|-
| [https://github.com/taskcluster taskcluster] || [[TaskCluster]] Team || {{Mozillian|sdeckelmann|Selena Deckelmann}}
|-
| [https://github.com/MozillaCH MozillaCH] || Mozilla [[Switzerland]] || {{Mozillian|mkohler|Michael Kohler}}, {{Mozillian|freaktechnik|freaktechnik}}
|}

=== Are there other unofficial or Mozilla-related repositories hosted on Github? ===
Why, yes! In no particular order:

* [https://github.com/kinetiknz/nestegg/ https://github.com/kinetiknz/nestegg/] : WebM demuxer
* [https://github.com/xiph/opus/ https://github.com/xiph/opus/] : Modern audio compression for the internet.
* [https://github.com/webmproject/libvpx https://github.com/webmproject/libvpx] : Mirror only. Please do not send pull requests.
* [https://github.com/campd/fxdt-adapters https://github.com/campd/fxdt-adapters] : Firefox Developer Tools protocol adapters
* [https://github.com/kripken/emscripten https://github.com/kripken/emscripten] : Emscripten: An LLVM-to-JavaScript Compiler
* [https://github.com/bbondy/codefirefox https://github.com/bbondy/codefirefox] : Video and exercise based tutorial site for coding Firefox and other Mozilla related technology
* [https://github.com/nickdesaulniers/where-is-firefox-os https://github.com/nickdesaulniers/where-is-firefox-os] : A map showing where in the world Firefox OS phones are being sold.
* [https://github.com/jdm/bugsahoy https://github.com/jdm/bugsahoy] : A landing page to make finding relevant bugs easier for new Mozilla contributors.
* [https://github.com/w3c/web-platform-tests https://github.com/w3c/web-platform-tests] : Test Suites for Web Platform specifications
* [https://github.com/w3c/wptserve https://github.com/w3c/wptserve] : Web server designed for use with web-platform-tests
* [https://github.com/w3c/wptrunner https://github.com/w3c/wptrunner] : Cross-browser and multi-platform test runner for web-platform-tests. Used in mozilla-central and servo.
* [https://github.com/w3c/testharness.js https://github.com/w3c/testharness.js] : (no description)
* [https://github.com/jdm/asknot https://github.com/jdm/asknot] : Ask not what Mozilla can do for you but what you can do for Mozilla.
* [https://github.com/jeffbryner/MozDef https://github.com/jeffbryner/MozDef]: Mozilla Defense Platform.
* [https://github.com/jgraham/webdriver-rust https://github.com/jgraham/webdriver-rust]: WebDriver library for Rust.

ScienceLab/Calls

2016-04-14T20:01:23Z

Abby: add project call

__NOTOC__
=== Science Lab Community Calls ===
Second Thursday of every month

'''Our next call:'''
<ul>
<li>April 14, 2016 8 am PT / 11 am ET / 4 pm GMT - [https://mozillascience.org/community-call-apr-14-11-et Etherpad] </li>
</ul>

11 AM ET Calls (2nd Thursday of the month):

Conference Number: +1 800 707 2533,
Password: 369
Room: 7677

If you have trouble accessing the above number, try one of the following numbers (note these are not toll-free numbers and regular billing rates will apply). Enter the conference ID, 7677, after you enter the extension:

<ul>
<li>US/California/Mountain View: +1 650 903 0800, extension 92
<li>US/California/San Francisco: +1 415 762 5700, extension 92
<li>US/Oregon/Portland: +1 971 544 8000, extension 92
<li>CA/Vancouver: +1 778 785 1540, extension 92
<li>CA/Toronto: +1 416 848 3114, extension 92
<li>UK/London: +44 (0)207 855 3000, extension 92
<li>FR/Paris: +33 1 84 88 37 37, extension 92
<li>DE/Berlin: +49 30 983 333 000, extension 92</li>
<li>NZ/Auckland: +64 9 555 1100, extenstion 92</li>
</ul>

 Calendar ICS File : https://www.google.com/calendar/ical/mozilla.com_2fucb8cru2pl84i43grso9mj6s%40group.calendar.google.com/public/basic.ics
 Subscribe to Calender : https://www.google.com/calendar/embed?src=mozilla.com_2fucb8cru2pl84i43grso9mj6s%40group.calendar.google.com&ctz=America/Toronto



=== What is the Science Lab Community Call? ===

The Science Lab meeting is our community call, taking place the second Thursday of every month, highlighting what we're up to as well as work of the community relevant to science and the web. Join us to hear more about current projects, ways you can get involved, and discuss issues around open science. The calls are made stronger by your participation, so do join us.

Join us on the second Thursday of every month // 11 am Eastern .

Hear more about what we're up to, ask questions, and interact with other call participants. Join us.

=== Science Lab Project Calls ===
Fourth Thursday of each month, 12pm ET

Featuring the open source projects for science in our Collaborate platform, this call is a forum where we:

* highlight new or outstanding contributors,
* learn and discuss best practices in open source and
* share updates and invite new contributors to our Collaborate projects.

Everyone is welcome to join in! Designers, developers, researchers, publishers — pretty much anyone interested in participating and learning how to get involved in an open science project. We could use all sorts of input (beyond just code), so if you’re new to open source, come join us! We’d love to have you involved.

===Call archives===
2nd Thursdays (11 AM ET)

* [https://etherpad.mozilla.org/sciencelab-calls-nov14 November 14, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-dec12 December 12, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-jan9-2014 January 9, 2014]
* [http://etherpad.mozilla.org/sciencelab-calls-feb13-2014 February 13, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-mar20-2014 March 20, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-apr10-2014 April 10, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-may08-2014 May 8, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-june12-2014 June 12, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-july10-2014 July 10, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-aug14-2014 August 14, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-sep11-2014 September 11, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-oct9-2014 October 9, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-nov13-2014 November 13, 2014]
* NO DECEMBER 2014 CALL
* [https://etherpad.mozilla.org/sciencelab-calls-jan15-2015 January 15, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-feb12-2015 February 12, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-mar12-2015 March 12, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-apr09-2015 April 9, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-may14-2015 May 14, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-june11-2015 June 11, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-july09-2015 July 9, 2015]
* [https://etherpad-mozilla.org/sciencelab-calls-aug13-2015 August 13, 2015]
* [https://etherpad-mozilla.org/sciencelab-calls-sep10-2015 September 10, 2015]
* [https://public.etherpad-mozilla.org/p/T007eAyPQG October 8,2015]
* [https://public.etherpad-mozilla.org/p/sciencelab-calls-nov19-2015 November 19, 2015]
* NO DECEMBER 2015 CALL
* [https://public.etherpad-mozilla.org/p/sciencelab-calls-jan14-2016 January 14, 2016]
* [https://public.etherpad-mozilla.org/p/sciencelab-calls-feb11-2016 February 11, 2016]
* [https://public.etherpad-mozilla.org/p/sciencelab-calls-mar10-2016 March 10, 2016]

Australasia Calls:
* [https://etherpad.mozilla.org/sciencelab-calls-may28-2015 May 28, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-june25-2015 June 25, 2015]

Community:SummerOfCode16:Brainstorming

2016-03-01T15:25:44Z

Abby: Update Mozilla Science's idea with more details

Mozilla community members - submit proposals here for 2016 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode16|official list]].) '''The''' absolute last '''deadline for submitting ideas''' in time to help us get accepted by Google '''is February 19th'''.

Are you a student looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode16|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - 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 can, 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.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''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.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''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.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Support OpenGL graphics acceleration on Linux
| [https://bugzilla.mozilla.org/show_bug.cgi?id=594876 bug 594876]
| C/C++
| marco
|
|
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|-
| File Watcher
| This is the bug topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=958280 :: Bugzilla 958280]]. Using pipes, create a XPCOM component for Mac file watching (Window and GTK are done) or and complete the js-ctypes version. For XPCOM: Windows topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992894 :: Bugzilla 992894]], this is the GTK topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992895 :: Bugzilla 992895]], this is the Mac topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992896 :: Bugzilla 992896]]. This is the preliminary js-ctypes file watcher, but it uses timeout instead of pipes to interrupt/cancel a watch: https://github.com/Noitidart/jscFileWatcher.
| C/C++/Javascript
| [[https://mozillians.org/en-US/u/Noitidart/ :: Noit]]
| Noit
|
|-
| Modernize Library (Bookmarks, History, Downloads) UI and move its window to a tab
| [https://bugzilla.mozilla.org/show_bug.cgi?id=697359 bug 697359]
| Javascript
| marco
|
|
|-
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox OS / Boot2Gecko ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Group MMS proper support
| See the [https://bugzilla.mozilla.org/show_bug.cgi?id=1106663 meta bug 1106663]
| CSS, JavaScript
|
| Julien Wajsberg
| For this feature, the mentoree will need to change mostly Gaia code, but also likely fix some Gecko code. All the code is in JavaScript. The mentoree will need a Firefox OS device (we can likely supply one though).
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Update to mozmill 2.0
| We are currently using an older version of [https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Mozmill Mozmill], a framework for automated UI tests similar to Selenium. In order to stay future proof we need to update to the latest version, which requires some API changes. You will get hands on experience in creating automated tests and your debugging skills will certainly imprve. See [https://bugzilla.mozilla.org/show_bug.cgi?id=930732 bug 930732] for additional details.
| JS and python coding, debug mozmill tests
| aceman
|
|
|-
| Finish remaining maildir features
| [https://bugzilla.mozilla.org/show_bug.cgi?id=845952 bug 845952]
| C++ coding, JS coding, some tests
| aceman
|
|
|-
| Add UI for creating boolean filter expressions in filter editor
| [https://bugzilla.mozilla.org/show_bug.cgi?id=297852 bug 297852]
| JS+XUL coding, some tests, maybe a bit of C++ coding
| aceman
|
| Supposedly this mostly needs creating the UI. The backend should be ready for such expressions. But it needs checking if it still works as it wasn't exercised so far.
|-
| Integrate pdf.js support
| [https://bugzilla.mozilla.org/show_bug.cgi?id=810815 bug 810815]
| JavaScript
| marco
|
|
|-
| Tabbed Composition
| [https://bugzilla.mozilla.org/show_bug.cgi?id=449299 bug 449299]
| JavaScript
| marco
|
|
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Redesign libpurple integration
| Change libpurple from being an XPCOM component to a separate (sub-)process that uses IPC to communicate to it
| C++, XPCOM, JavaScript
| Patrick Cloke
|
|
|-
| OTR (Off-the-Record) Integration
| [https://trac.torproject.org/projects/tor/wiki/doc/TorMessenger Tor Messenger], which is based on Instantbird, has support for end-to-end encrypted instant messaging using OTR ([https://github.com/arlolra/ctypes-otr via an extension]). The goal of this project would be to upstream these changes from Tor Messenger into Instantbird while incorporating UI changes designed by the Instantbird team.
| c-types, XPCOM, JavaScript, XUL
| arlolra
| Patrick Cloke [:clokep]
|
|-
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

==NSS (Network Security Services)==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== OpenArt ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Port LibreOffice to the Web
| https://wiki.documentfoundation.org/Development/Emscripten
| C/C++/JavaScript
| marco
|
|
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Build system ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Assurance ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| ZAP Bug tracker support
| https://github.com/zaproxy/zaproxy/issues/440
| Java
| Simon Bennetts
| Simon Bennetts
|
|-
| ZAP Auto login detection and configuration
| https://github.com/zaproxy/zaproxy/issues/2251
| Java
| Simon Bennetts
| Simon Bennetts
|
|-
| Zest text representation and parser
| https://github.com/mozilla/zest/issues/23
| Java
| Simon Bennetts
| Simon Bennetts
|
|-
|}

== WADI ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Add Service Workers to forum
| https://github.com/mozilla/wadi/issues/54
| HTML5, JavaScript
| Salvador de la Puente
|
|
|-
| Make Hatnote progressive
| https://github.com/mozilla/wadi/issues/51
| HTML5, JavaScript
| Salvador de la Puente
|
|
|-
| Best of Planet stream
| https://github.com/mozilla/wadi/issues/44
| HTML5, JavaScript, some server side technology
| Salvador de la Puente
|
|
|-
| Create a (broccoli/ember)-oghliner addon
| https://github.com/mozilla/wadi/issues/43
| HTML5, JavaScript
| Salvador de la Puente
| Salva
|
|-
| Add SW functionalities to Phaser (or other HTML5 game engine)
| https://github.com/mozilla/wadi/issues/32
| HTML5, JavaScript
| Salvador de la Puente
| Salva
|
|-
| Use a service worker with Firefox Accounts
| https://github.com/mozilla/wadi/issues/30
| HTML5, JavaScript
| Salvador de la Puente
|
|
|-
| Implement Service Workers on the MDN
| https://github.com/mozilla/wadi/issues/21
| HTML5, JavaScript
| Salvador de la Puente
| David Walsh
|
|-
| App for watching air.mozilla video podcasts
| https://github.com/mozilla/wadi/issues/11
| HTML5, JavaScript
| Salvador de la Puente
|
|
|-
| Add offlining to Shower
| https://github.com/mozilla/wadi/issues/3
| HTML5, JavaScript
| Salvador de la Puente
|
|
|}

== Webmaker ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| [https://github.com/mozillascience/paperbadger Contributorship Badges for Science].
| Issuing badges to credit authors for their work on academic papers. As the research environment becomes more digital, we want to test how we can use this medium to help bring transparency and credit for individuals in the publication process.

Using Mozilla's Badgekit-api to implement our badges, we can issue and fetch badges from badgekit via the badgkit-api-client. By authenticating against ORCID, a user can reliably issue badges to a valid ORCID, the standard unique researcher identifier.

Since launching our MVP last fall, we've realized that badgekit-api isn't optimized for our use case. In this project, you will migrate our badge system away from badgekit-api and update the system to make it easier for publishers to integrate Paper Badger in their submission system.

More details:
https://github.com/mozillascience/PaperBadger/issues/159
https://github.com/mozillascience/PaperBadger/issues/160

| Strong JavaScript programming skills. Familiar with node.
| Abigail Cabunoc Mayes
| [https://mozillians.org/en-US/u/Abby/ Abigail Cabunoc Mayes :abbycabs]
| The [https://mozillascience.org/ Mozilla Science Lab], an initiative of the Mozilla Foundation, works to make research collaborative, accessible and usable.
|}

== MozVR ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Reporter
! Mentor(s)
! Comments
|-
|}

Community:SummerOfCode16:Brainstorming

2016-01-27T00:45:36Z

Abby: add mozilla science lab idea proposal

Mozilla community members - submit proposals here for 2016 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode16|official list]].) '''The''' absolute last '''deadline for submitting ideas''' in time to help us get accepted by Google '''is February 19th'''.

Are you a students looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode16|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - 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 can, 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.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''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.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''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.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|-
| File Watcher
| This is the bug topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=958280 :: Bugzilla 958280]]. Using pipes, create a XPCOM component for Mac file watching (Window and GTK are done) or and complete the js-ctypes version. For XPCOM: Windows topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992894 :: Bugzilla 992894]], this is the GTK topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992895 :: Bugzilla 992895]], this is the Mac topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992896 :: Bugzilla 992896]]. This is the preliminary js-ctypes file watcher, but it uses timeout instead of pipes to interrupt/cancel a watch - [[https://github.com/Noitidart/jscFileWatcher|GitHub :: Github jscFileWatcher]].
| C/C++/Javascript
| [[https://mozillians.org/en-US/u/Noitidart/ :: Noit]]
| Noit
|
|-
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox OS / Boot2Gecko ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Group MMS proper support
| See the [https://bugzilla.mozilla.org/show_bug.cgi?id=1106663 meta bug 1106663]
| CSS, JavaScript
|
| Julien Wajsberg
| For this feature, the mentoree will need to change mostly Gaia code, but also likely fix some Gecko code. All the code is in JavaScript. The mentoree will need a Firefox OS device (we can likely supply one though).
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

==NSS (Network Security Services)==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Web-based GDB Frontend
| Write a graphical frontend for gdb/rr in react.js communicating with backend (gdb/rr) over a websocket.
| Javascript, react.js, CSS/HTML (gdb/c++ is nice to have)
| [https://mozillians.org/en-US/u/jonasfj/ jonasfj]
| [https://mozillians.org/en-US/u/jonasfj/ jonasfj]
| I'll happily add the backend to TaskCluster workers, so we can debug processes in CI tasks from a browser.
|-
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== OpenArt ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Build system ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Assurance ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Mozilla Investigator: Auditd integration
| Implement support for syscall monitoring on Linux system via the Audit daemon. This should include integration with the [https://github.com/mozilla/audit-go audit-go] library, as well as reporting and escalation. A key component of the project is to correlate anomalies across nodes, to identify unusual systems registered by isolated systems but not by the rest of the infrastructure.
| Strong Go and C programming skills. Good knowledge of Operating Systems architecture and the Linux kernel.
| Julien Vehent
| [https://mozillians.org/en-US/u/jvehent/ Julien Vehent :ulfr] & [https://mozillians.org/en-US/u/kang/ Guillaume Destuynder :kang]
| MIG (github.com/mozilla/mig) is a distributed digital forensics framework deployed across thousands of systems at Mozilla. It is used by various groups to maintain good security levels across the environments, and investigate incidents and vulnerabilities.
|}

== Webmaker ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Contributorship Badges for Science.
| Exploring the use of digital badges for crediting contributors to scholarly papers for their work. As the research environment becomes more digital, we want to test how we can use this medium to help bring transparency and credit for individuals in the publication process.

Using Mozilla's Badgekit-api to implement our badges, we can issue and fetch badges from badgekit via the badgkit-api-client. By authenticating against ORCID, a user can reliably issue badges to a valid ORCID, the standard unique researcher identifier.

In this project, you will integrate with the publishers paper submission system to generate the badges.
| Strong JavaScript programming skills. Familiar with node.
| Abigail Cabunoc Mayes
| [https://mozillians.org/en-US/u/Abby/ Abigail Cabunoc Mayes :abbycabs]
|
|}

ScienceLab/Calls

2015-07-10T20:32:29Z

Abby: /* Science Lab Community Calls */ update call link

__NOTOC__
=== Science Lab Community Calls ===
Second Thursday of every month

'''Our next calls:'''
<ul>
<li>July 9, 2015 8 am PT / 11 am ET / 4 pm BST [https://etherpad.mozilla.org/sciencelab-calls-july09-2015 etherpad]</li>
</ul>

11 AM ET Calls (2nd Thursday of the month):

Conference Number: +1 800 707 2533,
Password: 369
Room: 7677

If you have trouble accessing the above number, try one of the following numbers (note these are not toll-free numbers and regular billing rates will apply). Enter the conference ID, 7677, after you enter the extension:

<ul>
<li>US/California/Mountain View: +1 650 903 0800, extension 92
<li>US/California/San Francisco: +1 415 762 5700, extension 92
<li>US/Oregon/Portland: +1 971 544 8000, extension 92
<li>CA/Vancouver: +1 778 785 1540, extension 92
<li>CA/Toronto: +1 416 848 3114, extension 92
<li>UK/London: +44 (0)207 855 3000, extension 92
<li>FR/Paris: +33 1 84 88 37 37, extension 92
<li>DE/Berlin: +49 30 983 333 000, extension 92</li>
<li>NZ/Auckland: +64 9 555 1100, extenstion 92</li>
</ul>

 Calendar ICS File : https://www.google.com/calendar/ical/mozilla.com_2fucb8cru2pl84i43grso9mj6s%40group.calendar.google.com/public/basic.ics
 Subscribe to Calender : https://www.google.com/calendar/embed?src=mozilla.com_2fucb8cru2pl84i43grso9mj6s%40group.calendar.google.com&ctz=America/Toronto



=== What is the Science Lab Meeting? ===

The Science Lab meeting is our community call, taking place the second Thursday of every month, highlighting what we're up to as well as work of the community relevant to science and the web. Join us to hear more about current projects, ways you can get involved, and discuss issues around open science. The calls are made stronger by your participation, so do join us.

Join us on the second Thursday of every month // 11 am Eastern .

Hear more about what we're up to, ask questions, and interact with other call participants. Join us.

===Call archives===
2nd Thursdays (11 AM ET)

* [https://etherpad.mozilla.org/sciencelab-calls-nov14 November 14, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-dec12 December 12, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-jan9-2014 January 9, 2014]
* [http://etherpad.mozilla.org/sciencelab-calls-feb13-2014 February 13, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-mar20-2014 March 20, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-apr10-2014 April 10, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-may08-2014 May 8, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-june12-2014 June 12, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-july10-2014 July 10, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-aug14-2014 August 14, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-sep11-2014 September 11, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-oct9-2014 October 9, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-nov13-2014 November 13, 2014]
* NO DECEMBER 2014 CALL
* [https://etherpad.mozilla.org/sciencelab-calls-jan15-2015 January 15, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-feb12-2015 February 12, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-mar12-2015 March 12, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-apr09-2015 April 9, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-may14-2015 May 14, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-june11-2015 June 11, 2015]

4th Thursdays (10 AM AEST)

* [https://etherpad.mozilla.org/sciencelab-calls-may28-2015 May 28, 2015]
* [https://etherpad.mozilla.org/sciencelab-calls-june25-2015 June 25, 2015]

Community:SummerOfCode15:Brainstorming

2015-02-26T21:14:23Z

Abby: /* Mozilla Science Lab */ note for clokep

Mozilla community members - submit proposals here for 2015 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode15|official list]].) '''The''' absolute last '''deadline for submitting ideas''' in time to help us get accepted by Google '''is February 20th'''.

Are you a students looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode15|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - 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 can, 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.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''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.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''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.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Firefox Performance Dashboard
| This project would implement the dashboard described in [https://bugzilla.mozilla.org/show_bug.cgi?id=1132498 bug 1132498]. Collecting the memory and CPU usage of addons and webpages and displaying it in a fashion that shows bad actors would be valuable for power users.
| HTML, CSS, JavaScript
| [https://mozillians.org/en-US/u/jdm/ jdm]
|
|
|-
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox OS / Boot2Gecko ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Contact Blacklist
| {{bug|1133501}} Implement a blacklist to prevent specified contacts from calling or messaging the user.
| HTML, CSS, JS
| [mailto:yvtheja@gmail.com Vishnu Teja (:ythej)]
| [mailto:dsherk@mozilla.com Doug Sherk (:drs)]
| Already assigned to [mailto:yvtheja@gmail.com Vishnu Teja (:ythej)]
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Performance testing
| Add and deploy a performance testsuite for Thunderbird to catch regressions in areas such as startup, message search, folder display, message display, etc.
| JavaScript, Python, preferably some performance analysis experience
| jcranmer
| ?
| Needs a mentor -- florian
|-
| Secure email UI
| Develop good interfaces for key management and illustrating the security levels of messages succinctly, preferably applicable to both S/MIME and OpenPGP.
| Strong UX experience; JS, XUL or HTML; crypto background advantageous
| jcranmer
| ?
| Summer of Code is about coding, not about UX work; asking students to do UX work often leads to disappointing results -- florian. This may be too large a task; narrowing focus could be useful.
|-
| Integrated pdf.js support in thunderbird (bug 810815)
| Firefox ships with integrade PDF viewing capabilities using pdf.js. This functionality is not present in Thunderbird yet but would obviously be useful.
| JavaScript
| mkmelin
| ?
| Unclear about how much work it is.
|-
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Infinite scroll
| Add additional messages from the logs on-demand as the user scrolls up/down. Old messages should be removed when no longer needed, while not breaking any existing features.
| JavaScript, XUL, CSS
| nhnt11
| nhnt11 + ???
|
|-
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

==NSS (Network Security Services)==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|Treeherder for mobile
|Threeherder is a tool that allows to monitor test and build results generated by the gecko CI system.
The goal of this project is to build a simplified version of Treeherder, targeted to a mobile audience.
The data is already available through a restful API.
The mobile UI should allow to see if a push has failures and eventually drill down to identify which job failed on which platform.
|Good knowledge of JavaScript and CSS. Previous experience with angularjs would be beneficial, but it's not needed.
| mdoglio
| mdoglio
|
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== OpenArt ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Build system ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Assurance ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Webmaker ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| AWS cli tool for deploys/rapid prototyping
| Help build/explore options for a heroku-like cli tool for rapid prototyping and development in the Webmaker ecosystem that interfaces with our AWS infrastructure.
| nodejs
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: There are tools that let you interact with AWS on the command line. I'm unsure if they do exactly what you want and doubt they're written in node (the [https://github.com/aws/aws-cli official one] is written on top of their [https://github.com/boto/boto Python library]).
|-
| Developer experience for Cordova Android/Firefox OS
| Help fix bugs, improve documentation, learning resources, and developer experience for build tools, tests, and deployment of Cordova Firefox OS / Android projects
| javascript, nodejs
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: I'm unsure what this is, it sounds like "Work on Cordova Android/Firefox OS and fix some documentation for 3 months". We like GSoC projects to have a specific goal in mind. Maybe this just needs a bit of rewording though.
|-
| Webmaker.app for iOS
| Develop an iOS version of our Cordova application (currently implemented for Android/Firefox OS)
| javascript, nodejs
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: I have no idea how Webmaker.app works, but does this not need any iOS specific development skills (e.g. ObjectiveC)?
|-
| Prototype in-app payments for Webmaker.app
| Users can create mobile web apps with Webmaker.app, but what if they could accept payments? Explore options like paypal, stripe, etc. and develop a prototype using Cordova/web tech.
| javascript, nodejs, css, html
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: I'm having a bit of trouble understanding the final end goal of this: is it simply to have a prototype that includes, e.g., PayPal? What will that help us do?
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| [http://www.mozillascience.org/projects/contributorship-badges Contributorship Badges] Visualizations
| Create a series of javascript snippets that authors and publishers can use to display authorship badges on their sites. Badges will be issued using PaperBadger -- a service using Open Badges to issue badges to an ORCID and paper DOI. Exploring the use of digital badges for crediting contributors to scholarly papers for their work.
| javascript, PaperBadger API (in development)
| [[User:Abby|Abby]]
| [[User:Abby|Abby]]
| As the research environment becomes more digital, we want to test how we can use this medium to help bring transparency and credit for individuals in the publication process. This work is a collaboration with publishers BioMed Central (BMC) and the Public Library of Science (PLoS); the biomedical research foundation, The Wellcome Trust; the software and technology firm Digital Science; the registry of unique researcher identifiers, ORCID; and the Mozilla Science Lab.

Background Reading: http://mozillascience.org/contributorship-badges-a-new-project/

http://news.sciencemag.org/scientific-community/2014/11/could-digital-badges-clarify-roles-co-authors

http://www.nature.com/news/publishing-credit-where-credit-is-due-1.15033

Note for clokep: I removed dependent projects if that's what's holding this project back in brainstorming?
|}

Community:SummerOfCode15:Brainstorming

2015-02-24T19:36:39Z

Abby: /* Mozilla Science Lab */ Clarify projects some more

Mozilla community members - submit proposals here for 2015 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode15|official list]].) '''The''' absolute last '''deadline for submitting ideas''' in time to help us get accepted by Google '''is February 20th'''.

Are you a students looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode15|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - 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 can, 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.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''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.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''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.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Firefox Performance Dashboard
| This project would implement the dashboard described in [https://bugzilla.mozilla.org/show_bug.cgi?id=1132498 bug 1132498]. Collecting the memory and CPU usage of addons and webpages and displaying it in a fashion that shows bad actors would be valuable for power users.
| HTML, CSS, JavaScript
| [https://mozillians.org/en-US/u/jdm/ jdm]
|
|
|-
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox OS / Boot2Gecko ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Contact Blacklist
| {{bug|1133501}} Implement a blacklist to prevent specified contacts from calling or messaging the user.
| HTML, CSS, JS
| [mailto:yvtheja@gmail.com Vishnu Teja (:ythej)]
| [mailto:dsherk@mozilla.com Doug Sherk (:drs)]
| Already assigned to [mailto:yvtheja@gmail.com Vishnu Teja (:ythej)]
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Performance testing
| Add and deploy a performance testsuite for Thunderbird to catch regressions in areas such as startup, message search, folder display, message display, etc.
| JavaScript, Python, preferably some performance analysis experience
| jcranmer
| ?
| Needs a mentor -- florian
|-
| Secure email UI
| Develop good interfaces for key management and illustrating the security levels of messages succinctly, preferably applicable to both S/MIME and OpenPGP.
| Strong UX experience; JS, XUL or HTML; crypto background advantageous
| jcranmer
| ?
| Summer of Code is about coding, not about UX work; asking students to do UX work often leads to disappointing results -- florian. This may be too large a task; narrowing focus could be useful.
|-
| Integrated pdf.js support in thunderbird (bug 810815)
| Firefox ships with integrade PDF viewing capabilities using pdf.js. This functionality is not present in Thunderbird yet but would obviously be useful.
| JavaScript
| mkmelin
| ?
| Unclear about how much work it is.
|-
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Infinite scroll
| Add additional messages from the logs on-demand as the user scrolls up/down. Old messages should be removed when no longer needed, while not breaking any existing features.
| JavaScript, XUL, CSS
| nhnt11
| nhnt11 + ???
|
|-
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

==NSS (Network Security Services)==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|Treeherder for mobile
|Threeherder is a tool that allows to monitor test and build results generated by the gecko CI system.
The goal of this project is to build a simplified version of Treeherder, targeted to a mobile audience.
The data is already available through a restful API.
The mobile UI should allow to see if a push has failures and eventually drill down to identify which job failed on which platform.
|Good knowledge of JavaScript and CSS. Previous experience with angularjs would be beneficial, but it's not needed.
| mdoglio
| mdoglio
|
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== OpenArt ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Build system ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Assurance ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Webmaker ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| AWS cli tool for deploys/rapid prototyping
| Help build/explore options for a heroku-like cli tool for rapid prototyping and development in the Webmaker ecosystem that interfaces with our AWS infrastructure.
| nodejs
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: There are tools that let you interact with AWS on the command line. I'm unsure if they do exactly what you want and doubt they're written in node (the [https://github.com/aws/aws-cli official one] is written on top of their [https://github.com/boto/boto Python library]).
|-
| Developer experience for Cordova Android/Firefox OS
| Help fix bugs, improve documentation, learning resources, and developer experience for build tools, tests, and deployment of Cordova Firefox OS / Android projects
| javascript, nodejs
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: I'm unsure what this is, it sounds like "Work on Cordova Android/Firefox OS and fix some documentation for 3 months". We like GSoC projects to have a specific goal in mind. Maybe this just needs a bit of rewording though.
|-
| Webmaker.app for iOS
| Develop an iOS version of our Cordova application (currently implemented for Android/Firefox OS)
| javascript, nodejs
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: I have no idea how Webmaker.app works, but does this not need any iOS specific development skills (e.g. ObjectiveC)?
|-
| Prototype in-app payments for Webmaker.app
| Users can create mobile web apps with Webmaker.app, but what if they could accept payments? Explore options like paypal, stripe, etc. and develop a prototype using Cordova/web tech.
| javascript, nodejs, css, html
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: I'm having a bit of trouble understanding the final end goal of this: is it simply to have a prototype that includes, e.g., PayPal? What will that help us do?
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| [http://www.mozillascience.org/projects/codemeta Code as a Research Object]
| Using the proposed [https://github.com/mbjones/codemeta crosswalk schema] between existing software metadata, create a service (can be a simple website) that will allow users to search and filter software across exiting data archives and repositories (Zenodo, figshare, GitHub). Comparing the exiting schemas for code storage to help create a metadata standard that allows for discoverability, reuse and citation.
| json, [http://zenodo.org/dev zenodo api], [http://api.figshare.com/docs/intro.html figshare api], [https://developer.github.com/ github api]
| [[User:Abby|Abby]]
| [[User:Abby|Abby]]
| "Code as a Research Object" is exploring integrating software into the scholarly workflow. Collaboration with GitHub, figshare and Zenodo.

Background reading: http://www.mozillascience.org/code-as-as-research-object-new-phase/

http://www.mozillascience.org/code-as-a-research-object-metadata-for-software-discovery/

http://www.mozillascience.org/code-as-a-research-object-updates-prototypes-next-steps/

|-
| [http://www.mozillascience.org/projects/contributorship-badges Contributorship Badges] Visualizations
| Create a series of javascript snippets that authors and publishers can use to display authorship badges on their sites. Badges will be issued using PaperBadger -- a service using Open Badges to issue badges to an ORCID and paper DOI. Exploring the use of digital badges for crediting contributors to scholarly papers for their work.
| javascript, PaperBadger API (in development)
| [[User:Abby|Abby]]
| [[User:Abby|Abby]]
| As the research environment becomes more digital, we want to test how we can use this medium to help bring transparency and credit for individuals in the publication process. This work is a collaboration with publishers BioMed Central (BMC) and the Public Library of Science (PLoS); the biomedical research foundation, The Wellcome Trust; the software and technology firm Digital Science; the registry of unique researcher identifiers, ORCID; and the Mozilla Science Lab.

Background Reading: http://mozillascience.org/contributorship-badges-a-new-project/

http://news.sciencemag.org/scientific-community/2014/11/could-digital-badges-clarify-roles-co-authors

http://www.nature.com/news/publishing-credit-where-credit-is-due-1.15033
|}

Community:SummerOfCode15:Brainstorming

2015-02-23T19:29:32Z

Abby: /* Mozilla Science Lab */ Add actual tasks to proposed projects

Mozilla community members - submit proposals here for 2015 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode15|official list]].) '''The''' absolute last '''deadline for submitting ideas''' in time to help us get accepted by Google '''is February 20th'''.

Are you a students looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode15|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - 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 can, 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.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''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.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''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.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Firefox Performance Dashboard
| This project would implement the dashboard described in [https://bugzilla.mozilla.org/show_bug.cgi?id=1132498 bug 1132498]. Collecting the memory and CPU usage of addons and webpages and displaying it in a fashion that shows bad actors would be valuable for power users.
| HTML, CSS, JavaScript
| [https://mozillians.org/en-US/u/jdm/ jdm]
|
|
|-
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox OS / Boot2Gecko ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Contact Blacklist
| {{bug|1133501}} Implement a blacklist to prevent specified contacts from calling or messaging the user.
| HTML, CSS, JS
| [mailto:yvtheja@gmail.com Vishnu Teja (:ythej)]
| [mailto:dsherk@mozilla.com Doug Sherk (:drs)]
| Already assigned to [mailto:yvtheja@gmail.com Vishnu Teja (:ythej)]
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Performance testing
| Add and deploy a performance testsuite for Thunderbird to catch regressions in areas such as startup, message search, folder display, message display, etc.
| JavaScript, Python, preferably some performance analysis experience
| jcranmer
| ?
| Needs a mentor -- florian
|-
| Secure email UI
| Develop good interfaces for key management and illustrating the security levels of messages succinctly, preferably applicable to both S/MIME and OpenPGP.
| Strong UX experience; JS, XUL or HTML; crypto background advantageous
| jcranmer
| ?
| Summer of Code is about coding, not about UX work; asking students to do UX work often leads to disappointing results -- florian. This may be too large a task; narrowing focus could be useful.
|-
| Integrated pdf.js support in thunderbird (bug 810815)
| Firefox ships with integrade PDF viewing capabilities using pdf.js. This functionality is not present in Thunderbird yet but would obviously be useful.
| JavaScript
| mkmelin
| ?
| Unclear about how much work it is.
|-
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Infinite scroll
| Add additional messages from the logs on-demand as the user scrolls up/down. Old messages should be removed when no longer needed, while not breaking any existing features.
| JavaScript, XUL, CSS
| nhnt11
| nhnt11 + ???
|
|-
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

==NSS (Network Security Services)==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|Treeherder for mobile
|Threeherder is a tool that allows to monitor test and build results generated by the gecko CI system.
The goal of this project is to build a simplified version of Treeherder, targeted to a mobile audience.
The data is already available through a restful API.
The mobile UI should allow to see if a push has failures and eventually drill down to identify which job failed on which platform.
|Good knowledge of JavaScript and CSS. Previous experience with angularjs would be beneficial, but it's not needed.
| mdoglio
| mdoglio
|
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== OpenArt ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Build system ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Assurance ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Webmaker ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| AWS cli tool for deploys/rapid prototyping
| Help build/explore options for a heroku-like cli tool for rapid prototyping and development in the Webmaker ecosystem that interfaces with our AWS infrastructure.
| nodejs
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: There are tools that let you interact with AWS on the command line. I'm unsure if they do exactly what you want and doubt they're written in node (the [https://github.com/aws/aws-cli official one] is written on top of their [https://github.com/boto/boto Python library]).
|-
| Developer experience for Cordova Android/Firefox OS
| Help fix bugs, improve documentation, learning resources, and developer experience for build tools, tests, and deployment of Cordova Firefox OS / Android projects
| javascript, nodejs
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: I'm unsure what this is, it sounds like "Work on Cordova Android/Firefox OS and fix some documentation for 3 months". We like GSoC projects to have a specific goal in mind. Maybe this just needs a bit of rewording though.
|-
| Webmaker.app for iOS
| Develop an iOS version of our Cordova application (currently implemented for Android/Firefox OS)
| javascript, nodejs
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: I have no idea how Webmaker.app works, but does this not need any iOS specific development skills (e.g. ObjectiveC)?
|-
| Prototype in-app payments for Webmaker.app
| Users can create mobile web apps with Webmaker.app, but what if they could accept payments? Explore options like paypal, stripe, etc. and develop a prototype using Cordova/web tech.
| javascript, nodejs, css, html
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
| clokep: I'm having a bit of trouble understanding the final end goal of this: is it simply to have a prototype that includes, e.g., PayPal? What will that help us do?
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| [http://www.mozillascience.org/projects/codemeta Code as a Research Object]
| Using the proposed [https://github.com/mbjones/codemeta crosswalk schema] between existing software metadata, create a demo that will allow users to search and filter software across exiting data archives and repositories (Zenodo, figshare, GitHub). Comparing the exiting schemas for code storage to help create a metadata standard that allows for discoverability, reuse and citation.
| javascript, json
| [[User:Abby|Abby]]
| [[User:Abby|Abby]]
| "Code as a Research Object" is exploring integrating software into the scholarly workflow. Collaboration with GitHub, figshare and Zenodo.

clokep: This doesn't seem to propose a specific project for a student to work on. What would the student be doing?
|-
| [http://www.mozillascience.org/projects/contributorship-badges Contributorship Badges] ORCID and badgekit-api integration
| Create a layer that will integrate with [https://github.com/mozilla/badgekit-api badgekit-api] and [http://orcid.org/ ORCID] (the registry of unique researcher identifiers) oauth to allow us to assign badges to an ORCID (not an email). This will be part of the PaperBadger project that will issue digital badges to contributors to scholarly papers for their work.
| javascript, apis
| [[User:Abby|Abby]]
| [[User:Abby|Abby]]
| As the research environment becomes more digital, we want to test how we can use this medium to help bring transparency and credit for individuals in the publication process. This work is a collaboration with publishers BioMed Central (BMC) and the Public Library of Science (PLoS); the biomedical research foundation, The Wellcome Trust; the software and technology firm Digital Science; the registry of unique researcher identifiers, ORCID; and the Mozilla Science Lab.

clokep: This doesn't seem to propose a specific project for a student to work on. What would the student be doing?
|-
| [http://www.mozillascience.org/projects/contributorship-badges Contributorship Badges] Visualizations
| Create a series of javascript snippets that authors and publishers can use to display author badges on their sites. Exploring the use of digital badges for crediting contributors to scholarly papers for their work.
| javascript, apis
| [[User:Abby|Abby]]
| [[User:Abby|Abby]]
| As the research environment becomes more digital, we want to test how we can use this medium to help bring transparency and credit for individuals in the publication process. This work is a collaboration with publishers BioMed Central (BMC) and the Public Library of Science (PLoS); the biomedical research foundation, The Wellcome Trust; the software and technology firm Digital Science; the registry of unique researcher identifiers, ORCID; and the Mozilla Science Lab.
|}

User:Abby

2015-02-23T18:49:40Z

Abby:

Lead Developer, Mozilla Science Lab

Community:SummerOfCode15

2015-02-20T22:50:05Z

Abby: /* Mozilla Science Lab */ adding Mozilla Science Lab projects -- code as a research object & contributorship badges

This page lists all the [[SummerOfCode|Google Summer of Code]] 2015 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode15:Brainstorming|the Brainstorming page]]. Do not edit this page yourself; contact Florian for edits.

'''Potential students''': you may choose from the list below, '''but you do not have to'''. Feel free to submit a proposal for your own idea. However, before you do so, see the [[Community:SummerOfCode15:Brainstorming|guidelines for good ideas]]. You can also discuss your ideas or application in the #introduction channel on IRC: irc://irc.mozilla.org/#introduction . Your idea will have a significantly greater chance of being chosen if you can find an existing member of the Mozilla community who is willing to evaluate or mentor it. (You should name that person in your application.)

In addition to the specifically-named projects below, we have also tagged a number of bugs in Bugzilla with the keyword [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&keywords_type=allwords&keywords=student-project&resolution=--- student-project]. However, as the idea of a "student project" is wider than just the Summer of Code, students looking through the list will need to decide whether any particular bug listed there is actually the right size and scope for Summer of Code.

==Application Advice==

You should do the following:

* Talk to the mentor. Contact details are on this page; if all you have is a nickname, get on [[IRC|IRC]] and try and contact them.
* Read the [https://flossmanuals.net/GSoCStudentGuide/ GSoC Student Guide] and follow its advice.
* Read [http://blog.gerv.net/2006/05/how_not_to_apply_for_summer_of/ How Not To Apply For Summer Of Code] and avoid doing the things listed there.
* Read our examples of good applications: [[SummerOfCode/SampleApplications/1|1]], [[SummerOfCode/SampleApplications/2|2]], [[SummerOfCode/SampleApplications/3|3]].
* Apply on [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 the GSoC site] (note that we have an [[SummerOfCode/ApplicationTemplate|application template]]).
* It is entirely acceptable to apply for 2 or 3 projects, if more than one catches your eye; if the applications are high quality, that can improve your chances. However, more than 3 seems like spam.

Note that if a project suggests it would be helpful to know XUL (Mozilla's user interface description language), you may be able to get away with learning on the job. Don't be put off from applying if the project otherwise looks right for you.

Questions about individual projects are best addressed to the potential mentor of that project. These should be listed in the table below. If you want to contact a mentor and contact details are not here, ask people in the #introduction channel on IRC: irc://irc.mozilla.org/#introduction. If you have questions of any other sort, send mail to [mailto:florian@queze.net,clokep@gmail.com Florian and Patrick]. We will try and respond as soon as possible and get your questions directed to the right person. Please allow at least 48 hours for a reply.

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Download Integrity
| Enhance detection of broken downloads in Firefox. Methods may include:<ul><li>[http://www.w3.org/TR/SRI/#the-a-element-1 Subresource Integrity for the <a> element]<li>[[Features/HTTP_Digest_header_verification#Stage_1:_Definition|HTTP Digest header verification]]<li>Network-level indications like bad HTTP framing</ul>The activities include:<ul><li>Implement the front-end in JavaScript to display failed integrity checks<li>Implement and/or use the required back-end features in C++<li>Work with the Mozilla community to discuss and refine the behavior of the feature, including which methods should be implemented first</ul>
| C++, JavaScript
| Paolo
| Paolo
|
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Source Map Library
| This project would implement missing library support for certain of the source map spec, specifically "indexed" source maps, and experimenting with extensions for encoding the original source code's lexical environment in the source map.
| JavaScript, Node.js
| [https://mozillians.org/en-US/u/fitzgen/ fitzgen]
| [https://mozillians.org/en-US/u/fitzgen/ fitzgen]
| Easy for a contributor to ramp up on, because it can be done completely in Node.js without needing to build Firefox.
|}

== Firefox OS / Boot2Gecko ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Mailbox-to-maildir converter
| Mailbox and Maildir are two alternative on-disk storage formats for email messages. Thunderbird currently uses Mailbox, but wants to use Maildir. Hence the need for a converter. This is one of the last critical pieces blocking moving away from mbox-style mailboxes. See {{bug|856087}}.
| JavaScript, C++
| jcranmer
| rkent
|
|-
| Alternate protocol for mailnews folders
| Thunderbird has long-term plans to implement a variety of mail and mail-like protocols to be managed as mailnews folders. An existing addon (SkinkGlue) exists to provide the glue for this. Implement one other protocol, which might be Fastmail's JMAP, or Calendar events & tasks
| JavaScript
| rkent
| rkent and, depending on protocol brong from Fastmail, or Fallen
| I doubt having 2 twitter implementations in Thunderbird is a valuable investment of time. JMAP seems the most promising protocol idea here; do we know if brong is on board to (co-)mentor this? Even though the code would be primarily written in JS, I suspect having some C++ skills to be able to understand some of mailnews' internals would be very helpful.
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Improve the JavaScript XMPP implementation and implement new features.
| Includes better error handling, implementing multi-user chats (MUCs), test coverage and adding new/missing features. Feature-parity with libpurple's XMPP implementation is one of the prerequisites for replacing it with the JavaScript implementation and is an end-goal of this project. Students are expected to compile a list of bugs or unimplemented features in the JavaScript XMPP code.
| JavaScript, XPCOM, an understanding of XMPP is desired
| Florian Quèze
| aleth, Patrick Cloke
|
|-
| Implement a new protocol plug-in in JavaScript
| Instantbird supports protocol plugins implemented in JavaScript. The student will add support for a new protocol in Instantbird. The student working on new protocols should take every opportunity to improve the code and APIs shared by all JavaScript protocol plugins (IRC, XMPP, Yahoo and Twitter). It is expected that the student research the feasibility of interoperability concerns of the protocol during the application period. Students are expected to implement a protocol they use on a day-to-day basis to dog-food the code.
| JavaScript, XPCOM, maybe js-ctypes, understanding of network protocols
| Patrick Cloke
| Patrick Cloke
| Possible protocols include: Google Hangouts, Facebook, WhatsApp, SIP, Bonjour, OSCAR, TextSecure or Telegram
|-
| File transfer support
| API design, backend implementation, frontend UI for supporting file transfers in Instantbird.
| XPCOM, JavaScript, webrtc, networking protocols
| nhnt11
| Patrick Cloke
|
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Introducing Calendar Accounts
| Traditionally our calendar extension is organized into a list of calendars, each calendar being implemented by a “provider”, for example local storage or using the CalDAV protocol. The service to manage these calendars maintains a simple list, the entries have no connection to each other.
Some calendar providers would greatly benefit from being able to group calendars into accounts, for example free-busy lookups are usually per-server operations and not per-calendar. It would also open the door for some great new features that have been postponed because they can be implemented cleaner with the notion of accounts.
| XUL, CSS, JavaScript
| [mailto:mozilla@kewis.ch Fallen]
| [mailto:mozilla@kewis.ch Fallen]
| [[Media:Calendar-gsoc2015-calmgr.pdf|Click here for a detailed project description]]
|-
| Resource Booking Improvements
| The Lightning extension has a dialog for inviting attendees to an event, which also shows availability information. Albeit not very obvious, it also allows booking resources and rooms. To improve this experience we would like users to be able to pick rooms and resources in a way that they don't need to remember the room address and quickly see which rooms and resources exist and are available around the proposed time of the event.
| XUL, CSS, JavaScript
| [mailto:mozilla@kewis.ch Fallen]
| [mailto:mozilla@kewis.ch Fallen]
| [[Media:Calendar-gsoc2015-resourcebooking.pdf|Click here for a detailed project description]]
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Bugzilla Extension Exchange Format
| Write an installer script for Bugzilla extensions
| Perl
| dylan (dylan@mozilla.com)
| dylan
| Spec: http://hardison.net/~dylan/BEEF.html
|}

== Accessibility ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Performance Alerts Release Management Toolchain
| This GSOC project will deliver functionality of detecting alerts as they merge between branches. This is mostly important for regressions, but should also include improvements. We generate thousands of performance alerts every year, and we need a way to look at the high level of what is concerning while having the ability to drill down and understand what small details make up the bigger problems. This depends on us seeing these regression when the code was originally introduced and action being taken to file a bug. In many cases we have preferences that turn features on and off which will have an affect on the alerts that we care about. The target here is a release manager can go to a dashboard, and see the state of the release (most important after uplifting code) and get a list of bugs that are of interest.

This will be integrating a system into TreeHerder to store alerts and allow graphs of the data to be annotated. There will be an API so alert can be generated from other sources and managed by other tools as well.

| Python, AngularJS, SQL, Javascript
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| [[https://mozillians.org/en-US/u/wlach/ Will Lachance]], [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| The impact here is the ability for developers and release managers to see the performance impact of their changes while helping us track this.
|-
| Retry failures in automation and provide annotations for intermittent failures vs real failures
| Of the thousands of unitests which are run for each platform and each push we find many intermittent failures. This is a pain point for developers when they test their code on try server. Now that we have TreeHerder, it isn't much work to automatically annotate jobs as intermittent or a regression/failure. In mochitest we have --bisect-chunk which will retry the given test and determine if it is an intermittent or a real regression. The goal here is to do this automatically for all jobs on try server. Jobs will still turn orange. With the outcome of this project failures would need to have a different view in the UI.
| Python, Javascript
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| This will build off an existing set of tools while helping us bridge the gap towards a much better review and automated landing of patches system. In the short term, this will aid in developers who see failures and either do multiple pushes, many retriggers, or just ignore them- in summary we will not need to worry as much about wasting resources related to intermittents.
|-
| Unittest sanitizer
| With our thousands of test files, there are hundreds that have dangerous api calls which result in leftover preferences, permissions, and timing issues. A lot of work has been done here, we need to fix tests and expand our work on these resources to all our tests. In addition to cleaning up dangerous test code, we need to understand our tests and how reliable they are. We need to build tools that will allow us to determine how safe and reliable our tests are individually and as part of a suite. Upon completion of this project we should have the majority of tests cleaned up, and a toolchain that can be easily run and generate a report on how stable each test is.
| Python, Javascript
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| [[https://mozillians.org/en-US/u/mwargers/ Martijn Wargers]], [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| The impact this has is helping us cleanup our tests to reduce intermittents and give us tools to write better tests and understand our options for running tests in different configurations.
|-
|mozregression GUI
|Using Python, create a graphical user interface for mozregression (http://mozilla.github.io/mozregression) along with an installer and automatic update system to make it easier for less technical contributors to find and report regression ranges in Firefox and Thunderbird.
|Python
|[mailto:wlachance@mozilla.com William Lachance]
|[mailto:wlachance@mozilla.com William Lachance], [mailto:j.parkouss@gmail.com Julien Pagès]
|-
| Convert Mozmill test cases to Marionette
| he Mozmill framework is being replaced by Marionette to support multi-process Firefox. In the previous Mozmill toolchain we have dozens of libraries and hundreds of tests. This project will entail assessing those tests for uniqueness (compared to browser-chrome) and porting what tests and libraries make sense to Marionette. The goal here is to assess all the tests and have at least 75 converted.
| Python, Javascript
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]], [[https://mozillians.org/en-US/u/whimboo/ Henrik Skupin]]
| Existing tests live here:
http://hg.mozilla.org/qa/mozmill-tests/file/default

new tests live here:
https://github.com/mozilla/firefox-ui-tests
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Define, test, and publish json hyperschemas for all release engineering APIs
| We have several APIs (e.g. buildapi, clobberer, (modern) mapper, mozpool, slavealloc, slaveapi, ...) but have no central standardised way of defining them, publishing them, documenting them, or sharing them. A cool project would be to use json hyperschema (see e.g. https://brandur.org/elegant-apis) to define all our apis, and have a framework for auto testing them, auto-documenting them, even potentially auto-generating client libraries for them e.g. in python, and auto-publishing the schemas to a central location for reference. Another interesting option might be using http://swagger.io/.

Example REST apis that we have are:

* Build API: https://wiki.mozilla.org/ReleaseEngineering/Applications/BuildAPI
* Clobberer: https://api.pub.build.mozilla.org/docs/usage/clobberer/#endpoints
* (Modern) Mapper: https://wiki.mozilla.org/ReleaseEngineering/Applications/Mapper
* Mozpool: http://hg.mozilla.org/build/mozpool/file/tip/API.txt
* Slave API: http://mozilla-slaveapi.readthedocs.org/en/latest/api/#slaves-slave-actions-disable

This GSoC project would involve creating hyperschemas for the above APIs (and potentially others too), finding a good place to publish these references, and look at setting up some tools to generate documentation for these APIs, together with code generation of client libraries, and their associated documentation (godoc, javadoc, …) and if time allows, even auto-generation and deployment of new documentation, libraries, as and when these json hyper schemas get updated (perhaps with travis ci deploying to e.g. github pages or heroku).
| json, json hyperschema, solid programming skills, enthusiasm, code generation, web interface design
| [mailto:pmoore@mozilla.com Pete Moore]
| [mailto:pmoore@mozilla.com Pete Moore]
| Some good starting points:
* http://spacetelescope.github.io/understanding-json-schema/ (for json schema)
* https://brandur.org/elegant-apis (for json hyper schema)
* http://json-schema.org/
|-
| Decouple Mozharness internals by breaking it into standalone modules
| What is Mozharness: It's a configuration-driven script harness that is used for automating > 90% of Mozilla's build and test jobs. It is also used by release engineering services outside of continuous integration.

What needs to decoupled: Mozharness has reached some scaling issues. Jobs that do builds and tests inherit and share exhaustive number of mixins. This leads to a complicated Method Resolution Order and objects with too many attrs that are not even needed.

How can this be done: replace the mixins with standalone classes that act as services. The classes can be instantiated many times and are aware of only their own responsibilities. Once stand alone, you then make them into packages within a mozharness library and installable by pip.

The benefit:

* better scalability
* more pythonic so the entry for contribution is less intimidating
* tools outside of mozharness can avail of subcomponents of mozharness

steps and goals for gsoc:

* part (1) take mixins like log.py, config.py, buildbot.py, python.py, signing.py, and tooltool.py and convert them from mixins to standalone classes
** example of how that's done: {{bug|1063532}}
* part (2) turn the now standalone classes into python packages

| python, solid programming skills, enthusiasm
| [mailto:jlund@mozilla.com Jordan Lund], Armen Zambrano
| [mailto:jlund@mozilla.com Jordan Lund]
| more details:

* https://docs.google.com/a/mozilla.com/document/d/1AQZT9opDkqb0tgZaVAtfAX2_dVWFHNWmz0ImgS5-hPM
* https://etherpad.mozilla.org/mozharness-mixins
* http://hg.mozilla.org/build/mozharness
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| rustfmt
| Create a code formatting tool that automatically reformats Rust code to meet conventions.
| Experience with Rust.
| [https://mozillians.org/en-US/u/brson brson]
| [https://mozillians.org/en-US/u/brson brson]
|
|-
| Rust Code Completion for SublimeText
| This project would develop a plugin for the Sublime Text editor that provides code completion for the Rust programming language, by integrating with the Rust [https://github.com/phildawes/racer Racer] project. This would require interfacing between Python (for the Plugin) and Rust (for Racer).
| Rust, Python
| pnkfelix
| pnkfelix
|
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Speculative HTML parsing
| Servo's [https://github.com/servo/html5ever/ HTML parser] currently blocks whenever it needs to execute JS code (eg. when <script> tags are encountered in a page). We want to split the HTML parsing code into two threads, one of which can continue parsing the rest of the HTML source [http://www.dorothybrowser.com/portfolio/parallel-parser/ speculatively] while the other is busy executing JS; once the second is finished, the parser can use the result of the first thread's efforts to improve page load performance.
| Prior [http://www.rust-lang.org/ Rust] experience valuable. Familiarity with HTML.
| [https://mozillians.org/en-US/u/jdm/ jdm]
| [https://mozillians.org/en-US/u/kmcallister/ kmc]
|-
| HTTP/2 implementation in hyper
| [https://github.com/hyperium/hyper/ Hyper], the Rust HTTP library that Servo relies upon, is missing support for exciting new technologies like [https://http2.github.io/ HTTP/2]. This project would design and integrate an HTTP/2 implementation into the client and servo code for hyper.
| Experience writing code that interacts with network protocols. Prior [http://www.rust-lang.org/ Rust] experience valuable.
| [https://mozillians.org/en-US/u/jdm/ jdm]
| [https://mozillians.org/en-US/u/seanmonstar/ seanmonstar] and [https://github.com/reem/ reem]
|-
| Server-Sent Events
| Servo lacks an implementation of the [https://developer.mozilla.org/en-US/docs/Web/API/EventSource EventSource Web API]. The goal of this project is to implement that API, following the [https://html.spec.whatwg.org/multipage/comms.html#server-sent-events specification] as closely as possible and enabling the [https://github.com/w3c/web-platform-tests/tree/master/eventsource tests] for this feature that already exist.
| Prior experience with [http://www.rust-lang.org/ Rust] valuable. Comfortable reading and writing JavaScript for the web.
| [https://mozillians.org/en-US/u/jdm/ jdm]
| [https://mozillians.org/en-US/u/jdm/ jdm]
|
|-
| Improve form support
| Servo currently has rather basic form support, with simple widgets. We lack support for many form controls and functionality like file uploads and form validation. We'd like to add support for most form behavior, based on the [https://html.spec.whatwg.org/multipage/forms.html specification].
| Familiarity with web HTML/Javascript. Prior experience with [http://www.rust-lang.org/ Rust] and/or reading web specifications valuable.
| [https://mozillians.org/en-US/u/Manishearth Manishearth]
| [https://mozillians.org/en-US/u/Manishearth Manishearth] (or [https://mozillians.org/en-US/u/jdm/ jdm])
|
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== OpenArt ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| [https://github.com/noflo/noflo-ui NoFlo-UI]
| Implement an UI widget on noflo-ui. It could be a timeline (see [https://github.com/noflo/noflo-ui/issues/151 this issue]), plugins for IIP editing or packet display for particular data types. Considering the timeline widget, an initial prototype could be a component library (see [https://github.com/noflo/noflo-tween/blob/master/components/Timeline.coffee noflo-tween]). Proposals should include sketches and an implemented prototype (pull requested to noflo-ui).
| javascript, coffeescript, ux
| [[User:Forresto|Forresto]]
| [[User:Forresto|Forresto]]
| [http://noflojs.org NoFlo] is a JS dataflow implementation and has runtimes for browser, image processing ([https://github.com/jonnor/imgflo imgflo]), microcontrollers ([https://github.com/jonnor/microflo microflo]), SuperCollider ([https://github.com/jonnor/sndflo sndflo]) and other targets. [https://app.flowhub.io Flowhub] is the browser-based IDE for the creation of NoFlo graphs.
|-
| [https://github.com/tweenjs/tween.js Tween.JS]
| Port Tween.js to ES6 and make it a modern citizen of the JS world
| javascript, web animations, graphics
| [[User:Sole|Sole]]
| [[User:Sole|Sole]]
| Tween.JS is a small engine for declaring and running interpolations between values. It's used in interactive experiences, games and all sorts of projects.
|-
| [https://github.com/sole/Animated_GIF Animated_GIF]
| Refactor and build a version 2, splitting the library into independent reusable modules. Also work on compatibility with Firefox OS.
| javascript, web animations, graphics, web workers, pixel handling, canvas
| [[User:Sole|Sole]]
| [[User:Sole|Sole]]
| Animated_GIF is a library for generating Animated GIFs on the browser. It's used in demo apps in mozilla, some properties at webmaker, the wildly successful chat at meatspac.es and who knows where else.
|-
| Create image filters using [http://noflojs.org NoFlo]
| It's possible to start prototyping image filters using [https://app.flowhub.io Flowhub] (use [https://www.filterforge.com/ Filter Forge]'s filters as inspiration and our porting of [https://github.com/jonnor/imgflo/wiki/Recreating-Instagram-filters some Instagram filters]) and components libraries like [http://github.com/noflo/noflo-image noflo-image] and [http://github.com/noflo/noflo-canvas noflo-canvas], then port the filters to imgflo. Another option is to create filters directly on imgflo using GEGL. Proposals should include a running NoFlo graph for a non-trivial image filter, together with sketches and original/processed images. Imgflo+GEGL filters are preferred. Pull requests to noflo-image and imgflo are a plus.
| javascript, coffeescript, noflo, cpp, computer vision basics
| [[User:Vilsonvieira|Vilson Vieira]]
| [[User:Vilsonvieira|Vilson Vieira]]
| [http://noflojs.org NoFlo] is a JS dataflow implementation and has runtimes for browser, image processing ([https://github.com/jonnor/imgflo imgflo]), microcontrollers ([https://github.com/jonnor/microflo microflo]), SuperCollider ([https://github.com/jonnor/sndflo sndflo]) and other targets. [https://app.flowhub.io Flowhub] is the browser-based IDE for the creation of NoFlo graphs. [http://gegl.org GEGL] is a graph-based image processing framework used by imgflo (it's also possible to use noflo-canvas instead of GEGL, but GEGL is preferred due to performance reasons).
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| [http://www.mozillascience.org/projects/codemeta Code as a Research Object]
| comparing the exiting schemas for code storage to help create a metadata standard that allows for discoverability, reuse and citation.
| javascript, json
| [[User:Abby|Abby]]
| [[User:Abby|Abby]]
| "Code as a Research Object" is exploring integrating software into the scholarly workflow. Collaboration with GitHub, figshare and Zenodo.
|-
| [http://www.mozillascience.org/projects/contributorship-badges Contributorship Badges]
| Exploring the use of digital badges for crediting contributors to scholarly papers for their work.
| javascript, apis
| [[User:Abby|Abby]]
| [[User:Abby|Abby]]
| As the research environment becomes more digital, we want to test how we can use this medium to help bring transparency and credit for individuals in the publication process. This work is a collaboration with publishers BioMed Central (BMC) and the Public Library of Science (PLoS); the biomedical research foundation, The Wellcome Trust; the software and technology firm Digital Science; the registry of unique researcher identifiers, ORCID; and the Mozilla Science Lab.
|}

ScienceLab/Calls

2015-02-12T15:37:22Z

Abby: /* Science Lab Community Calls */

__NOTOC__
=== Science Lab Community Calls ===
Second Thursday of every month

'''Our next call:''' February 12, 2015 8 am PDT / 11 am ET / 4 pm GMT

Conference Number: +1 800 707 2533,
Password: 369
Room: 7677

If you have trouble accessing the above number, try one of the following numbers (note these are not toll-free numbers and regular billing rates will apply). Enter the conference ID, 7677, after you enter the extension:

<ul>
<li>US/California/Mountain View: +1 650 903 0800, extension 92
<li>US/California/San Francisco: +1 415 762 5700, extension 92
<li>US/Oregon/Portland: +1 971 544 8000, extension 92
<li>CA/Vancouver: +1 778 785 1540, extension 92
<li>CA/Toronto: +1 416 848 3114, extension 92
<li>UK/London: +44 (0)207 855 3000, extension 92
<li>FR/Paris: +33 1 84 88 37 37, extension 92
</ul>

 Calendar ICS File : http://bit.ly/mozsciencecall-ics
 Subscribe to Calender : http://bit.ly/mozsciencecalls

=== What is the Science Lab Meeting? ===

The Science Lab meeting is our community call, taking place the second Thursday of every month, highlighting what we're up to as well as work of the community relevant to science and the web. Join us to hear more about current projects, ways you can get involved, and discuss issues around open science. The calls are made stronger by your participation, so do join us.

Join us on the second Thursday of every month // 11 am Eastern .

Hear more about what we're up to, ask questions, and interact with other call participants. Join us.

===Call archives===
* [https://etherpad.mozilla.org/sciencelab-calls-nov14 November 14, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-dec12 December 12, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-jan9-2014 January 9, 2014]
* [http://etherpad.mozilla.org/sciencelab-calls-feb13-2014 February 13, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-mar20-2014 March 20, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-apr10-2014 April 10, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-may08-2014 May 8, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-june12-2014 June 12, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-july10-2014 July 10, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-aug14-2014 August 14, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-sep11-2014 September 11, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-oct9-2014 October 9, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-nov13-2014 November 13, 2014]
* NO DECEMBER 2014 CALL
* [https://etherpad.mozilla.org/sciencelab-calls-jan15-2015 January 15, 2015]

ScienceLab/2015roadmap

2014-12-05T20:14:02Z

Abby:

''This page includes high-level, detailed plans and deliverables for the Mozilla Science Lab's 2015 key initiatives.''

'''''NOTE: This is an active draft.'''''

The Science Lab launched in June 2013 to explore how Mozilla could help enable research that is not only like the web but of the web. Since then, we’ve and tested a model for the program built on Mozilla’s core values and expertise, and engaged in work with the community around open, *web-enabled* science.

We do this by:

* '''Building''' communities and technical prototypes;

* '''Teaching''' skills needed to further open practices;

* '''Empowering''' others to learn, solve problems and build new tools together.

This page will look at what we've learned in our first 18 months, and sketch out a plan to build on that foundation in 2015.

==What we’ve learned==

We’ve worked with open educational projects like Software Carpentry to train researchers in skills needed to do more efficient research and empower them to build on that knowledge, innovate and teach. Through that work, we’ve learned firsthand the need for skills training and mentorship in research if we’re going to shift practice. We’ve also seen the challenges in scaling and making sustainable volunteer efforts, as well as assessing their long-term impact.

Over the course of the past 18 months, we’ve also found our greatest successes in meeting the community where they are both in terms of skills and levels of awareness, working with them to support and amplify their work rather than the other way around. Through our work with Software Carpentry, we’ve also gained insight to the gaps in training in research settings globally, and the areas we can support as Mozilla across programs and pedagogy, rather than taking a boutique approach.

==2015 goals (and elevator pitch)==

In 2015, we’ll be further exploring how we can, along with the community, build the supports for truly scalable and connected learning that incentivizes long-term engagement, from curriculum in data to train-the-trainers and a fellowship program. We’ll also be focusing on how to foster best practice in open research through technical projects with the community, and honing our engagement strategy to enable researchers to identify with open science from within their disciplines.

Specifically, we plan to:

* '''Empower others to become open science champions''' and agents of change within their own communities. (ie., Fellows, mentors, train-the-trainers.)

* '''Craft resources and pathways''' to foster long-term engagement and learning. (i.e., data curriculum, skills training workshops, teaching materials, lasting communities.)

* '''Serve as an intersection point for the community''' to foster dialogue, collaborate on projects and innovate across disciplines, specialties and geographic location. (i.e., Sprints, MozFest, community calls, Collaborate platform, forum)

Below we’ve outlined our leading initiatives for the year to achieve these goals:

*'''FELLOWSHIPS''' - Our fellowship program empowers early career researchers to become open science community leaders. They will serve as our lead mentors and help empower members of the research community.

*'''TRAINING''' - We offer skills training workshops and materials for the research community around open practices and data. We provide the community with pathways to learn the methods and tools to do more open science on the web.

*'''SPRINTS + PROTOTYPING''' - We work with the community to build prototypes to test out ideas that further open, web-enabled science. Through our sprints, local events, and online platform, we provide a means for the community to collaborate on code to share within the broader research community.

*'''MENTORSHIP''' - We provide members of the research community with the supports needed to start local conversations in their communities. By supporting a community of peers working, learning and teaching one another, we will foster a network of open science champions.

*'''EVENTS''' - We host and facilitate events to bring together the open research community on a global and local scale. Through events such as the Mozilla Festival, global sprints, coding challenges and study groups, we provide a place for the open science community to come together, share skills and experiences, and connect.

==Defining our community==

The Mozilla Science Lab is helping a global network of researchers, tool developers, librarians and publishers collaborate to further science on the web. We believe a community of peers working, learning and building together is needed to make research thrive on the open web.

Below are some of the core characteristics of the diverse community we serve:

* Applying Mozilla's values to further research on the web - The Science Lab takes the values and fabric of the Manifesto and applies them to furthering "open" practice in scientific research. This involves a focus on open technologies, fostering collaboration and best practice, interoperability both socially and technically, and building on-ramps for researchers to gain the skills needed to further their work on the web. For a look at how these values map to the sciences, [[ScienceLab/OpenResearchMap|see v.0 of our "Open Research Map"]].

* Global as well as by topic/issue/specialty – The Science Lab community is a global one, and community members are grouped together by interest in topics/issues and member organizations which are tied to both key regions and topics.

* Mozilla’s Role – Mozilla’s role is to facilitate and enable engagement between community members (individuals, organizations, technology providers, publishers). We do not direct the community; we enable it and help amplify.

* A Community of Practitioners and Leaders -

* Value for All Community Members – We are modeling the Mozilla Science Lab Community in a way that provides value to all participants – from the individual researcher to the institution and funders.

==Cross-org Opportunities==

* Open News via Erika Owens: fellows hiring strategy. Open news has iterated on their hiring strategy for their fellowship program, and have a number of lessons learned for promoting diversity and healthy community relationships in their hiring practice.

* Webmaker Mentorship (Laura H., Hive, Chris): Webmaker training has developed and tested ways to identify, engage and incentivize their mentors through an infrastructure prototype and platform that can be remixed. As well, an online learning as a mechanism for engaging outside the super mentors.

* Mozilla Fellows (An-Me, Dan, Dave): We're contributing to building a picture of what makes a Mozilla Fellow; what do the fellows have in common across programs, and how can we frame these programs to understand how the Fellows can best carry Mozilla's values outwards to their communities.

==Cultivating community and building for reach==

* Connect with academic and research community to identify fellows, champions and hosts

* Enable our mentors to make compelling connections to their colleagues by framing events from within their fields

* Support our fellows' efforts to build lasting movements within their fields

==2015 (Q1-Q2) Roadmap==

{| class="wikitable"
|-
! Swim Lanes !! 2014 Wrap !! Q1 !! Q2 !! Change of State
|-
| MSL Infrastructure || <ul><li>Build new site</li> <li>lessons learned reflections</li></ul> || <ul><li>Launch new MSL site</li><li>Website testing (ongoing)</li><li>Design and articulate terms on Collaborate</li><li>Open up Collaborate to new projects</li></ul> || Community Blog Launch || <ul><li>Enabling more & easier engagement through website, Collaborate and the forum</li><li>Increased discoverability of people, tools and resources.</li></ul>
|-

| Leadership & Train the Trainer || || <ul><li>University Road Show planning & relationship building</li><li>1st cut at train the trainers curriculum</li><li>Leaders Summit Planning (see Webmaker lessons learned)</li><li>Call for Fellows opens</li></ul> || <ul><li>Fellows workweek & training</li><li>Leaders Summit</li></ul> || <ul><li>Generate more community leaders</li><li>(Re)activate community members</li><li>Train & support fellows</li></ul>
|-

| Assessment || Year-end SWC wrap up and lessons learned || <ul><li>ID experts and assessment methods</li><li>Gather experts to discuss measuring impact</li></ul> || || <ul><li>Have a concrete plan / system for MSL assessment</li><li>Be able to make decisions based on data</li></ul>
|-

| Prototyping || || <ul><li>Badges planning</li><li>Standardize infrastructure/practice -> MoFo engineering</li></ul> || <ul><li>Ship Contributorship badges project prototype v.0</li><li>Code as a research object continued development</li></ul> || <ul><li>Working "Contributorship badges"</li><li>Generate funnel of ideas + process to operationalize</li></ul>
|-

| Curriculum || Code review wrap-up blog + curriculum || <ul><li>Train-the-trainer first cut</li><li>Create resourcds for non-SWC events</li><li>Hire Data and Training Lead</li></ul> || Beta tests of event-based materials (ie., study groups, weekend challenges, etc) || <ul><li>Have a resource stack to support community leaders + fellows</li><li>Create + test data training</li><li>More accessible(/empowering) curriculum</li></ul>
|-

| Events || || <ul><li>ResBaz (Australia event/community launch)</li><li>Coders Crowd/weekend challenge/pilot study group</li><li>Train-the-trainers @ UC Davis</li><li>Test out local sprint/hackathon in Toronto (Feb)</li><li>Planning for global sprint</li></ul> || Global sprint || <ul><li>Clearer understanding of how to increase engagement through events</li><li>Work towards model of community supports + leaders</li><li>Generate project and leadership pipeline</li></ul>

|}

==Background links==

* [https://kt.etherpad.mozilla.org/MSL-strategic-planning-2015 Planning etherpad]

* [https://wiki.mozilla.org/ScienceLab/OpenResearchMap Open Research Map v.0]

ScienceLab/Calls

2014-09-11T17:44:09Z

Abby: /* Call archives */

__NOTOC__
=== Science Lab Community Calls ===
Second Thursday of every month

'''Our next call:''' October 9 2014, 8 am PDT / 11 am EDT / 4 pm BST

Conference Number: +1 800 707 2533,
Password: 369
Room: 7677

If you have trouble accessing the above number, try one of the following numbers (note these are not toll-free numbers and regular billing rates will apply). Enter the conference ID, 7677, after you enter the extension:

<ul>
<li>US/California/Mountain View: +1 650 903 0800, extension 92
<li>US/California/San Francisco: +1 415 762 5700, extension 92
<li>US/Oregon/Portland: +1 971 544 8000, extension 92
<li>CA/Vancouver: +1 778 785 1540, extension 92
<li>CA/Toronto: +1 416 848 3114, extension 92
<li>UK/London: +44 (0)207 855 3000, extension 92
<li>FR/Paris: +33 1 84 88 37 37, extension 92
</ul>

 Calendar ICS File : http://bit.ly/mozsciencecall-ics
 Subscribe to Calender : http://bit.ly/mozsciencecalls

=== What is the Science Lab Meeting? ===

The Science Lab meeting is our community call, taking place the second Thursday of every month, highlighting what we're up to as well as work of the community relevant to science and the web. Join us to hear more about current projects, ways you can get involved, and discuss issues around open science. The calls are made stronger by your participation, so do join us.

Join us on the second Thursday of every month // 11 am Eastern .

Hear more about what we're up to, ask questions, and interact with other call participants. Join us.

===Call archives===
* [https://etherpad.mozilla.org/sciencelab-calls-nov14 November 14, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-dec12 December 12, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-jan9-2014 January 9, 2014]
* [http://etherpad.mozilla.org/sciencelab-calls-feb13-2014 February 13, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-mar20-2014 March 20, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-apr10-2014 April 10, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-may08-2014 May 8, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-june12-2014 June 12, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-july10-2014 July 10, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-aug14-2014 August 14, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-sep11-2014 September 11, 2014]

ScienceLab/Calls

2014-09-11T17:38:14Z

Abby: /* Science Lab Community Calls */

__NOTOC__
=== Science Lab Community Calls ===
Second Thursday of every month

'''Our next call:''' October 9 2014, 8 am PDT / 11 am EDT / 4 pm BST

Conference Number: +1 800 707 2533,
Password: 369
Room: 7677

If you have trouble accessing the above number, try one of the following numbers (note these are not toll-free numbers and regular billing rates will apply). Enter the conference ID, 7677, after you enter the extension:

<ul>
<li>US/California/Mountain View: +1 650 903 0800, extension 92
<li>US/California/San Francisco: +1 415 762 5700, extension 92
<li>US/Oregon/Portland: +1 971 544 8000, extension 92
<li>CA/Vancouver: +1 778 785 1540, extension 92
<li>CA/Toronto: +1 416 848 3114, extension 92
<li>UK/London: +44 (0)207 855 3000, extension 92
<li>FR/Paris: +33 1 84 88 37 37, extension 92
</ul>

 Calendar ICS File : http://bit.ly/mozsciencecall-ics
 Subscribe to Calender : http://bit.ly/mozsciencecalls

=== What is the Science Lab Meeting? ===

The Science Lab meeting is our community call, taking place the second Thursday of every month, highlighting what we're up to as well as work of the community relevant to science and the web. Join us to hear more about current projects, ways you can get involved, and discuss issues around open science. The calls are made stronger by your participation, so do join us.

Join us on the second Thursday of every month // 11 am Eastern .

Hear more about what we're up to, ask questions, and interact with other call participants. Join us.

===Call archives===
* [https://etherpad.mozilla.org/sciencelab-calls-nov14 November 14, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-dec12 December 12, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-jan9-2014 January 9, 2014]
* [http://etherpad.mozilla.org/sciencelab-calls-feb13-2014 February 13, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-mar20-2014 March 20, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-apr10-2014 April 10, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-may08-2014 May 8, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-june12-2014 June 12, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-aug14-2014 August 14, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-sep11-2014 September 11, 2014]

ScienceLab/Calls

2014-09-11T17:37:45Z

Abby: /* Call archives */

__NOTOC__
=== Science Lab Community Calls ===
Second Thursday of every month

'''Our next call:''' August 14 2014, 8 am PDT / 11 am EDT / 4 pm BST

Conference Number: +1 800 707 2533,
Password: 369
Room: 7677

If you have trouble accessing the above number, try one of the following numbers (note these are not toll-free numbers and regular billing rates will apply). Enter the conference ID, 7677, after you enter the extension:

<ul>
<li>US/California/Mountain View: +1 650 903 0800, extension 92
<li>US/California/San Francisco: +1 415 762 5700, extension 92
<li>US/Oregon/Portland: +1 971 544 8000, extension 92
<li>CA/Vancouver: +1 778 785 1540, extension 92
<li>CA/Toronto: +1 416 848 3114, extension 92
<li>UK/London: +44 (0)207 855 3000, extension 92
<li>FR/Paris: +33 1 84 88 37 37, extension 92
</ul>

 Calendar ICS File : http://bit.ly/mozsciencecall-ics
 Subscribe to Calender : http://bit.ly/mozsciencecalls

=== What is the Science Lab Meeting? ===

The Science Lab meeting is our community call, taking place the second Thursday of every month, highlighting what we're up to as well as work of the community relevant to science and the web. Join us to hear more about current projects, ways you can get involved, and discuss issues around open science. The calls are made stronger by your participation, so do join us.

Join us on the second Thursday of every month // 11 am Eastern .

Hear more about what we're up to, ask questions, and interact with other call participants. Join us.

===Call archives===
* [https://etherpad.mozilla.org/sciencelab-calls-nov14 November 14, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-dec12 December 12, 2013]
* [https://etherpad.mozilla.org/sciencelab-calls-jan9-2014 January 9, 2014]
* [http://etherpad.mozilla.org/sciencelab-calls-feb13-2014 February 13, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-mar20-2014 March 20, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-apr10-2014 April 10, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-may08-2014 May 8, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-june12-2014 June 12, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-aug14-2014 August 14, 2014]
* [https://etherpad.mozilla.org/sciencelab-calls-sep11-2014 September 11, 2014]

ScienceLab

2014-08-19T16:08:36Z

Abby: /* The team */

__NOTOC__
<section begin=summary />{{RoadmapSummary
|icon=Mozilla_science_lab_logo-icon.jpg‎
|pagelocation=ScienceLab
|pagetitle=Mozilla Science Lab
|updated=Jan 13, 2014
|owner=Kaitlin Thaney
|description=The Mozilla Science Lab is an initiative of the Mozilla Foundation exploring how the power of the open web can change the way science is done. We build educational resources, tools and prototypes for the research community to make science more open, collaborative and efficient. For more, visit [http://mozillascience.org mozillascience.org].
}}<section end=summary />

== The vision ==

The web has revolutionized many aspects of our everyday life, from media to education and business. But even though the web was invented ''by scientists'', we still have not yet seen it change scientific practice to nearly the same extent. In scientific research, we’re dealing with special circumstances, trying to innovate upon hundreds of years of entrenched norms and practices, broken incentive structures and gaps in training that are dramatically slowing down the system, keeping us from making the steps forward needed to better society.

The aim of the Science Lab is to foster an ongoing dialogue between the open web community and researchers to tackle this challenge. Together they'll share ideas, tools and best practices for using next-generation web solutions to solve real problems in science, and explore ways to make research faster, more agile and collaborative.

== Focus areas ==

=== Code and data literacy ===

Digital literacy is as important as reading, writing and arithmetic. In academia, skills training to match the tools and technology is still leagues behind where it should be. We need to find a way to better empower students to be "digital researchers" by shortening the gap and providing the means for them to learn how to share, reuse and reproduce research on the web.

==== Software Carpentry ====

Software Carpentry helps researchers be more productive by teaching them basic computing skills. Its volunteers have run over 90 intensive two-day boot camps at dozens of sites around the world in the last 18 months for over 2500 scientists, and the site provides open access material online for self-paced instruction. For more on Software Carpentry, [http://software-carpentry.org/ visit their website].

=== Support and innovate with the community ===

There are some incredible tools out there pushing the limits to what the future of science on the web can be. We want to help support that work as well as find ways to help coordinate efforts and innovate together.

=== Convening a global conversation ===

Science is a global enterprise, and this needs to be a global conversation. We want to make sure we are getting tools into the hands of the people who need them most, and continually soliciting your thoughts about how we can, together, work towards more open, efficient science on the web.

== The team ==

* Kaitlin Thaney (Director, Mozilla Science Lab): Kaitlin came to Mozilla from Digital Science, a technology company that works to make research more efficient through better use of software. She also advises the UK government on digital technology, is a Director for DataKind UK, and chairs the London Strata Conference series on big data. Prior to Mozilla and Digitial Science, Kaitlin managed the science program at Creative Commons, worked on education technology with MIT and Microsoft, and wrote for the Boston Globe. You can follow her at [http://twitter.com/kaythaney/ @kaythaney].

* Greg Wilson (project lead, Software Carpentry): Greg started the Software Carpentry project in 1998. He has been a professional software developer, an author, and a university professor, and was the lead editor for ''[http://www.amazon.com/Beautiful-Code-Leading-Programmers-Practice/dp/0596510047/ Beautiful Code]'', ''[http://www.amazon.com/Making-Software-Really-Works-Believe/dp/0596808321/ Making Software]'', and ''[http://aosabook.org The Architecture of Open Source Applications]''. You can follow him at [http://twitter.com/gvwilson @gvwilson].

* Arliss Collins (bootcamp facilitator): Arliss handles communication, scheduling and administration for Software Carpentry bootcamps and trainings. In her previous life she was a geophysical engineer and an IT analyst.

* Abigail Cabunoc (lead developer, Mozilla Science Lab): Abby comes to Mozilla after longtime contributions to open source projects helping science. Previously at the Ontario Institute for Cancer Research where she led development on WormBase, an online biological database aiding nematode research, she bring some serious worm knowledge to the team, as well as a background in bioinformatics and computer science. Abby's also an active member of the Toronto software development community as a mentor and educator. You can follow her at [http://twitter.com/abbycabs @abbycabs].

== How to get involved ==

* '''Twitter''': [http://twitter.com/mozillascience @MozillaScience], [http://twitter.com/swcarpentry @swcarpentry]
* '''[https://wiki.mozilla.org/ScienceLab/Calls Join our community calls]''': Second Thursday of every month. Come hear more about what we're up to, interact with community members and join the conversation.
* '''Join us for a Software Carpentry bootcamp''': [http://software-carpentry.org/bootcamps/index.html a list of upcoming events], and [http://mozillascience.org/get-involved/ how you can get involved]
* Follow our planning here on the wiki, for new ways to get involved over the coming week. We'll be hosting community calls, running events, and providing other means for you to join the conversation. Stay tuned.

== Support ==

The Mozilla Science Lab is supported by the [http://www.sloan.org Alfred P. Sloan Foundation]. If you'd like to find out how you too can support the Science Lab, [mailto:kaitlin@mozillafoundation.org contact us].

ScienceLab

2014-08-19T15:50:46Z

Abby: /* The team */

__NOTOC__
<section begin=summary />{{RoadmapSummary
|icon=Mozilla_science_lab_logo-icon.jpg‎
|pagelocation=ScienceLab
|pagetitle=Mozilla Science Lab
|updated=Jan 13, 2014
|owner=Kaitlin Thaney
|description=The Mozilla Science Lab is an initiative of the Mozilla Foundation exploring how the power of the open web can change the way science is done. We build educational resources, tools and prototypes for the research community to make science more open, collaborative and efficient. For more, visit [http://mozillascience.org mozillascience.org].
}}<section end=summary />

== The vision ==

The web has revolutionized many aspects of our everyday life, from media to education and business. But even though the web was invented ''by scientists'', we still have not yet seen it change scientific practice to nearly the same extent. In scientific research, we’re dealing with special circumstances, trying to innovate upon hundreds of years of entrenched norms and practices, broken incentive structures and gaps in training that are dramatically slowing down the system, keeping us from making the steps forward needed to better society.

The aim of the Science Lab is to foster an ongoing dialogue between the open web community and researchers to tackle this challenge. Together they'll share ideas, tools and best practices for using next-generation web solutions to solve real problems in science, and explore ways to make research faster, more agile and collaborative.

== Focus areas ==

=== Code and data literacy ===

Digital literacy is as important as reading, writing and arithmetic. In academia, skills training to match the tools and technology is still leagues behind where it should be. We need to find a way to better empower students to be "digital researchers" by shortening the gap and providing the means for them to learn how to share, reuse and reproduce research on the web.

==== Software Carpentry ====

Software Carpentry helps researchers be more productive by teaching them basic computing skills. Its volunteers have run over 90 intensive two-day boot camps at dozens of sites around the world in the last 18 months for over 2500 scientists, and the site provides open access material online for self-paced instruction. For more on Software Carpentry, [http://software-carpentry.org/ visit their website].

=== Support and innovate with the community ===

There are some incredible tools out there pushing the limits to what the future of science on the web can be. We want to help support that work as well as find ways to help coordinate efforts and innovate together.

=== Convening a global conversation ===

Science is a global enterprise, and this needs to be a global conversation. We want to make sure we are getting tools into the hands of the people who need them most, and continually soliciting your thoughts about how we can, together, work towards more open, efficient science on the web.

== The team ==

* Kaitlin Thaney (Director, Mozilla Science Lab): Kaitlin came to Mozilla from Digital Science, a technology company that works to make research more efficient through better use of software. She also advises the UK government on digital technology, is a Director for DataKind UK, and chairs the London Strata Conference series on big data. Prior to Mozilla and Digitial Science, Kaitlin managed the science program at Creative Commons, worked on education technology with MIT and Microsoft, and wrote for the Boston Globe. You can follow her at [http://twitter.com/kaythaney/ @kaythaney].

* Greg Wilson (project lead, Software Carpentry): Greg started the Software Carpentry project in 1998. He has been a professional software developer, an author, and a university professor, and was the lead editor for ''[http://www.amazon.com/Beautiful-Code-Leading-Programmers-Practice/dp/0596510047/ Beautiful Code]'', ''[http://www.amazon.com/Making-Software-Really-Works-Believe/dp/0596808321/ Making Software]'', and ''[http://aosabook.org The Architecture of Open Source Applications]''. You can follow him at [http://twitter.com/gvwilson @gvwilson].

* Arliss Collins (bootcamp facilitator): Arliss handles communication, scheduling and administration for Software Carpentry bootcamps and trainings. In her previous life she was a geophysical engineer and an IT analyst.

* Abigail Cabunoc (lead developer, Mozilla Science Lab): Abby comes to Mozilla after longtime contributions to open source projects helping science. Previously at the Ontario Institute for Cancer Research where she lead development on WormBase, an online biological database aiding nematode research, she bring some serious worm knowledge to the team, as well as a background in bioinformatics and computer science. Abby's also an active member of the Toronto software development community as a mentor and educator. You can follow her at [http://twitter.com/abbycabs @abbycabs].

== How to get involved ==

* '''Twitter''': [http://twitter.com/mozillascience @MozillaScience], [http://twitter.com/swcarpentry @swcarpentry]
* '''[https://wiki.mozilla.org/ScienceLab/Calls Join our community calls]''': Second Thursday of every month. Come hear more about what we're up to, interact with community members and join the conversation.
* '''Join us for a Software Carpentry bootcamp''': [http://software-carpentry.org/bootcamps/index.html a list of upcoming events], and [http://mozillascience.org/get-involved/ how you can get involved]
* Follow our planning here on the wiki, for new ways to get involved over the coming week. We'll be hosting community calls, running events, and providing other means for you to join the conversation. Stay tuned.

== Support ==

The Mozilla Science Lab is supported by the [http://www.sloan.org Alfred P. Sloan Foundation]. If you'd like to find out how you too can support the Science Lab, [mailto:kaitlin@mozillafoundation.org contact us].