Closed danluu closed 8 years ago
This looks good after a cursory inspection. You can commit this, but we should consider what copyright year we want to use. We can update the year later with a global search/replace. Any ideas about the year we should use?
Based on the commit history, maybe we should do 2014-2016 on this? I don't really understand how much the date matters, if at all. I think we should just ping someone in legal about that because they'll be able to give us a response that's likely to be more accurate than whatever we'd get from reading random things on the internet, and they should also be able to point us to someone who knows it off the top of their heads.
For example, if it's important to be precise on a per-file basis, I could change my script to make the date range based on the actual commit dates. I'm guessing this doesn't matter, but I know approximately zero about copyright law.
Fixes #7.
This was done with a horrible hack script, so it should be easy to change this if we want to change the formatting. I couldn't Google up a good way to do this, so maybe I should clean up the script and make it generally available.
Also, I think we're going to start getting merge conflicts if we don't start reviewing/merging PRs. If the issue is that it's not in codeflow, I can grab a Windows machine and run codeflow, but I think that for stuff this simple even github should be ok.