Differences between revisions 14 and 15
Revision 14 as of 2010-10-19 14:34:52
Size: 5541
Editor: DidierRaboud
Comment: Add two WIPs
Revision 15 as of 2010-10-19 14:37:18
Size: 5855
Editor: DidierRaboud
Comment: + meegotouch-home
Deletions are marked like this. Additions are marked like this.
Line 31: Line 31:
|| DebianPts:meegotouch-home || DebianBug:xxxxxx || [[http://git.debian.org/?p=pkg-meego/meegotouch-home.git|Git]] || [[http://meego.gitorious.org/meegotouch/meegotouch-home|meegotouch-home]] || [[http://meego.gitorious.org/~odyx/meegotouch/meegotouch-home-clean|meegotouch-home-clean]] || DidierRaboud || … ||

Debian MeeGo stack maintainers

Infrastructure

Interacting with the team

  • Mailing list: <pkg-meego-maintainers AT alioth DOT debian DOT org>

  • Public IRC channel: #debian-meego on irc.debian.org (OFTC)

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:

  • ?MeeGo Core Software Platform

  • ?MeeGo Notebook UX

Packages list

Package

ITP

VCS

Upstream git

Cleaned up git

Uploaders

Comments

contextkit

600034

Git

contextkit

contextkit-clean

DidierRaboud

libcontentaction

600537

Git

libcontentaction

libcontentaction-clean

DidierRaboud

libmeegotouch

597295

Git

libmeegotouch

libmeegotouch-clean

DidierRaboud

meego-packaging-tools

592314

Git

meego-packaging-tools

N/A

?FathiBoudra

mic2

578170

Git

image-creator

N/A

?FathiBoudra

meegotouch-applauncherd

xxxxxx

Git

meegotouch-applauncherd

meegotouch-applauncherd-clean

DidierRaboud

meegotouch-compositor

600202

Git

meegotouch-compositor

meegotouch-compositor-clean

DidierRaboud

meegotouch-home

xxxxxx

Git

meegotouch-home

meegotouch-home-clean

DidierRaboud

meegotouch-theme

599738

Git

meegotouch-theme

meegotouch-theme-clean

DidierRaboud

meegotouch-qt-style

600285

Git

meegotouch-qt-style

meegotouch-qt-style-clean

DidierRaboud

meegotouch-systemui

xxxxxx

Git

meegotouch-systemui

meegotouch-systemui-clean

DidierRaboud

spectacle

592311

Git

spectacle

N/A

?FathiBoudra

Packaging practices

''upstream'' branches

Despite the [Proposal] Packaging management in DVCS mail, most upstream repositories still ship packaging files (debian/, *.spec, *.yaml files and directories). In order to workaround this, DidierRaboud runs a "cleaning" script bi-daily that pushes to gitorious too. The master branch of said "cleaned" repository doesn't contain the packaging files and upstream/${version} tags are created with "git changelogs" included. This master branch is regularly (hand-)merged into the "upstream" branch of the alioth git repositories.

Additionally, as the upstream/${version} are git leaves (not in the chain of commits leading to "upstream"), most alioth repositories include a "mergeNewUpstreamRelease.sh" that should be called from the "master" branch as $ debian/mergeNewUpstreamRelease.sh upstream/${version} . This handles the merging and the pristine-tar generation.

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: