> 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 [email protected] http://lists.meego.com/listinfo/meego-packaging
