Re: [VOTE] Release Apache Celeborn(Incubating) 0.2.0-incubating-rc3

[Yu Li]

*bq. no need to add anything into NOTICE*
Correction: here we need to analyze the Spark NOTICE file and the relevant
portions bubbled up into the top-level NOTICE file [1], as already pointed
out by Justin in previous reply [2].

Best Regards,
Yu

[1] https://infra.apache.org/licensing-howto.html#alv2-dep
[2] https://lists.apache.org/thread/bopd2yql1nvjt1kmn9vcd86zqg924g21

On Tue, 31 Jan 2023 at 14:03, Yu Li  wrote:

> Thanks for the further clarification Justin, it helps a lot. And thanks
> for correcting me. Now I understand that I should have referred to the
> 3rd-party section [1] instead.
>
> Explicitly, I think the action-to-do is to add (append) the below lines
> into the Celeborn LICENSE file [2] (similar to that of Spark [3]), meantime
> keep the copyright text in the source file and no need to add anything into
> NOTICE:
>
>
> **
>
> *This product bundles various third-party components under other open
> source licenses.*
>
> *This section summarizes those components and their licenses. See
> licenses/*
>
> *for text of these licenses.*
>
>
>
> *Apache Software Foundation License 2.0*
>
> *--*
>
>
>
> *common/src/main/java/org/apache/celeborn/common/network/util/LimitedInputStream.java*
>
>
>
> ==
> PS. attaching the detailed license instructions below for easier reference:
>
>1. The term "third-party work" refers to a work not submitted directly
>to the ASF by the copyright owner or owner's agent. This includes parts of
>a work submitted directly to the ASF for which the submitter is not the
>copyright owner or owner's agent.
>2. Do not modify or remove any copyright notices or licenses within
>third-party works.
>3. Make sure that every third-party work includes its associated
>license, even if that requires adding a copy of the license from the
>third-party download site into the distribution.
>4. Do not add the standard Apache License header to the top of
>third-party source files.
>5. Minor modifications/additions to third-party source files should
>typically be licensed under the same terms as the rest of the third-party
>source for convenience.
>6. The project's PMC should deal with major modifications/additions to
>third-party source files on a case-by-case basis.
>
>
> Best Regards,
> Yu
>
> [1] https://www.apache.org/legal/src-headers.html#3party
> [2] https://github.com/apache/incubator-celeborn/blob/main/LICENSE
> [3] https://github.com/apache/spark/blob/master/LICENSE#L204-L213
>
>
> On Tue, 31 Jan 2023 at 13:11, Justin Mclean 
> wrote:
>
>> Hi,
>>
>> > *bq. It belongs in LICENSE not NOTICE only copyright notices that have
>> been
>> > removed (by or with the permission of the owner) get listed in NOTICE*
>> > Since Guava is also with ALv2, referring to [1], my understanding is
>> that:
>> > 1. There should be no copyright notice in the header (#2)
>> > 2. We need to move the copyright to the NOTICE file associated with each
>> > applicable project release (#1.b)
>> >
>> > And referring to [2], "Copyright notifications which have been
>> relocated,
>> > rather than removed, from source files must be preserved in NOTICE
>> (unless
>> > embedded in MIT/BSD license)". I'm not sure whether reserving the
>> copyright
>> > in Spark way means "relocate", but if it is, then it seems the copyright
>> > should occur (be reserved) in NOTICE.
>>
>> Sorry that's not correct as:
>> - Relocated in this context means that the owner has given the software
>> to the ASF (usually via a software grant).
>> - Guava is 3rd party software so it needs to be mentioned in LICENSE.
>> - Guava is not an ASF project so its header would have a copyright line
>>
>> This will probably help [1]
>>
>> Kind Regards,
>> Justin
>>
>> 1. https://infra.apache.org/licensing-howto.html#alv2-dep
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [RESULT] [VOTE] Release Apache Liminal (incubating) 0.0.5rc2-INCUBATING

[陈卓宇]

+1 (non-binding):

Lidor Ettinger  于2023年1月25日周三 16:27写道：

> Hi all,
>
> Thanks for your review and vote for Apache Liminal version
> 0.0.5rc2-INCUBATING. I'm happy to announce the vote has passed:
>
> +1 (binding):
> Justin Mclean
> Jean-Baptiste Onofré
> Davor Bonaci
>
>
> +1 (non-binding):
> Lior Schachter
> Aviem Zur
>
> Many thanks to our mentors for helping us with the release and IPMC voters
> that reviewed and approved this version. I will be working on publishing
> the artifacts in the next few days.
>
> Cheers,
> Lidor Ettinger
>

Re: [VOTE] Release Apache Celeborn(Incubating) 0.2.0-incubating-rc3

[Yu Li]

Thanks for the further clarification Justin, it helps a lot. And thanks for
correcting me. Now I understand that I should have referred to the
3rd-party section [1] instead.

Explicitly, I think the action-to-do is to add (append) the below lines
into the Celeborn LICENSE file [2] (similar to that of Spark [3]), meantime
keep the copyright text in the source file and no need to add anything into
NOTICE:

**

*This product bundles various third-party components under other open
source licenses.*

*This section summarizes those components and their licenses. See licenses/*

*for text of these licenses.*



*Apache Software Foundation License 2.0*

*--*


*common/src/main/java/org/apache/celeborn/common/network/util/LimitedInputStream.java*



==
PS. attaching the detailed license instructions below for easier reference:

   1. The term "third-party work" refers to a work not submitted directly
   to the ASF by the copyright owner or owner's agent. This includes parts of
   a work submitted directly to the ASF for which the submitter is not the
   copyright owner or owner's agent.
   2. Do not modify or remove any copyright notices or licenses within
   third-party works.
   3. Make sure that every third-party work includes its associated
   license, even if that requires adding a copy of the license from the
   third-party download site into the distribution.
   4. Do not add the standard Apache License header to the top of
   third-party source files.
   5. Minor modifications/additions to third-party source files should
   typically be licensed under the same terms as the rest of the third-party
   source for convenience.
   6. The project's PMC should deal with major modifications/additions to
   third-party source files on a case-by-case basis.


Best Regards,
Yu

[1] https://www.apache.org/legal/src-headers.html#3party
[2] https://github.com/apache/incubator-celeborn/blob/main/LICENSE
[3] https://github.com/apache/spark/blob/master/LICENSE#L204-L213


On Tue, 31 Jan 2023 at 13:11, Justin Mclean 
wrote:

> Hi,
>
> > *bq. It belongs in LICENSE not NOTICE only copyright notices that have
> been
> > removed (by or with the permission of the owner) get listed in NOTICE*
> > Since Guava is also with ALv2, referring to [1], my understanding is
> that:
> > 1. There should be no copyright notice in the header (#2)
> > 2. We need to move the copyright to the NOTICE file associated with each
> > applicable project release (#1.b)
> >
> > And referring to [2], "Copyright notifications which have been relocated,
> > rather than removed, from source files must be preserved in NOTICE
> (unless
> > embedded in MIT/BSD license)". I'm not sure whether reserving the
> copyright
> > in Spark way means "relocate", but if it is, then it seems the copyright
> > should occur (be reserved) in NOTICE.
>
> Sorry that's not correct as:
> - Relocated in this context means that the owner has given the software to
> the ASF (usually via a software grant).
> - Guava is 3rd party software so it needs to be mentioned in LICENSE.
> - Guava is not an ASF project so its header would have a copyright line
>
> This will probably help [1]
>
> Kind Regards,
> Justin
>
> 1. https://infra.apache.org/licensing-howto.html#alv2-dep
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Celeborn(Incubating) 0.2.0-incubating-rc3

[Justin Mclean]

Hi,

> *bq. It belongs in LICENSE not NOTICE only copyright notices that have been
> removed (by or with the permission of the owner) get listed in NOTICE*
> Since Guava is also with ALv2, referring to [1], my understanding is that:
> 1. There should be no copyright notice in the header (#2)
> 2. We need to move the copyright to the NOTICE file associated with each
> applicable project release (#1.b)
> 
> And referring to [2], "Copyright notifications which have been relocated,
> rather than removed, from source files must be preserved in NOTICE (unless
> embedded in MIT/BSD license)". I'm not sure whether reserving the copyright
> in Spark way means "relocate", but if it is, then it seems the copyright
> should occur (be reserved) in NOTICE.

Sorry that's not correct as:
- Relocated in this context means that the owner has given the software to the 
ASF (usually via a software grant).
- Guava is 3rd party software so it needs to be mentioned in LICENSE.
- Guava is not an ASF project so its header would have a copyright line

This will probably help [1]

Kind Regards,
Justin

1. https://infra.apache.org/licensing-howto.html#alv2-dep
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Celeborn(Incubating) 0.2.0-incubating-rc3

[Yu Li]

Hi Justin,

Thanks for the quick reply.

*bq. Not sure why you are discussing this on your private list*
Since I'm not sure whether the team has already addressed the issue and
prepared another RC, and I'm not sure whether my understanding is correct,
so I reduce the discussion scope to internal to prevent bothering others.
Now I'm adding back the @general list since the discussion might also help
others.

*bq. It belongs in LICENSE not NOTICE only copyright notices that have been
removed (by or with the permission of the owner) get listed in NOTICE*
Since Guava is also with ALv2, referring to [1], my understanding is that:
1. There should be no copyright notice in the header (#2)
2. We need to move the copyright to the NOTICE file associated with each
applicable project release (#1.b)

And referring to [2], "Copyright notifications which have been relocated,
rather than removed, from source files must be preserved in NOTICE (unless
embedded in MIT/BSD license)". I'm not sure whether reserving the copyright
in Spark way means "relocate", but if it is, then it seems the copyright
should occur (be reserved) in NOTICE.

Please further correct me if I misunderstood anything. Thanks.

Best Regards,
Yu

[1] https://www.apache.org/legal/src-headers.html#headers
[2] https://infra.apache.org/licensing-howto.html#mod-notice

On Tue, 31 Jan 2023 at 11:51, Justin Mclean 
wrote:

> Hi,
>
> Not sure why you are discussing this on your private list.
>
> 3. The Spark project directly nests the Guava copyright in the source
> file, which is incorrect according to [1] from my perspective. Instead, it
> should include the Guava copyright in its NOTICE file.
>
>
> It belongs in LICENSE not NOTICE only copyright notices that have been
> removed (by or with the permission of the owner) get listed in NOTICE.
>
>
> 4. For us, I believe the correct thing to do is to add the Guava copyright
> into our NOTICE file, in a way like below (referring to [4]):
> The codes of common/network/util/LimitedInputStream partially derives
> from Guava
> Copyright (C) 2007 The Guava Authors
>
>
> No that is not correct.
>
> Kind Regards,
> Justin
>
> On 31 Jan 2023, at 2:36 pm, Yu Li  wrote:
>
> Hi Team,
>
> I'm wondering whether this issue is already addressed, if not, here are my
> two cents:
> 1. Overall we should follow the instructions here: [1].
> 2. From the originated Spark source file [2], it stems from the Google
> Guava project [3].
> 3. The Spark project directly nests the Guava copyright in the source
> file, which is incorrect according to [1] from my perspective. Instead, it
> should include the Guava copyright in its NOTICE file.
> 4. For us, I believe the correct thing to do is to add the Guava copyright
> into our NOTICE file, in a way like below (referring to [4]):
> The codes of common/network/util/LimitedInputStream partially derives
> from Guava
> Copyright (C) 2007 The Guava Authors
> 5. The Spark modified part (if any, didn't check details) should already
> be covered by the existing notice in NOTICE file
> This product includes software developed at
> The Apache Software Foundation (https://www.apache.org/).
>
> @Mentors:
> Feel free to correct me if you have different ideas
>
> CC @Justin here for easier follow-up (and thanks for the careful review,
> Justin!)
>
> Best Regards,
> Yu
>
> [1] https://www.apache.org/legal/src-headers.html#headers
> [2]
> https://github.com/apache/spark/blob/master/common/network-common/src/main/java/org/apache/spark/network/util/LimitedInputStream.java
> [3]
> https://github.com/google/guava/blob/master/guava/src/com/google/common/io/ByteStreams.java#L706
> [4] https://infra.apache.org/licensing-howto.html#example-notice
>
>
> -- Forwarded message -
> From: Ethan Feng 
> Date: Sat, 28 Jan 2023 at 10:39
> Subject: Re: [VOTE] Release Apache Celeborn(Incubating)
> 0.2.0-incubating-rc3
> To: 
>
>
> Hi Justin,
>Thanks for your advice. We'll consult our mentors.
>
>This vote is closed.
>
> Thanks,
> Ethan Feng
>
> Justin Mclean  于2023年1月26日周四 06:29写道：
> >
> > Hi,
> >
> > I suggest you ask you mentors for help on this.
> >
> > >  Thanks for your advice. We’ve checked the spark distribution
> > > package, and we figure out that there is no [3] related notice in
> > > [1][2].
> >
> > You still need to take the relevant parts from that NOTICE file and add
> it to yours. Please see [1] and [2]. This IMO would include the "Apache
> Spark Copyright 2014 and onwards The Apache Software Foundation.” part.
> >
> > > Do we need to add the following text block to notice file in our
> > > source package according to [4]?
> > >
> > >
> “./common/src/main/java/org/apache/celeborn/common/network/util/LimitedInputStream.java
> > > is based on LimitedInputStream.java from Google Guava
> > > Copyright (C) 2007 The Guava Authors”
> >
> > No license information goes in LICENSE not NOTICE, and the Google Guava
> file doesn’t have a NOTICE file that I can see.
> >
> > 

Does ASF have any agreement with docker?

[Jeff Zhang]

Docker desktop is not free any more, I am wondering whether ASF has any
agreement with docker. Or does each apache project need to apply for this
docker open source program separately?

https://www.docker.com/community/open-source/application/


-- 
Best Regards

Jeff Zhang

Re: [VOTE] Release Apache HugeGraph(Incubating) 1.0.0

[Justin Mclean]

Hi,

> I'm a little confused about the license process;
> 1. If the license header of the third-party code contains Copyright, can it 
> be kept in our code, or should it be removed and only declared in the NOTICE 
> file

The 3rd party header has to be keep in your code and not removed. Copyright 
notices are only relocated if they are donated to the ASF as part of a software 
grant.

> 2. If a large class/file refers to a small piece of code (or subclass), how 
> to choose to cancel the license header, can both be kept, or should only one 
> be selected

> 3. A subclass is a third-party code reference, can its license header be 
> placed on the subclass name, or must it be placed in the entire file to open 
> (if so, how to indicate which part is referenced)

I’m not sure what you are asking, but if you copy any 3rd party code you should 
also keep the header, and not change it even if you make modifications to the 
code.

Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache DevLake (Incubating) v0.15.0-rc4

[Felix Cheung]

As I understand you can release under the WIP disclaimer


On Mon, Jan 30, 2023 at 12:31 AM Zikuan An  wrote:

> Thanks for your valuable suggestion.
>
> I will revisit the whole process and re-open the vote after fixing the
> issues you mentioned.
>
>
> Best,
>
> Zikuan An
>
> Justin Mclean  于2023年1月19日周四 16:25写道：
>
> > Hi,
> >
> > Because it contains a restriction of use clause e.g. "This license does
> > not include the right to compile assets, vectors or images from
> ManyPixels
> > to replicate a similar or competing service, in any form or distribute
> the
> > assets in packs or otherwise. This extends to automated and non-automated
> > ways to link, embed.” It would be best to ask on legal discuss about
> this.
> >
> > For instance this license has been considered Category X. [1]
> >
> > Kind Regards,
> > Justin
> >
> > 1. https://www.pexels.com/license/
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [QUESTION] How do Java-based projects handle Hibernate?

[Romain Manni-Bucau]

Hi Jason,

AFAIK it is ok to use it in tests while you don't reference it explicitly
in your code (which means delivering it or implementing its SPI/classes and
you don't let it be transitive in any assembly somehow) so would mean ok to
use in test while you stay under JPA API.
So it would be more JPA for the code, OpenJPA/Hibernate in tests and
OpenJPA for the runtime until you download it at runtime (like Karaf
features can do for ex).

Regards,
Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le lun. 30 janv. 2023 à 20:01, Jason Porter  a
écrit :

> Question for the group, since I have seen things that seem contradictory.
> How do projects handle Hibernate since it's LGPL and as such, a Category X
> dependency?
>
> It seems like simply using the library is fine. However, then you see
> things about "linking" to the library, does simply using the classes and
> the imports mean it's included in the source?
>
> Is that allowed if we're using JPA and OpenJPA for the classes and
> Hibernate for the implementation?
>
> Along the same lines, what about test libraries?
>
> Jason Porter
> Software Engineer
> He/Him/His
>
> IBM
>
>

[QUESTION] How do Java-based projects handle Hibernate?

[Jason Porter]

Question for the group, since I have seen things that seem contradictory. How 
do projects handle Hibernate since it's LGPL and as such, a Category X 
dependency?

It seems like simply using the library is fine. However, then you see things 
about "linking" to the library, does simply using the classes and the imports 
mean it's included in the source?

Is that allowed if we're using JPA and OpenJPA for the classes and Hibernate 
for the implementation?

Along the same lines, what about test libraries?

Jason Porter
Software Engineer
He/Him/His

IBM

Re: [VOTE] Release Apache HugeGraph(Incubating) 1.0.0

[Yan Zhang]

Hi,
there are some example:
1. Contains Copyright: 
https://github.com/apache/incubator-hugegraph/pull/2100/files#diff-4b9f512f829374901fd2d6e736770a6bd4652b35730c63745f7547b4b32a
2. Both are apache licenses, but the format is different. Do we want to keep 
the license of the other party and whether we need to declare it in the notice： 
https://github.com/apache/incubator-hugegraph/pull/2100/files#diff-1310571ebbb0bf7126d8f2dab4c170c06fd7ab341c6b498413a83fcb74db6470


On 2023/01/30 18:01:22 Yan Zhang wrote:
> Hi,
> I'm a little confused about the license process;
> 1. If the license header of the third-party code contains Copyright, can it 
> be kept in our code, or should it be removed and only declared in the NOTICE 
> file
> 2. If a large class/file refers to a small piece of code (or subclass), how 
> to choose to cancel the license header, can both be kept, or should only one 
> be selected
> 3. A subclass is a third-party code reference, can its license header be 
> placed on the subclass name, or must it be placed in the entire file to open 
> (if so, how to indicate which part is referenced)
> 
> On 2023/01/10 13:36:43 Willem Jiang wrote:
> > -1（binding）
> > 
> > There are some License header issues that need to be fixed.
> > 1. The License header of the Java source files has the wrong copyright
> > declaration.
> > We can put this copyright information into the NOTICE file[1]
> > 2. The copyright time is not right.  We may need to consider the end
> > time HugeGraph was donated to ASF.  such as "Copyright 2017-2021
> > HugeGraph Authors"
> > 3. We cannot put the ASF License header to the swagger-ui files in the
> > hugegraph-dist/src/assembly/static/swagger-ui/, as these files are
> > generated.
> > If we can generate these during the compile time, it could save us
> > some effort.
> > 4. "It is important to keep NOTICE as brief and simple as possible, as
> > each addition places a burden on downstream consumers.
> > Do not add anything to NOTICE which is not legally required."[2][3]
> > 
> > 
> > [1]https://www.apache.org/legal/src-headers.html#headers
> > [2]https://infra.apache.org/licensing-howto.html#mod-notice
> > [3]https://www.apache.org/legal/src-headers.html#notice
> > 
> > 
> > 
> > Willem Jiang
> > 
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> > 
> > On Sun, Jan 8, 2023 at 11:19 PM Imba Jin  wrote:
> > >
> > > Hello Incubator Community,
> > >
> > > This is a call for a vote to release Apache HugeGraph(Incubating) version 
> > > 1.0.0
> > >
> > > The Apache HugeGraph community has voted on and approved a proposal to 
> > > release
> > > Apache HugeGraph(Incubating) version 1.0.0
> > >
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > > HugeGraph community vote thread:
> > >   • https://lists.apache.org/thread/vsc9gh3obhwzgvj9v36g26w006xr2vjv
> > >
> > > Vote result thread:
> > >   • https://lists.apache.org/thread/9brtvd0l2q9ow83dmvpl3g3kngo7cggz
> > >
> > > The release candidate:
> > >   • https://dist.apache.org/repos/dist/dev/incubator/hugegraph/1.0.0
> > >
> > > Git tag for the release:
> > >   • https://github.com/apache/incubator-hugegraph/tree/1.0.0
> > >   • https://github.com/apache/incubator-hugegraph-toolchain/tree/1.0.0
> > >   • https://github.com/apache/incubator-hugegraph-computer/tree/1.0.0
> > >   • https://github.com/apache/incubator-hugegraph-commons/tree/1.0.0
> > >
> > > Release notes:
> > >   • 
> > > https://hugegraph.apache.org/docs/changelog/hugegraph-1.0.0-release-notes/
> > >
> > > Due to this is the first release version, we have 3 people to participate 
> > > in it.
> > >
> > > The GPG user ID(s): Imba Jin, vaughn, coderzc, corresponding to
> > >  j...@apache.org, vau...@apache.org, zhaoc...@apache.org
> > >
> > > that can be found in public keys file:
> > >   • https://downloads.apache.org/incubator/hugegraph/KEYS
> > >
> > > The vote will be open for at least 72 hours or until necessary number
> > > of votes are reached.
> > >
> > > Please vote accordingly:
> > >   [ ] +1 approve
> > >   [ ] +0 no opinion
> > >   [ ] -1 disapprove with the reason
> > >
> > > More detail checklist  please refer:
> > > • 
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > >
> > > Steps to validate the release，Please refer to:
> > > • 
> > > https://hugegraph.apache.org/docs/contribution-guidelines/validate-release/
> > > (EN)
> > > • 
> > > https://hugegraph.apache.org/cn/docs/contribution-guidelines/validate-release/
> > > (CN)
> > >
> > >
> > > Thanks,
> > > On behalf of Apache HugeGraph(Incubating) community
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > 
> > -
> > To unsubscribe, e-mail: 

Re: [VOTE] Release Apache HugeGraph(Incubating) 1.0.0

[Yan Zhang]

Hi,
I'm a little confused about the license process;
1. If the license header of the third-party code contains Copyright, can it be 
kept in our code, or should it be removed and only declared in the NOTICE file
2. If a large class/file refers to a small piece of code (or subclass), how to 
choose to cancel the license header, can both be kept, or should only one be 
selected
3. A subclass is a third-party code reference, can its license header be placed 
on the subclass name, or must it be placed in the entire file to open (if so, 
how to indicate which part is referenced)

On 2023/01/10 13:36:43 Willem Jiang wrote:
> -1（binding）
> 
> There are some License header issues that need to be fixed.
> 1. The License header of the Java source files has the wrong copyright
> declaration.
> We can put this copyright information into the NOTICE file[1]
> 2. The copyright time is not right.  We may need to consider the end
> time HugeGraph was donated to ASF.  such as "Copyright 2017-2021
> HugeGraph Authors"
> 3. We cannot put the ASF License header to the swagger-ui files in the
> hugegraph-dist/src/assembly/static/swagger-ui/, as these files are
> generated.
> If we can generate these during the compile time, it could save us
> some effort.
> 4. "It is important to keep NOTICE as brief and simple as possible, as
> each addition places a burden on downstream consumers.
> Do not add anything to NOTICE which is not legally required."[2][3]
> 
> 
> [1]https://www.apache.org/legal/src-headers.html#headers
> [2]https://infra.apache.org/licensing-howto.html#mod-notice
> [3]https://www.apache.org/legal/src-headers.html#notice
> 
> 
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> On Sun, Jan 8, 2023 at 11:19 PM Imba Jin  wrote:
> >
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache HugeGraph(Incubating) version 
> > 1.0.0
> >
> > The Apache HugeGraph community has voted on and approved a proposal to 
> > release
> > Apache HugeGraph(Incubating) version 1.0.0
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > HugeGraph community vote thread:
> >   • https://lists.apache.org/thread/vsc9gh3obhwzgvj9v36g26w006xr2vjv
> >
> > Vote result thread:
> >   • https://lists.apache.org/thread/9brtvd0l2q9ow83dmvpl3g3kngo7cggz
> >
> > The release candidate:
> >   • https://dist.apache.org/repos/dist/dev/incubator/hugegraph/1.0.0
> >
> > Git tag for the release:
> >   • https://github.com/apache/incubator-hugegraph/tree/1.0.0
> >   • https://github.com/apache/incubator-hugegraph-toolchain/tree/1.0.0
> >   • https://github.com/apache/incubator-hugegraph-computer/tree/1.0.0
> >   • https://github.com/apache/incubator-hugegraph-commons/tree/1.0.0
> >
> > Release notes:
> >   • 
> > https://hugegraph.apache.org/docs/changelog/hugegraph-1.0.0-release-notes/
> >
> > Due to this is the first release version, we have 3 people to participate 
> > in it.
> >
> > The GPG user ID(s): Imba Jin, vaughn, coderzc, corresponding to
> >  j...@apache.org, vau...@apache.org, zhaoc...@apache.org
> >
> > that can be found in public keys file:
> >   • https://downloads.apache.org/incubator/hugegraph/KEYS
> >
> > The vote will be open for at least 72 hours or until necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove with the reason
> >
> > More detail checklist  please refer:
> > • 
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Steps to validate the release，Please refer to:
> > • 
> > https://hugegraph.apache.org/docs/contribution-guidelines/validate-release/
> > (EN)
> > • 
> > https://hugegraph.apache.org/cn/docs/contribution-guidelines/validate-release/
> > (CN)
> >
> >
> > Thanks,
> > On behalf of Apache HugeGraph(Incubating) community
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache EventMesh (incubating) 1.8.0-rc2

[heng du]

+1，I checked：

 [√] Download links are valid.
 [√] DISCLAIMER is included.
 [√] Source code artifacts have correct names matching the current release.
 [√] LICENSE and NOTICE files are correct for each EventMesh repo.
 [√] All files have license headers if necessary.


vnbear  于2023年1月30日周一 11:13写道：

> +1, I have checked:
>
>
> [√] Download links are valid.
> [√] Checksums and PGP signatures are valid.
> [√] DISCLAIMER is included.
> [√] Source code artifacts have correct names matching the current release.
> [√] LICENSE and NOTICE files are correct for each EventMesh repo.
> [√] All files have license headers if necessary.
> [√] No compiled archives bundled in source archive.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> At 2023-01-30 11:05:25, "杨军"  wrote:
> >+1, I have checked:
> >
> >
> >[√] Download links are valid.
> >[√] Checksums and PGP signatures are valid.
> >[√] DISCLAIMER is included.
> >[√] Source code artifacts have correct names matching the current
> release.
> >[√] LICENSE and NOTICE files are correct for each EventMesh repo.
> >[√] All files have license headers if necessary.
> >[√] No compiled archives bundled in source archive.
> >
> >发自我的 iPhone
> >
> >> 在 2023年1月29日，16:08，walterzywei  写道：
> >>
> >> Thank you all for your check and vote , and I also want to carry over
> >> the vote by Justin Mclean and Francois Fpapon from dev, so I would
> >> like to send the result later.
> >>
> >> Thanks,
> >> Your EventMesh Release Manager
> >>
> >> Alex Luo  于2023年1月28日周六 23:02写道：
> >>>
> >>> +1, I have checked:
> >>>
> >>>
> >>> [√] Download links are valid.
> >>> [√] Checksums and PGP signatures are valid.
> >>> [√] DISCLAIMER is included.
> >>> [√] Source code artifacts have correct names matching the current
> release.
> >>> [√] LICENSE and NOTICE files are correct for each EventMesh repo.
> >>> [√] All files have license headers if necessary.
> >>> [√] No compiled archives bundled in source archive.
> >>>
> >>> Alex
> >>>
>  On 2023/01/28 14:32:53 Mengyang Tang wrote:
>  +1, I have checked:
> 
> 
>  [√] Download links are valid. [√] Checksums and PGP signatures are
> valid. [√] DISCLAIMER is included. [√] Source code artifacts have correct
> names matching the current release. [√] LICENSE and NOTICE files are
> correct for each EventMesh repo. [√] All files have license headers if
> necessary. [√] No compiled archives bundled in source archive.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  At 2023-01-18 20:23:00, "walterzywei"  wrote:
> > Hello Incubator Community,
> >
> >   This is a call for a vote to release Apache EventMesh(Incubating)
> > version 1.8.0-rc2
> >
> >   The Apache EventMesh community has voted on and approved a
> > proposal to release
> >   Apache EventMesh(Incubating) version 1.8.0-rc2
> >
> >   We now kindly request the Incubator PMC members review and vote on
> this
> >   incubator release.
> >
> >   EventMesh community vote thread:
> >   • https://lists.apache.org/thread/z6p2kxw2l1zv641fsx4bhjgtmdh4xwyg
> >
> >   Vote result thread:
> >   • https://lists.apache.org/thread/16js8nnlbypy203snxk2fqzt3vjz1yg5
> >
> >   The release candidate:
> >   •
> https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.8.0-rc2
> >
> >   Git tag for the release:
> >   • https://github.com/apache/incubator-eventmesh/tree/v1.8.0-rc2
> >   Release notes:
> >   • https://eventmesh.apache.org/events/release-notes/v1.8.0
> >
> >   The artifacts signed with PGP key
> > 16D5190EA34AC32AE3CE05A753FF44C181774D3F, corresponding to
> > walterzy...@apache.org, that can be found in keys file:
> >   • https://downloads.apache.org/incubator/eventmesh/KEYS
> >
> >   The vote will be open for at least 72 hours or until necessary
> > number of votes are reached.
> >
> >   Please vote accordingly:
> >
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove with the reason
> >
> > Thanks,
> > On behalf of Apache EventMesh(Incubating) community
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> 
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@eventmesh.apache.org
> >>> For additional commands, e-mail: dev-h...@eventmesh.apache.org
> >>>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >
> >-
> >To unsubscribe, e-mail: 

Re: [VOTE] Release Apache HugeGraph(Incubating) 1.0.0

[Imba Jin]

Thanks for the reply, we choose the "loose license" in the multiple choices, 
and now we only keep one (selected) license instead of list them all in 
'LICENSE' file.

Could you help us to review the correctness of the latest update?[1] After 
confirmation, we will modify all other repos soon

1. https://github.com/apache/incubator-hugegraph/pull/2099/files

On 2023/01/24 02:46:12 Justin Mclean wrote:
> HI,
> 
> > Thanks for your suggestion, we are working on the issues you mentioned, but 
> > we did't found the gpl and cc license in hugegraph repositories, could you 
> > please tell us where it was found and how to find it, thanks a lot.
> 
> It's mentioned in your LICENSE files for instance [1]. Not that in this case 
> it is Dual licensed and you should select which license applies. Hint don’t 
> pick the GPL one.
> 
> Kind Regards,
> Justin
> 
> 1. 
> https://github.com/apache/incubator-hugegraph/blob/8047fe7d9e62ae1125bc566726cbb9c6afd52d74/hugegraph-dist/release-docs/licenses/LICENSE-javax.json.txt
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [QUESTION] do pom files need to have a license header

[Jean-Baptiste Onofré]

Hi,

It's a better to have ASF header in all files where it's possible.
However, it's sometime difficult (test static files, web content, ..).
So if you can, it's better Pekko community fixes it.

Thanks,
Regards
JB

On Sun, Jan 29, 2023 at 6:31 PM PJ Fanning  wrote:
>
> Hi everyone,
>
> The Apache Pekko builds use the sbt tool for building and this generates pom 
> files for us. They do not include any headers (example [1]).
> It seems the norm to add an XML comment with Apache License info (example 
> from log4j [2]).
> Does the Pekko team need to fix this or is it just a nicety to have the 
> license header in the pom files? If the answer is that we do need to fix 
> this, does this also apply to other published files? sbt generates and 
> publishes a 'buildinfo' file as part of the maven publish (example [2]).
>
> Regards,
> PJ
>
>
> [1] 
> https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.pom
> [2] 
> https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-api/2.19.0/log4j-api-2.19.0.pom
> [3] 
> https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.buildinfo
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[CANCEL][VOTE] Release Apache DevLake (Incubating) v0.15.0-rc4

[Zikuan An]

Hello everyone,



I'm cancelling this vote


https://lists.apache.org/thread/jysnc4q3z99x4bwjf7ztm06zhh35ob4x


due to licenses issues. I'll fix them and start a new vote process.



Thanks a lot for all your help.



Best,

Zikuan An

Re: [VOTE] Release Apache DevLake (Incubating) v0.15.0-rc4

[Zikuan An]

Thanks for your valuable suggestion.

I will revisit the whole process and re-open the vote after fixing the
issues you mentioned.


Best,

Zikuan An

Justin Mclean  于2023年1月19日周四 16:25写道：

> Hi,
>
> Because it contains a restriction of use clause e.g. "This license does
> not include the right to compile assets, vectors or images from ManyPixels
> to replicate a similar or competing service, in any form or distribute the
> assets in packs or otherwise. This extends to automated and non-automated
> ways to link, embed.” It would be best to ask on legal discuss about this.
>
> For instance this license has been considered Category X. [1]
>
> Kind Regards,
> Justin
>
> 1. https://www.pexels.com/license/
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>