Re: [VOTE] Release Apache Seata (Incubating) 2.3.0-RC4
Hi PJ, Thanks for your careful review. As you've seen, these files were indeed copied from a third party, and we've mentioned that in the comments.The related code is mainly about extracting properties from JavaScript objects and a couple of lines for concatenating log format strings.Given the simplicity and general nature of the code, along with future maintenance considerations, we decided to refactor these parts instead of adding them to the license. Warm regards, Ji Min PJ Fanning 于2025年3月11日周二 17:56写道： > > Ok. I have the commit now. > > https://github.com/apache/incubator-seata/commit/d2f3554a656aa84ae423cf6cf84aa214fc8c#diff-724497593d9df5966fe458e68a556e9c715fc69dce406b93acf7b3858d020976 > > This seems like a minor rewrite that does exactly the same thing. > Since the code is simple enough, I guess it is hard to completely > rewrite it. > > I will retract my -1. > > > On Tue, 11 Mar 2025 at 10:49, PJ Fanning wrote: > > > > This is a vote on the tar.gz that you supplied. I cannot find the > > license change in apache-seata-2.3.0-incubating-src.tar.gz that > > relates to ExtendedWhitespaceThrowableProxyConverter. > > > > On Tue, 11 Mar 2025 at 07:08, Min Ji wrote: > > > > > > Hi PJ, > > > > > > PJ Fanning 于2025年3月11日周二 03:00写道： > > > > > > > > https://github.com/apache/incubator-seata/blob/151ea4f6757fab260ea21227ab793e0cdeee2d92/server/src/main/java/org/apache/seata/server/logging/logback/ExtendedWhitespaceThrowableProxyConverter.java#L28 > > > > > > > > This file has an invalid source header. Since the source file was > > > > copied from spring-boot, it should retain the header from the > > > > spring-boot file. > > > > > > > > The key thing missing is the copyright. > > > > > > > > https://github.com/spring-projects/spring-boot/blob/b6bccc13789224e80328057506c31b9d2dee9026/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/logging/logback/ExtendedWhitespaceThrowableProxyConverter.java#L2 > > > > > > > > -1 (binding) because the LICENSE change was not made to mention > > > > ExtendedWhitespaceThrowableProxyConverter and the fact that it comes > > > > from spring-boot. > > > > > > Jean-Baptiste already pointed out this issue during the 2.3.0-RC3 > > > voting process [1]. As a result, we canceled the RC3 vote, refactored > > > the relevant code, and initiated the 2.3.0-RC4 voting thread. The > > > files that were flagged have been updated in the new commit. So, I > > > think we should check using the commit ID > > > `0ad2847465fa877a2c65ea84ed43f5b0984c3ce9` mentioned in the voting > > > email. I've verified that the source code on GitHub and what's > > > submitted to SVN has been updated [2][3]. > > > > > > [1]. https://lists.apache.org/thread/wbq6jsykj2cd9nn91ys1b8r99bfl1h2r > > > [2]. > > > https://github.com/apache/incubator-seata/tree/0ad2847465fa877a2c65ea84ed43f5b0984c3ce9/server/src/main/java/org/apache/seata/server/logging/logback > > > [3]. > > > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata/2.3.0-RC4/apache-seata-2.3.0-incubating-src.tar.gz > > > > > > > > > > > > > > On 2025/03/10 06:18:52 yixia wrote: > > > > > Hello, > > > > > > > > > > This is a call for vote to release Apache Seata(incubating) 2.3.0-RC4. > > > > > > > > > > > > > > > The vote thread: > > > > > > > > > > https://lists.apache.org/thread/gfvr1rjh9zgfpbbcow0bmbqpg8ngq9wk > > > > > > > > > > > > > > > Vote Result: > > > > > > > > > > https://lists.apache.org/thread/yc16ch0s99yfvhb7xvvw6d0gmjdh0r1j > > > > > > > > > > > > > > > The release candidates: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata/2.3.0-RC4/ > > > > > > > > > > > > > > > The staging repo: > > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheseata-1137/ > > > > > > > > > > > > > > > Git tag for the release: > > > > > > > > > > https://github.com/apache/incubator-seata/releases/tag/v2.3.0 > > > > > > > > > > > > > > > Git commit id for the release: > > > > > > > > > > https://github.com/apache/incubator-seata/commit/0ad2847465fa877a2c65ea84ed43f5b0984c3ce9 > > > > > > > > > > > > > > > Release Notes: > > > > > > > > > > https://github.com/apache/incubator-seata/releases/tag/v2.3.0 > > > > > > > > > > > > > > > The artifacts have been signed with Key [ 7ACD1A52F5AEF76A ], > > > > > corresponding > > > > > to[ yi...@apache.org ] > > > > > > > > > > which can be found in the keys file: > > > > > > > > > > https://downloads.apache.org/incubator/seata/KEYS > > > > > > > > > > > > > > > Build Environment: JDK 8+, Apache Maven 3.6.0+. > > > > > > > > > >- > > > > > > > > > >osx_aarch64： ./mvnw clean package -DskipTests=true -Parrch64 > > > > >- > > > > > > > > > >osx-x86_64/other: ./mvnw clean package -DskipTests=true > > > > > > > > > > > > > > > CI Test Workflow: > > > > > > > > > > https://github.com/apache/incubator-seata/actions/runs/13435379453/job/37579216082 > > > > > > > > > > > > > > > The vote will be open
Re: [VOTE] Release Apache Seata-go(incubating) SDK 2.0.0-RC1
Hi PJ, I will close this vote and then launch a new voting email. I'm sorry for causing trouble for everyone. On 2025/03/10 20:07:21 PJ Fanning wrote: > Is this vote open or not? This thread looks valid to me. There was a previous > thread that had the wrong email subject. > > On 2025/03/08 04:40:44 Yuecai Liu wrote: > > The content of this email is wrong. I will launch a new voting email. I'm > > sorry for causing trouble for everyone. > > > > On 2025/03/07 00:31:22 "luky...@apache.org" wrote: > > > Hello, > > > This is the first release of Apache Seata-go(incubating) SDK. > > > > > > > > > The vote thread: > > > https://lists.apache.org/thread/6yym26plkrf4ld6s0bf9zts5wwwg0gtq > > > > > > > > > Vote Result: > > > https://lists.apache.org/thread/ko9hf9t9wp14wzgoxcks5cyglg68jrpb > > > > > > > > > The release candidates: > > > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata-go/2.0.0-RC1/ > > > > > > > > > Git tag for the release: > > > https://github.com/apache/incubator-seata-go/tree/v2.0.0 > > > > > > > > > Git commit id for the release: > > > https://github.com/apache/incubator-seata-go/commit/cf2212a41550649b5b32dc029a608d3746f5de3a > > > > > > > > > Release Notes: > > > https://github.com/apache/incubator-seata-go/releases/tag/v2.0.0 > > > > > > > > > The artifacts have been signed with Key [ A2EF5873 ], corresponding to > > > [ luky...@apache.org ] > > > which can be found in the keys file: > > > https://downloads.apache.org/incubator/seata/KEYS > > > > > > > > > Build Environment: Golang 1.20+. > > > Build Command: make build > > > > > > > > > CI Test Workflow: > > > > > > > > > https://github.com/apache/incubator-seata-go/actions/runs/12517972078/job/34919641932 > > > https://github.com/apache/incubator-seata-go/actions/runs/12517972075/job/34919641931 > > > > > > > > > The vote will be open for at least 72 hours. > > > > > > > > > Please vote accordingly: > > > > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > > > > Checklist for reference: > > > [ ] Download links are valid. > > > [ ] Checksums and signatures. > > > [ ] LICENSE/NOTICE files exist > > > [ ] No unexpected binary files > > > [ ] All source files have ASF headers > > > [ ] Can compile from source > > > > > > > > > To learn more about Apache Seata , please see https://seata.apache.org/ > > > > > > > > > Warm regards, > > > Yuecai Liu > > > - > > > 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 > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Seata (Incubating) 2.3.0-RC4
This is a vote on the tar.gz that you supplied. I cannot find the license change in apache-seata-2.3.0-incubating-src.tar.gz that relates to ExtendedWhitespaceThrowableProxyConverter. On Tue, 11 Mar 2025 at 07:08, Min Ji wrote: > > Hi PJ, > > PJ Fanning 于2025年3月11日周二 03:00写道： > > > > https://github.com/apache/incubator-seata/blob/151ea4f6757fab260ea21227ab793e0cdeee2d92/server/src/main/java/org/apache/seata/server/logging/logback/ExtendedWhitespaceThrowableProxyConverter.java#L28 > > > > This file has an invalid source header. Since the source file was copied > > from spring-boot, it should retain the header from the spring-boot file. > > > > The key thing missing is the copyright. > > > > https://github.com/spring-projects/spring-boot/blob/b6bccc13789224e80328057506c31b9d2dee9026/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/logging/logback/ExtendedWhitespaceThrowableProxyConverter.java#L2 > > > > -1 (binding) because the LICENSE change was not made to mention > > ExtendedWhitespaceThrowableProxyConverter and the fact that it comes from > > spring-boot. > > Jean-Baptiste already pointed out this issue during the 2.3.0-RC3 > voting process [1]. As a result, we canceled the RC3 vote, refactored > the relevant code, and initiated the 2.3.0-RC4 voting thread. The > files that were flagged have been updated in the new commit. So, I > think we should check using the commit ID > `0ad2847465fa877a2c65ea84ed43f5b0984c3ce9` mentioned in the voting > email. I've verified that the source code on GitHub and what's > submitted to SVN has been updated [2][3]. > > [1]. https://lists.apache.org/thread/wbq6jsykj2cd9nn91ys1b8r99bfl1h2r > [2]. > https://github.com/apache/incubator-seata/tree/0ad2847465fa877a2c65ea84ed43f5b0984c3ce9/server/src/main/java/org/apache/seata/server/logging/logback > [3]. > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata/2.3.0-RC4/apache-seata-2.3.0-incubating-src.tar.gz > > > > > > On 2025/03/10 06:18:52 yixia wrote: > > > Hello, > > > > > > This is a call for vote to release Apache Seata(incubating) 2.3.0-RC4. > > > > > > > > > The vote thread: > > > > > > https://lists.apache.org/thread/gfvr1rjh9zgfpbbcow0bmbqpg8ngq9wk > > > > > > > > > Vote Result: > > > > > > https://lists.apache.org/thread/yc16ch0s99yfvhb7xvvw6d0gmjdh0r1j > > > > > > > > > The release candidates: > > > > > > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata/2.3.0-RC4/ > > > > > > > > > The staging repo: > > > > > > https://repository.apache.org/content/repositories/orgapacheseata-1137/ > > > > > > > > > Git tag for the release: > > > > > > https://github.com/apache/incubator-seata/releases/tag/v2.3.0 > > > > > > > > > Git commit id for the release: > > > > > > https://github.com/apache/incubator-seata/commit/0ad2847465fa877a2c65ea84ed43f5b0984c3ce9 > > > > > > > > > Release Notes: > > > > > > https://github.com/apache/incubator-seata/releases/tag/v2.3.0 > > > > > > > > > The artifacts have been signed with Key [ 7ACD1A52F5AEF76A ], > > > corresponding > > > to[ yi...@apache.org ] > > > > > > which can be found in the keys file: > > > > > > https://downloads.apache.org/incubator/seata/KEYS > > > > > > > > > Build Environment: JDK 8+, Apache Maven 3.6.0+. > > > > > >- > > > > > >osx_aarch64： ./mvnw clean package -DskipTests=true -Parrch64 > > >- > > > > > >osx-x86_64/other: ./mvnw clean package -DskipTests=true > > > > > > > > > CI Test Workflow: > > > > > > https://github.com/apache/incubator-seata/actions/runs/13435379453/job/37579216082 > > > > > > > > > The vote will be open for at least 72 hours. > > > > > > Please vote accordingly: > > > > > > [ ] +1 approve > > > > > > [ ] +0 no opinion > > > > > > [ ] -1 disapprove with the reason > > > > > > > > > Checklist for reference: > > > > > > [ ] Download links are valid. > > > > > > [ ] Checksums and signatures. > > > > > > [ ] LICENSE/NOTICE files exist > > > > > > [ ] No unexpected binary files > > > > > > [ ] All source files have ASF headers > > > > > > [ ] Can compile from source > > > > > > > > > To learn more about Apache Seata , please see https://seata.apache.org/ > > > > > > > > > Warm regards, > > > > > > Te Wang > > > > > > > - > > 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: OpenClovis SAFplus-Availability-Scalability-Platform would like to join Apache Incubator
Hi PJ, The proposal is ready for review. This is the link: https://docs.google.com/document/d/1f1AJ18xjIoGw40lWGaWVf1AgPrcwYHlDiu4Agj7UV0E/edit?usp=sharing I'd like your help with the review. Thanks. Regards, Hung On Thu, Mar 6, 2025 at 8:24 PM PJ Fanning wrote: > Hi Hung, > > The next step would be to put together a proposal. > > An example is: > https://cwiki.apache.org/confluence/display/INCUBATOR/Iggy+Proposal > > The are other proposals in: > https://cwiki.apache.org/confluence/display/INCUBATOR/Proposals > > The format is a set format. > > I can act as champion. > > If you create a proposal in Google Docs or some other shared document, > then I help review it when it is ready. > > Regards, > PJ > > On Thu, 6 Mar 2025 at 04:00, Hung Ta wrote: > > > > Hi Justin, > > > > After discussing with our boss, we agree with the Apache license for our > > future versions. > > > > Would you please instruct us to do the next steps? Thanks. > > > > Regards, > > Hung > > > > On Tue, Feb 25, 2025 at 10:40 AM Justin Mclean > > > wrote: > > > > > Hi, > > > > > > >> 2. The license will need to change after you become an ASF project > but > > > you > > > >> also won't be able to use any GPL licensed libraries in the project > > > either. > > > >> Have you done an audit of how hard these changes will be? > > > >> > > > > [Hung] Yes, we agree that the license needs to change after we > become an > > > > ASF project. However, can we still keep the current license for our > > > current > > > > or future customers? Is this ok? > > > > > > Only for previous software versions released before you joined the > > > Incubator. All future versions must be Apache licensed. > > > > > > Kind Regards, > > > Justin > > > - > > > 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 Seata (Incubating) 2.3.0-RC4
Ok. I have the commit now. https://github.com/apache/incubator-seata/commit/d2f3554a656aa84ae423cf6cf84aa214fc8c#diff-724497593d9df5966fe458e68a556e9c715fc69dce406b93acf7b3858d020976 This seems like a minor rewrite that does exactly the same thing. Since the code is simple enough, I guess it is hard to completely rewrite it. I will retract my -1. On Tue, 11 Mar 2025 at 10:49, PJ Fanning wrote: > > This is a vote on the tar.gz that you supplied. I cannot find the > license change in apache-seata-2.3.0-incubating-src.tar.gz that > relates to ExtendedWhitespaceThrowableProxyConverter. > > On Tue, 11 Mar 2025 at 07:08, Min Ji wrote: > > > > Hi PJ, > > > > PJ Fanning 于2025年3月11日周二 03:00写道： > > > > > > https://github.com/apache/incubator-seata/blob/151ea4f6757fab260ea21227ab793e0cdeee2d92/server/src/main/java/org/apache/seata/server/logging/logback/ExtendedWhitespaceThrowableProxyConverter.java#L28 > > > > > > This file has an invalid source header. Since the source file was copied > > > from spring-boot, it should retain the header from the spring-boot file. > > > > > > The key thing missing is the copyright. > > > > > > https://github.com/spring-projects/spring-boot/blob/b6bccc13789224e80328057506c31b9d2dee9026/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/logging/logback/ExtendedWhitespaceThrowableProxyConverter.java#L2 > > > > > > -1 (binding) because the LICENSE change was not made to mention > > > ExtendedWhitespaceThrowableProxyConverter and the fact that it comes from > > > spring-boot. > > > > Jean-Baptiste already pointed out this issue during the 2.3.0-RC3 > > voting process [1]. As a result, we canceled the RC3 vote, refactored > > the relevant code, and initiated the 2.3.0-RC4 voting thread. The > > files that were flagged have been updated in the new commit. So, I > > think we should check using the commit ID > > `0ad2847465fa877a2c65ea84ed43f5b0984c3ce9` mentioned in the voting > > email. I've verified that the source code on GitHub and what's > > submitted to SVN has been updated [2][3]. > > > > [1]. https://lists.apache.org/thread/wbq6jsykj2cd9nn91ys1b8r99bfl1h2r > > [2]. > > https://github.com/apache/incubator-seata/tree/0ad2847465fa877a2c65ea84ed43f5b0984c3ce9/server/src/main/java/org/apache/seata/server/logging/logback > > [3]. > > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata/2.3.0-RC4/apache-seata-2.3.0-incubating-src.tar.gz > > > > > > > > > > On 2025/03/10 06:18:52 yixia wrote: > > > > Hello, > > > > > > > > This is a call for vote to release Apache Seata(incubating) 2.3.0-RC4. > > > > > > > > > > > > The vote thread: > > > > > > > > https://lists.apache.org/thread/gfvr1rjh9zgfpbbcow0bmbqpg8ngq9wk > > > > > > > > > > > > Vote Result: > > > > > > > > https://lists.apache.org/thread/yc16ch0s99yfvhb7xvvw6d0gmjdh0r1j > > > > > > > > > > > > The release candidates: > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata/2.3.0-RC4/ > > > > > > > > > > > > The staging repo: > > > > > > > > https://repository.apache.org/content/repositories/orgapacheseata-1137/ > > > > > > > > > > > > Git tag for the release: > > > > > > > > https://github.com/apache/incubator-seata/releases/tag/v2.3.0 > > > > > > > > > > > > Git commit id for the release: > > > > > > > > https://github.com/apache/incubator-seata/commit/0ad2847465fa877a2c65ea84ed43f5b0984c3ce9 > > > > > > > > > > > > Release Notes: > > > > > > > > https://github.com/apache/incubator-seata/releases/tag/v2.3.0 > > > > > > > > > > > > The artifacts have been signed with Key [ 7ACD1A52F5AEF76A ], > > > > corresponding > > > > to[ yi...@apache.org ] > > > > > > > > which can be found in the keys file: > > > > > > > > https://downloads.apache.org/incubator/seata/KEYS > > > > > > > > > > > > Build Environment: JDK 8+, Apache Maven 3.6.0+. > > > > > > > >- > > > > > > > >osx_aarch64： ./mvnw clean package -DskipTests=true -Parrch64 > > > >- > > > > > > > >osx-x86_64/other: ./mvnw clean package -DskipTests=true > > > > > > > > > > > > CI Test Workflow: > > > > > > > > https://github.com/apache/incubator-seata/actions/runs/13435379453/job/37579216082 > > > > > > > > > > > > The vote will be open for at least 72 hours. > > > > > > > > Please vote accordingly: > > > > > > > > [ ] +1 approve > > > > > > > > [ ] +0 no opinion > > > > > > > > [ ] -1 disapprove with the reason > > > > > > > > > > > > Checklist for reference: > > > > > > > > [ ] Download links are valid. > > > > > > > > [ ] Checksums and signatures. > > > > > > > > [ ] LICENSE/NOTICE files exist > > > > > > > > [ ] No unexpected binary files > > > > > > > > [ ] All source files have ASF headers > > > > > > > > [ ] Can compile from source > > > > > > > > > > > > To learn more about Apache Seata , please see https://seata.apache.org/ > > > > > > > > > > > > Warm regards, > > > > > > > > Te Wang > > > > > > > > > > - > >
Re: [VOTE] Release Apache Seata (Incubating) 2.1.0-RC5
Hi, The email subject looks a bit off – it doesn't match what's written in the body. Warm regards, Ji Min luky116 于2025年3月7日周五 00:05写道： > > > > Hello, > > This is the first release of Apache Seata-go(incubating) SDK. > > > The vote thread: > https://lists.apache.org/thread/6yym26plkrf4ld6s0bf9zts5wwwg0gtq > > > Vote Result: > https://lists.apache.org/thread/ko9hf9t9wp14wzgoxcks5cyglg68jrpb > > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata-go/2.0.0-RC1/ > > > Git tag for the release: > https://github.com/apache/incubator-seata-go/tree/v2.0.0 > > > Git commit id for the release: > https://github.com/apache/incubator-seata-go/commit/cf2212a41550649b5b32dc029a608d3746f5de3a > > > Release Notes: > https://github.com/apache/incubator-seata-go/releases/tag/v2.0.0 > > > The artifacts have been signed with Key [ A2EF5873 ], corresponding to > [ luky...@apache.org ] > which can be found in the keys file: > https://downloads.apache.org/incubator/seata/KEYS > > > Build Environment: Golang 1.20+. > Build Command: make build. > > > CI Test Workflow: > https://github.com/apache/incubator-seata-go/actions/runs/12517972078/job/34919641932 > https://github.com/apache/incubator-seata-go/actions/runs/12517972075/job/34919641931 > > > The vote will be open for at least 72 hours. > > > Please vote accordingly: > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > > Checklist for reference: > [ ] Download links are valid. > [ ] Checksums and signatures. > [ ] LICENSE/NOTICE files exist > [ ] No unexpected binary files > [ ] All source files have ASF headers > [ ] Can compile from source > > > To learn more about Apache Seata , please see https://seata.apache.org/ > Warm regards, > Yuecai Liu > - > 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
[ANN] Apache Polaris 0.9.0-incubating has been released!
The Apache Polaris podling team is pleased to announce Apache Polaris 0.9.0-incubating release. Apache Polaris (incubating) is an open-source, fully-featured catalog for Apache Iceberg™. It implements Iceberg's REST API, enabling seamless multi-engine interoperability across a wide range of platforms, including Apache Doris™, Apache Flink®, Apache Spark™, Dremio®, StarRocks, and Trino. This release is the first one in the project. It provides source distribution only. You can download the release from there: https://polaris.apache.org/downloads/ The Release Notes are available there: https://github.com/apache/polaris/milestone/1?closed=1 The Polaris community is now focusing on Polaris 1.0.0-incubating release, which will be an important milestone for the podling. Website: https://polaris.apache.org Mailing list: d...@polaris.apache.org -- The Apache Polaris podling team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Seata (Incubating) 2.3.0-RC4
Hello, This is a call for vote to release Apache Seata(incubating) 2.3.0-RC4. The vote thread: https://lists.apache.org/thread/gfvr1rjh9zgfpbbcow0bmbqpg8ngq9wk Vote Result: https://lists.apache.org/thread/yc16ch0s99yfvhb7xvvw6d0gmjdh0r1j The release candidates: https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata/2.3.0-RC4/ The staging repo: https://repository.apache.org/content/repositories/orgapacheseata-1137/ Git tag for the release: https://github.com/apache/incubator-seata/releases/tag/v2.3.0 Git commit id for the release: https://github.com/apache/incubator-seata/commit/0ad2847465fa877a2c65ea84ed43f5b0984c3ce9 Release Notes: https://github.com/apache/incubator-seata/releases/tag/v2.3.0 The artifacts have been signed with Key [ 7ACD1A52F5AEF76A ], corresponding to[ yi...@apache.org ] which can be found in the keys file: https://downloads.apache.org/incubator/seata/KEYS Build Environment: JDK 8+, Apache Maven 3.6.0+. - osx_aarch64： ./mvnw clean package -DskipTests=true -Parrch64 - osx-x86_64/other: ./mvnw clean package -DskipTests=true CI Test Workflow: https://github.com/apache/incubator-seata/actions/runs/13435379453/job/37579216082 The vote will be open for at least 72 hours. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and signatures. [ ] LICENSE/NOTICE files exist [ ] No unexpected binary files [ ] All source files have ASF headers [ ] Can compile from source To learn more about Apache Seata , please see https://seata.apache.org/ Warm regards, Te Wang
Re: [VOTE] Release Apache Seata-go(incubating) SDK 2.0.0-RC1
Is this vote open or not? This thread looks valid to me. There was a previous thread that had the wrong email subject. On 2025/03/08 04:40:44 Yuecai Liu wrote: > The content of this email is wrong. I will launch a new voting email. I'm > sorry for causing trouble for everyone. > > On 2025/03/07 00:31:22 "luky...@apache.org" wrote: > > Hello, > > This is the first release of Apache Seata-go(incubating) SDK. > > > > > > The vote thread: > > https://lists.apache.org/thread/6yym26plkrf4ld6s0bf9zts5wwwg0gtq > > > > > > Vote Result: > > https://lists.apache.org/thread/ko9hf9t9wp14wzgoxcks5cyglg68jrpb > > > > > > The release candidates: > > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata-go/2.0.0-RC1/ > > > > > > Git tag for the release: > > https://github.com/apache/incubator-seata-go/tree/v2.0.0 > > > > > > Git commit id for the release: > > https://github.com/apache/incubator-seata-go/commit/cf2212a41550649b5b32dc029a608d3746f5de3a > > > > > > Release Notes: > > https://github.com/apache/incubator-seata-go/releases/tag/v2.0.0 > > > > > > The artifacts have been signed with Key [ A2EF5873 ], corresponding to > > [ luky...@apache.org ] > > which can be found in the keys file: > > https://downloads.apache.org/incubator/seata/KEYS > > > > > > Build Environment: Golang 1.20+. > > Build Command: make build > > > > > > CI Test Workflow: > > > > > > https://github.com/apache/incubator-seata-go/actions/runs/12517972078/job/34919641932 > > https://github.com/apache/incubator-seata-go/actions/runs/12517972075/job/34919641931 > > > > > > The vote will be open for at least 72 hours. > > > > > > Please vote accordingly: > > > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist > > [ ] No unexpected binary files > > [ ] All source files have ASF headers > > [ ] Can compile from source > > > > > > To learn more about Apache Seata , please see https://seata.apache.org/ > > > > > > Warm regards, > > Yuecai Liu > > - > > 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: [DISCUSS] running a trial where podlings need to have their names reviewed before they join
> On Mar 6, 2025, at 9:20 AM, Niall Pemberton wrote: > > On Thu, 6 Mar 2025 at 14:53, PJ Fanning wrote: > >> Seems best to allow the discussion thread to proceed and if things seem >> ok, then start the name approval step. The vote only happens after the name >> is approved by Brand Management. > > > Does it have to be strict in where it takes place in the process? The main > issue AIUI, is leaving the name search until close to graduation - throwing > away possibly years of building their “brand”. ASAP at the start of > incubation would avoid that issue - but is it a big deal whether it’s just > before being accepted or very soon after? Yes, this has proven to be a serious and expensive issue for a podling recently - in this case Apache Fury was denied. And for another (Apache Hunter now Otava) it is a slow problem as changing resources for Infra is not automatic and we get into a series of back and forth to test that every resource has been properly adjusted. It really is a problem. I think that it is now important enough that the Champion should be responsible for this. If a prospective project really loves their name and yet they cannot use it at the ASF then it’s only fair to have that happen before spending years in the Incubator. The old policy wasn’t so bad 15 years ago when Incubation time was shorter and resources were less. Best, Dave > > Niall > > > On 2025/03/06 14:45:45 Calvin Kirs wrote: >>> If the Brand team has no objections, then I’m absolutely +1. >>> >>> But procedurally, should this happen after the discussion and before the >>> vote? >>> >>> On Thu, Mar 6, 2025 at 10:32 PM PJ Fanning wrote: >>> Hi everyone, This has been discussed on the private mailing list and ASF members can view the main discussion here [1]. Mark Thomas, VP of Brand Management, has suggested a willingness to do the Podling Name Search at the start of the onboarding process. Can I suggest that we trial out having the Champions for new podlings submit the Podling Name approval application before we commence the vote for new podlings? The main advantage of the early name check is that it is less disruptive for podling name changes when the podling resources have not yet been set up and announcements and PR has not yet been done. We have a few applications in the early stages. We can try the process change out for a few months and discuss making it a permanent change to the process at that point? Discussion is welcome but let's not discuss specific cases on this >> public forum. Thanks, PJ [1] https://lists.apache.org/thread/y94f70sfzf2d959k6kl1bkbhmkklk260 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> -- >>> Best wishes！ >>> CalvinKirs >>> >> >> - >> 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: [ANN] Apache Polaris 0.9.0-incubating has been released!
Congrats! Thank JB and everyone! Yufei On Tue, Mar 11, 2025 at 10:15 AM Jean-Baptiste Onofré wrote: > The Apache Polaris podling team is pleased to announce Apache Polaris > 0.9.0-incubating release. > > Apache Polaris (incubating) is an open-source, fully-featured catalog > for Apache Iceberg™. It implements Iceberg's REST API, enabling > seamless multi-engine interoperability across a wide range of > platforms, including Apache Doris™, Apache Flink®, Apache Spark™, > Dremio®, StarRocks, and Trino. > > This release is the first one in the project. It provides source > distribution only. > > You can download the release from there: > https://polaris.apache.org/downloads/ > > The Release Notes are available there: > https://github.com/apache/polaris/milestone/1?closed=1 > > The Polaris community is now focusing on Polaris 1.0.0-incubating > release, which will be an important milestone for the podling. > > Website: https://polaris.apache.org > Mailing list: d...@polaris.apache.org > > -- > The Apache Polaris podling team >
Re: [VOTE] Release Apache Seata (Incubating) 2.3.0-RC4
+1 binding (fanningpj IPMC) * Download links are valid. * Incubating in name * Checksums and signatures. * LICENSE/NOTICE/DISCLAIMER files exist * No unexpected binary files * Source files have ASF headers * Can compile from source On 2025/03/11 12:56:51 Min Ji wrote: > Hi PJ, > > Thanks for your careful review. As you've seen, these files were > indeed copied from a third party, and we've mentioned that in the > comments.The related code is mainly about extracting properties from > JavaScript objects and a couple of lines for concatenating log format > strings.Given the simplicity and general nature of the code, along > with future maintenance considerations, we decided to refactor these > parts instead of adding them to the license. > > > Warm regards, > > Ji Min > > PJ Fanning 于2025年3月11日周二 17:56写道： > > > > Ok. I have the commit now. > > > > https://github.com/apache/incubator-seata/commit/d2f3554a656aa84ae423cf6cf84aa214fc8c#diff-724497593d9df5966fe458e68a556e9c715fc69dce406b93acf7b3858d020976 > > > > This seems like a minor rewrite that does exactly the same thing. > > Since the code is simple enough, I guess it is hard to completely > > rewrite it. > > > > I will retract my -1. > > > > > > On Tue, 11 Mar 2025 at 10:49, PJ Fanning wrote: > > > > > > This is a vote on the tar.gz that you supplied. I cannot find the > > > license change in apache-seata-2.3.0-incubating-src.tar.gz that > > > relates to ExtendedWhitespaceThrowableProxyConverter. > > > > > > On Tue, 11 Mar 2025 at 07:08, Min Ji wrote: > > > > > > > > Hi PJ, > > > > > > > > PJ Fanning 于2025年3月11日周二 03:00写道： > > > > > > > > > > https://github.com/apache/incubator-seata/blob/151ea4f6757fab260ea21227ab793e0cdeee2d92/server/src/main/java/org/apache/seata/server/logging/logback/ExtendedWhitespaceThrowableProxyConverter.java#L28 > > > > > > > > > > This file has an invalid source header. Since the source file was > > > > > copied from spring-boot, it should retain the header from the > > > > > spring-boot file. > > > > > > > > > > The key thing missing is the copyright. > > > > > > > > > > https://github.com/spring-projects/spring-boot/blob/b6bccc13789224e80328057506c31b9d2dee9026/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/logging/logback/ExtendedWhitespaceThrowableProxyConverter.java#L2 > > > > > > > > > > -1 (binding) because the LICENSE change was not made to mention > > > > > ExtendedWhitespaceThrowableProxyConverter and the fact that it comes > > > > > from spring-boot. > > > > > > > > Jean-Baptiste already pointed out this issue during the 2.3.0-RC3 > > > > voting process [1]. As a result, we canceled the RC3 vote, refactored > > > > the relevant code, and initiated the 2.3.0-RC4 voting thread. The > > > > files that were flagged have been updated in the new commit. So, I > > > > think we should check using the commit ID > > > > `0ad2847465fa877a2c65ea84ed43f5b0984c3ce9` mentioned in the voting > > > > email. I've verified that the source code on GitHub and what's > > > > submitted to SVN has been updated [2][3]. > > > > > > > > [1]. https://lists.apache.org/thread/wbq6jsykj2cd9nn91ys1b8r99bfl1h2r > > > > [2]. > > > > https://github.com/apache/incubator-seata/tree/0ad2847465fa877a2c65ea84ed43f5b0984c3ce9/server/src/main/java/org/apache/seata/server/logging/logback > > > > [3]. > > > > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata/2.3.0-RC4/apache-seata-2.3.0-incubating-src.tar.gz > > > > > > > > > > > > > > > > > > On 2025/03/10 06:18:52 yixia wrote: > > > > > > Hello, > > > > > > > > > > > > This is a call for vote to release Apache Seata(incubating) > > > > > > 2.3.0-RC4. > > > > > > > > > > > > > > > > > > The vote thread: > > > > > > > > > > > > https://lists.apache.org/thread/gfvr1rjh9zgfpbbcow0bmbqpg8ngq9wk > > > > > > > > > > > > > > > > > > Vote Result: > > > > > > > > > > > > https://lists.apache.org/thread/yc16ch0s99yfvhb7xvvw6d0gmjdh0r1j > > > > > > > > > > > > > > > > > > The release candidates: > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata/2.3.0-RC4/ > > > > > > > > > > > > > > > > > > The staging repo: > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheseata-1137/ > > > > > > > > > > > > > > > > > > Git tag for the release: > > > > > > > > > > > > https://github.com/apache/incubator-seata/releases/tag/v2.3.0 > > > > > > > > > > > > > > > > > > Git commit id for the release: > > > > > > > > > > > > https://github.com/apache/incubator-seata/commit/0ad2847465fa877a2c65ea84ed43f5b0984c3ce9 > > > > > > > > > > > > > > > > > > Release Notes: > > > > > > > > > > > > https://github.com/apache/incubator-seata/releases/tag/v2.3.0 > > > > > > > > > > > > > > > > > > The artifacts have been signed with Key [ 7ACD1A52F5AEF76A ], > > > > > > corresponding > > > > > > to[ yi...@apache.org ] > > > > > > > > > > > > which can be found in the keys file: > > > > > > > > > > > > https://do
Re: Clarification on the -1 policy for code changes
Hi, > On Mar 11, 2025, at 4:23 PM, Justin Mclean wrote: > > Hi, > > Looking at the first propopal, I was surprised to discover > https://www.kie.org/ - having a domain name like this is not in line with ASF > trademark policy, nor is having a domain name like https://kogito.kie.org/. > There are other trademark issues with those site(s), I trust the PPMC is > aware of this and is taking steps to fix this before graduation? While these issues may be true, let’s not spread the flow by adding something else. > I’m not part of your community, so it is possible I’m misreading this, but I > see some issues from a casual glance. IMO, the two proposals need to be > discussed further and consensus reached before moving forward. Calling for a > vote without discussion, like the second proposal, is not how things are done > in ASF projects. It looks like some community problems have been identified, discussed a lot with no consensus, then complex proposals were created by a couple of committers, these proposals were not discussed and instead pushed to a vote. I am not surprised that a number of community members responded with a -1. I think that rather than have an abstract battle on how to vote the proposers should do some work by adding to this examples repository. If it accomplishes what the proposers think it will then having it will help convince the rest of the community, and then the rest of the work can continue. Best, Dave > > Kind Regards, > Justin > >> On 12 Mar 2025, at 7:48 AM, Paolo Bizzarri wrote: >> >> Hello, >> >> this is Paolo Bizzarri. I am part of the Apache Kie project. >> >> I am looking for clarifications about the official policy of Apache >> foundation about code changes and vetoes. >> >> As per this document in the Apache web site, a -1 to a proposal for a code >> change is a veto - i.e. it "kills the proposals" >> >> https://www.apache.org/foundation/voting.html#:~:text=Votes%20On%20Code%20Modification,approve%20of%20this%20change.%27 >> >> However we got two proposals that are getting pushed through even in >> presence of -1 >> >> https://lists.apache.org/thread/drojdtvz6xx1zo35ggjm75xdngnfcl21 >> >> and >> >> https://lists.apache.org/thread/c09l9xq0d8jz7th6k23gf5svoky06955 >> >> I got an answer from Alex Porcelly stating that "-1 are not vetos on >> proposals" which seems wrong to me. These are code changes and so the rules >> for vetoes should apply. >> >> Otherwise I could make a proposal like "put all passwords in plain text in >> the code" and then pretend that the PR cannot be vetoed because the >> corresponding proposal has already been approved, so there is consensus. >> >> https://lists.apache.org/thread/r37j54k3fyg5h18d4xdlb43ff9wcq96b >> >> Can you clarify and provide an answer that I can forward to the kie mailing >> list? >> >> I understand that some projects have defined less restricting veto >> policies, but I understand also that this is a matter of internal rules - >> i.e. a way for the community of a project to decide how to work. My >> understanding is that in the absence of such a decision, the Apache default >> rules apply. >> >> Regards >> >> Paolo Bizzarri > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Clarification on the -1 policy for code changes
Hi, Looking at the first propopal, I was surprised to discover https://www.kie.org/ - having a domain name like this is not in line with ASF trademark policy, nor is having a domain name like https://kogito.kie.org/. There are other trademark issues with those site(s), I trust the PPMC is aware of this and is taking steps to fix this before graduation? I’m not part of your community, so it is possible I’m misreading this, but I see some issues from a casual glance. IMO, the two proposals need to be discussed further and consensus reached before moving forward. Calling for a vote without discussion, like the second proposal, is not how things are done in ASF projects. Kind Regards, Justin > On 12 Mar 2025, at 7:48 AM, Paolo Bizzarri wrote: > > Hello, > > this is Paolo Bizzarri. I am part of the Apache Kie project. > > I am looking for clarifications about the official policy of Apache > foundation about code changes and vetoes. > > As per this document in the Apache web site, a -1 to a proposal for a code > change is a veto - i.e. it "kills the proposals" > > https://www.apache.org/foundation/voting.html#:~:text=Votes%20On%20Code%20Modification,approve%20of%20this%20change.%27 > > However we got two proposals that are getting pushed through even in > presence of -1 > > https://lists.apache.org/thread/drojdtvz6xx1zo35ggjm75xdngnfcl21 > > and > > https://lists.apache.org/thread/c09l9xq0d8jz7th6k23gf5svoky06955 > > I got an answer from Alex Porcelly stating that "-1 are not vetos on > proposals" which seems wrong to me. These are code changes and so the rules > for vetoes should apply. > > Otherwise I could make a proposal like "put all passwords in plain text in > the code" and then pretend that the PR cannot be vetoed because the > corresponding proposal has already been approved, so there is consensus. > > https://lists.apache.org/thread/r37j54k3fyg5h18d4xdlb43ff9wcq96b > > Can you clarify and provide an answer that I can forward to the kie mailing > list? > > I understand that some projects have defined less restricting veto > policies, but I understand also that this is a matter of internal rules - > i.e. a way for the community of a project to decide how to work. My > understanding is that in the absence of such a decision, the Apache default > rules apply. > > Regards > > Paolo Bizzarri
Re: [VOTE] Release Apache Seata (Incubating) 2.3.0-RC4
https://github.com/apache/incubator-seata/blob/151ea4f6757fab260ea21227ab793e0cdeee2d92/server/src/main/java/org/apache/seata/server/logging/logback/ExtendedWhitespaceThrowableProxyConverter.java#L28 This file has an invalid source header. Since the source file was copied from spring-boot, it should retain the header from the spring-boot file. The key thing missing is the copyright. https://github.com/spring-projects/spring-boot/blob/b6bccc13789224e80328057506c31b9d2dee9026/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/logging/logback/ExtendedWhitespaceThrowableProxyConverter.java#L2 -1 (binding) because the LICENSE change was not made to mention ExtendedWhitespaceThrowableProxyConverter and the fact that it comes from spring-boot. On 2025/03/10 06:18:52 yixia wrote: > Hello, > > This is a call for vote to release Apache Seata(incubating) 2.3.0-RC4. > > > The vote thread: > > https://lists.apache.org/thread/gfvr1rjh9zgfpbbcow0bmbqpg8ngq9wk > > > Vote Result: > > https://lists.apache.org/thread/yc16ch0s99yfvhb7xvvw6d0gmjdh0r1j > > > The release candidates: > > https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata/2.3.0-RC4/ > > > The staging repo: > > https://repository.apache.org/content/repositories/orgapacheseata-1137/ > > > Git tag for the release: > > https://github.com/apache/incubator-seata/releases/tag/v2.3.0 > > > Git commit id for the release: > > https://github.com/apache/incubator-seata/commit/0ad2847465fa877a2c65ea84ed43f5b0984c3ce9 > > > Release Notes: > > https://github.com/apache/incubator-seata/releases/tag/v2.3.0 > > > The artifacts have been signed with Key [ 7ACD1A52F5AEF76A ], corresponding > to[ yi...@apache.org ] > > which can be found in the keys file: > > https://downloads.apache.org/incubator/seata/KEYS > > > Build Environment: JDK 8+, Apache Maven 3.6.0+. > >- > >osx_aarch64： ./mvnw clean package -DskipTests=true -Parrch64 >- > >osx-x86_64/other: ./mvnw clean package -DskipTests=true > > > CI Test Workflow: > > https://github.com/apache/incubator-seata/actions/runs/13435379453/job/37579216082 > > > The vote will be open for at least 72 hours. > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist > > [ ] No unexpected binary files > > [ ] All source files have ASF headers > > [ ] Can compile from source > > > To learn more about Apache Seata , please see https://seata.apache.org/ > > > Warm regards, > > Te Wang > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenClovis SAFplus-Availability-Scalability-Platform would like to join Apache Incubator
Hi Justin, We use "SAFplus" as a prefix for some products, and the word "SAFplus" used in the document implies the product (short name) to join ASF, it's "High Availability-Scalability-Platform" and I don't think it's a registered trademark. It usually stands behind "OpenClovis", an organization name, like OpenClovis SAFplus-... Thanks, Hung On Wed, Mar 12, 2025 at 11:41 AM Justin Mclean wrote: > Hi, > > One thing, well two, actually. I didn’t see in the document if the name is > a registered trademark, and will OpenClovis keep using SAFplus to refer to > other products? > > Kind Regards, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: OpenClovis SAFplus-Availability-Scalability-Platform would like to join Apache Incubator
Hi PJ, Thanks a lot for your comments. The proposal was revised. Can you please take a look again : https://docs.google.com/document/d/1f1AJ18xjIoGw40lWGaWVf1AgPrcwYHlDiu4Agj7UV0E/edit?usp=sharing Regards, Hung On Tue, Mar 11, 2025 at 3:20 PM Hung Ta wrote: > Hi PJ, > > The proposal is ready for review. This is the link: > https://docs.google.com/document/d/1f1AJ18xjIoGw40lWGaWVf1AgPrcwYHlDiu4Agj7UV0E/edit?usp=sharing > I'd like your help with the review. Thanks. > > Regards, > Hung > > On Thu, Mar 6, 2025 at 8:24 PM PJ Fanning wrote: > >> Hi Hung, >> >> The next step would be to put together a proposal. >> >> An example is: >> https://cwiki.apache.org/confluence/display/INCUBATOR/Iggy+Proposal >> >> The are other proposals in: >> https://cwiki.apache.org/confluence/display/INCUBATOR/Proposals >> >> The format is a set format. >> >> I can act as champion. >> >> If you create a proposal in Google Docs or some other shared document, >> then I help review it when it is ready. >> >> Regards, >> PJ >> >> On Thu, 6 Mar 2025 at 04:00, Hung Ta wrote: >> > >> > Hi Justin, >> > >> > After discussing with our boss, we agree with the Apache license for our >> > future versions. >> > >> > Would you please instruct us to do the next steps? Thanks. >> > >> > Regards, >> > Hung >> > >> > On Tue, Feb 25, 2025 at 10:40 AM Justin Mclean < >> jus...@classsoftware.com> >> > wrote: >> > >> > > Hi, >> > > >> > > >> 2. The license will need to change after you become an ASF project >> but >> > > you >> > > >> also won't be able to use any GPL licensed libraries in the project >> > > either. >> > > >> Have you done an audit of how hard these changes will be? >> > > >> >> > > > [Hung] Yes, we agree that the license needs to change after we >> become an >> > > > ASF project. However, can we still keep the current license for our >> > > current >> > > > or future customers? Is this ok? >> > > >> > > Only for previous software versions released before you joined the >> > > Incubator. All future versions must be Apache licensed. >> > > >> > > Kind Regards, >> > > Justin >> > > - >> > > 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 >> >>
Clarification on the -1 policy for code changes
Hello, this is Paolo Bizzarri. I am part of the Apache Kie project. I am looking for clarifications about the official policy of Apache foundation about code changes and vetoes. As per this document in the Apache web site, a -1 to a proposal for a code change is a veto - i.e. it "kills the proposals" https://www.apache.org/foundation/voting.html#:~:text=Votes%20On%20Code%20Modification,approve%20of%20this%20change.%27 However we got two proposals that are getting pushed through even in presence of -1 https://lists.apache.org/thread/drojdtvz6xx1zo35ggjm75xdngnfcl21 and https://lists.apache.org/thread/c09l9xq0d8jz7th6k23gf5svoky06955 I got an answer from Alex Porcelly stating that "-1 are not vetos on proposals" which seems wrong to me. These are code changes and so the rules for vetoes should apply. Otherwise I could make a proposal like "put all passwords in plain text in the code" and then pretend that the PR cannot be vetoed because the corresponding proposal has already been approved, so there is consensus. https://lists.apache.org/thread/r37j54k3fyg5h18d4xdlb43ff9wcq96b Can you clarify and provide an answer that I can forward to the kie mailing list? I understand that some projects have defined less restricting veto policies, but I understand also that this is a matter of internal rules - i.e. a way for the community of a project to decide how to work. My understanding is that in the absence of such a decision, the Apache default rules apply. Regards Paolo Bizzarri
Re: Clarification on the -1 policy for code changes
Adding some context to this discussion: - Apache KIE mentor Brian has provided guidance on similar matters before [1][2]. - A guideline is already in place to define how discussions, proposals, and votes should work [3], and it was formally approved [4]. Regarding the proposals in question, they strictly involve moving code from one repository to another. There is no impact on the software itself—only on contributors working within the project. The example given—storing passwords in plain text—seems extreme. Any change with serious implications for users would be subject to review and could be vetoed based on existing guidance [2]. Approved proposals do not grant a "blank check"; changes must still be scrutinized. Ultimately, I believe that in any open-source project, any proposal will lead to code changes, in a way or another. - Alex [1] - https://lists.apache.org/thread/1vrtdv4jy3db8wj86bgd3w6ofd0w5zb8 [2] - https://lists.apache.org/thread/sofswb9ol7srncj6fqwz1ohtq2x550ky [3] - https://cwiki.apache.org/confluence/display/KIE/%5BPROPOSAL%5D+Community+guideline+to+define+discussion%2C+proposal+and+vote [4] - https://lists.apache.org/thread/2vmnnnlx89f6tg4m4td46ofm7sk5mv76 On Tue, Mar 11, 2025 at 4:48 PM Paolo Bizzarri wrote: > > Hello, > > this is Paolo Bizzarri. I am part of the Apache Kie project. > > I am looking for clarifications about the official policy of Apache > foundation about code changes and vetoes. > > As per this document in the Apache web site, a -1 to a proposal for a code > change is a veto - i.e. it "kills the proposals" > > https://www.apache.org/foundation/voting.html#:~:text=Votes%20On%20Code%20Modification,approve%20of%20this%20change.%27 > > However we got two proposals that are getting pushed through even in > presence of -1 > > https://lists.apache.org/thread/drojdtvz6xx1zo35ggjm75xdngnfcl21 > > and > > https://lists.apache.org/thread/c09l9xq0d8jz7th6k23gf5svoky06955 > > I got an answer from Alex Porcelly stating that "-1 are not vetos on > proposals" which seems wrong to me. These are code changes and so the rules > for vetoes should apply. > > Otherwise I could make a proposal like "put all passwords in plain text in > the code" and then pretend that the PR cannot be vetoed because the > corresponding proposal has already been approved, so there is consensus. > > https://lists.apache.org/thread/r37j54k3fyg5h18d4xdlb43ff9wcq96b > > Can you clarify and provide an answer that I can forward to the kie mailing > list? > > I understand that some projects have defined less restricting veto > policies, but I understand also that this is a matter of internal rules - > i.e. a way for the community of a project to decide how to work. My > understanding is that in the absence of such a decision, the Apache default > rules apply. > > Regards > > Paolo Bizzarri - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenClovis SAFplus-Availability-Scalability-Platform would like to join Apache Incubator
Hi, One thing, well two, actually. I didn’t see in the document if the name is a registered trademark, and will OpenClovis keep using SAFplus to refer to other products? Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenClovis SAFplus-Availability-Scalability-Platform would like to join Apache Incubator
Hi, One thing, well two, actually. I didn’t see in the document if the name is a registered trademark, and will OpenClovis keep using SAFplus to refer to other products? Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
