On Thu, Sep 23, 2010 at 11:06:04AM -0500, Ibrahim Haddad wrote: > Hi Jared, > > I am confirming that we were contacted by RH and you were cc-ed on the > emails. We agreed on the wording of your spin (which is inline with the > trademark policy and guidelines [1]), and approval was given conditional to > meeting the compliance requirements.
BUT THERE ARE NO FINAL COMPLIANCE REQUIREMENTS AT THIS TIME!!! That's the problem, even if you are wanting to work through this whole thing, distros are wanting to ship stuff NOW. To hold things up, waiting for some document/requirement that isn't even finished is ludicrous. > As for the remark on connman, my personal thoughts on this are the > following: MeeGo compliance is stack based meaning you need to use MeeGo > Core as-is - you need to use same base code, same package format, same > package naming/versionning, etc. You can apply patches against components in > the MeeGo Core stack and you can add new components but not to replace > existing MeeGo components. Why not? What's the problem with this? > This is my understanding and to relate this to your remarks below, if > you were to remove connman (or for that purpose any component declared > as part of MeeGo Core stack) and replace it with another component, > you would not be Core stack compliant and therefore can't use MeeGo > mark as part of your product name or branding. Why not? There is nothing that makes any userspace application depend on ConnMan that I can see. Actually, I can see lots of reasons to NOT use ConnMan (reduced functionality being the biggest one.) > Compliance is work in progress - please participate in the compliance > discussion thread to help shape the compliance efforts and please refer to > http://wiki.meego.com/Quality/Compliance for details and roadmap > information. That's great, but again, distros wanting to ship today shouldn't be held hostage to this process. Especially as MeeGo 1.0 shipped so long ago. thanks, greg k-h _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
