MOSS: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Removing link to mailing list)
 
(78 intermediate revisions by 11 users not shown)
Line 1: Line 1:
=== <p>'''Program Overview'''</p> ===
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].


In October 2015, we are launching a grant program of up to $1 million specifically focused on supporting the Open Source and Free Software movement.  We invite you to help further develop the program and to participate in identifying and championing grantees.
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 a grant program for many years.  Now it is time to formalize 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 Awards 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 both: a) a “give back”  element for Open Source and Free Software projects that Mozilla relies on; and b) a “give forward” component for supporting other projects where financial resources from Mozilla can make our entire community more successful.
Use the links above to find out about each track, including details on how to apply.


===<p>'''Project Criteria: Projects Mozilla Relies On'''</p>===
==Application Deadlines==


Mozilla relies on a number of open source and free software projects.  In some cases the software produced by these projects isincorporated into Mozilla products.  In other cases we rely on as part of our infrastructure or to get our jobs done. Projects which fit into this category and who are in need of funds are welcome to apply for an award.
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.


* Awards should be jointly submitted by the leader of a project and an established Mozillian who will champion the grant.
==Selection Committee==


* The Mozillian may be (but does not need to be) a project contributor to the project they are championing.
We have formed a selection committee of 8 participants to assess awards on Tracks 1 and 2, as follows:


