Re: Very strange (AI generated) issues

Hi, Given what I read about the company, they will most likely ignore you. Some people think the company is a scam, and they seem to engage in unethical business practices. Kind Regards, Justin

Re: Contributor guidelines for becoming a committer

Hi, From a quick glance, this seems far too focused on code contributions. Remember, people can become committers from non-code contributions. A committer is someone that is committed to the project and may not review or write code. It would also be good to set some expectations around the amou

Re: [DISCUSS] Release source and binary verification

Hi, > Just to clarify that we're currently not adding the gradle wrapper in the > source distribution. We have some custom code > > for that exact reason that downloads the gradle wrapper if it's m

Re: [DISCUSS] Release source and binary verification

Hi, > I would add an additional check on the source distribution: the source > distribution should not contain any unexpected binary file (gradle > wrapper is OK, but other binary should be avoided). It’s not OK to include the gradle wrapper in the source release. A source release can't include

Re: Meeting time for catalog community sync

Hi, Rather than a set time, alternating the time might be beneficial for people in other time zones. I can’t attend the current one as it is on at 2am in the morning local time. I’m sure others have the same issue. Justin

Time of community sync

Hi, I noticed the community service is on at a similar time each time, which unfortunately is 2am my local time. Have you considered staggering the time of this meetup so that people from other time zones can attend? Kind Regards, Justin

Re: [Discussion] Apache Iceberg Community Guideline - Initial Version

e document title from "guidelines" back to "bylaws". Thanks for > pointing this out Carl! > > I have also updated the document with a few suggested edits from some people, > please let me know what everyone thinks! > > -Jack > > > On Wed, Jul 3, 202

Re: [Discussion] Apache Iceberg Community Guideline - Initial Version

HI, For some historical context, it used to be that the board / Incubator asked projects to have a set of bylaws when they graduated. This fell out of favour more than ten years ago, and projects were expected to follow documented policy. Before this, things were not as well documented, so we a

Re: Feedback Collection: Bylaws in Iceberg

HI, > This was in response to the discussion on emeritus, looks like Jack already > took this into account in the latest proposal, so it is ok with me. I'm > still for tracking emeritus status, as in the long run more PMC's naturally > become inactive and it is harder to pass a majority vote.

Re: [VOTE] Release Apache PyIceberg 0.6.1rc1

Hi, > I think you are right, some 3rd parties (including Apache projects) > are missing in the NOTICE file (you and I already mentioned that in a > previous release). We should at least mention this. I pointed Apache > Karaf NOTICE as example. This is the problem when people copy what other proje

Re: [VOTE] Release Apache PyIceberg 0.6.1rc1

Hi, If you were wondering where all of this comes from, it is from section 4/4d of the Apache license. Kind Regards, Justin

Re: [VOTE] Release Apache PyIceberg 0.6.1rc1

Hi, See [1] for why that NOTCE copyright line should be considered -"though the ASF copyright line and any other portions of NOTICE must be considered for propagation.” Kind Regards, Justin 1. https://infra.apache.org/licensing-howto.html#bundle-asf-product

Re: [VOTE] Release Apache PyIceberg 0.6.1rc1

Hi, You may not be aware that I have voted on 1,000+ releases and helped refine and improve ASF policy on this over the years. I also hold a number of other relevant ASF roles. > There are two main issues with the presented arguments: > > 1. This isn't a bundled dependency, it is an attributio

Re: [VOTE] Release Apache PyIceberg 0.6.1rc1

file. Kind Regards, Justin > On 5 Apr 2024, at 12:58 pm, Justin Mclean wrote: > > HI, > >> The ASF recommendation also clearly states: "Under normal circumstances, >> there is no need to modify NOTICE to mention a bundled dependency." > > If you read that

Re: [VOTE] Release Apache PyIceberg 0.6.1rc1

HI, > The ASF recommendation also clearly states: "Under normal circumstances, > there is no need to modify NOTICE to mention a bundled dependency." If you read that document carefully, it states this: - Under normal circumstances, there is no need to modify NOTICE to mention a bundled dependen

Re: [VOTE] Release Apache PyIceberg 0.6.1rc1

HI, Thanks for that. I don't understand "we don't bundle the code, but just took some part of it”. Either the code is in the source release or not in the source release; if any part of it is in the source release, then it is bundled. The LICENSE and NOTICE files need to relate to what is includ

Re: [VOTE] Release Apache PyIceberg 0.6.1rc1

Hi, I took a look at this, and the NOTICE file doesn't include the required information from the included Apache projects NOTICE files [1] Kind Regards, Justin 1. https://infra.apache.org/licensing-howto.html#alv2-dep

Re: [VOTE] Release Apache PyIceberg 0.6.0rc4

HI, > For the Thrift and Hive ones, we have an optional dependency that ships the > content under the vendor/ directory: > https://github.com/apache/iceberg-python/tree/main/vendor These are the > Python Thrift code for talking Thrift to the Hive metastore. Both the Hive > and Thrift NOTICES a

Re: [VOTE] Release Apache PyIceberg 0.6.0rc4

