Innovation/Experiment Setup

From MozillaWiki
< Innovation
Revision as of 00:49, 7 March 2017 by Dmarti (talk | contribs) (Created page with "These instructions are here in order to avoid duplicating work among projects. If something needs to work differently for a particular experiment, that's fine, but it might g...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

These instructions are here in order to avoid duplicating work among projects. If something needs to work differently for a particular experiment, that's fine, but it might go a little more slowly.

Documents

  • Contract: this is a standard Mozilla contract, with copyright assignment by default. This is assignments for the project deliverables only, not for open source work that you do in the course of the project. In order to keep a core open source project unencumbered, structure the project deliverables carefully.
  • Statement of Work: specifies the deliverables and dates

Contracts are sent using Adobe EchoSign after initial review. So far we have done US and Canada contracts, and other countries are available.

Infrastructure

Coming soon. Experiments will be able to submit containers to run within the Mozilla Participation Systems infrastructure.


Communications Plan

How to get the word about about your project.

  • Principal investigator's blog
  • Mozilla Hacks blog
  • other contributed articles and interviews.

It's better to learn about requirements and interests for potential places to publish your work as early as possible. Many media sites have long lead times and in order for an article to run at the most effective time it must be scheduled well in advance.