Re: [License-discuss] Protecting database integrity

2017-03-06 Thread Kevin Fleming
FYI, it's completely possible to build an Android device without connecting to any Google services or usage of any non-open-source software provided by Google (the radio and other hardware drivers may also be non-open-source byt come from the hardware manufacturers). However, if you want the users

Re: [License-discuss] Protecting database integrity

2017-03-05 Thread Grahame Grieve
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 wrote: > > On Sun, Mar 5, 2

Re: [License-discuss] Protecting database integrity

2017-03-05 Thread John Cowan
On Sun, Mar 5, 2017 at 10:52 PM, Terrence Bull 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

Re: [License-discuss] Protecting database integrity

2017-03-05 Thread Terrence Bull
Thanks John, I think the answer is - as you suggest - make the case for everyone to stay ‘on the system’ in the documentation. The case is basically: if you are ‘in the universal system’ then you will have access to lots of new free and cheap apps and add-ons and the ability to promote - throu

Re: [License-discuss] Protecting database integrity

2017-03-05 Thread John Cowan
On Sun, Mar 5, 2017 at 9:20 PM, Terrence Bull wrote: I want to release the software for everyone to use - however, It is > important that someone doesn’t simply ‘disconnect’ their copy of the > database as this will screw with the integrity of the ‘universal’ nature of > the system. > I don't se

[License-discuss] Protecting database integrity

2017-03-05 Thread Terrence Bull
Hi, I am wanting to open source our project - a browser based development environment. However, it has a unique feature - much of the code is in the database and there is a universal User ID to make integration (between apps inside a business and business-to-business) quickly and easily possibl