Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More correctly implement GPLv3 compliance #2610

Closed
wants to merge 1 commit into from
Closed

Conversation

hakusaro
Copy link
Member

@hakusaro hakusaro commented Apr 2, 2022

The previous startup disclaimer probably didn't do a good-enough job of
explaining license terms to people. This updates it emphasizing that
there is no warranty with the software, and that the actual license is
GPL v3 or later, not GPL v3. Further, since we don't ship the license
with the software (yet), this gives people a link to the license. The
license itself says we should provide a link if we don't, so yeah.

Inspired by the fact that we had another user pop into discord asking
why all of their stuff was deleted.

I tried to keep the startup disclaimer roughly-the-same-size as the
original disclaimer (no more than 3 lines, some-ish length), because
this is so annoying but I feel like we actually need to try to be
compliant here.

I'm 60% sure we should implement a command that explains this but I
really don't want to do that.

The previous startup disclaimer probably didn't do a good-enough job of
explaining license terms to people. This updates it emphasizing that
there is no warranty with the software, and that the actual license is
GPL v3 or later, not GPL v3. Further, since we don't ship the license
with the software (yet), this gives people a link to the license. The
license itself says we should provide a link if we don't, so yeah.

Inspired by the fact that we had another user pop into discord asking
why all of their stuff was deleted.

I tried to keep the startup disclaimer roughly-the-same-size as the
original disclaimer (no more than 3 lines, some-ish length), because
this is so annoying but I feel like we actually need to try to be
compliant here.

I'm 60% sure we should implement a command that explains this but I
really don't want to do that.
@hakusaro hakusaro requested a review from a team April 2, 2022 18:42
@hakusaro
Copy link
Member Author

hakusaro commented Apr 2, 2022

The exact thing I'm looking at is (from https://www.gnu.org/licenses/gpl-3.0.en.html):

If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:

<program>  Copyright (C) <year>  <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

The hypothetical commands show w' and show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.

@hakusaro
Copy link
Member Author

hakusaro commented Oct 6, 2022

I no longer care about this branch

@hakusaro hakusaro closed this Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants