3 ms·
I've got a small crowdsourced localization dictionary that I want to throw up on Github. http://thespanishsite.com/dictionary http://thespanishsite.com/diction
by melling 11y ago
I've got a small crowdsourced localization dictionary that I want to throw up on Github.
http://thespanishsite.com/dictionary http://thespanishsite.com/dictionary
Should I be using CC0? I thought the MIT License was always the best license to use. I might provide some small scripts, etc, along with the data.
The data is stored in a Google Spreadsheet: https://docs.google.com/spreadsheets/d/1xggGPUqjjy-qTnckFZqS3fUUYOUWOCXYwpbQrfUZvV8/htmlview#gid=0 https://docs.google.com/spreadsheets/d/1xggGPUqjjy-qTnckFZqS...
- dsr_ 11y agoIf it's crowdsourced, then in order to change the license you may have to go to every single contributor and ask for permission to change the license. I don't see a clear statement of license up at the top of your spreadsheet or your webpage. If you have a small number of contributors, and you have email addresses for all of them, you may be able to actually contact all of them in order to set a license. You may want to read up on contributory licenses like the one Wikipedia uses: https://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License https://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Com...
- artlogic 11y ago> I thought the MIT License was always the best license to use. This community in particular seems to like the MIT License because it is quite simple and perceived as commercial friendly. The truth is, like most things, it depends on what you are trying to accomplish. Open source licenses all have an agenda. If your agenda is "Anyone should be able to use this software, for any purpose, and not hold me liable," then the MIT License is perhaps the simplest option. In my (non-lawyer) opinion, where the MIT License falls short is in assuming that all contributors, companies, and users share the basic ideal that licensing software for free use and modification is in our collective best interest. Other licenses (Apache, GPL) try to attack this problem in various ways. It turns out it's a complicated and not fully understood domain - which is why those licenses are more complex. The point is that there is no "best" license to use because licensing is not a technical problem - it's a social problem. Licenses attempt to address the slippery concept of community using a legal framework. In choosing a license, you want to be thinking about not just the community you are currently contributing to, but the community you would ideally like to be contributing to.