Openembedded.org - User contributions [en]

User:Ronan

2008-08-13T16:41:03Z

Ronan: /* Centers of interest related to openembedded */

I'm more a [http://en.wikipedia.org/wiki/Software_architect Software architect].
Sometimes it's hard to explain what you should do in the enterprise. I work on improve this state of thing.

= OpenEmbedded Experience =

== 2006 - 2007 : Paper-book project ==

Prototype for [http://www.paper-book.com paper-book]

* http://scourge.fr/mathdesc/images/pb/PB-1.JPG
* http://scourge.fr/mathdesc/images/pb/PB-2.JPG
* http://scourge.fr/mathdesc/images/pb/PB-3.JPG

== 2007 - 2008 : Nao ==

Soon some information about it.

= Wishlist =

This section is my wiki for idea i'd like to work to improve my openembedded
Some are perhaps really bad ideas ( not enough searsh ), or already exists , let me know.

== bugzilla integration ==

if ( OE_WARN_BUG == 1 )
checkbug(${PN})

bitbake -bugz mozilla

cf http://code.google.com/p/pybugz/source/browse/trunk/README?r=28

== reduce image size method ==

Reduce image size using remote lsof session on target to check useless files , packages ( blame useless dependency ) ... diff with $ROOTFS and eventually try them by size.

#REMOTE_METHODE = "ssh 192.168.0.1"
REMOTE_METHODE = "tty /dev/USBtty1"
bitbake -lsof-session mycustom-image.bb

http://www.ibm.com/developerworks/linux/library/l-inotify.html

i should also try some code inspector ( to check code duplication etc to advise programmer where place could be saved ).
Some Steiner stuff on fusil could be useful.

== report tool ==

print beautiful documentation on the distro/packages/whatever.
* template design
* baobab ...

[http://www.reportlab.org/rl_toolkit.html reportlab]

== netboot images ==

mkelf-linux kernel-image [ramdiskimage]
keywords : initramdisk

== some QA ideas ==

=== fuzzing our softwares ===

opkg, bitbake etc

* using fusil [http://fusil.hachoir.org fusil] ( fuzzing report ) ,
i made the recipe see [http://bugs.openembedded.net/show_bug.cgi?id=4495 bug 4495]
look success story at http://fusil.hachoir.org/trac/wiki/CrashList

=== more documentation ===

bbclass documentation ( how - as a policy )
=> provide documentations about how to make better code in bitbake
=> pydoc , doctest , unittest , pyunit , pylint...
byte compiling bbclass ?
http://lists.idyll.org/listinfo/testing-in-python
categories for /classes : qa,pkg,build,doc,...

test quality of a recipe :
SRC_URI tarball contains no P/PV/PN => dangerous
example "${NONFREE_MIRRORS}/oki/OKI_fse.tar.gz"

cf : http://handhelds.org/~zecke/bitbake-qa-0.1.tar.bz2

== common & easy script encapsulation ==

== OpenEmbedded showcase ==

some demonstration of OE ( video , screenshots ... ).

== target web interface ==

* port Webif to OE
my bug report on this : WIP

* libopkg client support ( via http://packagekit.org/ ? )
* start a new one from scratch ? ( pylons based for example ).

== delivry/release class ==

Produice a report on a delivry.
Tool that give good report are often appricated ( there is something to show ).
Managers/custumers/developers can keep useful and pretty trace of the project.

* log/tag revision of each versioned tree ( that are not in distro/src-revs ) ( mtn status / svn info / -> rev-history , delivry-info )
* show software update
* show infos on bugs ( closed/news etc ) as a changelog
* show stats about image and packets ( boabab etc )
* show copyrights , licences ...

== emulator/qemu tasks ==

some tasks that could be used for tests and debug.
* image is bootable ? ( ca be call in testsuite of task that build the img )
* test first boot
* upgrade not failed ? ( print the guilty )
* broken linkage ? ( can be call in testsuite of sanity.bbclass )

provides some methods
* build image
* launch with adapted parameter according to a qemu-machine conf
* NFS etc

see poky anjuta plugin and poky qemu scripts.

== coreboot integration ==

* some recipes for utils
* use openembedded instead of buildrom ( yes another build system :/ )

== Gentoo ebuild compatibility ==

using script ( crazy ) or common variables ( completely crazy ).

= Centers of interest related to openembedded =

* Industrial applications ( automation , robotic )
* [[Quality Assurance]]
* [http://www.gnome.org/press/releases/gmae.html Gnome Mobile]

http://zecke.blogspot.com/2006/10/softwareengineering-and-qa-for-free.html http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000323.html

User:Ronan

2008-08-13T15:12:00Z

Ronan: /* more documentation */

I'm more a [http://en.wikipedia.org/wiki/Software_architect Software architect].
Sometimes it's hard to explain what you should do in the enterprise. I work on improve this state of thing.

= OpenEmbedded Experience =

== 2006 - 2007 : Paper-book project ==

Prototype for [http://www.paper-book.com paper-book]

* http://scourge.fr/mathdesc/images/pb/PB-1.JPG
* http://scourge.fr/mathdesc/images/pb/PB-2.JPG
* http://scourge.fr/mathdesc/images/pb/PB-3.JPG

== 2007 - 2008 : Nao ==

Soon some information about it.

= Wishlist =

This section is my wiki for idea i'd like to work to improve my openembedded
Some are perhaps really bad ideas ( not enough searsh ), or already exists , let me know.

== bugzilla integration ==

if ( OE_WARN_BUG == 1 )
checkbug(${PN})

bitbake -bugz mozilla

cf http://code.google.com/p/pybugz/source/browse/trunk/README?r=28

== reduce image size method ==

Reduce image size using remote lsof session on target to check useless files , packages ( blame useless dependency ) ... diff with $ROOTFS and eventually try them by size.

#REMOTE_METHODE = "ssh 192.168.0.1"
REMOTE_METHODE = "tty /dev/USBtty1"
bitbake -lsof-session mycustom-image.bb

http://www.ibm.com/developerworks/linux/library/l-inotify.html

i should also try some code inspector ( to check code duplication etc to advise programmer where place could be saved ).
Some Steiner stuff on fusil could be useful.

== report tool ==

print beautiful documentation on the distro/packages/whatever.
* template design
* baobab ...

[http://www.reportlab.org/rl_toolkit.html reportlab]

== netboot images ==

mkelf-linux kernel-image [ramdiskimage]
keywords : initramdisk

== some QA ideas ==

=== fuzzing our softwares ===

opkg, bitbake etc

* using fusil [http://fusil.hachoir.org fusil] ( fuzzing report ) ,
i made the recipe see [http://bugs.openembedded.net/show_bug.cgi?id=4495 bug 4495]
look success story at http://fusil.hachoir.org/trac/wiki/CrashList

=== more documentation ===

bbclass documentation ( how - as a policy )
=> provide documentations about how to make better code in bitbake
=> pydoc , doctest , unittest , pyunit , pylint...
byte compiling bbclass ?
http://lists.idyll.org/listinfo/testing-in-python
categories for /classes : qa,pkg,build,doc,...

test quality of a recipe :
SRC_URI tarball contains no P/PV/PN => dangerous
example "${NONFREE_MIRRORS}/oki/OKI_fse.tar.gz"

cf : http://handhelds.org/~zecke/bitbake-qa-0.1.tar.bz2

== common & easy script encapsulation ==

== OpenEmbedded showcase ==

some demonstration of OE ( video , screenshots ... ).

== target web interface ==

* port Webif to OE
my bug report on this : WIP

* libopkg client support ( via http://packagekit.org/ ? )
* start a new one from scratch ? ( pylons based for example ).

== delivry/release class ==

Produice a report on a delivry.
Tool that give good report are often appricated ( there is something to show ).
Managers/custumers/developers can keep useful and pretty trace of the project.

* log/tag revision of each versioned tree ( that are not in distro/src-revs ) ( mtn status / svn info / -> rev-history , delivry-info )
* show software update
* show infos on bugs ( closed/news etc ) as a changelog
* show stats about image and packets ( boabab etc )
* show copyrights , licences ...

== emulator/qemu tasks ==

some tasks that could be used for tests and debug.
* image is bootable ? ( ca be call in testsuite of task that build the img )
* test first boot
* upgrade not failed ? ( print the guilty )
* broken linkage ? ( can be call in testsuite of sanity.bbclass )

provides some methods
* build image
* launch with adapted parameter according to a qemu-machine conf
* NFS etc

see poky anjuta plugin and poky qemu scripts.

== coreboot integration ==

* some recipes for utils
* use openembedded instead of buildrom ( yes another build system :/ )

== Gentoo ebuild compatibility ==

using script ( crazy ) or common variables ( completely crazy ).

= Centers of interest related to openembedded =

* [http://www.gnome.org/press/releases/gmae.html Gnome Mobile]
* [[Quality Assurance]]
http://zecke.blogspot.com/2006/10/softwareengineering-and-qa-for-free.html http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000323.html

User:Ronan

2008-08-13T15:10:43Z

Ronan: /* fuzzing our software */

I'm more a [http://en.wikipedia.org/wiki/Software_architect Software architect].
Sometimes it's hard to explain what you should do in the enterprise. I work on improve this state of thing.

= OpenEmbedded Experience =

== 2006 - 2007 : Paper-book project ==

Prototype for [http://www.paper-book.com paper-book]

* http://scourge.fr/mathdesc/images/pb/PB-1.JPG
* http://scourge.fr/mathdesc/images/pb/PB-2.JPG
* http://scourge.fr/mathdesc/images/pb/PB-3.JPG

== 2007 - 2008 : Nao ==

Soon some information about it.

= Wishlist =

This section is my wiki for idea i'd like to work to improve my openembedded
Some are perhaps really bad ideas ( not enough searsh ), or already exists , let me know.

== bugzilla integration ==

if ( OE_WARN_BUG == 1 )
checkbug(${PN})

bitbake -bugz mozilla

cf http://code.google.com/p/pybugz/source/browse/trunk/README?r=28

== reduce image size method ==

Reduce image size using remote lsof session on target to check useless files , packages ( blame useless dependency ) ... diff with $ROOTFS and eventually try them by size.

#REMOTE_METHODE = "ssh 192.168.0.1"
REMOTE_METHODE = "tty /dev/USBtty1"
bitbake -lsof-session mycustom-image.bb

http://www.ibm.com/developerworks/linux/library/l-inotify.html

i should also try some code inspector ( to check code duplication etc to advise programmer where place could be saved ).
Some Steiner stuff on fusil could be useful.

== report tool ==

print beautiful documentation on the distro/packages/whatever.
* template design
* baobab ...

[http://www.reportlab.org/rl_toolkit.html reportlab]

== netboot images ==

mkelf-linux kernel-image [ramdiskimage]
keywords : initramdisk

== some QA ideas ==

=== fuzzing our softwares ===

opkg, bitbake etc

* using fusil [http://fusil.hachoir.org fusil] ( fuzzing report ) ,
i made the recipe see [http://bugs.openembedded.net/show_bug.cgi?id=4495 bug 4495]
look success story at http://fusil.hachoir.org/trac/wiki/CrashList

= more documentation =

bbclass documentation ( how - as a policy )
=> provide documentations about how to make better code in bitbake
=> pydoc , doctest , unittest , pyunit , pylint...
byte compiling bbclass ?
http://lists.idyll.org/listinfo/testing-in-python
categories for /classes : qa,pkg,build,doc,...

test quality of a recipe :
SRC_URI tarball contains no P/PV/PN => dangerous
example "${NONFREE_MIRRORS}/oki/OKI_fse.tar.gz"

cf : http://handhelds.org/~zecke/bitbake-qa-0.1.tar.bz2

== common & easy script encapsulation ==

== OpenEmbedded showcase ==

some demonstration of OE ( video , screenshots ... ).

== target web interface ==

* port Webif to OE
my bug report on this : WIP

* libopkg client support ( via http://packagekit.org/ ? )
* start a new one from scratch ? ( pylons based for example ).

== delivry/release class ==

Produice a report on a delivry.
Tool that give good report are often appricated ( there is something to show ).
Managers/custumers/developers can keep useful and pretty trace of the project.

* log/tag revision of each versioned tree ( that are not in distro/src-revs ) ( mtn status / svn info / -> rev-history , delivry-info )
* show software update
* show infos on bugs ( closed/news etc ) as a changelog
* show stats about image and packets ( boabab etc )
* show copyrights , licences ...

== emulator/qemu tasks ==

some tasks that could be used for tests and debug.
* image is bootable ? ( ca be call in testsuite of task that build the img )
* test first boot
* upgrade not failed ? ( print the guilty )
* broken linkage ? ( can be call in testsuite of sanity.bbclass )

provides some methods
* build image
* launch with adapted parameter according to a qemu-machine conf
* NFS etc

see poky anjuta plugin and poky qemu scripts.

== coreboot integration ==

* some recipes for utils
* use openembedded instead of buildrom ( yes another build system :/ )

== Gentoo ebuild compatibility ==

using script ( crazy ) or common variables ( completely crazy ).

= Centers of interest related to openembedded =

* [http://www.gnome.org/press/releases/gmae.html Gnome Mobile]
* [[Quality Assurance]]
http://zecke.blogspot.com/2006/10/softwareengineering-and-qa-for-free.html http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000323.html

User:Ronan

2008-08-13T15:07:19Z

Ronan: /* some QA ideas */

I'm more a [http://en.wikipedia.org/wiki/Software_architect Software architect].
Sometimes it's hard to explain what you should do in the enterprise. I work on improve this state of thing.

= OpenEmbedded Experience =

== 2006 - 2007 : Paper-book project ==

Prototype for [http://www.paper-book.com paper-book]

* http://scourge.fr/mathdesc/images/pb/PB-1.JPG
* http://scourge.fr/mathdesc/images/pb/PB-2.JPG
* http://scourge.fr/mathdesc/images/pb/PB-3.JPG

== 2007 - 2008 : Nao ==

Soon some information about it.

= Wishlist =

This section is my wiki for idea i'd like to work to improve my openembedded
Some are perhaps really bad ideas ( not enough searsh ), or already exists , let me know.

== bugzilla integration ==

if ( OE_WARN_BUG == 1 )
checkbug(${PN})

bitbake -bugz mozilla

cf http://code.google.com/p/pybugz/source/browse/trunk/README?r=28

== reduce image size method ==

Reduce image size using remote lsof session on target to check useless files , packages ( blame useless dependency ) ... diff with $ROOTFS and eventually try them by size.

#REMOTE_METHODE = "ssh 192.168.0.1"
REMOTE_METHODE = "tty /dev/USBtty1"
bitbake -lsof-session mycustom-image.bb

http://www.ibm.com/developerworks/linux/library/l-inotify.html

i should also try some code inspector ( to check code duplication etc to advise programmer where place could be saved ).
Some Steiner stuff on fusil could be useful.

== report tool ==

print beautiful documentation on the distro/packages/whatever.
* template design
* baobab ...

[http://www.reportlab.org/rl_toolkit.html reportlab]

== netboot images ==

mkelf-linux kernel-image [ramdiskimage]
keywords : initramdisk

== some QA ideas ==

= fuzzing our software =

opkg, bitbake etc

* using fusil [http://fusil.hachoir.org fusil] ( fuzzing report ) ,
i made the recipe see [http://bugs.openembedded.net/show_bug.cgi?id=4495 bug 4495]

= more documentation =

bbclass documentation ( how - as a policy )
=> provide documentations about how to make better code in bitbake
=> pydoc , doctest , unittest , pyunit , pylint...
byte compiling bbclass ?
http://lists.idyll.org/listinfo/testing-in-python
categories for /classes : qa,pkg,build,doc,...

test quality of a recipe :
SRC_URI tarball contains no P/PV/PN => dangerous
example "${NONFREE_MIRRORS}/oki/OKI_fse.tar.gz"

cf : http://handhelds.org/~zecke/bitbake-qa-0.1.tar.bz2

== common & easy script encapsulation ==

== OpenEmbedded showcase ==

some demonstration of OE ( video , screenshots ... ).

== target web interface ==

* port Webif to OE
my bug report on this : WIP

* libopkg client support ( via http://packagekit.org/ ? )
* start a new one from scratch ? ( pylons based for example ).

== delivry/release class ==

Produice a report on a delivry.
Tool that give good report are often appricated ( there is something to show ).
Managers/custumers/developers can keep useful and pretty trace of the project.

* log/tag revision of each versioned tree ( that are not in distro/src-revs ) ( mtn status / svn info / -> rev-history , delivry-info )
* show software update
* show infos on bugs ( closed/news etc ) as a changelog
* show stats about image and packets ( boabab etc )
* show copyrights , licences ...

== emulator/qemu tasks ==

some tasks that could be used for tests and debug.
* image is bootable ? ( ca be call in testsuite of task that build the img )
* test first boot
* upgrade not failed ? ( print the guilty )
* broken linkage ? ( can be call in testsuite of sanity.bbclass )

provides some methods
* build image
* launch with adapted parameter according to a qemu-machine conf
* NFS etc

see poky anjuta plugin and poky qemu scripts.

== coreboot integration ==

* some recipes for utils
* use openembedded instead of buildrom ( yes another build system :/ )

== Gentoo ebuild compatibility ==

using script ( crazy ) or common variables ( completely crazy ).

= Centers of interest related to openembedded =

* [http://www.gnome.org/press/releases/gmae.html Gnome Mobile]
* [[Quality Assurance]]
http://zecke.blogspot.com/2006/10/softwareengineering-and-qa-for-free.html http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000323.html

User:Ronan

2008-08-13T09:45:28Z

Ronan: /* some QA ideas */

I'm more a [http://en.wikipedia.org/wiki/Software_architect Software architect].
Sometimes it's hard to explain what you should do in the enterprise. I work on improve this state of thing.

= OpenEmbedded Experience =

== 2006 - 2007 : Paper-book project ==

Prototype for [http://www.paper-book.com paper-book]

* http://scourge.fr/mathdesc/images/pb/PB-1.JPG
* http://scourge.fr/mathdesc/images/pb/PB-2.JPG
* http://scourge.fr/mathdesc/images/pb/PB-3.JPG

== 2007 - 2008 : Nao ==

Soon some information about it.

= Wishlist =

This section is my wiki for idea i'd like to work to improve my openembedded
Some are perhaps really bad ideas ( not enough searsh ), or already exists , let me know.

== bugzilla integration ==

if ( OE_WARN_BUG == 1 )
checkbug(${PN})

bitbake -bugz mozilla

cf http://code.google.com/p/pybugz/source/browse/trunk/README?r=28

== reduce image size method ==

Reduce image size using remote lsof session on target to check useless files , packages ( blame useless dependency ) ... diff with $ROOTFS and eventually try them by size.

#REMOTE_METHODE = "ssh 192.168.0.1"
REMOTE_METHODE = "tty /dev/USBtty1"
bitbake -lsof-session mycustom-image.bb

http://www.ibm.com/developerworks/linux/library/l-inotify.html

i should also try some code inspector ( to check code duplication etc to advise programmer where place could be saved ).
Some Steiner stuff on fusil could be useful.

== report tool ==

print beautiful documentation on the distro/packages/whatever.
* template design
* baobab ...

[http://www.reportlab.org/rl_toolkit.html reportlab]

== netboot images ==

mkelf-linux kernel-image [ramdiskimage]
keywords : initramdisk

== some QA ideas ==

[http://fusil.hachoir.org fusil] ( fuzzing report ) , [http://bugs.openembedded.net/show_bug.cgi?id=4495 bug 4495]

bbclass documentation ( how - as a policy )
=> provide documentations about how to make better code in bitbake
=> pydoc , doctest , unittest , pyunit , pylint...
byte compiling bbclass ?
http://lists.idyll.org/listinfo/testing-in-python
categories for /classes : qa,pkg,build,doc,...

test quality of a recipe :
SRC_URI tarball contains no P/PV/PN => dangerous
example "${NONFREE_MIRRORS}/oki/OKI_fse.tar.gz"

cf : http://handhelds.org/~zecke/bitbake-qa-0.1.tar.bz2

== common & easy script encapsulation ==

== OpenEmbedded showcase ==

some demonstration of OE ( video , screenshots ... ).

== target web interface ==

* port Webif to OE
my bug report on this : WIP

* libopkg client support ( via http://packagekit.org/ ? )
* start a new one from scratch ? ( pylons based for example ).

== delivry/release class ==

Produice a report on a delivry.
Tool that give good report are often appricated ( there is something to show ).
Managers/custumers/developers can keep useful and pretty trace of the project.

* log/tag revision of each versioned tree ( that are not in distro/src-revs ) ( mtn status / svn info / -> rev-history , delivry-info )
* show software update
* show infos on bugs ( closed/news etc ) as a changelog
* show stats about image and packets ( boabab etc )
* show copyrights , licences ...

== emulator/qemu tasks ==

some tasks that could be used for tests and debug.
* image is bootable ? ( ca be call in testsuite of task that build the img )
* test first boot
* upgrade not failed ? ( print the guilty )
* broken linkage ? ( can be call in testsuite of sanity.bbclass )

provides some methods
* build image
* launch with adapted parameter according to a qemu-machine conf
* NFS etc

see poky anjuta plugin and poky qemu scripts.

== coreboot integration ==

* some recipes for utils
* use openembedded instead of buildrom ( yes another build system :/ )

== Gentoo ebuild compatibility ==

using script ( crazy ) or common variables ( completely crazy ).

= Centers of interest related to openembedded =

* [http://www.gnome.org/press/releases/gmae.html Gnome Mobile]
* [[Quality Assurance]]
http://zecke.blogspot.com/2006/10/softwareengineering-and-qa-for-free.html http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000323.html

User:Ronan

2008-08-13T08:33:06Z

Ronan: /* Wishlist */

I'm more a [http://en.wikipedia.org/wiki/Software_architect Software architect].
Sometimes it's hard to explain what you should do in the enterprise. I work on improve this state of thing.

= OpenEmbedded Experience =

== 2006 - 2007 : Paper-book project ==

Prototype for [http://www.paper-book.com paper-book]

* http://scourge.fr/mathdesc/images/pb/PB-1.JPG
* http://scourge.fr/mathdesc/images/pb/PB-2.JPG
* http://scourge.fr/mathdesc/images/pb/PB-3.JPG

== 2007 - 2008 : Nao ==

Soon some information about it.

= Wishlist =

This section is my wiki for idea i'd like to work to improve my openembedded
Some are perhaps really bad ideas ( not enough searsh ), or already exists , let me know.

== bugzilla integration ==

if ( OE_WARN_BUG == 1 )
checkbug(${PN})

bitbake -bugz mozilla

cf http://code.google.com/p/pybugz/source/browse/trunk/README?r=28

== reduce image size method ==

Reduce image size using remote lsof session on target to check useless files , packages ( blame useless dependency ) ... diff with $ROOTFS and eventually try them by size.

#REMOTE_METHODE = "ssh 192.168.0.1"
REMOTE_METHODE = "tty /dev/USBtty1"
bitbake -lsof-session mycustom-image.bb

http://www.ibm.com/developerworks/linux/library/l-inotify.html

i should also try some code inspector ( to check code duplication etc to advise programmer where place could be saved ).
Some Steiner stuff on fusil could be useful.

== report tool ==

print beautiful documentation on the distro/packages/whatever.
* template design
* baobab ...

[http://www.reportlab.org/rl_toolkit.html reportlab]

== netboot images ==

mkelf-linux kernel-image [ramdiskimage]
keywords : initramdisk

== some QA ideas ==

[http://fusil.hachoir.org fusil] ( fuzzing report ) , bug : WIP

bbclass documentation ( how - as a policy )
=> provide documentations about how to make better code in bitbake
=> pydoc , doctest , unittest , pyunit , pylint...
byte compiling bbclass ?
http://lists.idyll.org/listinfo/testing-in-python
categories for /classes : qa,pkg,build,doc,...

test quality of a recipe :
SRC_URI tarball contains no P/PV/PN => dangerous
example "${NONFREE_MIRRORS}/oki/OKI_fse.tar.gz"

cf : http://handhelds.org/~zecke/bitbake-qa-0.1.tar.bz2

== common & easy script encapsulation ==

== OpenEmbedded showcase ==

some demonstration of OE ( video , screenshots ... ).

== target web interface ==

* port Webif to OE
my bug report on this : WIP

* libopkg client support ( via http://packagekit.org/ ? )
* start a new one from scratch ? ( pylons based for example ).

== delivry/release class ==

Produice a report on a delivry.
Tool that give good report are often appricated ( there is something to show ).
Managers/custumers/developers can keep useful and pretty trace of the project.

* log/tag revision of each versioned tree ( that are not in distro/src-revs ) ( mtn status / svn info / -> rev-history , delivry-info )
* show software update
* show infos on bugs ( closed/news etc ) as a changelog
* show stats about image and packets ( boabab etc )
* show copyrights , licences ...

== emulator/qemu tasks ==

some tasks that could be used for tests and debug.
* image is bootable ? ( ca be call in testsuite of task that build the img )
* test first boot
* upgrade not failed ? ( print the guilty )
* broken linkage ? ( can be call in testsuite of sanity.bbclass )

provides some methods
* build image
* launch with adapted parameter according to a qemu-machine conf
* NFS etc

see poky anjuta plugin and poky qemu scripts.

== coreboot integration ==

* some recipes for utils
* use openembedded instead of buildrom ( yes another build system :/ )

== Gentoo ebuild compatibility ==

using script ( crazy ) or common variables ( completely crazy ).

= Centers of interest related to openembedded =

* [http://www.gnome.org/press/releases/gmae.html Gnome Mobile]
* [[Quality Assurance]]
http://zecke.blogspot.com/2006/10/softwareengineering-and-qa-for-free.html http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000323.html

Quality assurance

2008-08-06T16:41:59Z

Ronan: New page: Quality assurance, the process or set of processes used to measure and assure the quality of a product ( cf [http://en.wikipedia.org/wiki/Quality_Assurance wikipedia] ) * BitTest ...

[[Quality assurance]], the process or set of processes used to measure and assure the quality of a product ( cf [http://en.wikipedia.org/wiki/Quality_Assurance wikipedia] )

* [[BitTest]] :
http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000255.html
* [[oetest]] :

* [[oestats]] / [[TinderBox]] : [[How_do_I_send_automatic_success_and_failure_reports]]
* insane and sanity bbclass...

User:Ronan

2008-08-06T15:43:32Z

Ronan: /* Centers of interest related to openembedded */

Quality Assurance

2008-08-06T15:42:48Z

Ronan: New page: Quality assurance, the process or set of processes used to measure and assure the quality of a product ( cf [http://en.wikipedia.org/wiki/Quality_Assurance wikipedia] ) * BitTest : ht...

[[Quality assurance]], the process or set of processes used to measure and assure the quality of a product ( cf [http://en.wikipedia.org/wiki/Quality_Assurance wikipedia] )

* BitTest :
http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000255.html
* oetest
* tinderbox
* insane and sanity bbclass...

User:Ronan

2008-08-06T15:34:39Z

Ronan: /* Centers of interest related to openembedded */

User:Ronan

2008-08-05T16:41:19Z

Ronan: /* Centers of interest related to openembedded */

User:Ronan

2008-08-05T16:32:23Z

Ronan: /* OpenEmbedded Experience */

User:Ronan

2008-08-05T16:24:50Z

Ronan: /* Wishlist */

= OpenEmbedded Experience =

== 2006 - 2007 : Paper-book project ==

Prototype for [http://www.paper-book.com paper-book]

* http://scourge.fr/mathdesc/images/pb/PB-1.JPG
* http://scourge.fr/mathdesc/images/pb/PB-2.JPG
* http://scourge.fr/mathdesc/images/pb/PB-3.JPG

== 2007 - 2008 : Nao ==

Soon some information about it.

= Wishlist =

This section is my wiki for idea i'd like to work to improve my openembedded
Help is welcome. Perhaps somethings in the list already exists , let me know.

== buzilla integration ==

if ( OE_WARN_BUG == 1 )
checkbug(${PN})

bitbake -bugz mozilla

cf http://code.google.com/p/pybugz/source/browse/trunk/README?r=28

== lsof integration ==

Reduce image size using remote lsof session on target to check useless files , packages ( blame useless dependancy ) ... comparing with $ROOTFS and eventually try them by size.

#REMOTE_METHODE = "ssh 192.168.0.1"
REMOTE_METHODE = "tty /dev/USBtty1"
bitbake -lsof-session mycustom-image.bb

i should also try some code inspector ( to check code duplication etc to advise programmer where place could be saved ).
Some Steiner stuff on fusil could be useful.

== report tool ==

print beautiful documentation on the distro/packages/whatever.
keywords : baobab ...

== netboot images ==

mkelf-linux kernel-image [ramdiskimage]
keywords : initramdisk

== coreboot integration ==

* some recipes for utils
* use openembedded instead of buildrom ( yes another build system :/ )

== Gentoo ebuild compatibility ==

using script ( crazy ) or common variables ( completely crazy ).

= Centers of interest related to openembedded =

http://www.gnome.org/press/releases/gmae.html
http://zecke.blogspot.com/2006/10/softwareengineering-and-qa-for-free.html

User:Ronan

2008-08-05T14:21:37Z

Ronan: /* lsof integration */

User:Ronan

2008-08-05T14:19:33Z

Ronan: /* 2007 - 2008 : Nao */

User talk:Ronan

2008-07-18T15:03:48Z

Ronan: Removing all content from page

User:Ronan

2008-07-18T15:03:38Z

Ronan: New page: = OpenEmbedded Experience = == 2006 - 2007 : Paper-book project == Prototype for [http://www.paper-book.com paper-book] * http://scourge.fr/mathdesc/images/pb/PB-1.JPG * http://scourge....

User talk:Ronan

2008-07-18T14:51:35Z

Ronan:

My first Openembedded based BSP :

Prototype for [http://www.paper-book.com paper-book]

* http://scourge.fr/mathdesc/images/pb/PB-1.JPG
* http://scourge.fr/mathdesc/images/pb/PB-2.JPG
* http://scourge.fr/mathdesc/images/pb/PB-3.JPG

User talk:Ronan

2008-07-18T14:48:48Z

Ronan: add first openembedded experience

My first Openembedded based BSP :

http://scourge.fr/mathdesc/images/pb/PB-1.JPG
http://scourge.fr/mathdesc/images/pb/PB-2.JPG
http://scourge.fr/mathdesc/images/pb/PB-3.JPG