Task:Components and packages
 |
This article is continued discussion from the maemo.org brainstorm Please see the 100 Days agenda for more. |
|
This is an ongoing task, planned to be completed during the current maemo.org development sprint. Any help is appreciated! Please see the talk page for discussion. |
 |
This is a subtask of Task:Defining maemo coordinated by Soumya.
We need to come up with the list of packages that define Maemo 4.1, according to the new definition of Maemo:
- Maemo platform - The software stack from the Linux Kernel to the SDK. It's mostly open source code originated in upstream projects plus some open components developed by Nokia. Some exceptions of Nokia and third party proprietary software are included in order to provide a fully functional stack.
Integrating these components one should be able to generate a functional image and a complete SDK.
The list packages should be presented in a sensible way e.g. organized around the components described in the new Intro and the Maemo software architecture documentation.
Table of packages
A first draft is available HERE. It contains:
- Proposed list of packages that make Maemo. They come from the Maemo 4.1 SDK profile plus some additional packages needed to complete a bootable image. Compared to the OS2008 image, most applications and Nokia design elements are missing.
- Organization of packages in components.
- Basic status of the license of each package:
- OSS Upstream: packages that essentially have been integrated just as they come from their upstream projects.
- OSS Modified: packages originated upstream that have been adapted by Nokia to run on Maemo.
- OSS Nokia: open source packages developed by Nokia.
- Nokia closed: closed source packages developed by Nokia.
- 3rd party: closed source packages developed by third parties.
- A graph visualizing the amount and type of packages per each component.
ToDo
The current draft satisfies the core mission of this task. However, there is some work that could be done to improve it.
- Introduce approximate lines of code or size of each package to have a better view of the dimensions of each packages and the open/closed relation in a more accurate way. Now operator-wizard appears just as big as the whole Linux Kernel.
- Is it worth listing the specific licenses of each open source package? It's mostly a manual work...
- Better organization of packages. Ideally there would be a basic overview of the areas of the platform, a second level with the specific software components of each area and a third level listing the packages under a component.
- Nicer presentation of graphics and data in the spreadsheet.
- Export the data to HTML or PDF for easier access.
Let's see how far Soumya can go in this sprint. Except the LOC and the licenses, the rest of tasks can be done by anybody just as easily.