Re: [Firebird-devel] Commits visible in our main page.

DS>May be something like SF statistics "XX commits last week" could be enough?.. Looks good too. I think the web designer may decide what fits better the currently layout. []s Carlos http://www.firebirdnews.org FireBase - http://www.FireBase.com.br -

Re: [Firebird-devel] Commits visible in our main page.

05.03.2015 21:21, Carlos H. Cantu wrote: > I think the content must be short, > for example, showing only the last 5 commits (with its dates, and > titles trimmed when need). May be something like SF statistics "XX commits last week" could be enough?.. -- WBR, SD. --

Re: [Firebird-devel] Commits visible in our main page.

I agree that it would help to make people aware that something is happening behind the scenes, but I think the content must be short, for example, showing only the last 5 commits (with its dates, and titles trimmed when need). Clicking in a link could send the visitor the the full sourceforge list

Re: [Firebird-devel] Commits visible in our main page.

05.03.2015 23:53, Claudio Valderrama C. wrote: > People, maybe you're going to say that this would be ugly, but at > www.firebirdsql.org > after the PROJECT NEWS I would like to see information about latest commits, > maybe this whole page inside a frame: > http://sourceforge.net/p/firebird/code/c

Re: [Firebird-devel] Odp: READ UNCOMMITTED implementation

> On Mar 5, 2015, at 2:30 PM, Roman Simakov wrote: > > >> 5 марта 2015 г., в 20:26, Jim Starkey написал(а): >> >> "read imaginary» > > Is it not the same as "read uncommited"? :) Oh, certainly not! Read imaginary invents whole new record(s) conforming to the search criteria with random n

[Firebird-devel] Commits visible in our main page.

People, maybe you're going to say that this would be ugly, but at www.firebirdsql.org after the PROJECT NEWS I would like to see information about latest commits, maybe this whole page inside a frame: http://sourceforge.net/p/firebird/code/commit_browser While some readers may feel it's too nerdy

Re: [Firebird-devel] Odp: READ UNCOMMITTED implementation

> 5 марта 2015 г., в 20:26, Jim Starkey написал(а): > > "read imaginary» Is it not the same as "read uncommited"? :) -- Roman Simakov -- Dive into the World of Parallel Programming The Go Parallel Website, sponso

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

> On Mar 5, 2015, at 8:38 AM, marius adrian popa 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 simplify t

Re: [Firebird-devel] Odp: READ UNCOMMITTED implementation

> On Mar 5, 2015, at 1:04 PM, Ann Harrison wrote: > > > >> On Mar 5, 2015, at 11:26 AM, "liviusliv...@poczta.onet.pl" >> wrote: >> >> Hi, >> >> It is usefull for testing purposes. Consider monitoring what actually is in >> some table from other connection or software before some long tas

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

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, minu

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

> On Mar 5, 2015, at 12:07 PM, Paul Beach 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 project's si

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

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] Odp: READ UNCOMMITTED implementation

> On Mar 5, 2015, at 11:26 AM, "liviusliv...@poczta.onet.pl" > wrote: > > Hi, > > It is usefull for testing purposes. Consider monitoring what actually is in > some table from other connection or software before some long task has > finished. Nothing is in a table until it is committed, s

Re: [Firebird-devel] Firebird 3 API demo usage with Pascal

Adriano dos Santos Fernandes писал(а) в своём письме Thu, 05 Mar 2015 17:53:08 +0300: Thank You. Very interesting. Another would like to see will look like on UDR FreePascal. > Hi! > > I just build an example of Firebird 3 API usage with FreePascal. > > https://github.com/asfernandes/fbstuff

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

> 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.

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.

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

Re: [Firebird-devel] Firebird 3 API demo usage with Pascal

On 05/03/2015 12:37, Alex Peshkoff wrote: > On 03/05/15 18:23, Adriano dos Santos Fernandes wrote: >> On 05/03/2015 11:53, Adriano dos Santos Fernandes wrote: >>> The others things seems ok and easy to use. >>> >>> We need some new functions in the new API, for example, to convert >>> status vector

Re: [Firebird-devel] Firebird 3 API demo usage with Pascal

On 03/05/15 18:23, Adriano dos Santos Fernandes wrote: > On 05/03/2015 11:53, Adriano dos Santos Fernandes wrote: >> The others things seems ok and easy to use. >> >> We need some new functions in the new API, for example, to convert >> status vectors to strings, but this is not specific to pascal.

[Firebird-devel] Odp: READ UNCOMMITTED implementation

Hi, It is usefull for testing purposes. Consider monitoring what actually is in some table from other connection or software before some long task has finished. Regards, Karol Bieniaszewski - Reply message - Od: "Mark Rotteveel" Do: "For discussion among Firebird Developers" Temat:

Re: [Firebird-devel] Firebird 3 API demo usage with Pascal

On 05/03/2015 11:53, Adriano dos Santos Fernandes wrote: > > The others things seems ok and easy to use. > > We need some new functions in the new API, for example, to convert > status vectors to strings, but this is not specific to pascal. > > Also, we have a "half new API". To much constants com

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

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

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

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.

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.

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 -

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

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.

> 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

[Firebird-devel] Firebird 3 API demo usage with Pascal

Hi! I just build an example of Firebird 3 API usage with FreePascal. https://github.com/asfernandes/fbstuff/blob/db56fa93850a70c473362296df12a95c7494a7dc/src/pascal/FbApiTest.dpr As said early, working with input/output buffers directly in non-C/C++ is difficult. This requires auxiliary classes

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

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?.. -- WBR, SD. -- Dive

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

> 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/embarcader

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

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 t

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

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 1/1.1

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

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 wrote: > > While there can we upgrade the license to mpl2 ? > > http://oss-watch

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

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, Hele

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

Hi, http://www.firebirdsql.org/en/licensing/ Regards, Alexey > People, > http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=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 thi

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

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.

While there can we upgrade the license to mpl2 ? http://oss-watch.ac.uk/resources/mpl2 https://www.mozilla.org/MPL/2.0/ to be in sync with libreoffice On Thu, Mar 5, 2015 at 9:57 AM, Paul Beach wrote: > > < is pointing to nothing.