<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.openembedded.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Sveretenov</id>
	<title>Openembedded.org - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.openembedded.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Sveretenov"/>
	<link rel="alternate" type="text/html" href="https://www.openembedded.org/wiki/Special:Contributions/Sveretenov"/>
	<updated>2026-05-08T22:44:10Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.10</generator>
	<entry>
		<id>https://www.openembedded.org/w/index.php?title=User:Ronan&amp;diff=5467</id>
		<title>User:Ronan</title>
		<link rel="alternate" type="text/html" href="https://www.openembedded.org/w/index.php?title=User:Ronan&amp;diff=5467"/>
		<updated>2013-01-07T18:39:46Z</updated>

		<summary type="html">&lt;p&gt;Sveretenov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;I&#039;m more a [http://en.wikipedia.org/wiki/Software_architect Software architect].&lt;br /&gt;
Sometimes it&#039;s hard to explain what you should do in the enterprise. I work on improve this state of thing.&lt;br /&gt;
&lt;br /&gt;
= OpenEmbedded Experience =&lt;br /&gt;
&lt;br /&gt;
== 2006 - 2007 : Paper-book project ==&lt;br /&gt;
&lt;br /&gt;
Prototype for [http://www.paper-book.com paper-book]&lt;br /&gt;
&lt;br /&gt;
* http://scourge.fr/mathdesc/images/pb/PB-1.JPG&lt;br /&gt;
* http://scourge.fr/mathdesc/images/pb/PB-2.JPG&lt;br /&gt;
* http://scourge.fr/mathdesc/images/pb/PB-3.JPG&lt;br /&gt;
&lt;br /&gt;
== 2007 - 2008 : Nao ==&lt;br /&gt;
&lt;br /&gt;
Soon some information about it.&lt;br /&gt;
&lt;br /&gt;
= Wishlist =&lt;br /&gt;
&lt;br /&gt;
This section is my wiki for idea i&#039;d like to work to improve my openembedded &lt;br /&gt;
Some are perhaps really bad ideas ( not enough searsh ), or already exists , let me know.&lt;br /&gt;
&lt;br /&gt;
== better logs reports ==&lt;br /&gt;
&lt;br /&gt;
i missed important error compiling lost of software&lt;br /&gt;
* http://opensource.bolloretelecom.eu/projects/oestats/wiki/oestats&lt;br /&gt;
* should we use logging python module ?&lt;br /&gt;
&lt;br /&gt;
== bugzilla integration ==&lt;br /&gt;
&lt;br /&gt;
 if ( OE_WARN_BUG == 1 )&lt;br /&gt;
  checkbug(${PN})&lt;br /&gt;
&lt;br /&gt;
 bitbake -bugz mozilla &lt;br /&gt;
&lt;br /&gt;
cf :&lt;br /&gt;
* seppuku.bbclass&lt;br /&gt;
* http://code.google.com/p/pybugz/source/browse/trunk/README?r=28&lt;br /&gt;
&lt;br /&gt;
== reduce image size method ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
 #REMOTE_METHODE = &amp;quot;ssh 192.168.0.1&amp;quot;&lt;br /&gt;
 REMOTE_METHODE = &amp;quot;tty /dev/USBtty1&amp;quot;&lt;br /&gt;
 bitbake -lsof-session mycustom-image.bb&lt;br /&gt;
&lt;br /&gt;
http://www.ibm.com/developerworks/linux/library/l-inotify.html&lt;br /&gt;
&lt;br /&gt;
i should also try some code inspector ( to check code duplication etc to advise programmer where place could be saved ).&lt;br /&gt;
Some Steiner stuff on fusil could be useful.&lt;br /&gt;
&lt;br /&gt;
* /usr/include , /usr/share/, /usr/src ... .debug directory should be tested first.&lt;br /&gt;
&lt;br /&gt;
== report tool ==&lt;br /&gt;
&lt;br /&gt;
print beautiful documentation on the distro/packages/whatever.&lt;br /&gt;
* template design&lt;br /&gt;
* baobab ...&lt;br /&gt;
&lt;br /&gt;
perharps [http://www.reportlab.org/rl_toolkit.html reportlab] APPS for oestats. Look http://docs.djangoproject.com/en/dev/howto/outputting-pdf/ ( example works pretty well).&lt;br /&gt;
&lt;br /&gt;
== netboot images ==&lt;br /&gt;
&lt;br /&gt;
mkelf-linux kernel-image [ramdiskimage]&lt;br /&gt;
keywords : initramdisk &lt;br /&gt;
&lt;br /&gt;
== some QA ideas ==&lt;br /&gt;
&lt;br /&gt;
=== fuzzing our softwares ===&lt;br /&gt;
&lt;br /&gt;
opkg, bitbake etc&lt;br /&gt;
&lt;br /&gt;
* using [http://fusil.hachoir.org fusil] ( fuzzing report ) ,&lt;br /&gt;
i made the recipe see [http://bugs.openembedded.net/show_bug.cgi?id=4495 bug 4495]&lt;br /&gt;
look success story at http://fusil.hachoir.org/trac/wiki/CrashList&lt;br /&gt;
&lt;br /&gt;
=== more documentation ===&lt;br /&gt;
&lt;br /&gt;
==== bitbake documentation ====&lt;br /&gt;
I started bitbake developer documentation here : [[Bitbake]]&lt;br /&gt;
TODO :&lt;br /&gt;
&lt;br /&gt;
* provide documentations about how to make better code in bitbake&lt;br /&gt;
* pydoc , doctest , unittest , pyunit , pylint...&lt;br /&gt;
* byte compiling bbclass , what is done by cache ?&lt;br /&gt;
* http://lists.idyll.org/listinfo/testing-in-python&lt;br /&gt;
* categories for /classes : qa,pkg,build,doc,...&lt;br /&gt;
&lt;br /&gt;
==== bbclass documentation ====&lt;br /&gt;
&lt;br /&gt;
* should this features be implemented as a bbclass or in bitbake core library ? &lt;br /&gt;
* authors and contact in bbclass ! some of its need to be rewrite due to changes in python =&amp;gt; 2.4 , we should detects them&lt;br /&gt;
and add to a TODO-featuring tracker.&lt;br /&gt;
* force to provide documentation as a policy&lt;br /&gt;
&lt;br /&gt;
=== test quality of a recipe ===&lt;br /&gt;
&lt;br /&gt;
* (all ?) field well filled &lt;br /&gt;
* SRC_URI tarball contains no P/PV/PN =&amp;gt; dangerous&lt;br /&gt;
* no SRCREV fixed , PV = &amp;quot;x.y.z+svnr${SRCREV}&amp;quot; : &lt;br /&gt;
perharps allow in a pending branch and auto-apply in the stable one. &lt;br /&gt;
http://projects.linuxtogo.org/pipermail/openembedded-devel/2007-July/002639.html&lt;br /&gt;
* are SRC_URI fetchable ? we can fix it automagically changing SRC_URI for our MIRROR &lt;br /&gt;
* initscript without INITSCRIPT mecanism ( we need , for each new mecanism, write a recipe test and documentation )&lt;br /&gt;
* do_install with cp cmd instead of install &lt;br /&gt;
* warns on RPROVIDES&lt;br /&gt;
* recipe modification without upgrade the PR&lt;br /&gt;
&lt;br /&gt;
cf : http://handhelds.org/~zecke/bitbake-qa-0.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
== common &amp;amp; easy script encapsulation ==&lt;br /&gt;
&lt;br /&gt;
== OpenEmbedded showcase ==&lt;br /&gt;
&lt;br /&gt;
We should promote OE projects (not only fic &amp;amp; o-hand.com stuffs)&lt;br /&gt;
&lt;br /&gt;
== target web interface ==&lt;br /&gt;
&lt;br /&gt;
* port Webif to OE&lt;br /&gt;
my bug report on this : WIP&lt;br /&gt;
&lt;br /&gt;
* libopkg client support ( via http://packagekit.org/ ? )&lt;br /&gt;
* start a new one from scratch ? ( pylons based for example ).&lt;br /&gt;
&lt;br /&gt;
== delivery/release class ==&lt;br /&gt;
&lt;br /&gt;
Produce a report on a delivery.&lt;br /&gt;
Tool that give good report are often appreciated ( there is something to show ).&lt;br /&gt;
Managers/customers/developers can keep useful and pretty traces of their projects.&lt;br /&gt;
&lt;br /&gt;
* log/tag revision of each versioned tree ( that are not in distro/src-revs ) ( mtn status / svn info / -&amp;gt; rev-history , delivery-info )&lt;br /&gt;
* show software update&lt;br /&gt;
* show infos on bugs ( closed/news etc ) as a changelog&lt;br /&gt;
* show stats about image and packets ( boabab etc )&lt;br /&gt;
* show copyrights , licenses ...&lt;br /&gt;
&lt;br /&gt;
== emulator/qemu tasks ==&lt;br /&gt;
&lt;br /&gt;
some tasks that could be used for tests and debug.&lt;br /&gt;
* image is bootable ? ( ca be call in testsuite of task that build the img )&lt;br /&gt;
* test first boot&lt;br /&gt;
* upgrade not failed ?  ( print the guilty )&lt;br /&gt;
* broken linkage ? ( can be call in testsuite of sanity.bbclass )&lt;br /&gt;
&lt;br /&gt;
provides some methods&lt;br /&gt;
* build image&lt;br /&gt;
* launch with adapted parameter according to a qemu-machine conf&lt;br /&gt;
* NFS etc&lt;br /&gt;
&lt;br /&gt;
see poky anjuta plugin and poky qemu scripts.&lt;br /&gt;
&lt;br /&gt;
== coreboot integration ==&lt;br /&gt;
&lt;br /&gt;
* some recipes for utils &lt;br /&gt;
* use openembedded instead of buildrom ( yes another build system :/ )&lt;br /&gt;
&lt;br /&gt;
== Gentoo ebuild compatibility ==&lt;br /&gt;
&lt;br /&gt;
using script ( crazy ) or common variables ( completely crazy ).&lt;br /&gt;
&lt;br /&gt;
== use git facilities ==&lt;br /&gt;
&lt;br /&gt;
=== locate bug when upgrading oe ===&lt;br /&gt;
something like :&lt;br /&gt;
&lt;br /&gt;
 git bisect start&lt;br /&gt;
 git bisect bad&lt;br /&gt;
 ops = rec_ops(BB_CMD)&lt;br /&gt;
 if [ $? -eq 0 ]&lt;br /&gt;
  git bisect bad&lt;br /&gt;
  undo_ops(ops)&lt;br /&gt;
 else &lt;br /&gt;
  git bisect good&lt;br /&gt;
 fi&lt;br /&gt;
&lt;br /&gt;
* if bug is a non-version fixed package , fix version and continue&lt;br /&gt;
* make a report&lt;br /&gt;
* cf http://www.miximum.fr/methodes-et-outils/79-debusquer-une-regression-avec-git-bisect ( fr )&lt;br /&gt;
&lt;br /&gt;
== IDE integration ==&lt;br /&gt;
&lt;br /&gt;
http://community.buglabs.net/kgilmer/posts/3-OpenEmbedded-Tools-for-Eclipse&lt;br /&gt;
&lt;br /&gt;
= Centers of interest related to openembedded =&lt;br /&gt;
&lt;br /&gt;
* Industrial applications ( automation , robotic ) see http://objects.reprap.org/wiki/User:Ronan&lt;br /&gt;
* [[Quality Assurance]]&lt;br /&gt;
* [http://www.gnome.org/press/releases/gmae.html Gnome Mobile]&lt;br /&gt;
* [http://www.rushessay.com/prices.php buy essay]&lt;br /&gt;
&lt;br /&gt;
http://zecke.blogspot.com/2006/10/softwareengineering-and-qa-for-free.html http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000323.html&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://customessayorder.com/custom-essay.php essay writing services]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ordercustomessay.com/ custom essay]&lt;/div&gt;</summary>
		<author><name>Sveretenov</name></author>
	</entry>
	<entry>
		<id>https://www.openembedded.org/w/index.php?title=User:Ronan&amp;diff=5451</id>
		<title>User:Ronan</title>
		<link rel="alternate" type="text/html" href="https://www.openembedded.org/w/index.php?title=User:Ronan&amp;diff=5451"/>
		<updated>2012-12-24T20:45:20Z</updated>

		<summary type="html">&lt;p&gt;Sveretenov: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;I&#039;m more a [http://en.wikipedia.org/wiki/Software_architect Software architect].&lt;br /&gt;
Sometimes it&#039;s hard to explain what you should do in the enterprise. I work on improve this state of thing.&lt;br /&gt;
&lt;br /&gt;
= OpenEmbedded Experience =&lt;br /&gt;
&lt;br /&gt;
== 2006 - 2007 : Paper-book project ==&lt;br /&gt;
&lt;br /&gt;
Prototype for [http://www.paper-book.com paper-book]&lt;br /&gt;
&lt;br /&gt;
* http://scourge.fr/mathdesc/images/pb/PB-1.JPG&lt;br /&gt;
* http://scourge.fr/mathdesc/images/pb/PB-2.JPG&lt;br /&gt;
* http://scourge.fr/mathdesc/images/pb/PB-3.JPG&lt;br /&gt;
&lt;br /&gt;
== 2007 - 2008 : Nao ==&lt;br /&gt;
&lt;br /&gt;
Soon some information about it.&lt;br /&gt;
&lt;br /&gt;
= Wishlist =&lt;br /&gt;
&lt;br /&gt;
This section is my wiki for idea i&#039;d like to work to improve my openembedded &lt;br /&gt;
Some are perhaps really bad ideas ( not enough searsh ), or already exists , let me know.&lt;br /&gt;
&lt;br /&gt;
== better logs reports ==&lt;br /&gt;
&lt;br /&gt;
i missed important error compiling lost of software&lt;br /&gt;
* http://opensource.bolloretelecom.eu/projects/oestats/wiki/oestats&lt;br /&gt;
* should we use logging python module ?&lt;br /&gt;
&lt;br /&gt;
== bugzilla integration ==&lt;br /&gt;
&lt;br /&gt;
 if ( OE_WARN_BUG == 1 )&lt;br /&gt;
  checkbug(${PN})&lt;br /&gt;
&lt;br /&gt;
 bitbake -bugz mozilla &lt;br /&gt;
&lt;br /&gt;
cf :&lt;br /&gt;
* seppuku.bbclass&lt;br /&gt;
* http://code.google.com/p/pybugz/source/browse/trunk/README?r=28&lt;br /&gt;
&lt;br /&gt;
== reduce image size method ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
 #REMOTE_METHODE = &amp;quot;ssh 192.168.0.1&amp;quot;&lt;br /&gt;
 REMOTE_METHODE = &amp;quot;tty /dev/USBtty1&amp;quot;&lt;br /&gt;
 bitbake -lsof-session mycustom-image.bb&lt;br /&gt;
&lt;br /&gt;
http://www.ibm.com/developerworks/linux/library/l-inotify.html&lt;br /&gt;
&lt;br /&gt;
i should also try some code inspector ( to check code duplication etc to advise programmer where place could be saved ).&lt;br /&gt;
Some Steiner stuff on fusil could be useful.&lt;br /&gt;
&lt;br /&gt;
* /usr/include , /usr/share/, /usr/src ... .debug directory should be tested first.&lt;br /&gt;
&lt;br /&gt;
== report tool ==&lt;br /&gt;
&lt;br /&gt;
print beautiful documentation on the distro/packages/whatever.&lt;br /&gt;
* template design&lt;br /&gt;
* baobab ...&lt;br /&gt;
&lt;br /&gt;
perharps [http://www.reportlab.org/rl_toolkit.html reportlab] APPS for oestats. Look http://docs.djangoproject.com/en/dev/howto/outputting-pdf/ ( example works pretty well).&lt;br /&gt;
&lt;br /&gt;
== netboot images ==&lt;br /&gt;
&lt;br /&gt;
mkelf-linux kernel-image [ramdiskimage]&lt;br /&gt;
keywords : initramdisk &lt;br /&gt;
&lt;br /&gt;
== some QA ideas ==&lt;br /&gt;
&lt;br /&gt;
=== fuzzing our softwares ===&lt;br /&gt;
&lt;br /&gt;
opkg, bitbake etc&lt;br /&gt;
&lt;br /&gt;
* using [http://fusil.hachoir.org fusil] ( fuzzing report ) ,&lt;br /&gt;
i made the recipe see [http://bugs.openembedded.net/show_bug.cgi?id=4495 bug 4495]&lt;br /&gt;
look success story at http://fusil.hachoir.org/trac/wiki/CrashList&lt;br /&gt;
&lt;br /&gt;
=== more documentation ===&lt;br /&gt;
&lt;br /&gt;
==== bitbake documentation ====&lt;br /&gt;
I started bitbake developer documentation here : [[Bitbake]]&lt;br /&gt;
TODO :&lt;br /&gt;
&lt;br /&gt;
* provide documentations about how to make better code in bitbake&lt;br /&gt;
* pydoc , doctest , unittest , pyunit , pylint...&lt;br /&gt;
* byte compiling bbclass , what is done by cache ?&lt;br /&gt;
* http://lists.idyll.org/listinfo/testing-in-python&lt;br /&gt;
* categories for /classes : qa,pkg,build,doc,...&lt;br /&gt;
&lt;br /&gt;
==== bbclass documentation ====&lt;br /&gt;
&lt;br /&gt;
* should this features be implemented as a bbclass or in bitbake core library ? &lt;br /&gt;
* authors and contact in bbclass ! some of its need to be rewrite due to changes in python =&amp;gt; 2.4 , we should detects them&lt;br /&gt;
and add to a TODO-featuring tracker.&lt;br /&gt;
* force to provide documentation as a policy&lt;br /&gt;
&lt;br /&gt;
=== test quality of a recipe ===&lt;br /&gt;
&lt;br /&gt;
* (all ?) field well filled &lt;br /&gt;
* SRC_URI tarball contains no P/PV/PN =&amp;gt; dangerous&lt;br /&gt;
* no SRCREV fixed , PV = &amp;quot;x.y.z+svnr${SRCREV}&amp;quot; : &lt;br /&gt;
perharps allow in a pending branch and auto-apply in the stable one. &lt;br /&gt;
http://projects.linuxtogo.org/pipermail/openembedded-devel/2007-July/002639.html&lt;br /&gt;
* are SRC_URI fetchable ? we can fix it automagically changing SRC_URI for our MIRROR &lt;br /&gt;
* initscript without INITSCRIPT mecanism ( we need , for each new mecanism, write a recipe test and documentation )&lt;br /&gt;
* do_install with cp cmd instead of install &lt;br /&gt;
* warns on RPROVIDES&lt;br /&gt;
* recipe modification without upgrade the PR&lt;br /&gt;
&lt;br /&gt;
cf : http://handhelds.org/~zecke/bitbake-qa-0.1.tar.bz2&lt;br /&gt;
&lt;br /&gt;
== common &amp;amp; easy script encapsulation ==&lt;br /&gt;
&lt;br /&gt;
== OpenEmbedded showcase ==&lt;br /&gt;
&lt;br /&gt;
We should promote OE projects (not only fic &amp;amp; o-hand.com stuffs)&lt;br /&gt;
&lt;br /&gt;
== target web interface ==&lt;br /&gt;
&lt;br /&gt;
* port Webif to OE&lt;br /&gt;
my bug report on this : WIP&lt;br /&gt;
&lt;br /&gt;
* libopkg client support ( via http://packagekit.org/ ? )&lt;br /&gt;
* start a new one from scratch ? ( pylons based for example ).&lt;br /&gt;
&lt;br /&gt;
== delivery/release class ==&lt;br /&gt;
&lt;br /&gt;
Produce a report on a delivery.&lt;br /&gt;
Tool that give good report are often appreciated ( there is something to show ).&lt;br /&gt;
Managers/customers/developers can keep useful and pretty traces of their projects.&lt;br /&gt;
&lt;br /&gt;
* log/tag revision of each versioned tree ( that are not in distro/src-revs ) ( mtn status / svn info / -&amp;gt; rev-history , delivery-info )&lt;br /&gt;
* show software update&lt;br /&gt;
* show infos on bugs ( closed/news etc ) as a changelog&lt;br /&gt;
* show stats about image and packets ( boabab etc )&lt;br /&gt;
* show copyrights , licenses ...&lt;br /&gt;
&lt;br /&gt;
== emulator/qemu tasks ==&lt;br /&gt;
&lt;br /&gt;
some tasks that could be used for tests and debug.&lt;br /&gt;
* image is bootable ? ( ca be call in testsuite of task that build the img )&lt;br /&gt;
* test first boot&lt;br /&gt;
* upgrade not failed ?  ( print the guilty )&lt;br /&gt;
* broken linkage ? ( can be call in testsuite of sanity.bbclass )&lt;br /&gt;
&lt;br /&gt;
provides some methods&lt;br /&gt;
* build image&lt;br /&gt;
* launch with adapted parameter according to a qemu-machine conf&lt;br /&gt;
* NFS etc&lt;br /&gt;
&lt;br /&gt;
see poky anjuta plugin and poky qemu scripts.&lt;br /&gt;
&lt;br /&gt;
== coreboot integration ==&lt;br /&gt;
&lt;br /&gt;
* some recipes for utils &lt;br /&gt;
* use openembedded instead of buildrom ( yes another build system :/ )&lt;br /&gt;
&lt;br /&gt;
== Gentoo ebuild compatibility ==&lt;br /&gt;
&lt;br /&gt;
using script ( crazy ) or common variables ( completely crazy ).&lt;br /&gt;
&lt;br /&gt;
== use git facilities ==&lt;br /&gt;
&lt;br /&gt;
=== locate bug when upgrading oe ===&lt;br /&gt;
something like :&lt;br /&gt;
&lt;br /&gt;
 git bisect start&lt;br /&gt;
 git bisect bad&lt;br /&gt;
 ops = rec_ops(BB_CMD)&lt;br /&gt;
 if [ $? -eq 0 ]&lt;br /&gt;
  git bisect bad&lt;br /&gt;
  undo_ops(ops)&lt;br /&gt;
 else &lt;br /&gt;
  git bisect good&lt;br /&gt;
 fi&lt;br /&gt;
&lt;br /&gt;
* if bug is a non-version fixed package , fix version and continue&lt;br /&gt;
* make a report&lt;br /&gt;
* cf http://www.miximum.fr/methodes-et-outils/79-debusquer-une-regression-avec-git-bisect ( fr )&lt;br /&gt;
&lt;br /&gt;
== IDE integration ==&lt;br /&gt;
&lt;br /&gt;
http://community.buglabs.net/kgilmer/posts/3-OpenEmbedded-Tools-for-Eclipse&lt;br /&gt;
&lt;br /&gt;
= Centers of interest related to openembedded =&lt;br /&gt;
&lt;br /&gt;
* Industrial applications ( automation , robotic ) see http://objects.reprap.org/wiki/User:Ronan&lt;br /&gt;
* [[Quality Assurance]]&lt;br /&gt;
* [http://www.gnome.org/press/releases/gmae.html Gnome Mobile]&lt;br /&gt;
* [http://www.rushessay.com/prices.php buy essay]&lt;br /&gt;
&lt;br /&gt;
http://zecke.blogspot.com/2006/10/softwareengineering-and-qa-for-free.html http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000323.html&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://customessayorder.com/custom-essay.php essay writing services]&lt;/div&gt;</summary>
		<author><name>Sveretenov</name></author>
	</entry>
</feed>