License change to match Flask's BSD license

[esbullington]

Are there any objections if I change the license from Apache to 3-clause BSD? I actually prefer the MIT or Apache, but on retrospect I'd like for the project license to match Flask's license so that folks don't have to deal with more licenses that necessary for a single project.

In the words of the Flask license information page, the 3-clause BSD license basically means: "do whatever you want with it as long as the copyright in Flask sticks around, the conditions are not modified and the disclaimer is present. Furthermore you must not use the names of the authors to promote derivatives of the software without written consent".

So you're free to use this skeleton for closed-source proprietary projects under both Apache and BSD, as long as you keep the copyright.

Note that the 3-clause BSD is FSF-compatible, as well as OSD-compliant.

Any existing code that's already been used for a project would of course remain Apache-licensed. The BSD license would only apply to new projects.

[lizardlab]

Well I for one welcome it, smart idea on unifying all the code into one license. I don't see what was the whole deal about having it Apache in the first place. What advantages does it have over the 3 clause BSD or GPLv3 licenses?

[esbullington]

Great, thanks for your input. Really, I just pulled Apache out of a hat when I first put this project up -- I didn't anticipate doing any long-term maintenance. I may have pulled the license wholesale from another Python project using Jquery and Bootstrap, or from one of my projects -- can't remember.

I've since realized that quite a few people are interested in Flask project skeletons, so I intend to maintain it and even improve it (while still maintaining it as a minimal app skeleton). Thus the desire to harmonize this project's license with Flask's.

I'll probably going ahead and change the license next time I'm editing the README, since no one seems to object. Both Apache and BSD are pretty permissive and allow users to use the project for whatever they want -- including closed commercial projects -- as long as they retain the copyright notice and license.

[esbullington]

@lizardlab I changed the license as discussed and also added an AUTHORS file for contributors. May I add you to that file? Alternately, you're welcome to add your name/id yourself in a PR.

[lizardlab]

That would be great! I'll let you do it, no need to go through the trouble of making another pull request for a line in one file.

[esbullington]

Done!