[Pkg-meego-maintainers] Hello MeeGo

[Didier 'OdyX' Raboud]

Hi dear pkg-meego maintainers, 

Now that MeeGo released some prelimary versions and despite the downturn of the 
"Proposal for a Debian Packaging working group" [0], it sounds certainly 
interesting to package what the MeeGo project develops.

Now there are two paths that can be followed:

1) Create a MeeGo fork/clone that "Ensure that it's possible to build Meego 
systems based on DEB packages and optionally managed by APT" (from the MeeGo 
wiki page [0])
2) Package the software MeeGo creates on Debian.

IMHO 1) might not be very difficult, but of debatable interest, as this would 
not be shipped by default on official MeeGo images.

But 2) sounds interesting, at it will allow Debian users to develop for MeeGo, 
with a pure Debian stack and/or allow to run MeeGo-based software on Debian 
(think OpenMoko e.g.).
The code is available on http://meego.gitorious.org and as you can see: there's 
a huge codebase there. (Some of it are forks/patches over other upstream 
projects, so not everything is of interest for Debian.)

I plan to start packaging the meegotouch framework, beginning by libmeegotouch 
then heading onto other bricks. I intend to put those packages under the pkg-
meego umbrella, in git with a workflow similar as pkg-qt-kde guidelines [1].

Do you think ITPs about that would be well perceived in these Frozen days or 
should I/we wait until testing=Wheezy opens ?

Cheers, and looking forward for collaboration, 

OdyX


[0] http://wiki.meego.com/Proposal_for_a_Debian_Packaging_working_group
[1] http://wiki.debian.org/PkgKde/GitPackaging
-- 
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
didier at raboud.com