Hi,
I don't understand this page, even with the help of Google Translator [1].
The link in [2] tells me that this page is A Geodata Licensing Working Group
to look into parallel licensing developments and to consult on guidelines for
open licenses for geodata. in Working group section. Its
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Yves
I have no idea why this is the case, but for some reason or other the
Geodata_Licensing_Working_Group gets redirected to the German local
chapter page (D-A-CH)
http://wiki.osgeo.org/index.php?title=Geodata_Licensing_Working_Groupredirect=no
Le Thursday 02 April 2009 10:06:14 Judit Mays, vous avez écrit :
Hi Yves
I have no idea why this is the case, but for some reason or other the
Geodata_Licensing_Working_Group gets redirected to the German local
chapter page (D-A-CH)
I'm curious about the type if liability issues a company might open
itself up to by supporting open source software development. Let me give
you a scenario:
A graphic design company decides it will sponsor some development of the
SVG editor Inkscape. It puts out an RFP for the functionality it
Landon Blake wrote:
I’m curious about the type if liability issues a company might open
itself up to by supporting open source software development. Let me give
you a scenario:
A graphic design company decides it will sponsor some development of the
SVG editor Inkscape. It puts out an RFP
Landon,
We've wrestled with similar issues, and took the stance that we either contract
with the open-source project itself, one of it's developers or just plain old
donate funds on a handshake agreement. I have to admit the handshake stuff is
only for small quick turnaround types of things.
Frank wrote: Typically open source licenses include disclaimers of
responsibility, fitness for a purpose, etc.
I was aware that most open source licenses included this type of
language. My code would be released GPL/LGPL. I was actually hoping
there might be a white paper or article that was
Bob,
I'd be issuing and RFP for the work, and we would be working with
another company. I hadn't thought about it, but that might alleviate
some of the concern.
Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658
-Original Message-
From:
Landon,
Then it sounds like you are setting yourself up as the middle tier project
lead, doling out the monies to the developers and getting back the capabilities
you desire. I don't see the liability piece really getting in the way since
Franks' explanation would put the Liability issue
Thanks Bob. That is an interesting point that you make about being
liable for code that doesn't end up back in the larger community pool.
Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658
-Original Message-
From: discuss-boun...@lists.osgeo.org
Folks,
Mike Smith has written a nice article which highlights the work he
has been doing on web services in Maine which highlights a number
of OSGeo projects including GDAL, and MapServer.
http://www.govtech.com/gt/articles/633927
Best regards,
--
For limited distribution, to Community Leaders, Sponsors and media
outlets.
Sydney, Australia. 2 April 2009.
In 2007, 26% of delegates learned about the international FOSS4G
conference from weblinks. So again, the FOSS4G Organising Committee is
asking FOSS4G sponsors, Geospatial Open Source
I wonder if the California State Department of Boating and Waterways support of
Starspan (see http://starspan.casil.ucdavis.edu/doku/doku.php) might give you a
lead.
Bob Moskovitz
Research Analyst I
Seismic Hazard Zonation Project
California Geological Survey
13 matches
Mail list logo
