Task:Components and packages
m ({{task|accepted}}) |
(How to handle and publish data) |
||
| Line 2: | Line 2: | ||
{{task|accepted}} | {{task|accepted}} | ||
| - | ''This is a subtask of [[Task:Defining maemo]] | + | ''This is a subtask of [[Task:Defining maemo]] coordinated by [http://maemo.org/profile/view/bijjal/ Soumya].'' |
We need to come up with the list of packages that define Maemo 4.1, according to the new [[Task:Maemo brand|definition of Maemo]]: | We need to come up with the list of packages that define Maemo 4.1, according to the new [[Task:Maemo brand|definition of Maemo]]: | ||
| Line 11: | Line 11: | ||
The list packages should be presented in a sensible way e.g. organized around the components described in the new [http://maemo.org/intro Intro] and the [http://maemo.org/development/documentation/how-tos/4-x/maemo_architecture.html Maemo software architecture] documentation. | The list packages should be presented in a sensible way e.g. organized around the components described in the new [http://maemo.org/intro Intro] and the [http://maemo.org/development/documentation/how-tos/4-x/maemo_architecture.html Maemo software architecture] documentation. | ||
| + | |||
| + | ==Handling and presenting data== | ||
| + | About the way to process, maintain and present the data: | ||
| + | * Probably Soumya can come up with a table generated automatically showing package names, open/closed and perhaps the License. | ||
| + | * Then we will need to link packages to architecture components. Probably a 100% manual task. | ||
| + | * Then we will need to link packages to upstream projects, Nokia or 3rd party owners. Surely a 100% manual task. | ||
| + | * With all this we will get a table sitting on top of a spreadsheet or a simple database. First decision: how to handle the data. | ||
| + | * And then we will need to publish the information, in a way that is easy to update when there are chan ges in the data. It looks like trying to export to MediaWiki would be just nuts, massochism. Then I guess we would go for a simple HTML output? Second decision: how to publish the data. | ||
Revision as of 09:29, 29 June 2008
 |
This article is continued discussion from the maemo.org brainstorm Please see the 100 Days agenda for more. |
|
This is an accepted task and it is currently in the maemo.org development backlog. Probably nothing is stopping you from starting on it, though. 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.
Handling and presenting data
About the way to process, maintain and present the data:
- Probably Soumya can come up with a table generated automatically showing package names, open/closed and perhaps the License.
- Then we will need to link packages to architecture components. Probably a 100% manual task.
- Then we will need to link packages to upstream projects, Nokia or 3rd party owners. Surely a 100% manual task.
- With all this we will get a table sitting on top of a spreadsheet or a simple database. First decision: how to handle the data.
- And then we will need to publish the information, in a way that is easy to update when there are chan ges in the data. It looks like trying to export to MediaWiki would be just nuts, massochism. Then I guess we would go for a simple HTML output? Second decision: how to publish the data.