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

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

Hi, Sorry, its -1 (binding) due to 3rd party code in the release. I checked: - incubating in the name - signature and hashes are fine - disclaimer exists - License (and perhaps NOTICE) is missing 3rd party code licenses - No unexpected binary files - Source files have ASF headers, but there may

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

Hi, Sorry, it’s -1 (binding) due to 3rd party code not being listed in LICENSE. I checked: - incubating in the name - signatures and hashes are fine - LICENSE is missing 3rd party software licenses - NOTICE is OK - No unexpected binaries - All required files have ASF headers - I didn’t compile

Re: [VOTE] Release Apache SDAP (incubating) 1.2.0-rc2

Hi, I just looked in the requirements file and remembered that chardet was LGPL-licensed, but I assume there’s an automated way to do it. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional

Re: [VOTE] Release Apache SDAP (incubating) 1.2.0-rc2

Hi, -1 (binding), as I think you may have an issue here as apache-sdap-nexus-1.2.0-incubating-src depends on LGPL licensed chardet. [1] ASF project can not depend on LGPL software unless it is optional. Is this the case here? I checked: - incubating in names - signatures and hashes are fine -

Re: [VOTE] Release Apache Pekko(incubating) Connectors 1.0.1-RC1

Hi, Here’s my +1 (binding) carried over 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

Re: [VOTE] Release Apache Pekko(incubating) Projection 1.0.0-RC1

Hi, +1 (binding) I checked: - incubating n name - signatures and hashes are fine - disclaimer exists - LICENSE and NOTICE are fine - no unexpected binary files - source headers are fine - Can compile from source Kind Regards, Justin

Re: [IP CLEARANCE] Accept java-driver (into Cassandra)

Hi, I can see some minor issues with this, as there is 3rd party code included in the donation, but the 3rd party code is not listed and I couldn't find it mentioned in the mailing list discussion. Do you have a list of the 3rd party code and their licenses? I can see some, but not all 3rd

Re: [DISCUSS] Incubating Proposal of Seata

Hi, >> You may want to reconsider both the initial commit list and the high commit >> bar. Initial committers who end up not contributing can be removed when the >> project graduates. > > A committer is a lifelong honor awarded by the Seata community to > contributors, and we welcome all

Re: [DISCUSS] Incubating Proposal of Seata

Hi, > It is necessary for me to explain the community roles in Seata. The Seata > community includes roles of maintainer, committer, and contributor. In the > actual operation of the community, the committer role in the Seata > community is similar to the PMC (Project Management Committee) member

Re: [DISCUSS] Incubating Proposal of Seata

Hi, > 1. The measurement standard for past contributions is based on outstanding > contributions such as playing a crucial role in creating the community, > building transaction patterns, or submitting more than 30 PRs. This is quite a high committer bar and could exclude people from

[jira] [Closed] (INCUBATOR-267) Update the podling retirement guide