Hi, > However, I don't think the notice for thrift or hive needs to be included. > The license file states that the project uses the thrift definitions, but it > does not include them in the project or dependencies. There are no direct > artifacts from those projects. Since nothing is bundle

Re: [VOTE] Release Apache PyIceberg 0.6.0rc4

Hi, Sure, the LICENSE file says it includes code from other ASF projects i.e. Avro, Thrift and Hive. All of these have NOTICE files [1][2][3]. The content from those files (or rather a subset) needs to be included in this releases NOTICE fle. Kind Regards, Justin 1. https://github.com/apache

Re: [VOTE] Release Apache PyIceberg 0.6.0rc4

Hi, I checked the release and found: - signatures and hashes are fine - LICENSE is fine - NOTICE is missing content from NOTICE of bundled code NOTICE files - All files have ASF headers - No unexpected binary files With a NOTICE file, you need to include the relevant parts in your NOTCE file if

Gravitino an Iceberg REST catalog service

Hi, We open-sourced a new project, Gravitino, in December and have been working on growing the community and adding new functionality. We plan to donate the project to the ASF this year. Gravitino is a unified metadata lake solution offering a unified approach to managing datasets from diverse

Re: Iceberg 0.12 release ETA

Hi, > Who is "they"? It doesn't sound like you're speaking for yourself here. I was unable to find that information. I'm assuming that if I couldn't, then others may have the same issue. Sure, people who know where it is won't have any problems, but perhaps consider new people to the project an

Re: Iceberg 0.12 release ETA

HI, > Unfortunately, the sync has not been brought back to the mailing list yet… > until now! > > https://docs.google.com/document/d/1YuGhUdukLP5gGiqCbk0A5_Wifqe2CZWgOd3TbhY3UQg/edit A link to a google document is probably not ideal for a number of reasons, people need a google account(?) and i

Re: Iceberg 0.12 release ETA

Hi, > We haven't set a date for the 0.12 release yet, but we're going to be > discussing this in the Iceberg sync tomorrow if you'd like to join. Was what was discussed at the sync brought back to the mailing list? Remember not everyone in your community can attend synchronous meetings and may m

Re: PPMC report for April 2020

Hi, > I tried several times to fix it and I wasn't able to find what was wrong. It > looks fine in the editor, so I think it should be okay for the actual report. It will show like that in the actual report, so no it’s not really okay. If I get time I’ll take a look later today (my time that is

Re: PPMC report for April 2020

Hi, The format of your report is broken (new line issues?) Can you please correct ASAP. Thanks, Justin

Re: Podling Iceberg Report Reminder - January 2020

Hi, Just a friendly reminder the report is due today is anyone working on it? Thanks, Justin

Re: [DISCUSS] September report

Hi, I can a couple of concern about the report, first off I don't think any project would be ready to graduate if they have not made a release or added committers/PPMC members. And it would be grate to see some something other than meaningless stats on community growth in the report. Those numb

Re: IPMC report draft for July 2019

Hi, Anyone? This needs to be fixed before the report can be submitted. Thanks, Justin

Re: IPMC report draft for July 2019

Hi, Thanks for submitting the report, but can you please fix up the format of the report. The new report format is in markdown format (as requested by the board) and it seem you have removed all of thr formatting. Thanks, Justin

Re: IPMC report for March 2019

Hi, Thanks for the report but I would rather you didn't submit reports after been told to report next month. I'll let it pass this time but please in further get the report in before the date it is due. Thanks, Justin

Re: Podling Report Reminder - March 2019

Hi, Just a reminder that this is due today and you can fill out the report here. [1] If for some reason you can't submit the report on time you be asked to report next month. Thanks, Justin 1. https://wiki.apache.org/incubator/March2019

Incubator Podling Report (Due 6th February)

Hi, The incubator PMC would appreciated if you could complete the podling report on time it's due on 6th February in a few days. It's best if you discuss the contents of the report on the list a week before it is due and work collaboratively on it before submitting it. It takes time to prepare

Re: [DISCUSS] Draft report for January 2019

Hi, You were asked to report next month not submit a late report. Submitting a report ofter both the deadline for submission and mentor signoff is not acceptable. Thanks, Justin

Re: Incubator Podling Report (Due 2nd January)

HI, The deadline has come and gone and you will be asked to report again next month. Please don't miss this one. Thanks, Justin (V.P Incubator)

Re: Incubator Podling Report (Due 2nd January)

Hi, Just a reminder that the report is due today. [1] If you can't report this month you will asked to report next month. Thanks, Justin 1. https://wiki.apache.org/incubator/January2019

Incubator Podling Report (Due 2nd January)

Hi, The incubator PMC would appreciated if you could complete the podling report on time it's due on 2nd January in a few days. It takes time to prepare the incubator report, have your mentors sign off the report and for the board to review it, so it's best if you can get it in early. Thanks,

Incubator Podling Report (Due 5th December)

Hi, The incubator PMC would appreciated if you could complete the podling report on time it's due on 5th December in a few days. It takes time to prepare the incubator report, have your mentors sign off the report and for the board to review it, so it's best if you can get it in early. Thanks,

Podling Report Reminder - December 2018

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 19 December 2018, 10:30 am PDT. The report for your podling will for