> On Jan 6, 2016, at 7:16 AM, Steve Loughran <ste...@hortonworks.com> wrote: > >> On 5 Jan 2016, at 11:55, Daniel Gruno <humbed...@apache.org> wrote: >> >> See http://compliance.rocks/result.html?1152a2a9 for a list of minor >> nits (missing some license headers in a bunch of python scripts). >> > nice script
+1 > I think some other projects keep their protoc generated source files in SCM > —what do they do license-wise? Calcite’s process [1] is to generate the source files using a script that adds headers, then check them into git. The files, for example [2], are exempted from the usual checkstyle rules for formatting but have the usual Apache file headers. Julian [1] http://calcite.apache.org/docs/howto.html#rebuilding-generated-protocol-buffer-code <http://calcite.apache.org/docs/howto.html#rebuilding-generated-protocol-buffer-code>
