Translators: Click on the appropriate link to create a page for the translation. When finished, copy the template code and wiki links and paste into the "Translations of this page: " line on the English page.
Keep This Page or the Static One?
I just wanted to ask for opinions on where we should keep the license online. There's currently a copy of the LGPL at https://www.winehq.org/license, but this page also has a copy of it. It makes sense to display it somewhere (and any other licenses our software uses). License don't change often either, but I don't see a downside to keeping it on the wiki, plus updates would be easier whenever WineHQ switches between platforms. KyleAuble (talk) 11:33, 21 April 2018 (CDT)
- Keep this page. The plan is to eventually move all the static web pages to the wiki. --RosanneDiMesio (talk) 15:47, 21 April 2018 (CDT)
I just edited this page to add entries for other parts of the project, but since there's so much nitpicking involved with licensing, I didn't want to make any other changes without asking for a second opinion. I was wondering about making the following possible changes:
- Do we want/need to include the text of the LGPL on this page? Or isn't it enough to provide a link to the GNU website? And if we do want to keep the license on the page, should we also add copies of the GPLv2?
- Since the Wine source code already includes the short notice for the LGPL, do we need to have that here too? Or can we just explain the license in plain-language along with a link?
- I wasn't able to find any info on if and what conditions apply to the website, AppDB content, Bugzilla reports, and forum posts. Is that a non-issue or am I just having trouble finding it?
- Finally, it makes sense to keep the entry for Wine proper in its own section, but for all the other parts of the project, could we sort by license instead. E.g. something like "the LGPL also applies to the Vkd3d library and Wine Wiki content"?