you can do the same - you can release the code under open source license, but use the trademark to ensure certain policies are followed.
The community will probably ignore your code if they don't like the policies. Grahame On Mon, Mar 6, 2017 at 4:18 PM, John Cowan <co...@ccil.org> wrote: > > On Sun, Mar 5, 2017 at 10:52 PM, Terrence Bull <terre...@woogloo.com> > wrote: > > I do wonder how Google makes Android open source yet requires everyone >> that makes ‘copies’ to be connected to the Play store. Do they have some >> sort of special open source license they use? >> > > No, the license is straight Apache 2.0, except for the proprietary parts > that control the radio and the sensors. Google's leverage over Android > manufacturers comes from the Android trademark, which they license only to > OEMs who follow their rules, and from the fact that they give advance > copies of new releases to those same OEMs. > > -- > John Cowan http://vrici.lojban.org/~cowan co...@ccil.org > Don't be so humble. You're not that great. > --Golda Meir > > > > _______________________________________________ > License-discuss mailing list > License-discuss@opensource.org > https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss > > -- ----- http://www.healthintersections.com.au / grah...@healthintersections.com.au / +61 411 867 065
_______________________________________________ License-discuss mailing list License-discuss@opensource.org https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss
