MOSS: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Reorganize MOSS pages to split into tracks)
(Removing link to mailing list)
 
(51 intermediate revisions by 9 users not shown)
Line 1: Line 1:
==Program Overview==
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].


Mozilla Open Source Support (MOSS) is an awards program specifically focused on supporting the [http://opensource.org/osd Open Source] and [http://www.gnu.org/philosophy/free-sw.en.html Free Software] movement, with an initial allocation of USD $1 million.
MOSS currently has 3 tracks:


Mozilla is a part of the Open Source and Free Software movement. We were born out of this movement. We prosper because of the technology and activism which comes from this movement. And we know that Open Source and Free Software remains a key part of the Internet and the online life we seek to build. We have had an ad-hoc grants program for many years. MOSS is a systematic way to provide a new level of support to this community.
* MOSS Track 1 - [https://www.mozilla.org/en-US/moss/foundational-technology/ Foundational Technology]
* MOSS Track 2 - [https://www.mozilla.org/en-US/moss/mission-partners/ Mission Partners]
* MOSS Track 3 - [https://www.mozilla.org/en-US/moss/secure-open-source/ Secure Open Source]


The Mozilla Open Source Support program is designed to recognize and celebrate communities who are leading the way with open source projects that contribute to our work and the health of the Web.  It encompasses a “give back” element for Open Source and Free Software projects that Mozilla relies on (the "Foundational Technology" track), a “give forward” element for supporting other projects whose goals are in alignment with ours (the "Mission Partners" track), and an element for improving the security of the open source ecosystem (the "Secure Open Source" track).  
Use the links above to find out about each track, including details on how to apply.


* MOSS Track 1 - [[MOSS/Foundational Technology|Foundational Technology]]
==Application Deadlines==
* MOSS Track 2 - [[MOSS/Mission Partners|Mission Partners]] (not yet active)
* MOSS Track 3 - [[MOSS/Secure Open Source|Secure Open Source]]


To stay informed about and involved with this work, please join the MOSS [https://www.mozilla.org/en-US/about/forums/#moss discussion forum].
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.


==Mozilla Champions==
==Selection Committee==


For the "Foundational Technology" track, and perhaps later for other tracks, applications need to be jointly submitted by the project and a Mozilla Champion. A Champion is an established member of the Mozilla community who knows the project concerned. Being a champion means you believe in the project and its impact.  You believe that funds from a MOSS Award would make a meaningful difference in the success and effectiveness of the project. You believe the range of funds requested in the Award proposal is appropriate. And you believe that the project and/or the task fit the award criteria for the track you are applying for.
We have formed a selection committee of 8 participants to assess awards on Tracks 1 and 2, as follows:


A champion does a few different things:  
* '''Current Committed Mozillians''' - they bring a good working knowledge of Mozilla's day-to-day activities and how various open source projects are used.
** [https://mozillians.org/en-US/u/lthomson/ Laura Thomson]
** [https://ritter.vg/ Tom Ritter]


* sponsors the project’s award proposal (it is akin to vouching for someone);
* '''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.
* serves as the liaison between that project and Mozilla with regard to the award;
** [http://stormyscorner.com/ Stormy Peters]
* reviews the effectiveness of the award funds after an agreed upon period, to help Mozilla improve the effectiveness and impact of the MOSS program.
** [https://mozillians.org/en-US/u/rbarnes/ Richard Barnes]


This review process might involve answering a set of standard assessment questions at the mid-point and at the end of the award period, and giving your written opinion of the overall success of the award. The time commitment should not be massive, but it will require thoughtfulness and honesty.
* '''Other Open Source Experts''' - they bring knowledge of the role of different projects within the open source ecosystem.
** [http://www.cmu.edu/iii/innovators/faculty-staff/wasserman.html Tony Wasserman]
** [https://www.justindorfman.com/ Justin Dorfman]
 
==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.
 
* [[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]]
 
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.
* [https://mozillians.org/u/jcook/ Jim Cook]. Jim is Mozilla's Chief Financial Officer, and can provide assistance for those interested in the financial side of things. Jim knows a lot about cost and value!


==FAQs==
==Recipients==


;What if my project doesn’t have a legal organizational home?  I see this is disfavoured, and exceptional circumstances are required. What might count as "exceptional"?
'''''April 2019 Update: This project list is out of date, please see the [https://github.com/mozilla/MOSS-Directory/ MOSS Directory on GitHub]'''''  
: You tell us. If a project doesn't have a legal organizational home, we will be handing a large sum of money to an individual with only limited accountability. This means a higher level of complexity and risk. So you need to describe why it's reasonable and important for us to accept that additional risk. We will listen because Mozilla is a pretty flexible organization, but we can’t promise the result will be as you hope.


;What about tax?
* [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
: Recipients are responsible to determine the tax implications of receiving an award, based on their respective countries’ tax laws and compliance requirements. Amounts applied for should be sized such that any tax or other liability that will be incurred is accounted for. Mozilla reserves the right to use different payment mechanisms or tax characterisations for different awards in the MOSS program based on a number of factors specific to the award.
* [https://blog.mozilla.org/blog/2016/04/13/mozilla-open-source-support-moss-update-q1-2016/ 2016-04-13]: Django REST Framework, The Intern
* [https://blog.mozilla.org/blog/2016/06/22/mozilla-awards-385000-to-open-source-projects-as-part-of-moss-mission-partners-program/ 2016-06-22]: Tor, Tails, Caddy, Mio, DNSSEC/DANE Chain Stapling, Godot Engine, PeARS, NVDA
* [https://blog.mozilla.org/blog/2016/08/04/mozilla-awards-585000-to-nine-open-source-projects-in-q2-2016/ 2016-08-04]: PyPy
* [https://blog.mozilla.org/blog/2016/10/03/moss-supports-four-more-open-source-projects-with-300k/ 2016-10-03]: Redash, Review Board, Kea, Speech Rule Engine
* [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/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.mozilla.org/index.php?title=MOSS&oldid=1230917"