Re: KIE - Question about "staging" binaries/artifacts

Hi, > Thank you all for the inputs, but we still seeking clarity on NPM. > > We - Apache KIE podling - are trying to get a single release procedure for > all binaries, but with lack of NPM infra for staging makes it really > complex. > > I notice that OpenDAL publishes to NPM, is there anyone

Re: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1

Hi, A few questions occurred to me when looking at the website: - You list sponsors, how do these companies sponsor the project? - You list 1.9.0 for download, but there is no link to the KEYS files - You list Mohammad Sadoghi as the “Principle Investigator” This is problematic from an ASF point

Re: [VOTE] Drop the incubator- prefix for podling's GitHub repo name

Hi, +1 binding. We already have other requirements for the project to indicate that they are incubating (e.g. website disclaimer, DISCLAIMER, and release artifact name) that are more visible than having it in repo names. Kind Regards, Justin

Re: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1

HI, > Thanks for letting me know. > I have removed those dependencies. What goes in the license file is any 3rd party licenses that are included in the source release, not those that are dependencies. But unless it is optional, you also can’t have any GPL dependencies. Kind Regards, Justin

Re: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1

HI, I assume you mean [1] I’ve not looked at it in detail, but I note you include GPL licensed code. GPL-licensed code is Category X and can’t be used in an ASF project. Kind Regards, Justin 1. https://github.com/apache/incubator-resilientdb/blob/master/LICENSE

Re: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1

Hi, It’s -1 (binding) from me. I think you should use Apache Rat to check the release. I checked: - incubating in artifact name - signatures and hashes are correct - DISCLAIMER exists - LICENSE is missing mention of 3rd party code included in the release - NOTICE doesn't include correct text

Re: License for text content

Hi, The CC BY 4.0 is not compatible with the Apache license, so I would avoid it if you can. While the Apache license is intended for code, it’s OK to use for documentation as well. Kind Regards, Justin > On 2 May 2024, at 1:25 pm, tison wrote: > > Hi, > > IIUC, the Apache License 2.0 is

Re: [VOTE] Release Apache StreamPark(Incubating) 2.1.4-rc1

Hi, > Thanks for your clarification. We have submitted a PR[1] to address this > issue. I believe this issue will be resolved quickly. > > [1] https://github.com/apache/incubator-streampark/pull/3689 That looks good to me, thanks. Kind Regards, Justin

Re: [VOTE] Release Apache StreamPark(Incubating) 2.1.4-rc1

Hi, > * Some false positive on testing assertions utils. Match rate < 50%, file > is small, and those utilities are trivial. Even when I go to the "origins", > they are lost or changed a lot. Clearly not the same origin. Even if they have changed a lot, that could still be an issue. Copying an

Re: [VOTE] Release Apache StreamPark(Incubating) 2.1.4-rc1

Hi, -1 (binding) from me I checked: - incubating in name - signatures and hashes correct - disclaimer exists - LICENSE is missing some info on the MIT license - NOTICE looks fine - I didn't compile from source So a condition of including MIT licensed code is to include the relevant MIT license

Re: Verification of download pages and links

Hi, > Here is a patch to cover a minimal download page [1], which is derived from > OpenDAL's download page [2]. Welcome to leave comments if you find any > issues or things we can improve on. > > [1] https://github.com/apache/datafusion/pull/10271 > [2] https://opendal.apache.org/download The

Re: Verification of download pages and links

Hi, Projects need to make source releases on ASF infrastructure and have a download page for good reasons. Some users need a place to verify and download a trusted release. Having it hosted on ASF infrastructure means people can 100% trust it, unlike 3rd party providers. 3rd party providers

Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo

Hi, > 4. To clarify that a repo belongs to a podling, introduce a guideline or > policy to help PPMCs include the DISCLAIMER in the README of all their > repos. Alternatively, perhaps we can come up with something a little shorter shorter that points to DISCLAIMER? What is important is that the

Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc3

