incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Cole <adrian.f.c...@gmail.com>
Subject Re: the case of the maven wrapper
Date Thu, 14 Feb 2019 06:46:48 GMT
> Does it help, that I wrote that file and submitted it in a pull request to
> eliminate the binary jar needed prior to my change? ... Guess that's also
> an additional reason why there's an Apache header on it :-)


imho it helps in so far as the work itself (thanks!) and also a subject
matter expert. I see this file as useful but incidental.

If we set a precedent towards having to re-link this file in our NOTICE..
you might expect this to cause a flurry of low value activity across every
project that uses it, to do the same, or projects like us feeling unfair
burden by accident of the month we joined the incubator.  ex if we did
early last year surely this discussion would haven't happened (as others
graduated before the more recent scrutiny of incubees.

If we all say fine.. let's just throw more paperwork at it, I would ask you
to help draft a line for the NOTICE of what we would do. suppose we would
also have to do this for gradle etc.

So basically if we accept that the new norm is this level of detail on
incidental files, we likely have more volunteer time spent policing and
remediation. We could at least tell them what to say.

would it be "this includes source generated by the takari maven plugin"?
and of course if we say this, the next cruft is explaining gradle etc.

do we want to do this? we can but is it really worthwhile?

you tell me

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message