MOSS/Mission Partners - Revision history

FrostCleary: Switched out Google form application link for Fluxx application form

2018-06-01T15:55:13Z

Switched out Google form application link for Fluxx application form

← Older revision		Revision as of 15:55, 1 June 2018
Line 32:		Line 32:
	==How To Apply==		==How To Apply==

	The application form is [https://~~docs~~.~~google~~.~~com~~/~~forms~~/~~d/1rwYQTT-9-eldS-kElY646bMwMzJpxfL8lDskX86xgCQ/viewform~~ here]. For application deadline information, see the [[MOSS\|main page]].		The application form is [https://mozilla.fluxx.io/apply/MOSS here]. For application deadline information, see the [[MOSS\|main page]].

	If you need help completing your application, see the list of mentors on the [[MOSS\|main page]].		If you need help completing your application, see the list of mentors on the [[MOSS\|main page]].

Gerv: Tone down language about individuals

2017-06-30T03:54:51Z

Tone down language about individuals

← Older revision		Revision as of 03:54, 30 June 2017
Line 11:		Line 11:
	** Building something cool with web technologies		** Building something cool with web technologies
	** Translating open source software into another language		** Translating open source software into another language
	* 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 project’s home can be anywhere in the world where we can make payment without undue burden. We have a preference for funding legal organizations rather than individuals representing projects, although circumstances could lead to some flexibility.
	* The specific project activity should be endorsed (on the application form) by someone well-known and respected in a wider software community of which the project is a part.		* The specific project activity should be endorsed (on the application form) by someone well-known and respected in a wider software community of which the project is a part.

Line 37:		Line 37:

	==FAQs==		==FAQs==

	~~;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"?~~
	: 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 is an 'endorser'?		;What is an 'endorser'?

Gerv: Add deadline info

2016-08-24T14:36:34Z

Add deadline info

← Older revision		Revision as of 14:36, 24 August 2016
Line 32:		Line 32:
	==How To Apply==		==How To Apply==

	The application form is [https://docs.google.com/forms/d/1rwYQTT-9-eldS-kElY646bMwMzJpxfL8lDskX86xgCQ/viewform here]. ~~Applications are accepted on an ongoing basis~~. If you need help completing your application, see the list of mentors on the [[MOSS\|main page]].		The application form is [https://docs.google.com/forms/d/1rwYQTT-9-eldS-kElY646bMwMzJpxfL8lDskX86xgCQ/viewform here]. For application deadline information, see the [[MOSS\|main page]].

			If you need help completing your application, see the list of mentors on the [[MOSS\|main page]].

	==FAQs==		==FAQs==

Gerv: Update to say applications are ongoing

2016-07-20T11:06:23Z

Update to say applications are ongoing

← Older revision		Revision as of 11:06, 20 July 2016
Line 3:		Line 3:
	==Project Criteria==		==Project Criteria==

	~~Awards~~ should be submitted by a leader of the project. The project/people need to meet the following criteria:		Award applications should be submitted by a leader of the project. The project/people need to meet the following criteria:

	* The project should be to write or enhance some software or software documentation which is under an OSI open source and/or an FSF free software license (non-software exceptions will be considered on a case-by-case basis).		* The project should be to write or enhance some software or software documentation which is under an OSI open source and/or an FSF free software license (non-software exceptions will be considered on a case-by-case basis).
Line 32:		Line 32:
	==How To Apply==		==How To Apply==

	The application form is [https://docs.google.com/forms/d/1rwYQTT-9-eldS-kElY646bMwMzJpxfL8lDskX86xgCQ/viewform here]. ~~The deadline for applications for the first round of awards is 23:59 on Tuesday 31st May 2016. After that, applications~~ are accepted on an ongoing basis~~, but there may be a delay in processing while the first round of applications are handled~~. If you need help completing your application, see the list of mentors on the [[MOSS\|main page]].		The application form is [https://docs.google.com/forms/d/1rwYQTT-9-eldS-kElY646bMwMzJpxfL8lDskX86xgCQ/viewform here]. Applications are accepted on an ongoing basis. If you need help completing your application, see the list of mentors on the [[MOSS\|main page]].

	==FAQs==		==FAQs==

Gerv: Formatting

2016-05-10T13:34:39Z

Formatting

← Older revision		Revision as of 13:34, 10 May 2016
Line 6:		Line 6:

	* The project should be to write or enhance some software or software documentation which is under an OSI open source and/or an FSF free software license (non-software exceptions will be considered on a case-by-case basis).		* The project should be to write or enhance some software or software documentation which is under an OSI open source and/or an FSF free software license (non-software exceptions will be considered on a case-by-case basis).

	* The project should benefit Mozilla’s mission. This is normally demonstrated by tying the objective of the project to specific Mozilla manifesto principles or other demonstrated priorities.		* The project should benefit Mozilla’s mission. This is normally demonstrated by tying the objective of the project to specific Mozilla manifesto principles or other demonstrated priorities.

	* Activities which are not sufficient for an award on their own include:		* Activities which are not sufficient for an award on their own include:
	** Writing open source software (notwithstanding manifesto principle #7)		** Writing open source software (notwithstanding manifesto principle #7)
	** Building something cool with web technologies		** Building something cool with web technologies
	** Translating open source software into another language		** Translating open source software into another language

	* 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 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 specific project activity should be endorsed (on the application form) by someone well-known and respected in a wider software community of which the project is a part.		* The specific project activity should be endorsed (on the application form) by someone well-known and respected in a wider software community of which the project is a part.

Gerv: Update pre-launch of Track 2

2016-05-10T13:32:34Z

Update pre-launch of Track 2

← Older revision		Revision as of 13:32, 10 May 2016
Line 5:		Line 5:
	Awards should be submitted by a leader of the project. The project/people need to meet the following criteria:		Awards should be submitted by a leader of the project. The project/people need to meet the following criteria:

	* The project should be to write or enhance some software or software documentation which is under an OSI open source and/or an FSF free software license ( non-software exceptions will be considered on a case-by-case basis).		* The project should be to write or enhance some software or software documentation which is under an OSI open source and/or an FSF free software license (non-software exceptions will be considered on a case-by-case basis).

	* The project should benefit Mozilla’s mission. This is normally demonstrated by tying the objective of the project to specific Mozilla manifesto principles or other demonstrated priorities.		* The project should benefit Mozilla’s mission. This is normally demonstrated by tying the objective of the project to specific Mozilla manifesto principles or other demonstrated priorities.
Line 16:		Line 16:
	* 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 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 specific project activity should be endorsed (on the application form) by someone well-known and respected in ~~the applicant's~~ wider ~~open-source spoken-language~~ community.		* The specific project activity should be endorsed (on the application form) by someone well-known and respected in a wider software community of which the project is a part.

	==Selection Criteria==		==Selection Criteria==
Line 36:		Line 36:
	==How To Apply==		==How To Apply==

	The application form is [https://docs.google.com/forms/d/1rwYQTT-9-eldS-kElY646bMwMzJpxfL8lDskX86xgCQ/viewform here]. ~~Applications~~ are accepted on an ongoing basis.		The application form is [https://docs.google.com/forms/d/1rwYQTT-9-eldS-kElY646bMwMzJpxfL8lDskX86xgCQ/viewform here]. The deadline for applications for the first round of awards is 23:59 on Tuesday 31st May 2016. After that, applications are accepted on an ongoing basis, but there may be a delay in processing while the first round of applications are handled. If you need help completing your application, see the list of mentors on the [[MOSS\|main page]].

			==FAQs==

			;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"?
			: 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 is an 'endorser'?
			: We are keen to enable applications from groups not currently connected with Mozilla, and from communities outside the English-speaking free software world. Therefore, applications for Mission Partners do not require a Mozillian to support them, as applications for Foundational Technology do. Instead, they must be endorsed by a well-known and respected figure from a wider software community of which the project is a part, who is not directly connected with your project. This could be a language community, or a national community - it does not have to be the international open source community.

			;What about tax?
			: 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.

Gerv at 15:25, 5 May 2016

2016-05-05T15:25:41Z

← Older revision		Revision as of 15:25, 5 May 2016
Line 14:		Line 14:
	** Translating open source software into another language		** Translating open source software into another language

	* The specific project activity should be endorsed (on the application form) by someone well-known in the applicant's wider open source spoken language community.		* 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 specific project activity should be endorsed (on the application form) by someone well-known and respected in the applicant's wider open-source spoken-language community.

	==Selection Criteria==		==Selection Criteria==

Gerv at 15:24, 5 May 2016

2016-05-05T15:24:08Z

← Older revision		Revision as of 15:24, 5 May 2016
Line 1:		Line 1:
	The Mission Partners track is open to any open source/free software project which is undertaking an activity which significantly furthers Mozilla's [https://www.mozilla.org/about/manifesto/ mission].		The Mission Partners track is open to any open source/free software project which is undertaking an activity which significantly furthers Mozilla's [https://www.mozilla.org/about/manifesto/ mission].

	==Project Criteria==		==Project Criteria==
Line 7:		Line 7:
	* The project should be to write or enhance some software or software documentation which is under an OSI open source and/or an FSF free software license ( non-software exceptions will be considered on a case-by-case basis).		* The project should be to write or enhance some software or software documentation which is under an OSI open source and/or an FSF free software license ( non-software exceptions will be considered on a case-by-case basis).

	* The project should benefit Mozilla’s mission. This is normally demonstrated by ~~tieing~~ the objective of the project to specific Mozilla manifesto principles or other demonstrated priorities.		* The project should benefit Mozilla’s mission. This is normally demonstrated by tying the objective of the project to specific Mozilla manifesto principles or other demonstrated priorities.

	* Activities which are not sufficient for an award on their own include:		* Activities which are not sufficient for an award on their own include:
Line 13:		Line 13:
	** Building something cool with web technologies		** Building something cool with web technologies
	** Translating open source software into another language		** Translating open source software into another language

			* The specific project activity should be endorsed (on the application form) by someone well-known in the applicant's wider open source spoken language community.

	==Selection Criteria==		==Selection Criteria==

Gerv: Rejig to add Mission Partners info

2016-05-05T15:11:23Z

Rejig to add Mission Partners info

← Older revision		Revision as of 15:11, 5 May 2016
Line 1:		Line 1:
	This MOSS track is ~~not yet active~~.		The Mission Partners track is open to any open source/free software project which is undertaking an activity which significantly furthers Mozilla's [https://www.mozilla.org/about/manifesto/ mission].

			==Project Criteria==

			Awards should be submitted by a leader of the project. The project/people need to meet the following criteria:

			* The project should be to write or enhance some software or software documentation which is under an OSI open source and/or an FSF free software license ( non-software exceptions will be considered on a case-by-case basis).

			* The project should benefit Mozilla’s mission. This is normally demonstrated by tieing the objective of the project to specific Mozilla manifesto principles or other demonstrated priorities.

			* Activities which are not sufficient for an award on their own include:
			** Writing open source software (notwithstanding manifesto principle #7)
			** Building something cool with web technologies
			** Translating open source software into another language

			==Selection Criteria==

			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 significantly does the project advance the Mozilla mission?
			* 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 award 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?

			We expect the vast majority of MOSS awards 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.

			The minimum award for the Mission Partners track is $10,000, and the maximum is $250,000.

			==How To Apply==

			The application form is [https://docs.google.com/forms/d/1rwYQTT-9-eldS-kElY646bMwMzJpxfL8lDskX86xgCQ/viewform here]. Applications are accepted on an ongoing basis.

Gerv: Reorganize MOSS pages to split into tracks

2016-01-14T10:40:11Z

Reorganize MOSS pages to split into tracks

New page

This MOSS track is not yet active.