HI, I’m happy to share it, but as I said, I'm travelling right now and don't have access. I used ScanOSS workbench, but there are other checkers out there. And yes, tools like this can sometimes give false positives, and it can sometimes be unclear where things were originally copied or, in

Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo

Hi, I would be for requiring the incubator disclaimer text in the project's README: "Apache FOO is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates

Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc3

Hi, I’m currently travelling and may be slow in responding to emails. > The MemoryBufferWritableChannel[5] and MockWritableChannel[6] was written > by me before we open-sourced Fury and > I submitted it to Ray in PR[8] ,which was planned to optimize zero-copy > serialization in Ray. I think

Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc3

HI, Sorry, it’s -1 (binding) from me as it looks like there is additional third-party code without correct headers or mentioned in LICENSE. I checked: - incubating in name - signatures and hashes are fine - LICENSE has some issues (see below) - NOTICE is fine - It looks like some 3rd party code

Re: Questions about a new project entering Apache Incubator

HI, So, I had an informal chat with Infra, and they don't care which one they do, but is it some work for them to change from “incubator-foo” to “foo” on graduation. I’m curious as to why some people in this thread think this is a big issue if the project clearly states it is an incubating

Re: [MENTORS] May report timeline - reports due May 2024

HI, As Sdap has just graduated, it doesn’t need to report. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: Questions about a new project entering Apache Incubator

Hi, Both of these projects are new and just getting set up. I'd give them a little time to do that. Infra in recent years have asked to minimise work for them on graduation. We recently dropped the requirement for having incubating in podling domain names so I don't see it's needed in repo names

Re: Should we mention license of other projects in NOTICE file

Hi, Any license information goes in LICENSE, not NOTICE. If you include something that is MIT or BSD licensed, nothing goes in the NOTICE. The NOTICE file will include re-located copyright statements removed from files and the contents of any Apache code you have included NOTICE files. 1. is

[MENTORS] Missing podling reports

Hi, We are missing a large number of reports this month. Mentors, can you please help your projects submit reports on time. We are still waiting on reports from: - Annotator - Gluten - HoraeDB - HugeGraph - Liminal - Pony Mail - ResilientDB - Teaclave - XTable Kind Regards, Justin

Re: Trademarks and incubation (was: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project)

Hi, > Question: where did the incubation process fail in this case? How can we > prevent something like this from happening again? The Incubator pointed out the issue during a graduation discussion at the end of 2021 (which put off graduation). The people involved said they would not use the

Re: Update project maturity model to include trademark and branding?

Hi, > Besides, the maturity model is applied for all ASF projects and under the > management of ComDev pmc. > > Shall we cc this thread to dev@community.a.o or start a new thread after we > have a consensus within the Incubator first? I had intended to bring it up on dev@community.a.o for

Re: Registering a release

Hi, >> You might want to remove those old releases there, as they are automatically >> archived here: >> https://archive.apache.org/dist/incubator/sdap/ > > Would that affect the closer.lua download links on our website? Yes, but it’s not needed for old releases because they presumably don’t

Re: [MENTORS] April report timeline - reports due April 2024

Hii, Please note that Kie doesn't need to report. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: Registering a release

Hi, In SDAPs case: https://dist.apache.org/repos/dist/release/incubator/sdap/ You might want to remove those old releases there, as they are automatically archived here: https://archive.apache.org/dist/incubator/sdap/ Kind Regards, Justin

Re: Registering a release

Hi, I’m not sure what you mean by registering a release. All ASF releases need to go here: https://dist.apache.org/repos/dist/release/ Kind Regards, Justin > On 21 Mar 2024, at 10:29 am, Julian Hyde wrote: > > Can someone remind me where I go (whimsy or reporter, I presume) to > register a

Re: [VOTE] Podling web sites: make (incubator.) optional in podling urls

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

[RESULT][VOTE] Accept Amoro into the ASF Incubator

