Paul Moore

Ah, I see. Thanks - that's a lot more subtle than I realised.

This was omitted originally because there was no consensus over what tool/structure/markup to use for documentation. I'm not sure if there is more consensus now. > That's what this sampleproject...

TBH, I don't have a strong opinion, I'm no longer the owner of this project. Its original role definitely *wasn't* in support of the PyPUG, as it predates that document...

As the owner of the new project, can't you simply relicense it as you please? Obviously the new license has to be compatible with the project being derived from MIT-licensed...

... um, I just noticed (a) that this is an old issue, and (b) that even though `setup.py` states that the license is MIT (which was my intent, as noted)...

Al I said, my intention was that it was licensed under MIT (From what I understand, there's no legal concept of "not licensed" so we should be explicit). I have...

Agreed. Should I add a `LICENSE.txt` file with the MIT details to make it clearer that the project is under MIT license (as per `setup.py`)?

Done via #40 If someone wants to clone this project to use as a base for a non-MIT licensed project, I suggest they get legal advice on what would be...

One thought - why is this not an issue for cookiecutter templates (https://github.com/audreyr/cookiecutter)? From a quick check, their templates seem to have various licenses including BSD. Maybe it's worth seeing...

I'm sorry if this is awkward for anyone, but to be clear, I licensed the original code as MIT, and I'd like it to stay that way. Ownership of the...