>> 1) Eclipse project files, like .classpath and .project. These should >> obviously not contain license headers. > > IMO they shouldn't be in the distributable at all. This will spark > discussion on general@ as well.
I removed them >> 2) package.html (Javadoc) files. Likewise > > A single line package.html is not copyrightable, but when you have a > paragraph, or even more, it is copyrighted, and required license > header. Our package.html files are all basically 1 line right now, but I added the license header anyways just to "future proof" ourselves and to sidestep the discussion on general@ :) >> 3) Resource files (.json). Likewise. > > Not 100% convinced. I do think it is a burden to put those headers in > those files. However, if these files are intended to be modified by > downstream users, they should have a header. But you might want to > postpone this until you presented the release to a larger audience at > general@ I actually realized a few minutes ago that there's a problem with adding license headers to these files - our JSONSerializer will barf on comments. So I left the license headers out of the files in the most recent artifacts.