HI, Thanks to everyone who voted. [1] There are 15 +1 binding votes, 19 +1 non-binding votes, and no 0 or -1 votes, so the vote has passed. Binding +1 votes: Yu Li Ayush Saxena PJ Fanning Felix Cheung Craig Russell Zili Chen (tison) Xinyu Zhou Xin Wang Jean-Baptiste Onofré Duo Zhang Furkan

Re: [DISCUSS] Graduate Apache Paimon (Incubating) as a Top Level Project

Hi, > Thanks for pointing this out Justin. The description of the first > mentioned vedio (a CoC Asia talk) [1] has been updated (thanks @Willem > for the help), and PPMC is actively working on correcting the second > one. Those two links were only some of the instances I found. I suggest you do

Re: [DISCUSS] Graduate Apache Paimon (Incubating) as a Top Level Project

HI, In your discussion on graduation, you refer to the proposed chair as “the founder of Paimon”. While this person may have come up with the initial design before it was an Apache project, the project is run by the community. Please do not refer to anyone as a founder of an Apache project. I

Re: [DISCUSS] Incubating Proposal for GraphAr

gt; > [1] https://github.com/alibaba/GraphAr/graphs/contributors > [2] https://cwiki.apache.org/confluence/display/INCUBATOR/GraphArProposal > > Justin Mclean 于2024年3月4日周一 14:59写道： >> >> HI, >> >> I was looking at your initial committer list and noticed, according to

Re: [DISCUSS] Incubating Proposal for GraphAr

HI, I was looking at your initial committer list and noticed, according to GitHub, that: - sighingnow is #1 in activity - acezen is #6 in activity - lixueclaire is #30 in activity - Thespica is not a commmiter in the main project. Is the repo elsewhere, and does that intend to be donated to teh

[VOTE] Have Amoro join the Incubator

Hi, Following on from the discussion of the Amoro proposal [1][2], let's vote on having it join the Incubator. Please cast your vote: [ ] +1, have it join the Incubator as an incubating project [ ] +0, I have no strong opinion either way [ ] -1, do not have it join the Incubator because...

Re: [DISCUSS] Apache Amoro proposal

HI, As the discussion seems to have died down, I’ll put this up for a vote. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: [DISCUSS] Incubating Proposal for GraphAr

Hi, > 2. Slack Channel: > We intend to continue maintaining the Slack channel as an additional > real-time communication platform for both users and developers. Slack > provides a convenient and efficient means of real-time communication. It can > serve as an additional tool for people to

Re: [DISCUSS] Graduate Apache SDAP (Incubating) as a Top Level Project

Hi, +1 (binding) as well - all the best. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP

Hi, +1 from me and best wishes on your journey as a TLP. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: Podling web sites: .incubator. required?

HI, > I would propose that as part of our official policy we recommend the > podling's url as https://podling.apache.org and get rid of the .incubator. in > the url. > > WDYT? +1 from me. Kind Regards, Justin - To

Re: [NOTICE] Incubation Report for February 2024

HI, The report_runbook.py script tells you most of what to do. A few more projects need t report than listed below, including some new projects that need to report monthly. I’ve also left the monthly properties as is. The report_email.py script will send an email to this list with the

Re: [MENTORS] March report timeline - reports due March 2023

Please ignore this as I put in the wrong year > On 25 Feb 2024, at 12:12 pm, jmcl...@apache.org wrote: > > Dates for next board report: > Wed March 01 - Podling reports due by end of day > Sun March 05 - Shepherd reviews due by end of day > Sun March 05 - Summary due by end of day > Tue March 07

[DISCUSS] Apache Amoro proposal

Hi, I would like to propose a new project to the ASF incubator - Apache Amoro. I’m one of the mentors, but there are a lot of other people involved who have done all of the hard work. Amoro is a Lakehouse management system built on open data lake formats like Apache Iceberg and Apache Paimon

