Task:Components and packages - Revision history

qgil: /* Table of packages */

qgil — Wed, 06 Aug 2008 06:23:58 GMT

Table of packages

← Older revision		Revision as of 06:23, 6 August 2008
Line 13:		Line 13:

	==Table of packages==		==Table of packages==
		+	=== Third draft ===
		+	A third draft is available '''[https://garage.maemo.org/docman/view.php/106/354/maemopackages-20080725.ods HERE]'''. Now all packages have LOC counts.
		+
	=== Second draft ===		=== Second draft ===
	A second draft is available '''[https://garage.maemo.org/docman/view.php/106/353/maemopackages-20080723.ods HERE]'''. It contains the same data as the first draft plus the approximate lines of code of the packages. This data wasn't initially required in this task yet now it can be used now to compare the amount of code open vs closed.		A second draft is available '''[https://garage.maemo.org/docman/view.php/106/353/maemopackages-20080723.ods HERE]'''. It contains the same data as the first draft plus the approximate lines of code of the packages. This data wasn't initially required in this task yet now it can be used now to compare the amount of code open vs closed.

qgil: /* ToDo */ to discussion page

qgil — Wed, 23 Jul 2008 07:16:18 GMT

ToDo: to discussion page

← Older revision		Revision as of 07:16, 23 July 2008
Line 38:		Line 38:
	** 3rd party: closed source packages developed by third parties.		** 3rd party: closed source packages developed by third parties.
	* A graph visualizing the amount and type of packages per each component.		* 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.~~

qgil: /* Second draft */

qgil — Wed, 23 Jul 2008 07:14:54 GMT

Second draft

← Older revision		Revision as of 07:14, 23 July 2008
Line 14:		Line 14:
	==Table of packages==		==Table of packages==
	=== Second draft ===		=== Second draft ===
-	A ~~sedcond~~ draft is available '''[https://garage.maemo.org/docman/view.php/106/353/maemopackages-20080723.ods HERE]'''. It contains the same data as the first draft plus the approximate lines of code of the packages. This data wasn't initially required in this task yet now it can be used now to compare the amount of code open vs closed.	+	A second draft is available '''[https://garage.maemo.org/docman/view.php/106/353/maemopackages-20080723.ods HERE]'''. It contains the same data as the first draft plus the approximate lines of code of the packages. This data wasn't initially required in this task yet now it can be used now to compare the amount of code open vs closed.

	Some packages are still missing LOC counts:		Some packages are still missing LOC counts:
Line 24:		Line 24:
	* gcc		* gcc
	* initfs-diablo		* initfs-diablo
-	* kernel-diablo	+	* kernel-diablo

	=== First draft ===		=== First draft ===

qgil: New version with LOC

qgil — Wed, 23 Jul 2008 07:14:14 GMT

New version with LOC

← Older revision		Revision as of 07:14, 23 July 2008
Line 1:		Line 1:
	{{Template:100Days agenda}}		{{Template:100Days agenda}}
-	{{task\|~~ongoing~~}}	+	{{task\|completed}}

	''This is a subtask of [[Task:Defining maemo]] coordinated by [http://maemo.org/profile/view/bijjal/ Soumya].''		''This is a subtask of [[Task:Defining maemo]] coordinated by [http://maemo.org/profile/view/bijjal/ Soumya].''
Line 13:		Line 13:

	==Table of packages==		==Table of packages==
		+	=== Second draft ===
		+	A sedcond draft is available '''[https://garage.maemo.org/docman/view.php/106/353/maemopackages-20080723.ods HERE]'''. It contains the same data as the first draft plus the approximate lines of code of the packages. This data wasn't initially required in this task yet now it can be used now to compare the amount of code open vs closed.
		+
		+	Some packages are still missing LOC counts:
		+	* netbase
		+	* libxmu
		+	* libxpm
		+	* libxres
		+	* linux-kernel-headers
		+	* gcc
		+	* initfs-diablo
		+	* kernel-diablo
		+
		+	=== First draft ===
	A first draft is available '''[https://garage.maemo.org/docman/view.php/106/352/maemopackages-20080716.ods HERE]'''. It contains:		A first draft is available '''[https://garage.maemo.org/docman/view.php/106/352/maemopackages-20080716.ods HERE]'''. It contains:

qgil: /* Table of packages */ Link to file

qgil — Mon, 21 Jul 2008 09:35:23 GMT

Table of packages: Link to file

← Older revision		Revision as of 09:35, 21 July 2008
Line 13:		Line 13:

	==Table of packages==		==Table of packages==
-	A first draft is available '''HERE''' ~~(couldn't upload it because ".ods" is not allowed)~~. It contains:	+	A first draft is available '''[https://garage.maemo.org/docman/view.php/106/352/maemopackages-20080716.ods 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.		* 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.

qgil: /* Table of packages */

qgil — Thu, 17 Jul 2008 00:00:43 GMT

Table of packages

← Older revision		Revision as of 00:00, 17 July 2008
Line 12:		Line 12:
	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/maemo_release_documentation/maemo4.1.x/node6.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/maemo_release_documentation/maemo4.1.x/node6.html Maemo software architecture] documentation.

-	==~~Handling and presenting data~~==	+	==Table of packages==
-	~~About~~ the ~~way~~ to ~~process~~, ~~maintain~~ and ~~present~~ the ~~data~~:	+	A first draft is available '''HERE''' (couldn't upload it because ".ods" is not allowed). It contains:
-	* ~~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~~.	+	* 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.
-	* ~~Then we will need to link~~ packages ~~to upstream projects,~~ Nokia or 3rd party ~~owners. Surely a 100% manual task~~.	+	* Organization of packages in components.
-	* ~~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~~.	+	* Basic status of the license of each package:
-	* ~~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.	+	** OSS Upstream: packages that essentially have been integrated just as they come from their upstream projects.
-	* ~~We need~~ to ~~agree also on~~ the ~~final output~~ and ~~presentation~~ of ~~data~~. ~~What is expected? Mockups welcome!~~	+	** 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.

qgil: fixed link

qgil — Wed, 02 Jul 2008 12:35:48 GMT

fixed link

← Older revision		Revision as of 12:35, 2 July 2008
Line 10:		Line 10:
	Integrating these components one should be able to generate a functional image and a complete SDK.		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 [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/maemo_release_documentation/maemo4.1.x/node6.html Maemo software architecture] documentation.

	==Handling and presenting data==		==Handling and presenting data==

qgil: {{task|ongoing}}

qgil — Mon, 30 Jun 2008 22:01:01 GMT

← Older revision		Revision as of 22:01, 30 June 2008
Line 1:		Line 1:
	{{Template:100Days agenda}}		{{Template:100Days agenda}}
-	{{task\|~~proposed~~}}	+	{{task\|ongoing}}

	''This is a subtask of [[Task:Defining maemo]] coordinated by [http://maemo.org/profile/view/bijjal/ Soumya].''		''This is a subtask of [[Task:Defining maemo]] coordinated by [http://maemo.org/profile/view/bijjal/ Soumya].''

qgil: {{task|proposed}}

qgil — Sun, 29 Jun 2008 12:14:06 GMT

← Older revision		Revision as of 12:14, 29 June 2008
Line 1:		Line 1:
	{{Template:100Days agenda}}		{{Template:100Days agenda}}
-	{{task\|~~accepted~~}}	+	{{task\|proposed}}

	''This is a subtask of [[Task:Defining maemo]] coordinated by [http://maemo.org/profile/view/bijjal/ Soumya].''		''This is a subtask of [[Task:Defining maemo]] coordinated by [http://maemo.org/profile/view/bijjal/ Soumya].''

qgil: /* Handling and presenting data */

qgil — Sun, 29 Jun 2008 09:30:39 GMT

Handling and presenting data

← Older revision		Revision as of 09:30, 29 June 2008
Line 19:		Line 19:
	* 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.		* 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.		* 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.
		+	* We need to agree also on the final output and presentation of data. What is expected? Mockups welcome!