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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  January 2015

CODE4LIB January 2015

Subject:

Re: know of guidelines for contributing to open source projects?

From:

John Kunze <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Sun, 11 Jan 2015 08:58:40 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (141 lines)

Thanks very much, Tom. This is really helpful stuff.

On Sat, Jan 10, 2015 at 1:34 PM, Tom Cramer <[log in to unmask]> wrote:

> John,
>
> Here are the relevant source docs at Stanford:
>
> Research Policy Handbook, Section 9.2: Copyright Policy, which states that
> the copyright of artistic, scholarly and pedagogical works remain with the
> creator, unless the work is a work-for-hire, or an institutional work. (We
> interpret that our work is generally if not always work-for-hire.)
>
> Office of Technology Licensing, Software, which states that
> Stanford-copyrighted software can be licensed to the academic or commercial
> community under an open source license. (It can also be put in the public
> domain.)
>
> Office of Technology Licensing, Open Source Primer, which states that
> Stanford staff may open source software with the appropriate departmental
> approval.
>
> Based on the university policies, our departmental policy states:
> > As a matter of practice, we publish software into publicly accessible
> code repositories. This facilitates the review, exchange, reuse and
> possible code contributions from other sites--a key part of our development
> strategy and methodology. As best practice, we endeavor to put a clear
> license on this code so others know what they may and may not do with it.
> >
> > Staff should release it under an open source license.
> >
> > If it is a contribution to a current codebase that has an approved OSS
> license, we should contribute the code back under the this same license.
> > If it is new Stanford code, then it should use an Apache 2 license as
> the default.
> > Why Apache 2? It is desirable to have a single license to consistently
> to apply across all our products:
> > so developers and managers need not try and follow a (potentially
> complex) decision tree on which license to apply
> > so potential collaborators can encounter a single, well-known OSS
> license on our code, which facilitates adoption and contribution
> > most if not all current projects (e.g., Hydra, Blacklight, Fedora, solr,
> grant-funded development is licensed under an Apache 2 license, either due
> to an IP agreement (with the funder), or Contributor License Agreements
> (CLA's) and project convention with other project stakeholders
> > as software created in one project / effort often makes it way into
> reuse in another project (by design); a single license allows for this
> portability (i.e., local Stanford code could easily become Hydra code
> without a relicense or rewrite)
> > How to License the Code: Follow the instructions here:
> http://www.apache.org/licenses/LICENSE-2.0.html The name of the Copyright
> Owner is "The Board of Trustees of the Leland Stanford Junior University"
> >
> > Copyright yyyy The Board of Trustees of the Leland Stanford Junior
> University
> >
> > Licensed under the Apache License, Version 2.0 (the "License");
> > you may not use this file except in compliance with the License.
> > You may obtain a copy of the License at
> >
> > http://www.apache.org/licenses/LICENSE-2.0
> >
> > Unless required by applicable law or agreed to in writing, software
> > distributed under the License is distributed on an "AS IS" BASIS,
> > WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> > See the License for the specific language governing permissions and
> > limitations under the License.
> >
>
>
>
> Finally, the Hydra Project has put considerable effort into defining a
> clear, repeatable licensing procedure for the community's efforts, which is
> particulalry useful for community-sourced efforts. (A lot of our work is
> contributing to shared projects, not stand-alone projects.) The Hydra
> community software licensing mechanics are outlined here:
> https://wiki.duraspace.org/display/hydra/Code+Copyright+Statement. (FYI,
> there is much current discussion within UC about how to legally and
> effectively contribute to Hydra, so this may be particularly germane.)
>
> Hope this helps,
>
> - Tom
>
>
>
>
>
> On Jan 9, 2015, at 12:11 PM, John Kunze wrote:
>
> > Hi Tom,
> >
> > This sounds terrific. Yes, it would be very useful if you could share
> the
> > source docs. I assume that the Research Policy Handbook is at
> > https://doresearch.stanford.edu/policies/research-policy-handbook ?
> >
> > -John
> >
> > On Thu, Jan 8, 2015 at 5:10 PM, Tom Cramer <[log in to unmask]> wrote:
> >
> >> John,
> >>
> >> At Stanford, this is governed by the Research Policy Handbook; there is
> >> some tech transfer and copyright detail, but essentially it says staff
> may
> >> release University-funded code with with an open source license with
> >> officer (Dean-level) approval.
> >>
> >> At Stanford, we have put this into place with blanket approval for
> >> releasing any code we deem shareable under a license (Apache 2 being
> >> default, but not required). We have similar approval under the same
> terms
> >> to release non-code artifacts under a CC license.
> >>
> >> Based on this, we have templates for inserting license files into repos
> on
> >> Github, and default text to use for copyright statements.
> >>
> >> I can dig up source docs if that's useful.
> >>
> >> - Tom
> >>
> >>
> >>
> >>
> >> On Jan 8, 2015, at 4:22 PM, John A. Kunze wrote:
> >>
> >>> Does anyone have existing institutional policy guidelines for staff who
> >>> contribute to open source software projects?
> >>>
> >>> A group at the California Digital Library is looking to learn from
> prior
> >>> art in dealing appropriately with non-technical things like licensing,
> >>> intellectual property, legal policy, cost/benefit issues, etc.
> >>>
> >>> It would be great if any of you have something like that to share.
> >>>
> >>> -John
> >>
>

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

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