Re: podling reports for January 2024

Hi, I’ll sort this out in the next 24 hours. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP

Hi, > Also, for trademark attribution, I understand the databend.rs, if it > refers to OpenDAL, it should contain a Footer like Datastax does[2]. Datastax has had recent issues regarding trademarks; please follow the policy, not what other 3rd party companies do. I can see the project, from

Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP

Hi, The (P)PMC must be able to do this independently. Just look at each of the resources you listed and ask yourself: - Is Apache Foo being used in the most prominent place? - Are we using the trademark symbol? - Does the page include trademark attribution for any Apache trademarks used? Our

Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP

Hi, I’ll also note that this site (which I assume you have control of) also doesn’t comply with our policy. [1] Kind Regards, Justin 1. https://xuanwo.io/

Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP

Hi, Several of those pages still do not comply with our trademark policy; the TM symbol needs to be used, and a trademark attribution included. Kind Regards, Justin - To unsubscribe, e-mail:

Community over code incubator track

Hi, There's less than 20 hours to go before submissions close and I'd like to see some more submissions to the incubator track. Talks about your journey as an incubating project or if you just want to promote your project are welcome. Please submit your last minute tasks at

Re: [QUESTION] Oracle JDBC Driver as a test dependency

Hi, > In your source release anything in Category A is fair game. Things in > Category B are not. Things in Category X never are. While correct, that’s not the full story; you also can’t have anything as a dependency whose license is a category X one. Kind Regards, Justin

Re: [QUESTION] Handling of licensing issues for dependencies of dependencies

HI, > I was performing a more thorough check of our dependencies in preparation of > opening graduation discussions with the Incubator PMC and found at least one > package that, while not directly used in the code, is installed as a > dependency of multiple top-level dependencies that is LGPL

Re: [VOTE] Release Apache Celeborn(Incubating) 0.3.2-incubating-rc2

Hi, +1 (binding) I checked in the source release: - incubating in the name - signatures and hashes are fine - DISCLAIMER exists - LICENSE looks good - The NOTICE file needs to be updated and likely does not contain all the needed information. For example, The Flink Remote Shuffle Project NOTICE

Re: [RESULT][VOTE] Release Apache OpenDAL, incubating, 0.44.0-rc.1 - Incubator Vote Round 1

Hi, It’s best to wait for 72 hours before closing a vote. Kind Regards, Justin > On 31 Dec 2023, at 1:19 pm, Liuqing Yue wrote: > > Hi Incubator PMC, > > The vote to release Apache OpenDAL(incubating) 0.44.0-rc.1 has passed with > 3 +1 binding and 1 +1 non-binding votes, no +0 or -1 votes. >

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

Hi, > If today, someone on the internet, for any reason, buys a domain name > and redirects it to opendal.apache.org. You don't even have contact to > that person. Do you still argue that the PMC should take control of > that domain? Of course not, the issue is not with redirecting a domain. The

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

Hi, > As an analogy, think of answer.dev and answer.apache.org. You are in > the thread of a similar situation[1]. This projct has just entered incubation and is not seeking to graduate. It will need to hand over ownership of that domain name before it does. Kind Regards, Justin

Re: Update project maturity model to include trademark and branding?

HI, >> TB40 The project performs some monitoring of 3rd party use of its >> trademarks, addressing any instances of misuse. > > Do you have some examples of how podlings or TLPs perform this today? This varies from project to project: - Some projects have PMC members working at a company who

Re: [VOTE] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

Hi, > As for branding and trademarks, the OpenDAL (P)PMC is actively > handling known issues, including Anything referred in... I’m not sure they are. What about, for instance, various download pages e.g. [1] and the ownership of the opendal.databend.rs domain

Update project maturity model to include trademark and branding?

Hi, It seems the updated podling report template has not had the impact it was hoped to have around issues of branding and trademarks. It was pointed out on the trademark list that the current maturity model [1] is missing checks for trademarks and branding. Here is my first attempt at it;

Re: [VOTE] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

Hi, -1 (binding) until the branding and trademark issues have been resolved and the podling has a better understanding of what is involved here. Kind Regards, Justin - To unsubscribe, e-mail:

Re: [DISCUSS] Branding in Thirdparty Platform Distribution

HI, > Users should run `npm install xxx`, `pip install xxx`, or `cargo add xxx` > to include our library in their dependency list. Users should write code > in their own libraries or applications using statements such as `use xxx` > or `import xxx`. Adding the prefixes `apache-` or `asf-`

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

Hi, > The domain `opendal.databend.rs` is owned by Databend Labs and was used as > the > primary domain before OpenDAL entered the incubation stage. The PMC will > coordinate > with Databend Labs to ensure that all instances are updated to > `opendal.apache.org`. It would be best if the

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

Hi, > Thanks for your reply to report potential branding issues. The PMC is > actively responding to these comments. > > * https://github.com/apache/incubator-opendal/pull/3829/files > * https://github.com/apache/incubator-opendal/pull/3830/files > *

Re: [VOTE] Release Apache Celeborn(Incubating) 0.3.2-incubating-rc1

Hi, > We just checked their repo and found the PR[1] which added Celeborn's code > in their repo. We got in touch with them and they told us that the code was > deleted a month ago. I also checked their release[2] and didn't find > Celeborn's code in their source ball. So I guess this is no

Re: [DISCUSS] Branding in Thirdparty Platform Distribution

Hi, > The proposal here is to improve the expression on NPM / PyPI for the > package name to be either: > > 1. apache-projectname > 2. projectname Existing ASF policy has this to say: - "All PMCs must to comply with the Apache Project Branding Requirements.” [1] - “PMCs are directly responsible

Re: [DISCUSS] Branding in Thirdparty Platform Distribution

Hi, I’ll note these guidelines were discussed and voted on by the IPMC a while back. Legal and trademarks also reviewed them and had input, and the work is based on existing policy and years of discussion. They, however, have only had minor updates since being formed. Kind Regards, Justin

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

Hi, -1 (binding) to graduation, the PMC needs to understand the importance of and follow our randing policy; something seems to have been missed here. > About the https://opendal.apache.org/docs/python/opendal.html, it is > already on the apache.org site. It is obvious that it belongs to the >

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

HI, >> 2. https://opendal.apache.org/docs/python/opendal.html This is not fixed. I suggest the PMC members have a good read of our branding policy to understand what is needed here. [1] At a minimum, the project needs to be referred to as “Apache OpenDAL”, and the trademark attribution needs

Re: [LICENSE QUESTION] Use jmh as a benchmark tool

Hi, As listed in that document, a GPL license with a classpath exception is category X, so everything that applies to other category X licenses applies to that license. System dependencies that users or developers typically have installed that don't impact the license of the compiled package

Re: [VOTE] Release Apache Celeborn(Incubating) 0.3.2-incubating-rc1

Hi, Sorry, but it is -1 (binding) for now. Clearing up some of the issues below may mean that I change my vote. I checked - incubating in artifact name - signatures and hashes are correct - LICENSE mentions 1 3rd party file from Guava; however, the NOTICE lists both Apache Spark and Apache

Re: [VOTE] Release Apache HugeGraph (Incubating) 1.2.0 rc1

Hi, +1 (binding) I checked all source releases. - incubating in names - all release include LICENSE, NOTICE and DISCLAIMER - The NOTICE file for huge graph-computer could be improved, as it contains unnecessary information. "Copyright 2012 and onwards JanusGraph Authors” is clearly not

Re: [VOTE] Release Apache HugeGraph (Incubating) 1.2.0 rc1

Hi, Only the release artifacts need incubating in their name. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [LICENSE QUESTION] Use jmh as a benchmark tool

