Grab SPDX license code and populate with license file if it doesn't exist about build-a-space HOT 9 OPEN

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.

from build-a-space.

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

from build-a-space.

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

from build-a-space.

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).

from build-a-space.

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

from build-a-space.

// pseudo-js

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

Basically. Make sense?

from build-a-space.

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!

from build-a-space.

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

from build-a-space.

@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.

from build-a-space.