[Meego-architecture] Maliit and MeeGo Core Compliance
carsten at maemo.org
Fri Jul 15 05:46:16 PDT 2011
2011/7/15 Michael Hasselmann <michaelh at openismus.com>
> On Fri, 2011-07-15 at 14:34 +0200, Carsten Munk wrote:
> > IMHO, I think the way to do it would be to submit a merge request to
> > https://meego.gitorious.org/meego-os-base/package-groups - there is a
> > Compliance group. And at same time, submit a bug to compliance and
> > specs, CC'ing architects and such.
> Where is that documented?
I don't honestly think it's documented anywhere. But as with any open source
project, when the issue comes up, it's a good time as any to get the
process documented / one made. I don't think there has been any formal
process before than what was mandated by API needs, but I might be wrong.
Package groups are usually how things get handled when it comes to how
images are made and where compliance packages are listed in.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MeeGo-architecture