Hi, GPL files with classpath exceptions are not allowed [1]. Any files with that license cannot be in an ASF distribution [2] in source or binary form. They cannot be a non-optional dependency. [3] Kind Regards, Justin 1. https://www.apache.org/legal/resolved.html#category-x 2.

Re: [DISCUSS] Gluten proposal

Hi, Looks like a good proposal. Only one thing stood out to me, while not impossible, planning to graduate in a year might not be easily achievable. Kind Regards, Justn - To unsubscribe, e-mail:

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

Hi, Sorry, that should be "trademark attribution”, not “trademark attribute”. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

Hi, I found a few minor issues where some name and branding work needs to be done. Note that the project should be referred to as “OpenDAL” in the first instances and generally in headings, and 3rd parties need to make it clear it is an Apache project and includes the trademark attribute. For

Re: [VOTE] Release Apache Answer(Incubating) v1.2.1-RC1 (Round2)

Hi, +1 (binding) In the source release, I checked: - incubating in artifacts name - signatures and hashes are correct - LICENSE and NOTICE are fine - DISCLAIMER exists - all files have ASF headers - no unexpected binary files - my system isn't setup to compile it In the REDME.md it suggests

Re: [VOTE] Release Apache Answer(Incubating) v1.2.1-RC1 (Round2)

Hi, +1 (binding) In the source release, I checked: - incubating in artifacts name - signatures and hashes are correct - LICENSE and NOTICE are fine - DISCLAIMER exists - all files have ASF headers - no unexpected binary files - my system isn't setup to compile it In the REDME.md it suggests

Re: [VOTE] Release Apache Answer(Incubating) v1.2.1-RC1

HI, The previous signing key also needs to be revoked as it has been shared. Kind Regards, Justn - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: December Podling reports

I’ll get to it in the next 24 hours. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] HoraeDB proposal

HI, > project still wants to use the CeresDB name in some form. Is this correct > or not? > NO. Then why does the code in the code still refer to CeresDB in 100+ places? for instance, the source path is: /horaedb/src/ceresdb looking at horaedbsrc/ceresdb/bin/ceresdb-server.rs it contains

Re: [DISCUSS] HoraeDB proposal

HI, From the discussion and proposal, I had understood that the HoraeDB project still wants to use the CeresDB name in some form. Is this correct or not? Kind Regards, Justin - To unsubscribe, e-mail:

Re: [DISCUSS] HoraeDB proposal

Hi, > I don't see if anywhere “CeresDB” should be used. If so, HoraeDB will change. In the proposal, IMO CeresDB is not used where it should be, giving a false impression. e.g. "HoraeDB has been open-sourced on GitHub for over a year.” that is not correct as it was CeresDB as the name change

Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1

Hi, The release artefacts include incubating in their names [1] as Incubator policy requires [2]. Kind Regards, Justin 1. https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.0-incubating-RC1/ 2. https://incubator.apache.org/policy/incubation.html#releases

Re: [DISCUSS] HoraeDB proposal

Hi, > Using a new name to avoid any possible confusion or conflict is reasonable > I think. That was not given as the reason. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands,

Re: [DISCUSS] HoraeDB proposal

Hi, > We have tons of examples here in the ASF of project Foo being used to > power commercial product Bar (Geode/Gemfire, Ignite/GridGain, > Kafka/Confluent, and many, many more). So this kind of dual branding > is nothing new -- there's no community fork involved per se. "Daul branding" is

Re: [DISCUSS] HoraeDB proposal

as its > name, but it can be unrelated to the donation (forget "CeresDB" and > nothing changes). > > Best, > tison. > > tison 于2023年11月28日周二 09:12写道： >> >> Perhaps think of an analogy with Docker vs. Moby? >> >> Justin Mclean 于2023年11月28日 周二07:15写道：

Re: [DISCUSS] HoraeDB proposal

HI, > This is included in the proposal: Since Ant Group wants to retain the brand > of CeresDB, we renamed the OSS project as HoraeDB before this proposal. Why do they want to retrain that brand? They are not using an internal version of the project currently. Do they intend to fork the

