Project submission

Submitted by Tariq Shureih, updated on 18 May 2009 - 0 comments
  1. Criteria

    2.

    Moblin accepts submission of components that meet the following criteria:

    1. Must be, at minimum, alpha feature quality.
    2. Must be an open source project with an appropriate license compatible with Linux and other open source components in all aspects such as dynamic or static linking.
    3. Must be a released version, in a tar archive or source RPM format, with release notes and a minimum level of unit and quality testing.
    4. Both build and run-time dependencies are identified and listed.
    5. Complies with Moblin footprint requirements: components must be optimized for low run-time memory use, as well as permanent storage (or disk) footprint.
    6. Complies with Moblin power and battery-life requirements: components must be designed to implement the latest power-saving techniques.
    7. Changes to existing upstream components, such as the Linux kernel of Xorg, should be in the form of patches with the version of the base component that the patch applies to.
    8. New components should submitted as a tarball containing the source and Makefile.

      9. Note: It's highly recommended that your component use automake and autoconf to build your component.

  2. Kernel Specific Submissions

    3. Moblin has specific requirements for kernel development and the submission process.

    • All components, drivers, and feature patches, as well as bug fixes, must be accepted and available in the mainline Linux kernel at Kernel.org.
    • All submissions must be reviewed and approved by the Moblin kernel team.
    • All components, drivers, and patches must follow the Kernel development guidelines.
    • Please contact the Moblin kernel maintainer, Rolla Selbak, for all questions.

  3. General Development Process

    4. Once a project or component reaches alpha and is ready to be integrated into Moblin builds, the maintainer needs to complete a submission outlining:

    1. Project/component name
    2. Source download location
    3. License
    4. Known build and run-time dependencies
    5. Copyright attestation
    6. Project web site/URL
    7. Maintainer name and email address

Once the above is complete, the Moblin distribution team obtains the component’s source and applies the “Moblinization” steps needed to package the project into an RPM package, build and obtain dependencies in the Moblin build infrastructure, and produce pure Moblin package(s). They are then made available in the Moblin RPM repository accessible through YUM, and for MIC through an updated or new function-set “fset”.

The new package/component will also have a “git” source repository added to the Moblin master git repository.

Subsequent updates must be in the form of patches that add new functionality and/or address integration issues.

In the case of the Moblin Kernel and device drivers, all patches and device drivers must be accepted and available in Linus’s tree and at kernel.org.

Any and all exceptions to the above process and criteria must be submitted to and approved by the Moblin PDT.

The submission should be in the form of a Bugzilla new feature request.

The Moblin bugzilla is located at:
https://bugzilla.moblin.org
You must create an account to add requests.