Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi,

I'm trying to revive the postgresql-sdbc (native) driver (from
http://dba.openoffice.org/drivers/postgresql/index.html ), and making
good progress on the technical side.

Eventually, I'd like it to be included in LibreOffice and the
OpenOffice at Apache, just like the MySQL SDBC (native) driver.

Because that code is, AFAIK, not in tag OOO340 at openoffice.org, nor
in any pending CWS, I've been led to believe it is not currently in
the planned code grant. Would it be possible to have it added to that
grant? Thank you very much in advance.

The web page says it can be downloaded from "special tags" (I presume
branch) of CVS. There is also a version at
http://cgit.freedesktop.org/libreoffice/build/tree/patches/postgresql,
and that's what I started from.

All files that have any kind of copyright notice say "Sun copyright,
LGPLv2.1 / Sun Industry SSLv1.1" with no other copyright notice, so
I'm assuming all contributors either assigned their copyright to Sun
or so small contribution that no copyright holds
(e.g. gcc-4.3-postgresql.diff and sdbc-postgresql-build-lst.diff are
so small / trivial that I would not bother about copyright problems on
these ones).

NOTE THAT some files have no copyright header AT ALL. I just consider
them under the same copyright / license than the rest, but possibly
I'm on more shaky ground there.

-- 
Lionel

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.