El Miércoles, 16 de octubre de 2013 23:26:19 Ravi Kumar escribió:
> How many of the OSGeo Softwares are Copy Left and Copy Right
> Pl give a link where therationale is explained especially for OSGeo.
STFW.
http://www.osgeo.org/content/foundation/legal/licenses.html
«The Open Source Geospatial Fo
How many of the OSGeo Softwares are Copy Left and Copy Right
Pl give a link where therationale is explained especially for OSGeo.
I am aware that Free Software Foundation has things explained.
This is to a great extent true only in countries like USA where software can be
copy righted.
In many cou
Sure, but it should be the GIO's role to decide when to go with one
solution vs another. To me that is their job description.
Duties:
Assess and plan implementation of geospatial software solutions that
meet the needs of the science team.
Includes web, field, desktop and database geospatial inte
Norman,
We're thoroughly entrenched with a OpenSource installation right along side a
bunch of commercial products. It's been very hard for any commercial vendor to
even get a leg up in our office for a number of years now because we've got so
much stuff already working via OpenSource (and als
disc
On Oct 16, 2013, at 11:34 AM, "Basques, Bob (CI-StPaul)"
wrote:
> Arnie,
>
> Vendor lock-in, or rather preventing it, would be a strong second as far as
> reasons go, but it's not really applicable to describing a positions work
> items (I don't think) and seems like it might be closer t
Arnie,
Vendor lock-in, or rather preventing it, would be a strong second as far as
reasons go, but it's not really applicable to describing a positions work items
(I don't think) and seems like it might be closer to a policy issue (in my
mind).
Thanks for the feedback.
Bobb
> -Original
Hi Maria,
Thanks for the thoughts. See my sudo responses inline . . . I'm using this
thread as a practice round of discussion . . .
> >
> > "Open Source software enforces standards"
> >
> In my experience (maybe because I don't discuss this with people
> who know much about the subject
Daniel,
I'm not sure why exactly, but the "facilitates interoperability" seems fluffy
for some reason. It might be something to integrate into the original
statement however. The vendor lock-in piece is definitely something that will
need to be included somehow, but I'm thinking there or two
Maybe take it from a different angle?
- Open Source software facilitates interoperability
or
- Open Source software breaks vendor lock-in
Vendor lock-in is a tactic used to protect a vendor's licensing revenue
stream by ensuring that customers cannot easily switch to another suite
of soft
Well, adherence to standards is integral to the issue of
interoperability, a critical project success factor in this
increasingly interconnected world.
And, there's no motivation for vendor lock-in, since the revenue
protection motivation (usually!) doesn't exist. (I can tell you re
all of the ve
On Wed, Oct 16, 2013 at 4:36 PM, Basques, Bob (CI-StPaul)
wrote:
> Hi all,
>
>
>
> I wonder if I could get some feedback on the following statement, I’m
> looking for the other side of the argument (I know it’s hard to put yourself
> there :c).
>
>
>
> “Open Source software enforces standards”
>
Hi all,
I wonder if I could get some feedback on the following statement, I'm looking
for the other side of the argument (I know it's hard to put yourself there :c).
"Open Source software enforces standards"
Now this might be better worded, and it seems straight forward enough here.
I'm tryi
12 matches
Mail list logo
