MOSS: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Clarify which bits of MOSS are active now)
(Removing link to mailing list)
 
(54 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 a grant 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 will encompass both: a) a “give back” element for Open Source and Free Software projects that Mozilla relies on; and b) a “give forward” element for supporting other projects where financial resources from Mozilla can make our entire community more successful. We will identify crisp names for these elements as we go forward.
Use the links above to find out about each track, including details on how to apply.


Currently, only the "give back" element (a.k.a. "Projects Mozilla Relies On" - still looking for a name) is active, and the information below relates to that.
==Application Deadlines==


=="Projects Mozilla Relies On"==
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 relies on [[MOSS/Projects_in_use_by_Mozilla|a number of open source and free software projects]] (please help fill out that list). In some cases the software produced by these projects is incorporated into Mozilla products.  In other cases we rely on as part of our infrastructure or to get our jobs done.
==Selection Committee==


===Project Criteria===
We have formed a selection committee of 8 participants to assess awards on Tracks 1 and 2, as follows:
 
Projects which Mozilla uses or relies on and who are in need of funds are welcome to apply for an award. Awards should be jointly submitted by the leader of a project and an established Mozillian who will champion the grant. The project/people need to meet the following criteria:
 
* Grant requests should be for the amount of financial support that helps accomplish a clear and current project goal. Projects that don’t have a need for funds at this time can be considered when such a need arises. A $10,000 grant request is just as valid as a $50,000 or $100,000 request.
 
* The money must be used to benefit the project, but it does not have to be used on things which themselves would directly benefit Mozilla.
 
* The project’s home can be anywhere in the world where we can make payment without undue burden. We have a reasonably strong preference for funding legal organizations rather than individuals representing projects, although exceptional circumstances could lead to some flexibility.
 
* The Mozillian champion may be (but does not need to be) a project contributor to the project they are championing.
 
* The Mozillian champion must vouch for the usefulness of the software, commit to monitoring the project, and report on the effectiveness of the grant after the money is spent (perhaps using a standardized form). They will also make themselves available to the application evaluation committee to help them assess the appropriateness of the grant to the needs of the project.
 
We expect the vast majority of MOSS grants to be singular rather than regular - that is, support for doing a particular defined thing, rather than ongoing support for a project in general. However a previous award proposal, successful or unsuccessful, does not disqualify a project from applying again.
 
===Selection Criteria===
 
These are a work in progress; further feedback is welcome on the MOSS mailing list until November 8th. All criteria are indicative rather than determinative - that is to say, they will make us more or less likely to make an award, but none will guarantee a particular outcome.
 
* How reliant is Mozilla on the project's technology?
* Do others also rely on it outside of Mozilla products?
* Is the technology unique? Are they doing something different?
* What role does the project play in the open source ecosystem?
* What sort of reputation does the project have in general, if any? 
** This includes reputation in technical, inclusion and other areas
** Is the project known for something besides the code we are relying on?
* Will this grant make a significant impact on the project?
* Is the level of funding appropriate for the task to be accomplished?
* Does the person (or group) who will receive the money have a track record of delivering? 
* What does the champion have to say? Is the case compelling?
 
===Selection Committee===
 
We have formed a selection committee of 7 participants, 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.
* '''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/bkerensa/ Benjamin Kerensa]
** [https://mozillians.org/en-US/u/lthomson/ Laura Thomson]
** [https://mozillians.org/en-US/u/laura/ Laura Thomson]
** [https://ritter.vg/ Tom Ritter]
** [https://mozillians.org/en-US/u/dougt/ Doug Turner]


* '''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]


