[meego-packaging] Packaging two versions of mcompositor

[fathi.boudra at nokia.com]

As additional notes from Abdiel:
 Window transitions are customizable using plugins.
 The plugin interface makes it easier to customize UX.
 We can have a "base" code and customized UX can be written using internal plugins.

Fathi
________________________________________
From: meego-packaging-bounces at meego.com [meego-packaging-bounces at meego.com] on behalf of Boudra Fathi (Nokia-SD/Helsinki)
Sent: Thursday, April 14, 2011 9:39 AM
To: rusty.lynch at intel.com; meego-packaging at meego.com; rolla.n.selbak at intel.com
Subject: Re: [meego-packaging] Packaging two versions of mcompositor

> how about we just make this simple and create a new meego-ux'ish
> compositor package, and back out all the meego-ux inspired patches to
> meegotouch-compositor?

Could you clarify?

Do you propose a fork of meegotouch-compositor? It will need a maintainer, not a package maintainer.

Or do you propose to have 2 OBS projects with a common packaging like we have for cmake/cmake-gui (and some other packages)?
In that case, a package co-maintainer is required to push the divergence and follow upstream changes (re-apply patches on top of a new release).

Fathi
_______________________________________________
MeeGo-packaging mailing list
MeeGo-packaging at meego.com
http://lists.meego.com/listinfo/meego-packaging