On Sun, Nov 13, 2016 at 5:31 AM, Stefano Zacchiroli <z...@upsilon.cc> wrote:
> Heya, > I've tried to understand the actual license under which Beancount is > released, but I haven't found a conclusive answer --- hence my question > here. > > - the top-level COPYING file is the text of the GPL, version 2.0 > - most .py files have no explicit license header > The license at the root of the project applies. Do I need to repeat the license in each and every file? I used to do that on some other projects, didn't bother for this project. > - setup.py and PKGINFO say "GPL" (without version); hence PyPi says the > same > - bin/treeify contains "__license__ = 'GNU GPL v2'" > - README says: "This code is distributed under the `GNU General Public > License <COPYING>`_;" (which looks like a typo/incomplete sentence?) > > So it looks like Beancount is GPL2, but is not clear if it's "version 2 > only" or "version 2 or above". Either way, being more explicit about all > this would be ideal and helps, for instance, distribution packagers. > (My 0.02 EUR: "2 or above" would be better.) > Thanks for pointing out some loose ends. Martin: can you clarify? > Yes, it's v2. No strong opinions about moving it to v3, I just don't have time to review the implications. While we are at it, I remember that in the past you started a discussion > about contributor agreements, but I don't remember reading a conclusion > about that. What do you currently require in order to accept patches > coming from contributors? > (My 0.02 EUR: just for something very lightweight, like the DCO, and > avoid other CAAs/CLAs.) > After much reading about this, I'm still set on having something like the Clojure project (and many others) with a signed CA for contributions beyond a few LOC. This hasn't been a problem yet, because most of the contributions are done upstream in the fava project (lots of activity there!). So far I've tried to respond to their needs myself and implement core changes when they need them. Note: It's still a GPL'ed project, and as always, my intent is for it to remain free forever. I remember the license issue used to be somewhat of a problem for you, and I have no solution to offer. You'll have to decide for yourself whether ideology trumps practicality. (Note that you can accomplish a *lot* of customization via plugins, which you don't have to contribute back by changes to the project itself, so that's an alternative.) Many thanks in advance for your clarifications, > Cheers. > -- > Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o > Computer Science Professor . CTO Software Heritage . . . . . o . . . o o > Former Debian Project Leader . OSI Board Director . . . o o o . . . o . > « the first rule of tautology club is the first rule of tautology club » > > -- > You received this message because you are subscribed to the Google Groups > "Beancount" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beancount+unsubscr...@googlegroups.com. > To post to this group, send email to beancount@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beancount/20161113103108.ppk3vo2ider4ocky%40upsilon.cc. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To post to this group, send email to beancount@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhO-MdkiGg-YnarzXwZ%3DWWzNtcvGzccyP6X2fqCE-MeqCw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