* '''Other Open Source Experts''' - they bring knowledge of the role of different projects within the open source ecosystem.
* '''Other Open Source Experts''' - they bring knowledge of the role of different projects within the open source ecosystem.
** [http://www.rcbowen.com/ Rich Bowen]
** [http://www.cmu.edu/iii/innovators/faculty-staff/wasserman.html Tony Wasserman]
** [https://www.cmu.edu/silicon-valley/faculty-staff/wasserman-tony.html Tony Wasserman]
** [https://www.justindorfman.com/ Justin Dorfman]
 
==Other Tracks==
 
In the future, MOSS will have other tracks. We are developing one with a particular focus on providing security audit and remediation for key projects with a significant attack surface and exposure. These may have similar or different application criteria, or they may not have a public application process at all.
 
==How To Apply==
 
The application form is [https://docs.google.com/a/mozilla.com/forms/d/1Pa5IsuhT6vMUfg0HUXxr7SzrSwq5fpiZfZIJVPxN1Mc/viewform here].
 
==FAQs==
 
;What does it mean to “champion” a project for a MOSS Award?
: 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.  And you believe the range of funds requested in the Award proposal is appropriate.  In the case of the “give back” category of awards you should also also believe that project has meaningful impact on Mozilla’s work.
 
: A champion does a few different things:
* sponsors the project’s award proposal (it is akin to vouching for someone);
* serves as the liaison between that project and Mozilla with regard to the award;
* reviews the effectiveness of the award funds after an agreed upon period, to help Mozilla improve the effectiveness and impact of the MOSS program.


This review process might involve answering a set of standard assessment questions at the mid-point and at the end of the grant 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.
==Applicant/Awardee Resources==


;What if the project I care most about doesn’t have a legal organizational home?  I see this is disfavored and exceptional circumstances are required. What might count as "exceptional"?
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.
: 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.


;How can I, as a Mozillian, get started while the terms of the application and evaluation process are being finalized?
* [[Media:Tor-sow.odt|Sample Schedule of Work (SoW) for Tor Project Metrics]]
: Here are some things you can do immediately:
* [[Media:Kea-sow.pdf|Sample Schedule of Work (SoW) for Kea DHCP Server]]
* Do some due diligence with other community members. Find out if others share your sense of a project’s impact.
* Identify a contact inside the project who is a good person to talk to about such things.  Not every project needs funds all the time.  Explore whether there is a current need within the project that could be met with a MOSS award. If there is such a need then turn to exploring the size of the amount. Think about the impact that could occur at several different ranges of money.
* If you find a project you care about has other types of needs, note that in the project list above. We aren't yet thinking about non-financial support, but we may do that in the future.
* If you are interested in participating in the finalization of the program criteria, join the discussion.


;Can I get help with thinking about or preparing a proposal? I’m not that practiced at figuring out ranges of funding, or I’d like help in thinking about the need.
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]].
: So far we have three identified mentors: [https://blog.mozilla.org/press/bios/david-bryant/ David Bryant], [https://mozillians.org/en-US/u/pfinette/ Pascal Finette] and [https://blog.mozilla.org/press/bios/jim-cook/ Jim Cook].  David is obviously clueful about software, and he’s also signed on to assist with the topics of project needs, possible solutions and appropriate amounts.  For those of you who don’t know Pascal, he 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.  Our CFO Jim Cook will provide assistance for those interested in the financial side of things.  And Jim knows a lot about cost and value! We’ll look into adding to this list.


;Is there an amount of an award that is expected?  Or a size that is too big or too small?
==Mentors==
: In the next week we expect to identify a range within which we prefer the Awards proposals land, and to have some guidance what to do if you believe an Award really should be smaller or larger. At the moment, we are looking at a minimum of $10,000, and a maximum of $250,000.


;What’s happening by [[Coincidental_work_weeks/2015_Orlando|Orlando]]?
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:
: Identification of the first set of projects we want to celebrate and fund. This way we can make the program tangible while we are together.


;How does the $1 million work?  Does it all get allocated at Orlando?  How does the $1 million figure interact with the “up to 10 projects” goal?
* [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.
: The $1 million is the initial allocation for the MOSS program. We will evaluate the program as we go.  It is our hope and expectation that the program provides value to the recipients and the Open Source ecosystem, and we expect to make additional allocations to the MOSS program in the future.
* [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.


: We want to focus on making up to 10 good awards, to projects we think are great, where an award can make a real difference, and where we’ve had time to interact with the project and its leadership.  More than 10 is difficult to impossible to do well before Orlando.  Indeed, 10 may turn out to be more than we can manage.
==Recipients==


: It is conceivable that the 10 awards could use the entire first $1 million allocation, but this is not a goal, and seems unlikely.
'''''April 2019 Update: This project list is out of date, please see the [https://github.com/mozilla/MOSS-Directory/ MOSS Directory on GitHub]'''''


;How can I stay informed and involved with this work?
* [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
: Please join the MOSS [https://lists.mozilla.org/listinfo/moss public mailing list].
* [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"