[ https://issues.apache.org/jira/browse/INCUBATOR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-267. --- Resolution: Fixed completed > Update the podling retirement gu

[jira] [Closed] (INCUBATOR-275) Need to update Incubator statistics on the website landing page

[ https://issues.apache.org/jira/browse/INCUBATOR-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-275. --- Resolution: Fixed stats have been updated > Need to update Incubator statist

Re: Jira issues largely being ignored

Hi, Like any project, we are all volunteers here and this may mean that sometimes issues may go unaddressed or unclosed. If something needs attention you could bring it up on the mailing list. Kind Regards, Justin - To

Re: [DISCUSS] Incubating Proposal of Answer

HI, We’ve already asked trademarks the question if the project can use the name. For the answer, see [1] Kind Regards, Justin 1. https://lists.apache.org/thread/ovx9wfst80f28xolf0vhvzzdtzhh1ovq

[jira] [Closed] (INCUBATOR-277) Allow GitHub Actions to create PRs

[ https://issues.apache.org/jira/browse/INCUBATOR-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-277. --- Resolution: Invalid > Allow GitHub Actions to create

[jira] [Closed] (INCUBATOR-270) Install osschat GitHub app

[ https://issues.apache.org/jira/browse/INCUBATOR-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-270. --- Resolution: Invalid > Install osschat GitHub

[jira] [Closed] (INCUBATOR-273) remove jul...@apache.org from moderators of heron and toree podlings mailing lists

[ https://issues.apache.org/jira/browse/INCUBATOR-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-273. --- Resolution: Invalid > remove jul...@apache.org from moderators of heron and to

[jira] [Closed] (INCUBATOR-274) Gives Orbit (orbit.love) access to GitHub repos

[ https://issues.apache.org/jira/browse/INCUBATOR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-274. --- Resolution: Invalid > Gives Orbit (orbit.love) access to GitHub re

Re: [DISCUSS] Incubating Proposal for OzHera

Hi, As other IPMC members have mentioned, this project’s proposal has several issues, including IP, licensing and community issues and has probably been proposed too soon. I also want to add that 6 mentors are too many, and the project should consider including IPMC members outside of China.

Re: [KIE] Code import question

Hi, My understanding is that is all come across, but it would be best to ask infra. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC2

Hi, +1 (binding) I checked: - incubating in name - signatures and hashes exist - DISCLAIMER exists - LICENSE and NOTICE exists - no unexpected binary files - fees have corrected headers - can compile from source Kind Regards, Justin

[Mentors] September 2023 Incubator report timeline:

Hi, Fill in your report here - https://cwiki.apache.org/confluence/display/INCUBATOR/September2023 Wed September 06 -- Podling reports due by end of day Sun September 10 -- Shepherd reviews due by end of day Sun September 10 -- Summary due by end of day Tue September 12 --

Re: [VOTE] Release Apache Livy 0.8.0-incubating (RC1)

Hi, -1 (binding) as well as the Category X license issues with the binaries, LICENSE is missing a 3rd party licenses which may not be compatible with the ALv2. Note that the font and NOTICE file issue have been brought up before. I checked: - incubating in name - signatures and hashes are

Re: Feedback requested - How to deal with retired podling resources

list include only the voting, or is it also appropriate to > have discussion along with the voting? > > Best regards, > Ruslan > > On 2023/08/01 00:28:11 Justin Mclean wrote: >> Hi, >> >> I’m not sure what happen to that page or why it doesn’t exist. It did >

Re: [VOTE] Release Apache Livy 0.8.0-incubating (RC1)

HI, There are GPL and LGPL licensed jars in the zip. I'm not sure but I thought we couldn't include jars with category X licenses in our binary distributions. It could be that Category X licenses are only a problem with Source Releases. They are an issue with binary

Re: Feedback requested - How to deal with retired podling resources

Hi, I’m not sure what happen to that page or why it doesn’t exist. It did recenly: https://web.archive.org/web/20230327140005/https://incubator.apache.org/guides/retirement.html Justin

[MENTORS] August 2023 Incubator report timeline

Hi, Here is the August 2023 Incubator report timeline: https://cwiki.apache.org/confluence/display/INCUBATOR/August2023 Wed August 02 -- Podling reports due by end of day Sun August 06 -- Shepherd reviews due by end of day Sun August 06 -- Summary due by end of day Tue August 08 -- Mentor

Re: [VOTE] Release Apache Pekko(incubating) HTTP 1.0.0-RC2

Hi, I've already voted +1 on the project's mailing list. If any IPMC members vote +1 on the previous vote it best to note that in the vote email. Kind Regards, Justin - To unsubscribe, e-mail:

Re: PR for Publicity/Media Guidelines

Hi, Looks fine to me. Justin > On 29 Jul 2023, at 4:10 am, Melissa Logan wrote: > > ASF Marketing & Publicity have made updates to the Podling Publicity/Media > Guidelines on the website to current best practices (while fixing a few > historical hyperlinking issues). > > As noted on the

Re: [VOTE] IP Clearance of Pekko HTTP CORS code donation

Hi, It not easy to check what is being donated here. Can you point to the 3rd party repo or a tar/zip of the donated code? I can see an SGA has been signed, but did the contributors agree to the donation and do we have ICLAs for any of them? Kind Regards, Justin

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.1-rc1 - Incubator Vote Round 1

Hi, +1 (binding) I checked: - incubating in name - signatures and hashes are file - No unexpected binary files - LICENSE and NOTICE are fine - a few files don’t have ASF headers e.g. [1][2] I don’t have an environment set up to compile this, but including some easy to find instructions in the

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

Hi, > I just had an look at the entire git history of the file (see > https://github.com/lightbend/paradox/commit/7f55c0c71bfbfc6a987c2693b19dcbb74c9dc9a3) > and the original version > of the code that was committed is pretty much the same as the latest > version (see >

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

Hi, > b) it uses the same formatting/style as the original example, which is > different to the style of the rest of the code. > > The indentation/formatting/style of the code is entirely consistent I'd suggest you look again; other code put chained functions on a single line rather than

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

Hi, > So the groups.js has some documentation from that mozilla page copied > as a comment. This is not an uncommon practice. The text is not in > example code and most people would assume that the copying of small > fragments of documentation as code comments is fair use. IANAL but fair use is

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

HI, Sorry I meant to say: “...but the cookie code puts method calls on SEPERATE lines in the same style...“ Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

Hi, You'll notice that most of the code uses function chaining on a single line, but the cookie code puts method calls on a single line in the same style as the cookie examples on the website. I would also think a more commonly used JS implementation would use a simple for loop or RegEx

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

the license for these Mozilla links. > The links are there to point at the API documentation and none of the > sample code that appears in that documentation was copied. > > On Fri, 14 Jul 2023 at 00:05, Justin Mclean wrote: >> >> HI, >> >> Both CC0 [1] and M

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

HI, Both CC0 [1] and MIT [2] are treated as Category A licenses so can be included in a source release. Kind Regards, Justin 1. https://www.apache.org/legal/resolved.html#handling-public-domain-licensed-works 2. https://www.apache.org/legal/resolved.html#category-a

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

Hi, > There is no license header on the file we copied and slightly modified. > > https://github.com/lightbend/paradox/blob/8e30c341f1f8351a19b71599219d2f636ba68eb4/themes/generic/src/main/assets/js/groups.js That contains code from [1] which I thought was licensed under the MPL [2], but it

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

Hi, Sorry but it’s - 1 (binding from me). The source release seems to contain code that is licensed under a Category B Mozilla license and missing headers from files. I checked: - incubating in name - signatures and hashes are fine - DISCLAIMER exists - LICENSE is missing some 3rd party code

Re: Access to Incubator Wiki - Submission of Podling report - Apache Training

Hi, Only PPMC members can edit those pages. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: release votes - should there be a minimum number of days that the vote is open for?

Hi, In general you should wait a minimum of 3 days, but if there an urgent security fix then that can be ignored. 3 days gives people in different time zones or who don’t work full time on the project a chance to respond and be involved in the project. A lot of releases taken more than 3 days.

Re: [CANCEL] [VOTE] Release Apache Pekko(incubating) 1.0.0-RC2

Hi, There’s no need to cancel it - just put it on hold until you get the last needed vote. For the process see [1] - “The vote is successful if there are at least three +1 votes from PPMC members, and more +1 than -1 votes from PPMC members." Kind Regards, Justin 1.

Re: July 2023 Incubator report timeline

Hi, > Hi Justin, SeaTunnel already graduated, are we still need report to > incubator? No you do not need to report. It would be good to update podlings.xml to reflect this. Thanks, Justin - To unsubscribe, e-mail:

July 2023 Incubator report timeline

Hi, https://cwiki.apache.org/confluence/display/INCUBATOR/July2023 Wed July 05 -- Podling reports due by end of day Sun July 09 -- Shepherd reviews due by end of day Sun July 09 -- Summary due by end of day Tue July 11 -- Mentor signoff due by end of day Wed July 12 -- Report

Re: switching Pekko to use the WIP Disclaimer

Hi, Yes, using the work-in-progress disclaimer does give you some leeway. However, it may not be as much as you think. See [1]. Note that issues such as: • Missing ASF headers • 3rd party Category A bundled code licenses not listed in LICENSE • Including uncategorised source code

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

Hi, > Based on concerns from this thread: > https://lists.apache.org/thread/wq3l6y4l4wwl6ngt91ycxll96p62n5g3 (point > number 4) > our Apache Datalab community organized vote in private list for removing > non-active PMC members. > No one from the list of non-active PMC members has reached out

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

Hi, I'm sorry, but your response raises further concerns: - Project communication need to occur on the mailing list, not on other channels. - The "centralized project management system" doesn't seem visible to people outside the project. ASF projects need to operate openly and transparently. -

Re: [VOTE] Graduate Apache DataLab (Incubating) as a Top Level Project

Hi, Sorry, but it's -1 from me. Given the response to my concerns, I think the project needs to reflect on how they fit in with Apache values. I would value input from the project's mentors on where they think the project is and what they need to do to get to the point where they can

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

Hi, I have some minor concerns. If people are working in their own branches, how do people collaborate? How do you know who is working on what and that two people don’t try the fix the same thing? I also see you have a lot of issues marked “waiting for review”. I also noticed that you removed

[jira] [Commented] (INCUBATOR-277) Allow GitHub Actions to create PRs

[ https://issues.apache.org/jira/browse/INCUBATOR-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726120#comment-17726120 ] Justin Mclean commented on INCUBATOR-277: - You'll need to raise a ticket with Infra to help

Re: [VOTE] Release Apache OpenDAL(incubating) 0.34.0-rc1

HI, >> - “incubating" is not in the release name > > Could you please explain the phrase "not in the release name"? Our release > includes the term "incubating," such as > "apache-incubator-opendal-0.34.0-src.tar.gz.” That's “incubator” not “incubating”. Kind Regards, Justin

Re: [VOTE] Release Apache OpenDAL(incubating) 0.34.0-rc1

Hi, >> - Where did these files come from, and how are they licensed?[1][2][3] > > We have drawn them ourselves, and they are all licensed under Apache 2.0. > Should we include any additional notes for them? I’m sorry but a a google image search shows otherwise. From the style (and file names)

Re: [VOTE] Release Apache OpenDAL(incubating) 0.34.0-rc1

Hi, Sorry, but it -1 binding from me, LICENSE and NOTICE need to be corrected and the lease artefacts need incubating in the name. I checked: - “incubating" is not in the release name - signatures and hash are fine - LICENSE and NOTICE are not correct, LICENSE information goes in LICENSE not

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

Hi, > I opened an issue in https://github.com/dermesser/leveldb-rs/issues/26. > The auther confirmed the original and gave some explanation about the > different license. In general if something is ported to anther language it keeps the same license. It this case both licenses are compatible

Re: [VOTE] Release Apache Paimon(incubating) 0.4.0-incubating rc5

Hi, Sorry but it's -1 (binding) from me as LICENSE and NOTICE need a little more work and quite a few sure files are missing ASF headers. I checked: - incubating in name - signature and hash are fine (Although you might want to consider changing your apache id, it's signed with

Re: [VOTE] Release Apache Paimon(incubating) 0.4.0-incubating rc5

HI, > The NOTICE and the copy of LICENSE.scala in paimon-codegen are incorrect due > to https://www.scala-lang.org/news/license-change.html > > I am not sure if this is a blocker or not. I think that can be fixed in a later release, both licenses are compatible with the Apache license so it

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

Hi, I would need to do a review in more detail to find out what should be added to LICENSE (and NOTICE) or if there are any other issues. I can see there further 3rd party software included in your source please than needs to bee mentioned in LICENSE. Re [1] it is under the MIT license but

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

Hi, A search for “General Public License” shows up in these files: ./third_party/wamr.patch ./third_party/rust-sgx-sdk/licenses/LICENSE-tlibc.txt ./third_party/rust-sgx-sdk/licenses/LICENSE-common-inc.txt ./third_party/rust-sgx-sdk/sgx_backtrace/sgx_backtrace_sys/libbacktrace/ltmain.sh

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

Hi, A quick glance at this release shows it still includes GPL licensed software. Anything with that's GPL licensed can't be included in a ASF software release or be a non optional dependancy. What licensing issues were corrected in this release from the previous one? Kind Regards, Justin

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

ttps://lists.apache.org/thread/0979png8rp7jxfdfdzbyptd022y3q8xb. The v0.5.0 > is left untouched in github and removed from teaclave.apache.org. > > Thanks, > He > > On 2023/04/12 04:26:23 Justin Mclean wrote: >> Hi, >> >> Please remove the 0.5.0 download f

Re: [DISCUSS] Graduate Apache SeaTunnel (incubating) as a TLP

ern. It is impossible for new or potential users to your community to discover what happened more than 90 days ago or for the project committers/PPMC to revisit old conversations. Kind Regards, Justin > On 14 Apr 2023, at 3:59 pm, Justin Mclean wrote: > > Hi, > > Also is it a pai

Re: [DISCUSS] Graduate Apache SeaTunnel (incubating) as a TLP

Hi, Also is it a paid version of Slack and if so who pays for it? Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Graduate Apache SeaTunnel (incubating) as a TLP

Hi, > - We created apacheseatunnel.slack.com < http://apacheseatunnel.slack.com/ >> , It is voluntarily managed by PPMC members of the Apache SeaTunnel > (incubating) community. Do all PPMC members have access to manage this slack platform? Kind Regards, Justin

Re: [DISCUSS] Graduate Apache SeaTunnel (incubating) as a TLP

Hi, > To be honest, It is not very convenient to create a seatunnel channel > in asf-slack space, because the time zone is different, I cannot see what the timezone has to do with it. Communication should occur in a way that enables people from all time zones to participate equally. Kind

Re: [DISCUSS] Graduate Apache SeaTunnel (incubating) as a TLP

HI, A few minor things: - The website has no link to the ASF’s privacy policy - The project doesn’t seem to be using the ASF slack - who controls apacheseatunnel.slack.com ? - There doesn’t seem to be much conversation on the mailing list - The project may have

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Hi, Please remove the 0.5.0 download from this page https://teaclave.apache.org/download/ . You cannot put unreleased software on your download page. Justin

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Hi, I‘ll also note that the code contains code under the GPL license, and you are not abiding by the arms of the license or informing your users of this. GPL code is considered category X and cannot be included in a source release. This issue and the compiled code issues were pointed out

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

HI, -1 (binding) due to compiled code in the source release. I checked: - incubating in name - signature and hashes are fine - WIP disclaimer exists - LICENSE needs work - Unexpected binary files in release. This includes multiple .wasm and .exe files. - ASF header on ASF files but hard to

Re: A little incubator game

HI, > I liked your original version better. This version never offers to make a > frickin’ release. I changed it so that making a release was easier, it may be that you didn’t have many active contributors/committers because a company stopped contributing to your project? It will tell you

Re: A little incubator game

Hi, I made a few improvements (you many need to to a shift refresh to get the latest changes). Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: A little incubator game

Hi, Internally the game tracks: - Interest in the project - Company committer membership. You'll note the starting message is slightly different depending on the company contributor mix you have. Mentors will also give you advice around the diversity of your committer base (in terms of

Re: A little incubator game

Hi, > I could not figure out how to make a release… In order to make a release you need to work on the code creating features or fixing bugs. The more active committers you have you less time it takes to make a release. Depending on how you start out, the better strategy may be to generate

Re: A little incubator game

Apache > foundation and incubator. > > My favorite part of the game is when you keep clicking on “work on the > code” and the months pass by with no releases or new committers. > > Good thinking and +1 to you, Justin. > > On Mon, Apr 3, 2023 at 5:07 PM Justin Mclean >

Re: A little incubator game

Hi, Maybe some of the Twinery comments could be displayed, or the mentor output > displayed in a div on the page without having to click there separately? > That was done on purpose to show you need to engage with your mentors. kind regards, Justin >

Re: A little incubator game

be displayed, or the mentor output > displayed in a div on the page without having to click there separately? > > Also - you're missing filing incubator reports, I think? > > On Mon, Apr 3, 2023 at 3:07 PM Justin Mclean > wrote: > > > Hi, > > > > A work in pro

A little incubator game

Hi, A work in progress, so there may be spelling errors and bugs. Just like in real life, the game ends when you stop playing it but things can happen to you along the way. http://incubator-game.s3-website-us-east-1.amazonaws.com Made using an open source engine https://twinery.org, the

Re: Confluence wiki page gives "Unknown macro: markdown"

Hi, The report has been edited so it is now malformed I’ve reverted it to a previous version. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: [MENTORS] March 2023 Incubator report timeline

Hi, Podlings that are expected to report are: Baremaps Kie Marvin-AI Nemo Nlpcraft Opendal Pagespeed Spot Toree Training Uniffle Wayang Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org

[MENTORS] March 2023 Incubator report timeline

Hi, Sorry the delay in sending this out but here are the dates for March. 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 -- Mentor signoff due by end of day Wed March 08 --

Re: [Question] LimitedInputStream license issue in Spark source.

Hi, The issue is not the original header it is the addition of the ASF header. The ASF header states "Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.” I ‘m not sure this is true with this file even though both Spark and this file are under the

Re: Seeking ASF Champion for a New ASF “podling”

Hi, For top level project the ASF requires a minimum of 3 PMC member to provide oversight. is there someone else you think can help in providing oversight and manage the direction of the project? Kind Regards, Justin - To

Re: Seeking ASF Champion for a New ASF “podling”

Hi, Trying to incubate a project and grow a community at the same time can be difficult. We tend to prefer projects with an existing community, but that doesn’t rule out the project becoming an incubating project. Is there some way you can encourage users to become more involved in the

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

Hi, It looks like Spark may have incorrectly added that header. You could ask them why it was added perhaps or just leave it as is. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For

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

HI, > 4. People you have noticed help us by consulting about new features, > architecture, and other improvements. > And actually some of them are not very active now. Should we remove them from > PPMC members before the graduation process? Perhaps best approach is to ask these people if

Re: [DISCUSS] Incubating Proposal for Paimon

pache.org/thread/h3hkvt3nq9gfblt3k0w2pr6xrg54pqxt > [2] https://lists.apache.org/thread/hgpcg6mhhoblzbnh1opkrxynmc93vxzp > [3] https://www.mail-archive.com/hbase-dev@hadoop.apache.org/msg18236.html > [4] > > https://cwiki.apache.org/confluence/display/HADOOP/Ozone+Hadoop+subproject+to+Apache+TLP+proposal >

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

Hi, +1 (binding) I checked: - incubating in the name - signature and hashes are fine - DISCLAIMER exists - LICENSE and NOTICE are fine - No unexpected binary files - ASF headers on source files - Can compile from source I dislike "Copyright 2014 and onwards", but that's Spark's issue, not

Re: [DISCUSS] Incubating Proposal for Paimon

Hi, Given that most of the people involved are familiar with the ASF and how projects should operate, I wonder if you should not just become a subproject of Fink or a separate TLP? Are there any reasons you think the project needs to go through incubation? Kind Regards, Justin

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

Hi, Thanks for the resolution. There are a few issues I've noticed: - One minor thing in your website footer mentions the "DataLab feather logo", which AFAICS doesn't exist. - Your last committer was added last July and your last PMC member was almost a year ago. Do you have plans to add any

Re: [VOTE] Retire Marvin-AI from Incubator

HI, +1 (binding) Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: Seeking ASF Champion for a New ASF “podling”

HI, Can you tell us a bit more about activity on the project? From [1] I can see the project doesn’t seems less active than it once was there seems to be only one person who is currently contributing. In general we prefer incubating projects that already have a community around them. What are

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

Hi, I ‘m sorry but this vote has not passed yet. you need 3 +1 votes from IPMC members. Kind Regards, Justin > On 23 Feb 2023, at 4:25 am, Sergey Kamov wrote: > > NLPCraft-ers, > The vote for Apache NLPCraft (incubating) release version 1.0.0 is closed > now. > Vote result: The vote PASSES

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

Hi, > It can be a case of The Ship of Theseus. When you take a look at the issued > files[1][2], you may find a commit history touching them and modifying > them. Anyway, it's not an identical copy or one-shot translation. This has been discussed many times on various lists, translating an

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

Hi, In general porting a file from one language to another would not change the original license. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: [QUESTION] are binary distributions/releases required?

HI, > I'm struggling to find any examples of ASF jars pushed to maven > central that have anything other than the standard boilerplate Apache > LICENSE and NOTICE. Having a transitive dependency on another jar > doesn't appear to be mentioned in any jar LICENSE/NOTICE that I > checked. See [1].

Re: [QUESTION] are binary distributions/releases required?

Hi, Those jars are likely to have different LICENSE and NOTICE files so I would suggest you vote on both at the same time. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC3

HI, > Do you mean that: all frontend dependencies' licenses need to included in > binary license file ( /LICENSE), right? Just a note it’s not all dependancies that need to be listed but only what is included in the release see [1] Kind Regards, Justin 1.

<    1   2   3   4   5   6   7   8   9   10   >