Maemo contribution guidelines
(→Upstream) |
(→Releases) |
||
| Line 12: | Line 12: | ||
The best timing for contributions is prior to the final version of a release. Alphas and betas are released for that purpose. | The best timing for contributions is prior to the final version of a release. Alphas and betas are released for that purpose. | ||
| - | Early contributions on new releases are encouraged too, noting that UI changes | + | Early contributions on new releases are encouraged too, noting that UI changes might be difficult to be accepted because of design, localization, usability and end user testing implications. |
=== Upstream === | === Upstream === | ||
Revision as of 12:54, 20 November 2008
DRAFT
These are the guidelines third party developers need to observe when contributing code to open source software maintained or distributed by Nokia in the Maemo platform:
Contents |
Contributions welcome!
The Maemo SW team at Nokia encourages revision and feedback of the open source components of the Maemo platform and related open source applications.
Sources
The sources of the Maemo platform and related Nokia developed open source applications are available at [URL with sources of lastest version].
Releases
The best timing for contributions is prior to the final version of a release. Alphas and betas are released for that purpose.
Early contributions on new releases are encouraged too, noting that UI changes might be difficult to be accepted because of design, localization, usability and end user testing implications.
Upstream
Patches to software components developed upstream need to be submitted to their original projects.
It is recommended to notify in bugs.maemo.org the contribution to the related Maemo SW developers by providing URLs to the bug/patch submitted upstream. They might help pushing the patch and/or committing it to the Maemo related component.
If the upstream is not Maemo SW but another team at Nokia (for instance Qt SW) then their contribution guidelines prevail.
License
The license of the code contributed is the one of the component patched.
Copyright
Authors of code accepted in a software component are entitled to get copyright assignment when the solution provided conforms a creative work.
Bugfixes are generally not considered work subject to copyright assignment.