* The Mozillian 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. They will also work with the application evaluation committee to help them assess the appropriateness of the grant to the needs of the project.
* '''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]


* 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.  
* '''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]
** [https://mozillians.org/en-US/u/rbarnes/ Richard Barnes]


* 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. A previous award proposal, successful or unsuccessful, does not disqualify a project from applying again.
* '''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]


* 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.
==Applicant/Awardee Resources==


https://wiki.mozilla.org/MOSS#Current_List_of_Projects_Mozilla_Relies_On
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.
====<p>'''Current List of Projects Mozilla Works With'''</p>====
Mozilla’s mission is big and ambitious.  And fortunately, we’re not alone in our work.  There are many other groups that are pursuing similar or related goals and that we would like to see succeed. We want to do more to recognize those projects and nurture them along, and propose to begin by taking a look at all the free software and open source projects Mozilla relies upon, either incorporated in our products or that we rely upon as infrastructure.


This section is intended as a gathering place for information on those projects. As a starting point, it lists each project along with a short statement of how we depend on it. Where practical it would also be helpful to identify a Mozillian most closely associated with our use of each project, as next steps will involve contacting each one to find out more about how we can best provide support.
* [[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]]


This is a work in progress - please contribute to this list.
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]].


{| class="wikitable"
==Mentors==
|-
! Project !! Description !! Contact !! Candidate
|-
| [https://github.com/ansible/ansible Ansible] || Used by A-Team to manage deployments || GPS?  || Probably not
|-
| [http://buildbot.net/ BuildBot] || The base system currently in use for release automation - to be replaced by Task Cluster. We shouldn’t contribute to BuildBot as we’re moving off of it. || n/a || Probably not
|-
| [http://www.llvm.org%20 Clang/LLVM] || C/C++ compiler and infrastructure || Ehsan Akhgari || n/a
|-
| [https://github.com/docker/docker Docker] || Used by release engineering for Linux build and test containers and by ateam for managing test and production services. || Member of Selena Deckelmann's team  || n/a
|-
| [https://git-scm.com/ Git] || Version control system - https://git.mozilla.org || n/a || n/a
|-
| [http://canonware.com/jemalloc/ jemalloc] || n/a || n/a || n/a
|-
| libvpx (Google) || Library for support of Google’s VP* family of codecs || Tim Terriberry || n/a
|-
| Linux || n/a || n/a || n/a
|-
| [https://www.mercurial-scm.org/ Mercurial] || Version control system and source code management. || GPS || n/a
|-
| [https://www.nagios.org/ Nagios] || IT management system. Used for notifications of system failures. || IT or Amy Rich's team || n/a
|-
| nICEr || n/a || n/a || n/a
|-
| nrappkit || n/a || n/a || n/a
|-
|- NSS || n/a || n/a || n/a
|-
|- OpenH264 (Cisco) || n/a || n/a || n/a
|-
| Python || n/a || n/a || n/a
|-
| [https://www.reviewboard.org/ Review Board] || The base of MozReview, the new review tool being developed to replace Splinter. || Steven MacLeod || n/a
|-
| [http://www.seleniumhq.org/ Selenium] || Browser test driver. || ''Confirm still in use''. || n/a
|-
| [https://www.sqlite.org/ SQLite] || n/a || n/a || n/a
|-
| [https://subversion.apache.org/ Subversion] || Planning to decommission in near future https://svn.mozilla.org || n/a || Probably not.
|-
| [https://travis-ci.org/ Travis] || Continuous integration system used by several teams || Jonathan Griffin's team || n/a
|-
| [http://www.webrtc.org WebRTC.org] (Google) || Components to support real-time communication in browsers and mobile applications. || Randell Jesup || n/a
|-
|}


====<p>'''Other Projects'''</p>====
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:


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.
* [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.


===<p>'''How To Apply'''</p>===
==Recipients==
Please fill out [https://docs.google.com/a/mozilla.com/forms/d/1Pa5IsuhT6vMUfg0HUXxr7SzrSwq5fpiZfZIJVPxN1Mc/viewform this form] to be considered for MOSS.


===<p>'''FAQs'''</p>===
'''''April 2019 Update: This project list is out of date, please see the [https://github.com/mozilla/MOSS-Directory/ MOSS Directory on GitHub]'''''  
<p>'''Q:''' This program seems unfinished right now. Why are you launching it in this state?</p>
<p>'''A:''' The foundational elements are clear.  We are going to invest in the open source and free software projects.  We are going to start with a significant amount of money.  We will start with open source and free software project that Mozilla is relying on.  This is a crisp, clear criteria and a good way to start our larger program.  We have an aggressive timeframe for a first set of grants to demonstrate we mean action.</p>


<p>Once the foundations are clear, we could take a couple of different approaches. One is to go off and create a fully polished program where we’ve decided exactly how things will work.   Another approach is to present the program while there is real room for your ideas, and for the cluefulness that is spread through Mozilla to make a program that represents all of us.</p>
* [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/2016/04/13/mozilla-open-source-support-moss-update-q1-2016/ 2016-04-13]: Django REST Framework, The Intern
<p>We've chosen the latter approach.  The cynical of you may say “hah, time is short, and that favors announcing this before all the terms are finalized.”  You are correct that time is short.  However, the latter approach also reflects our view that many Mozilla activities are better when people of different perspectives and unexpected expertise and interest are involved.  We hope you prove us right!</p>
* [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
<p>'''Q:''' What’s the evaluation process?</p>
* [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
<p>'''A:'''  That’s in process. Input welcome. </p>
* [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
<p>'''Q:'''  How can I get started while the terms of the application and evaluation process are being finalized?</p>
* [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
<p>'''A:'''  Here are some things you can do immediately:</p>
* ...
* Do some due diligence with your colleagues. Find out if others share your sense of a project’s impact.
* Identify a contact inside the project who is a good person tot all 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 reduced or fixed withe 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 identified in item 1 above.
* If you are interested in participating in the finalization of the program criteria, join the discussion.
-----
<p>'''Q:'''  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.</p>
<p>'''A:''' So far we have two identified mentors:  [https://blog.mozilla.org/press/bios/david-bryant/ David Bryant] and [https://mozillians.org/en-US/u/pfinette/ Pascal Finette].  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. We’ll look into adding to this list.</p>
-----
<p>'''Q:'''  What does it mean to “champion” a project for a MOSS Award?</p>
<p>'''A:'''  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.</p>
 
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 and hopefully ongoing interaction
* reviews the effectiveness of the award funds after an agreed up on period to help Mozilla improve the effectiveness and impact of the MOSS Award program.
-----
<p>'''Q:'''  Is there an amount of an award that is expected?  Or a size that is too big or too small?</p>
<p>'''A:''' 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.</p>
-----
<p>'''Q:''' What’s happening by [[Coincidental_work_weeks/2015_Orlando|Orlando]]?</p>
<p>'''A:''' 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.</p>
-----
<p>'''Q:'''  How does the $1 million work?  Does it all get allocated at Orlando?  How does the $1  million interact with the “up to 10 projects”?</p>
<p>'''A:'''The $1 million is the initial allocation for the MOSS Awards.  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 Awards in the future.</p>
 
<p>We want to focus on making up to 10 good awards, to projects we think are great, and 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 be more than we can complete well.</p>
 
<p>It is conceivable that the 10 awards could use the entire first $1 million allocation, but this is not a goal and unlikely.</p>
-----
<p>'''Q:'''  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 these be?</p>
<p>'''A:''' This is where you’ll tell us.  Describe why it’s so important that this project be recognized, even though the level of complexity and risk goes up in this setting.   We’ll listen because Mozilla is a pretty flexible organization, but we can’t promise the result will be as you hope.</p>
-----
<p>'''Q:'''  How can I stay informed and involved with this work?</p>
<p>'''A:'''  Please join our [https://groups.google.com/a/mozilla.com/d/forum/mozilla-open-source-support-awards public mailing list].</p>
 
-----
<p>'''Q:''' This program seems unfinished right now.  Why are you launching it in this state?</p>
<p>'''A:''' The foundational elements are clear.  We are going to invest in the open source and free software projects.  We are going to start with a significant amount of money.  We will start with open source and free software project that Mozilla is relying on.  This is a crisp, clear criteria and a good way to start our larger program.  We have an aggressive timeframe for a first set of grants to demonstrate we mean action.</p>
 
<p>Once the foundations are clear, we could take a couple of different approaches.  One is to go off and create a fully polished program where we’ve decided exactly how things will work.    Another approach is to present the program while there is real room for your ideas, and for the cluefulness that is spread through Mozilla to make a program that represents all of us.</p>
 
<p>I've chosen the latter approach.  The cynical of you may say “hah, time is short, and that favors announcing this before all the terms are finalized.”  You are correct that time is short. However, the latter approach also reflects our view that many Mozilla activities are better when people of different perspectives and unexpected expertise and interest are involved. We hope you prove us right!</p>
-----

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"