On Sun, Jun 13, 2010 at 9:16 PM, Arjan van de Ven <[email protected]>wrote:
> On 6/13/2010 11:15 PM, Gary Birkett wrote: > > >> >> On Sun, Jun 13, 2010 at 8:50 PM, Arjan van de Ven >> <[email protected]<mailto: >> [email protected]>> wrote: >> >> On 6/12/2010 12:26 PM, Dome Charoenyost wrote: >> >> Dear All, >> I'm modify MeeGo for support nvidia , ati and include >> XBMC . >> I'm worry about copyright. so i want to know what's good way for >> distribute meeGo modify version. I don't want to folk. >> 1. Can i still use all graphic and logo in side Meego ? >> 2. Can i use MeeGo for name of my version? >> >> >> as long as your version is compliant the answer to both is yes, >> otherwise the answer to both is no. >> compliance is mostly about compatibility; if you use all our >> packages, and do not change the ABI >> in any patches you add you're fine. If you change versions of >> things it's a problem, or if you do things >> that change ABIs. >> >> >> the official build will be changing versions of components >> you best hope that can handle it easily itself too.. >> > > within a release? we'll not be changing versions of components > (I don't count maintenance-bugfix-only releases from upstream projects > quite as changing version in that sentence) > a new build is a new build. if you aren't counting minor revision changes in that, then what does it matter if other projects do the same?
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
