On Fri, May 27, 2016 at 7:30 PM, rjf <fate...@gmail.com> wrote: > The point is, if you don't claim authorship, someone else might, and (for > example) > restrict access, even by you. > > So you should claim authorship and copyright, and then declare that others > may > use it under whatever restrictions you determine. Personally, I find the > MIT or > Berkeley licenses much better than GPL, since they let anyone use the code > for any purpose and don't insist on other conditions. > > To say that someone else holds the copyright (e.g. a publisher) used to be > common. It is less common now, and probably a really bad idea. Do you > really want to have NO standing in any dispute about authorship etc.?
Technically I do. But for the most part I don't care. If I did care I would put it. But Sage isn't my project and isn't my problem or responsibility. > On Friday, May 27, 2016 at 2:21:37 AM UTC-7, Erik Bray wrote: >> >> On Thu, May 26, 2016 at 12:25 PM, Volker Braun <vbrau...@gmail.com> wrote: >> > There is no contributor license agreement. Every file must be GPLv2+ >> > licensed. If you start a new file you have copyright on that module >> > whether >> > you put your name in there or not; But we need the GPLv2+ statement to >> > distribute it as part of Sage. >> >> That I have no problem with. >> >> > On Thursday, May 26, 2016 at 12:16:11 PM UTC+2, Erik Bray wrote: >> >> >> >> Hi, >> >> >> >> I am not a lawyer, I don't pretend to be a lawyer, nor do I even >> >> pretend like I know anything about copyrights or licenses beyond what >> >> I can read on Wikipedia. >> >> >> >> So I'm very confused about the policy for copyrighting any work I >> >> contribute to sage. I would like to add a new file to sage--I've >> >> noticed that most files contain some kind of copyright notice, >> >> assigning copyright ownership to the original author of the file (many >> >> of these also have woefully outdated copyright dates despite the files >> >> being since updated, though my understanding is this technically >> >> doesn't matter). >> >> >> >> So my question is, what should I put in a new file? I don't want to >> >> claim copyright ownership under my own name, because I expect any file >> >> I contribute to the project to belong to all developers of the >> >> project, and for its protections to be covered under Sage's GPL >> >> license anyways. >> >> >> >> It would seem more efficient to simply put a notice at the top of the >> >> file to refer to Sage's license. >> >> >> >> Thanks, >> >> Erik >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "sage-devel" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to sage-devel+...@googlegroups.com. >> > To post to this group, send email to sage-...@googlegroups.com. >> > Visit this group at https://groups.google.com/group/sage-devel. >> > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
