There is scope for inaccurate results on licence matching, and exceptions could also be a pain if conducted pre-commit, so I'm not sure it should be a commit hook. We should really just have RAT running automated checks for us on the ASF CI boxes (along with several other types of testing...) on a regular basis.
I licenced a lot of stuff for the last release even if it was deemed not to require a licence in previous releases, so there is a vastly reduced scope of results for consideration now. Automating a check which ruled out known good files and alerted us on eg a weekly basis to any new suspects seems like it would be sufficient here. Adding licences to actual new code files wasnt that much of a burden for 0.8 from what I remember. Robbie On 15 February 2011 16:21, Rajith Attapattu <[email protected]> wrote: > Hi All, > > It seems there is good support for adding a pre-commit hook for checking > JIRA reference. > While we are at it, I'd like to draw your attention to another problem that > makes a release managers job unnecessarily tedious. > > We all have been guilty of adding files to the svn repo without the > mandatory license header. > > I believe there is a good case for adding a pre commit hook that checks the > license header when adding new files. > We also need to have a mechanism to ensure certain files get exempted from > this check. > > Thoughts ? > > Regards, > > Rajith Attapattu > Red Hat > http://rajith.2rlabs.com/ > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
