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

LICENSE: add title; collapse double newline at EOF #2

Closed
wants to merge 1 commit into from
Closed

LICENSE: add title; collapse double newline at EOF #2

wants to merge 1 commit into from

Conversation

waldyrious
Copy link

The title is not legally mandated, but it's recommended in the license template text (see http://choosealicense.com/licenses/isc/ and https://opensource.org/licenses/isc-license).

This PR is part of a project to improve the consistency and visibility of the ISC license. See github/choosealicense.com#377 for more details.

The title is not legally mandated, but it's recommended in the license template text (see http://choosealicense.com/licenses/isc/ and https://opensource.org/licenses/isc-license).
@juliohm
Copy link
Member

juliohm commented Nov 19, 2017

Thank you @waldyrious , since the title doesn't affect the legal aspect of it, I will leave it clean as it is.

@juliohm juliohm closed this Nov 19, 2017
@waldyrious
Copy link
Author

I understand that perspective -- I recognized it in the opening sentence of the PR, after all :)

Still, I'd suggest you to reconsider, in light of the desire you've demonstrated elsewhere to make this license more well-known: the title helps a great deal in making the license more visible. I think you might agree that the downsides of adding a single (quite relevant!) line are offset by the potential benefit that line can provide.

To give you an idea, in my efforts to disseminate the practice of including the title in the ISC license, multiple people have expressed surprise by finding out that the license they thought was MIT was instead ISC. You're right that these details don't matter for machines and for lawyers, but for regular human beings it plays a significant role in the social aspect of what makes a license more or less used.

@juliohm
Copy link
Member

juliohm commented Nov 19, 2017

I agree that the it is important to educate people about it, but I just don't see the point of merging pull requests everywhere where the license is already being used. New packages can include the title if they want.

@waldyrious
Copy link
Author

I just don't see the point of merging pull requests everywhere where the license is already being used. New packages can include the title if they want.

I see it this way: If someone has decided to pick ISC for a new project, it's because they already know about it, so for them the title adds no value. Instead, the intended audience for this change is people who don't know about ISC, look at a package's existing license (e.g. to check for compliance requirements), learn that it is ISC, happen to like its conciseness, and decide to use it for their own project. Does this makes sense?

@waldyrious
Copy link
Author

See juliohm/InverseDistanceWeighting.jl#1 for additional context.

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.

2 participants