In an effort to address issue #20, I've added some licensing information to the template. My dilemma is that when we use this template to generate a project for a client, the client may not wish to have the MIT license applied to all of the code we write for them, so we need to be careful about how we do this.
It seems like adding a license blurb in every file is a little excessive, but also can't be done to all files (images, for example) so adding a LICENSE file as recommended by opensource.org is preferred. I put separate LICENSE files inside each of our apps (accounts, common) so that those will always be covered, as well as a blurb inside the portion of README.md that will be stripped out by the template processor during startproject.
However, I'm not certain the LICENSE I've placed in the root of the template is a good idea. It feels like it's too easy to overlook, and accidentally leave unedited after adding a bunch of client code that isn't meant to fall under the MIT license. Maybe that should be removed?
Thoughts? Suggestions? @tbrimhall @lgunnell @kcole or anyone else..