MOSS: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Update Application Deadlines - oops)
(Removing link to mailing list)
 
(15 intermediate revisions by 5 users not shown)
Line 1: Line 1:
Mozilla Open Source Support (MOSS) has a [https://www.mozilla.org/moss new website] - see there for a program overview. You can also read our [https://blog.mozilla.org/wp-content/uploads/2017/04/MOSS_2016_review_april_25-v.1.0.pdf 2016 Review and 2017 Strategic Plan].
Mozilla Open Source Support (MOSS) awards recognize, celebrate, and support open source projects that contribute to Mozilla’s work and to the health of the Internet. Learn more about MOSS awards on the  [https://www.mozilla.org/en-US/moss/ project website].


MOSS currently has 3 tracks:
MOSS currently has 3 tracks:


* MOSS Track 1 - [[MOSS/Foundational Technology|Foundational Technology]]
* MOSS Track 1 - [https://www.mozilla.org/en-US/moss/foundational-technology/ Foundational Technology]
* MOSS Track 2 - [[MOSS/Mission Partners|Mission Partners]]
* MOSS Track 2 - [https://www.mozilla.org/en-US/moss/mission-partners/ Mission Partners]
* MOSS Track 3 - [[MOSS/Secure Open Source|Secure Open Source]]
* MOSS Track 3 - [https://www.mozilla.org/en-US/moss/secure-open-source/ Secure Open Source]


Use the links above to find out about each track, including details on how to apply. To stay informed about and involved with MOSS in general, please join the MOSS [https://www.mozilla.org/en-US/about/forums/#moss discussion forum]. And whether you apply successfully or not, if your open source project is looking for support you may be interested in contacting some of our [[MOSS/Friends|friends]].
Use the links above to find out about each track, including details on how to apply.


==Application Deadlines==
==Application Deadlines==


We consider MOSS applications in batches; deadline for the next batch is the last day of January 2018, and then every three months thereafter. Missing a deadline may cause a delay in the consideration of your application.
The review committee meets to consider MOSS applications in batches each month. Applications are considered in the order in which they are received and applicants can normally expect a response within 4-6 weeks, though this can vary based on current application volume.


==Selection Committee==
==Selection Committee==
Line 23: Line 23:
* '''Senior Mozilla Alumni''' - they are no longer actively involved with Mozilla on a day-to-day basis but have a deep understanding of our project and a different/outside perspective.
* '''Senior Mozilla Alumni''' - they are no longer actively involved with Mozilla on a day-to-day basis but have a deep understanding of our project and a different/outside perspective.
** [http://stormyscorner.com/ Stormy Peters]
** [http://stormyscorner.com/ Stormy Peters]
** [http://shaver.off.net/diary/ Mike Shaver]
** [https://mozillians.org/en-US/u/rbarnes/ Richard Barnes]
** [https://mozillians.org/en-US/u/rbarnes/ Richard Barnes]


Line 36: Line 35:
* [[Media:Tor-sow.odt|Sample Schedule of Work (SoW) for Tor Project Metrics]]
* [[Media:Tor-sow.odt|Sample Schedule of Work (SoW) for Tor Project Metrics]]
* [[Media:Kea-sow.pdf|Sample Schedule of Work (SoW) for Kea DHCP Server]]
* [[Media:Kea-sow.pdf|Sample Schedule of Work (SoW) for Kea DHCP Server]]
If your application is successful and you find yourself doing a blog post or conference talk about your work, we would appreciate a mention. Find some useful guidance at [[MOSS/Talking About Your MOSS Award|Talking About Your MOSS Award]].


==Mentors==
==Mentors==


Some projects may want to apply for a MOSS award but be nervous about preparing a proposal. We have identified three mentors who are willing to help with this, and you should feel free to contact any of them:  
Some projects may want to apply for a MOSS award but be nervous about preparing a proposal. We have identified some mentors who are willing to help with this, and you should feel free to contact any of them:  


* [https://mozillians.org/u/dbryant/ David Bryant]. David is Mozilla's VP of Platform Engineering, so he is obviously clueful about software, and he’s also signed on to assist with the topics of project needs, possible solutions and appropriate amounts.
* [https://mozillians.org/u/dbryant/ David Bryant]. David is a Fellow in Mozilla's Emerging Technologies organization and also led Mozilla's Platform Engineering organization in the past. He is comfortably clueful about software, and has also signed on to assist with the topics of project needs, possible solutions and appropriate amounts.
* [https://mozillians.org/u/pfinette/ Pascal Finette]. Pascal launched [http://webfwd.org WebFWD] when he was a Mozilla employee and now runs Singularity University’s [http://startup.singularityu.org/accelerator/ accelerator program].  Pascal has a long history and an abiding love of working with people to build things. He has great expertise in this type of task, matching by his abiding interest in contributing to Mozilla.
* [https://mozillians.org/u/pfinette/ Pascal Finette]. Pascal launched [http://webfwd.org WebFWD] when he was a Mozilla employee and now runs Singularity University’s [http://startup.singularityu.org/accelerator/ accelerator program].  Pascal has a long history and an abiding love of working with people to build things. He has great expertise in this type of task, matching by his abiding interest in contributing to Mozilla.


==Recipients==
==Recipients==
'''''April 2019 Update: This project list is out of date, please see the [https://github.com/mozilla/MOSS-Directory/ MOSS Directory on GitHub]'''''


* [https://blog.mozilla.org/blog/2015/12/10/mozilla-open-source-support-first-awards-made/ 2015-12-10]: Buildbot, CodeMirror, Discourse, Read The Docs, Mercurial, Django, Bro
* [https://blog.mozilla.org/blog/2015/12/10/mozilla-open-source-support-first-awards-made/ 2015-12-10]: Buildbot, CodeMirror, Discourse, Read The Docs, Mercurial, Django, Bro
Line 53: Line 56:
* [https://blog.mozilla.org/blog/2017/04/10/mozilla-awards-365000-to-open-source-projects-as-part-of-moss/ 2017-04-10]: SecureDrop, libjpeg-turbo, LLVM, LEAP Encryption Access Project, Tokio
* [https://blog.mozilla.org/blog/2017/04/10/mozilla-awards-365000-to-open-source-projects-as-part-of-moss/ 2017-04-10]: SecureDrop, libjpeg-turbo, LLVM, LEAP Encryption Access Project, Tokio
* [https://blog.mozilla.org/blog/2017/10/03/mozilla-awards-half-million-open-source-projects/ 2017-10-03]: Ushahidi, webpack, RiseUp, Phaser, mod_md
* [https://blog.mozilla.org/blog/2017/10/03/mozilla-awards-half-million-open-source-projects/ 2017-10-03]: Ushahidi, webpack, RiseUp, Phaser, mod_md
* [https://blog.mozilla.org/blog/2018/01/23/moss-q4-supporting-python-ecosystem/ 2018-01-23]: [https://pyfound.blogspot.com/2017/11/the-psf-awarded-moss-grant-pypi.html Python Package Index (PyPI)], Harfbuzz, Zappa, Tatoeba, Tor Project’s Open Observatory of Network Interference, Commento, libav/rust-av
* [https://blog.mozilla.org/blog/2019/01/03/moss-2018-year-in-review/ 2019-01-03]: SecureDrop, Tor, Processing Foundation, Dat, autoEdit2, Jandig, Open Data for Outbreak Science, Psych-DS, VRStoryGram, WorldBrain.io, Streetmix, Push, MoodleNet, Ciberseguras, Smart Greenhouse Monitoring System, CiviCRM Core Support and Development Inquiry, Engage, TorBirdy, and several others
* ...
* ...

Latest revision as of 19:53, 18 September 2020

Mozilla Open Source Support (MOSS) awards recognize, celebrate, and support open source projects that contribute to Mozilla’s work and to the health of the Internet. Learn more about MOSS awards on the project website.

MOSS currently has 3 tracks:

Use the links above to find out about each track, including details on how to apply.

Application Deadlines

The review committee meets to consider MOSS applications in batches each month. Applications are considered in the order in which they are received and applicants can normally expect a response within 4-6 weeks, though this can vary based on current application volume.

Selection Committee

We have formed a selection committee of 8 participants to assess awards on Tracks 1 and 2, as follows:

  • Current Committed Mozillians - they bring a good working knowledge of Mozilla's day-to-day activities and how various open source projects are used.
  • Senior Mozilla Alumni - they are no longer actively involved with Mozilla on a day-to-day basis but have a deep understanding of our project and a different/outside perspective.
  • Other Open Source Experts - they bring knowledge of the role of different projects within the open source ecosystem.

Applicant/Awardee Resources

The application form has an "Outcomes" section, and any award will require a contract or agreement with a Schedule of Work (SoW) which defines what work is to be done. Both of those things might benefit from examining a sample Schedule of Work.

If your application is successful and you find yourself doing a blog post or conference talk about your work, we would appreciate a mention. Find some useful guidance at Talking About Your MOSS Award.

Mentors

Some projects may want to apply for a MOSS award but be nervous about preparing a proposal. We have identified some mentors who are willing to help with this, and you should feel free to contact any of them:

  • David Bryant. David is a Fellow in Mozilla's Emerging Technologies organization and also led Mozilla's Platform Engineering organization in the past. He is comfortably clueful about software, and has also signed on to assist with the topics of project needs, possible solutions and appropriate amounts.
  • Pascal Finette. Pascal launched WebFWD when he was a Mozilla employee and now runs Singularity University’s accelerator program. Pascal has a long history and an abiding love of working with people to build things. He has great expertise in this type of task, matching by his abiding interest in contributing to Mozilla.

Recipients

April 2019 Update: This project list is out of date, please see the MOSS Directory on GitHub

  • 2015-12-10: Buildbot, CodeMirror, Discourse, Read The Docs, Mercurial, Django, Bro
  • 2016-04-13: Django REST Framework, The Intern
  • 2016-06-22: Tor, Tails, Caddy, Mio, DNSSEC/DANE Chain Stapling, Godot Engine, PeARS, NVDA
  • 2016-08-04: PyPy
  • 2016-10-03: Redash, Review Board, Kea, Speech Rule Engine
  • 2017-04-10: SecureDrop, libjpeg-turbo, LLVM, LEAP Encryption Access Project, Tokio
  • 2017-10-03: Ushahidi, webpack, RiseUp, Phaser, mod_md
  • 2018-01-23: Python Package Index (PyPI), Harfbuzz, Zappa, Tatoeba, Tor Project’s Open Observatory of Network Interference, Commento, libav/rust-av
  • 2019-01-03: SecureDrop, Tor, Processing Foundation, Dat, autoEdit2, Jandig, Open Data for Outbreak Science, Psych-DS, VRStoryGram, WorldBrain.io, Streetmix, Push, MoodleNet, Ciberseguras, Smart Greenhouse Monitoring System, CiviCRM Core Support and Development Inquiry, Engage, TorBirdy, and several others
  • ...
Retrieved from "https://wiki.allizom.org/index.php?title=MOSS&oldid=1230917"