13
edits
Innovation/Open Source Experiments: Difference between revisions
Innovation/Open Source Experiments (view source)
Revision as of 12:42, 26 December 2017
, 26 December 2017Fix broken link
(add related programs section) |
(Fix broken link) |
||
| (8 intermediate revisions by one other user not shown) | |||
| Line 10: | Line 10: | ||
* [http://sarah.thesharps.us/2016/10/29/measuring-the-impact-of-negative-language-on-foss-participation-part-i/ What can sentiment analysis of project discussions predict about contributor engagement in the future?] | * [http://sarah.thesharps.us/2016/10/29/measuring-the-impact-of-negative-language-on-foss-participation-part-i/ What can sentiment analysis of project discussions predict about contributor engagement in the future?] | ||
* [https://medium.com/@malvikar/incentives-in-open-source-participation-3e0b34a956fa#.tm1wjghc4 When people leave or cut back on their open source participation, what do they do instead, and what does that activity do for them that open source isn’t?] | * [https://medium.com/@malvikar/incentives-in-open-source-participation-3e0b34a956fa#.tm1wjghc4 When people leave or cut back on their open source participation, what do they do instead, and what does that activity do for them that open source isn’t?] | ||
* [http://www.filterbubbler.org/ Are users interested in collaborating on text classification in order to understand the "filter bubbles" they participate in?] | |||
In the future, we’re interested in finding answers to questions such as... | In the future, we’re interested in finding answers to questions such as... | ||
| Line 24: | Line 25: | ||
'''Burnout:''' People are putting in unsustainable amounts of time, so projects look artificially good. | '''Burnout:''' People are putting in unsustainable amounts of time, so projects look artificially good. | ||
'''Bugs:''' [https://medium.com/message/everything-is-broken- | '''Bugs:''' [https://medium.com/message/everything-is-broken-81e5f33a24e1 Quinn Norton said it best]: everything is broken. Open source got publicity by being “slightly less broken” than the Windows and Unix systems of the 1990s—but has open source quality peaked? Bugs tend to pile up over years. | ||
'''Bias:''' We’re not using all the people we could be using, for all the things they could be doing for us.This is not just a human equal opportunity thing. We’re facing the real risk that a closed platform will provide better safety and opportunity for underrepresented demographic groups than the open web does. | '''Bias:''' We’re not using all the people we could be using, for all the things they could be doing for us.This is not just a human equal opportunity thing. We’re facing the real risk that a closed platform will provide better safety and opportunity for underrepresented demographic groups than the open web does. | ||
| Line 78: | Line 79: | ||
The flow is relatively simple. | The flow is relatively simple. | ||
* Write and approve | * Write and approve a proposal (here is a sample [[Innovation/Proposal Outline]]) | ||
* [[Innovation/Experiment Setup]] | |||
* Run and document experiment | * Run and document experiment | ||
* Evaluate and transfer as needed | * Evaluate and transfer as needed | ||
| Line 89: | Line 91: | ||
* Questions that are important to Mozilla teams that do not have a project or PI in mind | * Questions that are important to Mozilla teams that do not have a project or PI in mind | ||
* Developers who want to take on a small contract project to build software needed for an experiment | |||
We will track these items and assemble complete experiments. In some cases there will be a principal investigator plus another contractor, on separate contracts. (For example, a project requiring a complex bot might have a PI focused on the codebase being developed and a bot developer/administrator working mostly in a separate bot repository.) | We will track these items and assemble complete experiments. In some cases there will be a principal investigator plus another contractor, on separate contracts. (For example, a project requiring a complex bot might have a PI focused on the codebase being developed and a bot developer/administrator working mostly in a separate bot repository.) | ||
Deliverables for experiments should be simple and self-contained. For example, an ideal deliverable is a report or blog post. Software projects for experiments will run more smoothly if the deliverable is a set of data or results _about_ the software, and not the whole project. | |||
== Project scope == | == Project scope == | ||
| Line 96: | Line 102: | ||
Organizational limits on a project include: | Organizational limits on a project include: | ||
* Total budget per contract: less than $25,000 | * Total budget per contract: less than $25,000 for small exploratory projects, larger for longer or multi-experimenter projects | ||
* Duration of project: 6 months or less (typical) | |||
* Duration of project: 6 months or less | |||
* Payment structure: paid by milestones, not hourly | * Payment structure: paid by milestones, not hourly | ||
| Line 109: | Line 114: | ||
We encourage people who are interested in open source experiments to sign up for other (independently operated) programs at Mozilla, too. | We encourage people who are interested in open source experiments to sign up for other (independently operated) programs at Mozilla, too. | ||
* [[TechSpeakers]]: Increase developer awareness and adoption of the Web, Firefox, and Mozilla through a strong community-driven technical speaker development program. | |||
* #[[Mozfest]]: is an annual gathering of passionate thinkers and inventors from around the world who meet to learn from each other and help forge the future of the web. | |||