LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  March 2005

CODE4LIB March 2005

Subject:

Re: What is open source?

From:

Jeremy Dunck <[log in to unmask]>

Reply-To:

Jeremy Dunck <[log in to unmask]>

Date:

Thu, 17 Mar 2005 11:08:12 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (115 lines)

On Thu, 17 Mar 2005 10:48:42 -0500, Andrew Darby <[log in to unmask]> wrote:
> How would one distinguish between an "open source" project like Linux or
> Apache or Mozilla, and a LAMP/WAMP program developed by a library and
> then made freely available to modify, distribute, etc.

Short answer: The license.  If there is no explicit license, full
copyright must be assumed under the law.

Long answer:
Free Software is Free-as-in-speech, and may be free-as-in-beer.  A
useful way of thinking about this (due to the differing English
meanings) is the French "libre" = "Free" and "gratis" = "free".

Free Software is a notion introduced by Richard Stallman.  His work
has been important in shaping the software landscape.  However, he is
staunchly moral and draws distinctions and makes mandates which
limited the popular acceptance of Free Software.  Open Source (led by
the Open Source Initiative and mascot'd by Eric Raymond) spun off as a
friendlier, gentler form of less-than-Iron-Curtain software.

It has indeed popularized a middle ground.  Unfortunately, it has also
muddied the water.  Some people consider "open source" to just mean
that source is available (as in Pirate Source).  The Open Source
Initiative has a more expansive definition:
http://www.opensource.org/docs/definition.php and they're pretty
authoritative.  They approve specific licenses as OSI certified
(http://opensource.org/docs/certification_mark.php) which is a quick
way to evaluate whether a particular license meets the requirements of
the OSI (http://opensource.org/docs/definition.html).

Open Source projects are only sometimes Libre, and rarely are gratis.
Free Software projects are always Libre, and usually gratis.

You do not necessarily have the right to modify or distribute source
of an "open source" project because of the muddied water above.  The
license is what really matters.  You do have those rights (and others)
in Free Software.  Lowercase "open source" means code is available,
uppercase "Open Source" means the code is licensed under an
OSI-certified license.

You may already be familiar with this, but it sets the context of your
question.  What really determines whether an Open Source project is
Free depends on the license the source is released under.

All source falls under copyright law; it is up to the copyright
holders to license it for use to others.  Free Software grants an
exceptional number of allowances to the licensee, and usually binds
the licensee in to a similar contract for modified works (CC's
optional share-alike, GNU's copyleft).

Software which is licensed under a (L)GPL-compatible license is
generally called Free.  Additionally, there are tons of licenses also
considered Free such as Apache, MIT, and BSD.  The general distinction
between OSI certified licenses and Free licenses are due to moral
distinctions.

> I'm specifically thinking of East Carolina University's "Pirate Source"
> (http://systems.lib.ecu.edu/piratesource/) which we have reworked and
> rebranded (rather lamely) as Resources by Subject
> (http://www.ithacalibrary.com/subjects/), but perhaps MyLibrary would
> fall in this category, too.

Pirate Source appears to be (lowercase) open source since you can
download the source.  We can't determine what rights we have because
there is no license included.  Well on the page, it says we can
modify, but says nothing about redistribution.  You are taking a legal
risk to redistribute that code without explicit licensing as it is
(necessarily) a copyrighted work and you have not been clearly granted
any rights to it.  In general, it's good practice to include the
license -in- the code.

> Is it wrong or inaccurate to refer to the latter sort of program as open
> source?  The source code is open, but it seems a quite different animal
> from the ever-evolving and distributed development of Mozilla, Linux, etc.

Determine what the license is for Pirate Source first.  Your decision
may be made for you at that point, because these licenses often
require you to use the same license if you redistribute.

If you still have a choice under Pirate Source's license, here's a
short howto on selecting a (Free) license:
http://www.dina.kvl.dk/~abraham/rants/license.html

There are more:
http://www.google.com/search?hl=en&q=howto+choose+%22open+source%22+license&btnG=Google+Search

You should realize that you only accrue the benefits generally
associated with Open Source if you encourage community involvement,
including tools for communication, discussion of ideas, common
principles, and accepting code contributions back into the original
source.

This takes a lot of infrastructure; SourceForge.net can help.

Having these tools won't magically create a community, but -not-
having these tools can keep one from forming.

> Is there a different/better label for these library-developed
> applications, or am I splitting hairs?

Unfortunately, no.  Without a license, software is not (uppercase)
Open Source (even if source is provided).  There are many Free and
Open Source projects around which no (or a small) community forms.
Not everyone can expect an Apache success.  The size of community does
not define whether something is Open Source.  However, you can be sure
that (other things being equal) a closed system will have less
community than an open one.

I think that to the extent possible, library-developed applications
should be Open Source, because this allows collaboration at low cost
(and in the absence of economic incentives).  Where a library stands
to benefit, perhaps Open Source (or commercial) is the better choice,
but consider your goals.

Sorry for verbosity; I hope it helps.

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager