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

remove splash msg #9

Closed
wants to merge 1 commit into from

Conversation

dradetsky
Copy link

Apart from anything else, when I first started playing with beamcoder to try to figure it out, these messages made it harder to read the errors.

@sparkpunkd
Copy link
Contributor

The splash message is mandated in the GPL license term and conditions. It cannot be removed.

@sparkpunkd sparkpunkd closed this May 27, 2019
@dradetsky
Copy link
Author

@sparkpunkd I do not think you are right about that. The mere fact that so many projects which come from the FSF and similar do not do this ought to make you realize that it probably is not required.

In any case, do you want to remove it? Or do you want to keep it in? Or do you not care either way, you just don't want to violate the GPL?

@dradetsky
Copy link
Author

@scriptorian opinion?

@scriptorian
Copy link
Contributor

I believe the splash message is "Appropriate Legal Notices" as described in the license agreement and should stay.

@dradetsky
Copy link
Author

@scriptorian @sparkpunkd I asked you both whether or not you wanted the notices for a reason. Whether or not the notices are required is a factual question on which you could seek expert guidance. For example, the FSF employs lawyers who might be willing to help you answer this question.

I made the PR to attempt to make beamcoder, in my opinion, better and more useful as a piece of technology. Without these messages, it's easier for me to use the library to solve my problems. If you agree with this, but are worried about the legal implications, that's totally understandable. It also tells us how to proceed. We figure out the actual legal implications, and try to solve the problem within the boundaries of what they permit.

If on the other hand, you don't agree, and you want the notices, then the requirements of the GPL are neither here nor there. It's your project, and you don't want this PR. You consider the ways in which it would improve my personal UX a non-goal for your project. That's your privilege.

So rather than disagree about what is or isn't required by the GPL, let me ask: do you approve of the goal or not?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants