Confirmed users, Bureaucrats and Sysops emeriti
2,088
edits
Firefox OS/Projects/How: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
=Firefox OS Projects= | =Firefox OS Projects= | ||
==Deliverables== | |||
* All projects should deliver a written summary containing the project results and findings, and feedback on the project, process, and technologies used. | |||
* Any code created as part of the project should be in a public Github repo, licensed under the MPL | |||
==Contributors/Programs== | |||
Types of programs and contributors | |||
* Individual contributor | |||
* Academic contributors | |||
** Undergraduate team project (Capstone) | |||
** Undergraduate/Vocational large programs | |||
** Graduate researchers | |||
** Special programs (GSOC, OpenAcademy) | |||
* Partner engineers | |||
** Working on core OS features | |||
** Working on R&D for apps/features specific to a market | |||
==Designing Projects for Success== | ==Designing Projects for Success== | ||
| Line 11: | Line 28: | ||
* '''Regular check-ins:''' Have a weekly or bi-weekly meeting. Regularly scheduled communication avoids projects from heading too far in the wrong direction, or falling too far behind. | * '''Regular check-ins:''' Have a weekly or bi-weekly meeting. Regularly scheduled communication avoids projects from heading too far in the wrong direction, or falling too far behind. | ||
* '''Create Incentives:''' For example, for academic groups ensure the work is being done for credit as part of a formal program. | * '''Create Incentives:''' For example, for academic groups ensure the work is being done for credit as part of a formal program. | ||