Using a standard license is great. Using a custom license that is extremely similar to an existing license is not as good, but is usually workable...
Showing legal how to use Github so they can confirm the age of the software you're using, then convincing them Github is a reputable party will likely result in an unpleasant conversation at best.
A conversation made far less pleasant by the ability to feed arbitrary dates into a Git repo's commit history: https://github.com/gelstudios/gitfiti
I'm sure there's a way to find the actual time a push happened; hopefully it doesn't involve subpoenaing GitHub (or Microsoft, I guess) for logs.
Also, print all of that, get the legal to seal the pages, and put them into a safe.
Wouldn't that be:
> Showing legal how to use [Microsoft] Github so they can confirm the age of the software you're using, then convincing them [Microsoft] Github is a reputable party will likely result in an unpleasant conversation at best.
Seems that 'Microsoft' prefix might get a bit more clout.
You only have to do that if you're setting up a commercial service that competes with sentry. If you're merely setting it up for your own company's self-hosted use, you don't need that.
This might be one actual positive of GitHub getting bought by Microsoft: convincing people who don't know anything about software that it's a reputable party.
Pick one which was cut at a particular point in time and you're done. Doesn't seem that complicated.