search

opendata-stuttgart / metaEFA

an easy to use api wrapper for EFA
Other
33 stars 6 forks source link

License and contributors #3

Closed michael-k closed 9 years ago

michael-k commented 9 years ago

@momorientes @asmaps @c1ko @dansch94: License and contributors are still filled with the django boilerplate content. I'd vote in favor of deleting CONTRIBUTORS.txt, but what about the license? Should we stay with the MIT license (the copyright notice needs an update) or switch to another one?

asmaps commented 9 years ago

I'm ok with MIT, but also BSD if you want. Best would be to put this link in contributors: https://github.com/momorientes/metaEFA/graphs/contributors

michael-k commented 9 years ago

BSD 2-clause, BSD 3-clause or ISC? http://choosealicense.com/licenses/ I think MIT has the advantage over “BSD” that it's clear which license is meant.

https://github.com/momorientes/metaEFA/graphs/contributors doesn't list @momorientes (author email not added to github account?) and @dansch94 (wiki only).

asmaps commented 9 years ago

yes, @momorientes didn't add the used mail to his account => no contribution ("I don't care")

I still think the github contributors page is the best place to link to, because it fills/updates automatically. We can add a "doc contributors" list in the readme or so, to give credit to people that didn't contribute code.

Regarding LICENSE: I don't really care. I don't see the need for GPL or so and BSD, MIT, ISC, etc are very close to each other.