Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Automating quality gates on contribution: Copyright header

The issue I see is that there is no strictly standardized header that is required across all repositories.  Eclipse Jetty is dual licensed so certainly not a standard block there.  I am not sure the value of something that simply scans for the words 'Eclipse Foundation' in a comment at the top of a file.

I think it is a part of the responsibilities of the project, we use a license checking maven plugin, and every new year we go through and update all the copyright dates as a part of the process, updating out base license template.


jesse mcconnell

On Wed, Mar 18, 2020 at 5:46 PM Mickael Istria <mistria@xxxxxxxxxx> wrote:

On Wed, Mar 18, 2020 at 11:40 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
What, specifically, are you frustrated by? Is it the response of the AC to this idea, the EMO, or both?


What, specifically, are your expectations? Based on the bug that you opened, it looks like you expect the EMO to run off and completely implement a solution based on a requirement described with a single sentence.

I'll clarify my expectations on the bug.
Mickael Istria
Eclipse IDE developer, for Red Hat Developers
_______________________________________________ mailing list
To unsubscribe from this list, visit

Back to the top