[Meego-architecture] Maliit and MeeGo Core Compliance
Wichmann, Mats D
mats.d.wichmann at intel.com
Fri Jul 15 12:57:28 UTC 2011
2011/7/15 Carsten Munk <carsten at maemo.org>
> 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.
it's the physical mechanism yes, but I don't think this is the right way to
get it done. there's nothing wrong with filing bugs in these locations but
to be honest, those will come to me and then I'll struggle with "how does a
decision get made", i.e. the same place we are now.
the conceptual flow really is, "if it's in the architecture diagram, it's in
compliance". so what you guys need to figure out is how to lobby for
getting it into the architecture (and it's already on the best mailing list
for that), then it can flow from there.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MeeGo-architecture