Perhaps in places like github. With central versioning systems where the server is under our control we simply run daemons that check the copyright. Each user can define how it should work for them. If copyright is not okay the user can either a) have the submit fail so he is notified that it needs fixing or b) let it be fixed automatically by the daemon.
This fixing also includes adding a copyright notice to new files that didn't have any. Nicely defined depending on the file type.
The implementation was a one time effort which now saves us from doing exactly what they are doing now. Manually going through thousands of files to fix a copyright.
Perhaps in places like github. With central versioning systems where the server is under our control we simply run daemons that check the copyright. Each user can define how it should work for them. If copyright is not okay the user can either a) have the submit fail so he is notified that it needs fixing or b) let it be fixed automatically by the daemon.
This fixing also includes adding a copyright notice to new files that didn't have any. Nicely defined depending on the file type.
The implementation was a one time effort which now saves us from doing exactly what they are doing now. Manually going through thousands of files to fix a copyright.