Hi all, It's time for a new roadmap :)
First and foremost: my wishful thinking is to have 1.2.0 final before Christmas 2009. Really. A very important objective is to *shorten* development cycles. Release early, release often. So, the very first thing to do is to setup the new hg repo. My only concern about that is the following? Should we convert the old CVS repo or it's enough to restart with an HEAD snapshot? I've mixed feelings. Keeping the whole story it is useful, but this will likely eat *A LOT* of bandwith. I wonder if this can be a problem for Joern. (BTW: hg looks amazing). Once solved the repo thing, here it is the roadmap to 1.2.0. As stated multiple times, we're already halfway done (!!!). (full story here: http://tcforge.berlios.de/articles/tasks/index.html) * import_alsa power up: the current module is pretty dumb. Too much dumb, really. * import_v4l2 tuning support. Self explanatory. * Deep review of tcframe*: in a nutshell: refactoring. Made possible by new framebuffer (cfr past thread) in transcode-legacy _AND_ into transcode-future. Anyway, this not on my short term TODO. * Split libtc in smaller libraries: because the mess into libtc reached the guard level. At very least two new libraries will spawn: libtcutil and libtcmodule. Libtcutil will be our very basic library, depending _only_ on POSIX. Almost everything else will depend on that. * NMS-compliant export layer. This also mean dropping (aka: hg rm...) the OMS layer. Only preset cfg file will survive into export/. This also mean *A LOT* of testing too and very likely minor changes (proper extradata, PTS handling). Bonus point: export profiles became working. * Import the Synchronizer patch into HEAD: basic coding is done. We need extensive testing and maybe better algorythms. Add OggSkeleton support. Self explanatory. Plus, a new topic: * switch to graphicksmagic (http://www.graphicsmagick.org/) The reasons are: [...] * GM does not use generic names for its utilities so it does not conflict with other installed software (including system tools.) * GM provides API and ABI stability and managed releases that you can count on. [...] Those two are more than enough for me. I'm sick and tired of the ImageMagick API. full list -I agree enterely with the whole- on the graphicsmagick homepage. Ok, that's the plan. Comments? :) -- Francesco Romani // Ikitt http://fromani.exit1.org ::: transcode homepage http://tcforge.berlios.de ::: transcode experimental forge
