On Tue, Aug 2, 2011 at 08:44, David Greaves <[email protected]> wrote: > cc'ed meego-dev as this may be of interest. Followup to meego-community > please. [sending to meego-dev as this is a development process question, possibly for the Architects; follow-ups there please, although this topic is *horribly* splintered :-/]
> Last week I suggested that the following statement summed up my > understanding and although I asked for an alternative, one did not appear: > > "The Linux Foundation have told us in private conversations that they will > not permit apps.meego.com to be served from the MeeGo.com infrastructure > hosted by them. They do not have the resource at this time to provide a > statement giving their reasons. We can not assess what other services may be > impacted in the future." Concern of patents in the US seem to be one of the primary concerns (as far as can be gathered, IIRC). What mechanisms does the Project have to ensure that the MeeGo Core doesn't have patent-infringing code in place? Is the risk something somehow delegated to the copyright holders (e.g. Intel)? If so, how is this compatible with individual patches submitted by contributors (I'm not aware of a contributor agreement)? Is this something the Project needs to be more widely concerned about & address? Or, are there processes which might be adaptable to COBS/apps.meego.com? Cheers, Andrew -- Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/ _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
