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

Grab SPDX license code and populate with license file if it doesn't exist #58

Open
RichardLitt opened this issue Nov 16, 2017 · 9 comments

Comments

@RichardLitt
Copy link
Member

No description provided.

@wooorm
Copy link
Collaborator

wooorm commented Nov 18, 2017

Could you expand on this? Such as with an input (readme.md) / output (LICENSE) example?

@wooorm
Copy link
Collaborator

wooorm commented Nov 18, 2017

I’m especially interested in what you’d like now, and what you’d like somewhere in the far away future!

@RichardLitt
Copy link
Member Author

Input: Repo with a README that has this at the bottom:

MIT © author

Or something similar, and no license file. Create the MIT license, cat it into a LICENSE file, and then link it in the Readme ([MIT](LICENSE) © Author).

@RichardLitt
Copy link
Member Author

In the future, I'd like to fix all inconsistencies and make sure that the license included is the one specified. Take all of the manual work away from the users.

@wooorm
Copy link
Collaborator

wooorm commented Nov 20, 2017

From you second comment, what do you expect to happen now (not the future), if ISC © author is in the README?

@RichardLitt
Copy link
Member Author

// pseudo-js

if (readme.contains('ISC © Name') && license.file !== true) {
     fs.writeSync({to: LICENSE.md, type: ISC_DOCUMENT, licensee: 'NAME'})
}

Basically. Make sense?

@wooorm
Copy link
Collaborator

wooorm commented Nov 20, 2017

Well that one makes sense, yes, but I was kinda looking for how long the list of supported (for now) licenses should be! Just supporting MIT (and/or ISC) is a very different task compared to supporting all licenses!

@RichardLitt
Copy link
Member Author

Make it so that we can add to it. At the beginning: MIT, ISC, Apache should be enough.

@RichardLitt
Copy link
Member Author

@wooorm This isn't a priority, issue, though. See the top issues in 'To Do' on https://github.com/mntnr/build-a-space/projects/1 for that.

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

No branches or pull requests

2 participants