Debian MeeGo stack maintainers

Infrastructure

Interacting with the team

Measuring the ''work-to-be-done''

As nothing from ?MeeGo is in Debian yet, there is a certain need of clear milestones, so here's a proposal:

Packages list

Package

ITP

VCS

Upstream git

Uploaders

Comments

contextkit

600034

Git

contextkit

DidierRaboud

libcontentaction

600537

Git

libcontentaction

DidierRaboud

libmeegotouch

597295

Git

libmeegotouch

DidierRaboud

meego-packaging-tools

592314

Git

meego-packaging-tools

?FathiBoudra

mic2

578170

Git

image-creator

?FathiBoudra

meegotouch-applauncherd

601012

Git

meegotouch-applauncherd

meegotouch-applauncherd-clean

DidierRaboud

meegotouch-compositor

600202

Git

meegotouch-compositor

meegotouch-compositor-clean

DidierRaboud

meegotouch-home

601015

Git

meegotouch-home

DidierRaboud

meegotouch-theme

599738

Git

meegotouch-theme

DidierRaboud

meegotouch-qt-style

600285

Git

meegotouch-qt-style

meegotouch-qt-style-clean

DidierRaboud

meegotouch-systemui

601014

Git

meegotouch-systemui

meegotouch-systemui-clean

DidierRaboud

spectacle

592311

Git

spectacle

?FathiBoudra

Packages relations

(Blue is "handled by pkg-meego", red is "in experimental") [ATTACH]

Packaging practices

''upstream'' branches

The upstream branches are the master branches of upstream repositories. When a new version is released, the tag is merged into the master branch without its debian/ sub-directory (git merge --no-commit; git checkout master -- debian/; git commit).

Usertags

Here is a proposal for the use of usertags (or user categories):

User: pkg-meego-maintainers@lists.alioth.debian.org

Usertags actually in use: