Re: [Firebird-devel] Time to update our headers.

2015-03-14 Thread Mark Rotteveel
On 13-3-2015 20:09, Jim Starkey wrote: MPL should never be used for Firebird code. It gives specific rights to Netscape. I have skimmed the MPL 1.0, 1.1 and 2.0 but as far as I can tell it never assigns specific rights to Netscape or Mozilla. Could you point out where it does this? I can't

Re: [Firebird-devel] Time to update our headers.

2015-03-14 Thread James Starkey
Indeed. The GPL is pathological. Sun developed a fantastic file system called ZFS and released under a Sun open source license that requires, like the Firebird licenses, that modifications be available under the same license. But Linux integration would require some mods, the mods would have to

Re: [Firebird-devel] Time to update our headers.

2015-03-14 Thread Ann Harrison
On Mar 14, 2015, at 8:00 AM, Mark Rotteveel m...@lawinegevaar.nl wrote: I have skimmed the MPL 1.0, 1.1 and 2.0 but as far as I can tell it never assigns specific rights to Netscape or Mozilla. Could you point out where it does this? In 1.0, the problems come in section 6. I haven't

Re: [Firebird-devel] Time to update our headers.

2015-03-13 Thread marius adrian popa
Mpl 1.0 , 1.1 licenses are outdated and shouldn't be used for new code http://opensource.org/licenses/do-not-use.html The old versions had issues with gpl licenses https://www.gnu.org/philosophy/license-list.html#GPLIncompatibleLicenses

Re: [Firebird-devel] Time to update our headers.

2015-03-13 Thread Jim Starkey
MPL should never be used for Firebird code. It gives specific rights to Netscape. The IPL can't be changed. A new version of the IDPL could be created, but it wouldn't apply to existing modules. And it will never be recognized by the self-appointed Open Source Gods because they refuse to

Re: [Firebird-devel] Time to update our headers.

2015-03-13 Thread Michal Kubecek
On Fri, Mar 13, 2015 at 03:09:04PM -0400, Jim Starkey wrote: I can't see any reason to muck around with licenses at all. MPL 2.0 claim to fame is that it's compatible with GPL, but at the moment approximately 100% of Firebird is already incompatible with GPL -- and very little of it can be

Re: [Firebird-devel] Time to update our headers.

2015-03-13 Thread Ann Harrison
Jim wrote: MPL should never be used for Firebird code. It gives specific rights to Netscape. And another several interesting and valuable lessons of history. It's not true that he had to talk me out of GPL. I knew that the goal of open source InterBase was to provide tools for future

Re: [Firebird-devel] Time to update our headers.

2015-03-13 Thread Leyne, Sean
By all means, change the headers to point to a more stable license repository, but don't change the license. Perhaps, rather than point to a web URL that could die at any time, (and then go through the process of changing the headers again), can't we simply: - ensure that a copy of the

Re: [Firebird-devel] Time to update our headers.

2015-03-06 Thread Claudio Valderrama C.
-Original Message- From: Paul Beach [mailto:pbe...@ibphoenix.com] Sent: Jueves, 05 de Marzo de 2015 12:07 The IPL license hosted on IBPhoenix was the license originally used, i.e. we hosted the original license that the InterBase code was released with (as Ann and I devised

Re: [Firebird-devel] Time to update our headers.

2015-03-06 Thread Helen Borrie
At 02:36 p.m. 7/03/2015, Claudio Valderrama C. wrote: -Original Message- From: Paul Beach [mailto:pbe...@ibphoenix.com] Sent: Jueves, 05 de Marzo de 2015 12:07 The IPL license hosted on IBPhoenix was the license originally used, i.e. we hosted the original license that the

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Paul Beach
The IPL license hosted on IBPhoenix was the license originally used, i.e. we hosted the original license that the InterBase code was released with (as Ann and I devised it). If I remember rightly the Inprise license was slightly modified after release. We also hosted the IDPL license

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Ann Harrison
I wrote: My recollection is that the IPL was worked out among Paul, me, Dale Fuller, and a few others. The original Mozilla licenses gave ownership rights to Netscape. We changed it to Inprise and its successors. When Firebird launched as an independent entity, we (same crowd, minus

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Ann Harrison
On Mar 5, 2015, at 8:38 AM, marius adrian popa map...@gmail.com wrote: Ok understand , What i ask is that new code to be under MPL 2.0 without any changes to the license text like they did in the libreoffice case http://cgit.freedesktop.org/libreoffice/core/tree/COPYING.MPL This will

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Helen Borrie
At 09:16 p.m. 5/03/2015, marius adrian popa wrote: While there can we upgrade the license to mpl2 ? No. The source code we used for Firebird is licensed under MPL v.1.0. *That* version of the source code, *that* version of the MPL. Helen

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Dimitry Sibiryakov
05.03.2015 17:49, Paul Beach wrote: I wasn't arguing about it - just pointing out some historical facts that were valid at some time in the past. So do I. I'm sorry if it looked like an offense. -- WBR, SD. --

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Dimitry Sibiryakov
05.03.2015 16:09, Dmitry Yemanov wrote: Huh? We are talking about sources (particularly headers), no?.. -- WBR, SD. -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Ann Harrison
On Mar 5, 2015, at 12:07 PM, Paul Beach pbe...@ibphoenix.com wrote: 05.03.2015 16:13, Dimitry Sibiryakov wrote: We are talking about sources (particularly headers), no?.. I mean that if you are going to update headers to a new license URL, it would be better if it is official

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread marius adrian popa
I'm thinking about the Firebird Initial Developer's Public License (based on MPL v1.1) For old headers still with old license we can incoporate them this way https://wiki.documentfoundation.org/Development/Re-Basing#What_does_your_license_header_look_like_.3F On Thu, Mar 5, 2015 at 10:33 AM,

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Adriano dos Santos Fernandes
On 05/03/2015 11:57, Leyne, Sean wrote: 05.03.2015 15:19, Leyne, Sean wrote: The fact that Inprise/Borland/embarcadero have not maintained the URL location is not our problem. What's the problem with broken IBPhoenix URL then?.. There is none with changing that -- the IDPL is a 'product'

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Dimitry Sibiryakov
05.03.2015 16:13, Dimitry Sibiryakov wrote: We are talking about sources (particularly headers), no?.. I mean that if you are going to update headers to a new license URL, it would be better if it is official project's site URL, not IBPhoenix one. -- WBR, SD.

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Paul Beach
05.03.2015 16:13, Dimitry Sibiryakov wrote: We are talking about sources (particularly headers), no?.. I mean that if you are going to update headers to a new license URL, it would be better if it is official project's site URL, not IBPhoenix one. The IPL license hosted on IBPhoenix was

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Dimitry Sibiryakov
05.03.2015 17:07, Paul Beach wrote: The IPL license hosted on IBPhoenix was the license originally used, i.e. we hosted the original license that the InterBase code was released with (as Ann and I devised it). If I remember rightly the Inprise license was slightly modified after release.

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread marius adrian popa
Ok understand , What i ask is that new code to be under MPL 2.0 without any changes to the license text like they did in the libreoffice case http://cgit.freedesktop.org/libreoffice/core/tree/COPYING.MPL This will simplify the license understanding (no more idpl/ipl license text forks of mpl

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Dmitry Yemanov
05.03.2015 15:38, marius adrian popa wrote: Ok understand, what i ask is that new code to be under MPL 2.0 What is our benefit? This will simplify the license understanding Nope, it will only complicate understanding. Old modules have to remain IPLed/IDPLed, so actually we'll be claiming

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Jim Starkey
I don't think you can change the license for modules from individuals without their permission. Vulcan modules explicitly forbid a change of license. Jim Starkey On Mar 5, 2015, at 4:16 AM, marius adrian popa map...@gmail.com wrote: While there can we upgrade the license to mpl2 ?

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread supp...@ibknowledgebase.com
Hi, http://www.firebirdsql.org/en/licensing/ Regards, Alexey People, http://www.ibphoenix.com/main.nfs?a=ibphoenixpage=ibp_idpl. is pointing to nothing. We need to update the files in the repository to point to the right location of the license or please suggest an alternative. I think

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Leyne, Sean
Plese do and fix the urls While there please replace the inprise.com with firebirdsql.org license location Absolutely not!!! The original license must remain untouched, we did not create the original files, we cannot change the license statement. The fact that Inprise/Borland/embarcadero

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Leyne, Sean
05.03.2015 15:19, Leyne, Sean wrote: The fact that Inprise/Borland/embarcadero have not maintained the URL location is not our problem. What's the problem with broken IBPhoenix URL then?.. There is none with changing that -- the IDPL is a 'product' of the project, as such it can be

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Dimitry Sibiryakov
05.03.2015 15:57, Leyne, Sean wrote: There is none with changing that -- the IDPL is a 'product' of the project, as such it can be changed. I just wonder why this product is on third-party site instead of firebirdsql.org. -- WBR, SD.

Re: [Firebird-devel] Time to update our headers.

2015-03-05 Thread Dmitry Yemanov
05.03.2015 18:03, Dimitry Sibiryakov wrote: I just wonder why this product is on third-party site instead of firebirdsql.org. Huh? http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0 Dmitry

[Firebird-devel] Time to update our headers.

2015-03-04 Thread Claudio Valderrama C.
People, http://www.ibphoenix.com/main.nfs?a=ibphoenixpage=ibp_idpl. is pointing to nothing. We need to update the files in the repository to point to the right location of the license or please suggest an alternative. I think that only FB v3 matters. C. --- Claudio Valderrama C. Consultant, SW

[Firebird-devel] Time to update our headers.

2015-03-04 Thread Paul Beach
http://www.ibphoenix.com/main.nfs?a=ibphoenixpage=ibp_idpl. is pointing to nothing. We need to update the files in the repository to point to the right location of the license or please suggest an alternative. I think that only FB v3 matters. ipl - http://www.ibphoenix.com/about/firebird/ipl

Re: [Firebird-devel] Time to update our headers.

2015-03-04 Thread marius adrian popa
Plese do and fix the urls While there please replace the inprise.com with firebirdsql.org license location https://github.com/FirebirdSQL/core/search?utf8=%E2%9C%93q=inprise.com On Thu, Mar 5, 2015 at 5:33 AM, Claudio Valderrama C. cva...@usa.net wrote: People,