Thanks very much, Tom. This is really helpful stuff.
On Sat, Jan 10, 2015 at 1:34 PM, Tom Cramer tcra...@stanford.edu 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
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
Thanks, Stuart. This is great site to know about.
-John
On Thu, Jan 8, 2015 at 4:56 PM, Stuart A. Yeates syea...@gmail.com wrote:
OSS Watch is a JISC-funded, Oxford, UK-based service that is funded to
answer questions like this: http://oss-watch.ac.uk/
cheers
stuart
--
...let us be
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 tcra...@stanford.edu wrote:
OSS Watch is a JISC-funded, Oxford, UK-based service that is funded to
answer questions like this: http://oss-watch.ac.uk/
cheers
stuart
--
...let us be heard from red core to black sky
On Fri, Jan 9, 2015 at 1:22 PM, John A. Kunze j...@ucop.edu wrote:
Does anyone have existing institutional
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
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
