+1 (non-binding)
Best regards,
Zhiguo Wu
On Fri, Oct 11, 2024 at 11:36 AM Willem Jiang
wrote:
> +1 binding.
> I'd be happy to be the mentor of this project.
>
> Thanks,
>
> Willem Jiang
>
>
>
> On Fri, Oct 4, 2024 at 8:11 AM Roman Shaposhnik wrote:
> >
> > Hi folks,
> >
> > Following the discu
+1 binding.
I'd be happy to be the mentor of this project.
Thanks,
Willem Jiang
On Fri, Oct 4, 2024 at 8:11 AM Roman Shaposhnik wrote:
>
> Hi folks,
>
> Following the discussion about CloudBerry
> (https://lists.apache.org/thread/1f8jwpjnn430bhsjq98qxlgjojpqrfdh),
> and after seeing a few upd
The binary variations would take quite some time to get there… would be
possible to - for the first release - limit the scope of the first
incubating release to the first step you mentioned (vanilla LICENSE,
NOTICE, DISCLAIMER-WIP)?
I’m afraid would take quite a lot to get to the level of details
You could start by adding the vanilla LICENSE, NOTICE, DISLAIMER-WIP
from https://github.com/apache/incubator-kie-tools into each tar.gz.
Later, you would need to update the LICENSE and NOTICE to comply with
the licenses/notices of any 3rd party source or binaries that appear
in the tar.gz.
If yo
PJ,
There are about 22 container images that are .tar.gz files, all those
files were generated with docker export command. My question is it
really needed to add to those image .tar.gz the LICENSE, NOTICE and
DISCLAIMER-WIP files?
If yes... is there any example how to write a NOTICE file for cont
The KIE PPMC will need to vote on the RC3. Usually votes in PPMC
happen before the IPMC vote. I'm not 100% sure if there is an absolute
requirement that the 2 votes need to be held at different times.
Ideally the mentors of the KIE project will get involved in the PPMC
vote because they know what t
PJ, since we're new to doing the release, for RC3 do we need to do another 72
hour voting period for the KIE PPMC, or do we roll an RC3 and start a new vote
here?
On 2024/10/09 23:17:48 PJ Fanning wrote:
> Thanks for your explanation. I fully understand where you are coming from. I
> don't wan
For the record the gradle-wrapper.jar was explicitly discussed under
LEGAL-570 [1] and it is not allowed in source releases. More general
binary code is highly discouraged [2].
Based on [3] if the binary code issues are listed in the
DISCLAIMER-WIP then the incubation release may still receive a +
