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 - 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.) Martin: can you clarify? 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.) Many thanks in advance for your clarifications, Cheers. -- Stefano Zacchiroli . [email protected] . 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 [email protected]. To post to this group, send email to [email protected]. 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.
