Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Is this legal / morally ok? #771
First of all, cool project this! So please don't see this is as negative criticism...
In your readme you state that
This is actually pretty common practice but I've always frowned upon it.
The copyright notice does not in itself hold much legal value afaik, so just putting the current year in it is probably not illegal, but it is definitely wrong technically and I wonder about it's moral implications...
The right thing to do would probably be to allow for the copyright notice details to be passed along in the URL itself, so they could be changed for each project:
Of course you could always fall back to the current year if no year was passed in the URL. Or better yet, use the year the cname was created. That will also stimulate people to pass the URL argument to 'update' the copyright when they make changes later.
What do you think?
A bit late, but I've been re-reading this (after there was an outage on the hosting and I had to update a few bits).
I've added the ability to pin to a specific year as you suggested: https://rem.mit-license.org/@2010
I guess the real source of the problem is that this is a service tied to a single user, whereas licenses are typically inserted into project code, so they're per project, which allows them to have a fixed date.
@belldandu given the context of this open issue, I'm not sure putting in the json file would actually make sense. It would then affect everywhere that you linked from... it's possible it's actually in the code already (I've not checked), and if there demand, I'd be happy to accept a PR for it.