1. 03 Dec, 2019 3 commits
  2. 02 Nov, 2017 1 commit
  3. 11 Jul, 2017 1 commit
  4. 03 Jul, 2017 1 commit
  5. 21 Apr, 2016 1 commit
  6. 10 Feb, 2016 1 commit
  7. 22 Jan, 2016 1 commit
  8. 06 Sep, 2015 1 commit
  9. 29 Jun, 2015 1 commit
  10. 15 Jun, 2015 1 commit
  11. 15 May, 2015 1 commit
    • Yorick Peterse's avatar
      Change license from MIT to MPL 2.0 · 0a7242ae
      Yorick Peterse authored
      While the MIT license is a fantastic license for those too lazy (or
      unable) to understand more complex licenses it's too lax when it comes
      to protecting authors (= me). For example, there are no clauses regarding
      patents or ownership of source code. This means that patent trolls
      could, in theory, drag me to court.
      
      Of course one can still do that when using the MPL, but at least it has
      an explicit clause regarding patents. The MPL also provides a nice
      balance between the MIT license and the Apache license. I don't like the
      Apache license as it requires listing any significant changes in every
      changed file.
      
      In short, I don't really care what people do with my software (they
      could sell it for millions for all I care), as long as they don't drag
      me to court or otherwise hold me accountable for something.
      0a7242ae
  12. 11 May, 2015 3 commits
  13. 27 Apr, 2015 2 commits
  14. 21 Mar, 2015 1 commit
  15. 17 Nov, 2014 2 commits
  16. 16 Nov, 2014 4 commits
  17. 16 Sep, 2014 2 commits
  18. 12 Sep, 2014 2 commits
  19. 11 Sep, 2014 1 commit
  20. 10 Sep, 2014 3 commits
  21. 09 Sep, 2014 1 commit
  22. 03 Sep, 2014 3 commits
  23. 22 Jul, 2014 2 commits
  24. 23 Jun, 2014 1 commit