Re: [DISCUSS] HoraeDB proposal

Hi, Looking at the existing governance, I see that 2/3 of existing PMC members are needed to vote for a new PMC member. I assume this requirement will be dropped? There are many communication channels e.g. Slack, WeChat, DingTalk. What will happen to these in the future and who controls them?

Re: [DISCUSS] HoraeDB proposal

HI, The ring license seems to include BSD-style licenses with advertising clauses. These are considered category X. [1] Kind Regards, Justin 1. https://www.apache.org/legal/resolved.html#category-x

Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1

Hi, > Thanks Justin. I'll look into those files again. With this RC, it includes > a security hardening change. Akka issued a CVE for the issue but we don't > think it really needs one. At the same time, I'd like to get out a change. > > Can we delay getting a fix for the possible license issue

Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1

Hi, > We have not modified these files since the Akka split so I do not > think we should put Apache headers on them. Nor do I. 3rd party files should not have ASF headers. > I removed one file using https://github.com/apache/incubator-pekko/pull/810 > > I cannot find any other files that

Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1

Hi, > Justin - if you are aware of more matches other than the bind.keys > file, could you make us aware of them? I think there are about 1/2 a dozen files in that directory from Bind9, but nothing outside of that I’ve found. I’ve not done an extensive check, but at a glance, the file names

Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1

HI, I’ve not finished my review, but I may have found an issue. Some of the content in /actor-tests/src/test/bind/etc/ seems to come from Bind9 (https://github.com/isc-projects/bind9). The project is under a Category B license (MPL 2.0), but given the nature of these files and their use, I’m

Re: [VOTE] Release Apache DevLake (Incubating) v0.19.0-rc2

Hi, I think a little more work is needed: - It is unclear what license yarn-3.4.1.cjs is under - why not just say it contains multiple pieces of 3rd party code under different licenses? - You are misisng the BSD license for Yarn. The full text of the license needs to be included. - You still

Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1

Hi, +1 (binding) - carrying over my vote from the dev list. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Commented] (INCUBATOR-281) Broken link

[ https://issues.apache.org/jira/browse/INCUBATOR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787384#comment-17787384 ] Justin Mclean commented on INCUBATOR-281: - It did exist at one point: https://web.archive.org

Re: [CANCEL][VOTE] Release Apache Answer(Incubating) v1.2.0-RC1

Hi, You’ve cancelled it, but I would have just left it open. The 72-hour period is a suggestion, and in some cases, if you have a good reason, e.g., an urgent security issue, you don’t have to wait 72 hours. Kind Regards, Justin > On 17 Nov 2023, at 11:04 pm, LinkinStar wrote: > > Hi, > >

Re: [VOTE] Release Apache OpenDAL(incubating) v0.42.0-rc.3 - Incubator Vote Round 1

Hi, Sorry, but it -1 binding from me I checked: - incubating in name - signatures and hashes are fine - LICENSE is missing mention of [1]. NOTICE is also incorrect, and would need to include info from The Netty Project NOTICE file. - no unexpected binary files - all source fils have ASF headers

Re: [VOTE] Release Apache DevLake (Incubating) v0.19.0-rc2

Hi, Sorry, but it’s -1 (binding) from me. As I pointed out in my last review, multiple pieces of 3rd party code exist under different licenses, not just one. I suggest you look for copyright statements and work out the 3rd party software and licenses from that. I can see: Copyright (c) 2014

Re: [VOTE] Release Apache StreamPark(Incubating) 2.1.2-rc2

HI, For useFormEvents.ts a Google/GitHub search shows several copies, at least one is exact except for the ASF header, it is possible, but seems unlikely that it is ASF code. For example, this code [1]. It could be possible that people have copied the code from the ASF repo but I think this is

  1   2   3   4   5   6   7   8   9   10   >