Looks like a great start...

I agree with a lot of the other comments here - especially about
splitting it up into two sections for apps and implementations.

Lines 60-62 seem to disallow the possibility of producing apps using
byte-code compiled languages like java or C# - is that intentional?

Warren

On Fri, Sep 3, 2010 at 6:59 PM, Wichmann, Mats D
<[email protected]> wrote:
>
> There's a rough early version available on
> http://wiki.meego.com/Quality/Compliance
>
> We'd like to ask for feeback on this at various levels,
> the most important being the highest level: does it
> get anywhere close to describing an implementation of
> the basic principles, as presented most recently
> at the TSC meeting:
>
> http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-18-18.58.html
> (follow to "full logs" to see the discussion)
>
> and mainly the reference:
>
> http://wiki.meego.com/Technical_Steering_Group_meetings/Compliance_Update_8-18-10
>
> Probably it's not worth worrying about small items
> (spelling, grammar) at the moment as there are likely
> to be large changes which could make those disappear
> as a side effect.
>
> For the moment this is too rudimentary for it to make
> a lot of sense to tie it in to bugzilla entries, but
> we'll add a category there later as the document matures.
>
> So I'm proposing we just follow up to this thread -
> edits, questions, comments, etc.
>
>
> Thanks,
>
> -- mats
> _______________________________________________
> MeeGo-dev mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-dev
>



-- 
Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to