[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Embeddded Debian meetup @ Extremadura



Hi,

emDebian development is again a bit staganting. One option to fuel
some fire is to have a worksession[0] at Extremadura[1][2]. Some ideas 
of things that could get done at or before emDebian worksession:

 * bring Ed's framework upto date with Etch.
 * create configurations for various devices and document howto do them
   * linksys routers, peplink, NAS devices, pda's/phones.. 
 * emdebian kernel integrations
 * prepare uclibc ports [4]
 * arm-eabi[5][6]/sh3/blackfin/coldfire and similar "slow/embedded" arch porting
 * gpe/opie/maemo packaging and uploading to debian
 * Kill scratchbox in it's current form and make a better scratchbox2 [7]
 * cross-compiling for buildd's
 * Discuss, Settle and stick in to one of: familiar/ipkg, emdebian or udebs
 * promote DEBUILD_OPTIONS=nodocs flag for not building docs
 * promote DEBUILD_OPTIONS=notest for skipping tests

Ofcourse, most of this can be done without the meeting, and is in fact
preferred over working at the place - But having a meeting sets a 
deadline to get something prepared and achieved, instead of endless 
planning!

I would personally favour March 22-26/April 19-23, as this would let us
have something to show at debconf for wider audience. If you have any
preferences for timing, you get to vote by promising to do some things
out of the list :)

Please rise your hand ( _o/ ) or edit wiki[0] directly if you have
interest in this happening, and I'll contact Extremadura.

Cheers,
Riku

[0] http://wiki.debian.org/DebianEmbeddedWorkSessionExtremadura2006
[1] http://lists.debian.org/debian-devel-announce/2005/12/msg00003.html
[2] http://wiki.debian.org/WorkSessionsExtremadura
[3] http://lists.debian.org/debian-embedded/2005/11/msg00014.html
[4] https://www.debconf.org/comas/general/proposals/11
[5] http://wiki.debian.org/ArmEabiPort
[6] https://www.debconf.org/comas/general/proposals/80
[7] https://www.debconf.org/comas/general/proposals/58



Reply to: