Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

2021-06-11 Thread Sheng Wu
Hi Pinot community

Glad and congrats you made this.
I did a review of your discussion thread, but I can't find the
decision process about PMC and V.P. candidates.
Could you share more context about this?
I can see you have a diversity committer list, should they be
considered as a PMC member during graduation?

Sheng Wu 吴晟
Twitter, wusheng1108

Jean-Baptiste Onofre  于2021年6月12日周六 下午12:31写道:
>
> +1 (binding)
>
> Regards
> JB
>
> > Le 11 juin 2021 à 17:57, Felix Cheung  a écrit :
> >
> > +1
> >
> > On Fri, Jun 11, 2021 at 4:18 AM Xun Liu  wrote:
> >
> >> +1
> >> Pinot is an open source project with a broad user base, and the community
> >> is also very active.
> >>
> >> Best regards
> >> Xun Liu
> >>
> >> On Fri, Jun 11, 2021 at 7:16 PM Xun Liu  wrote:
> >>
> >>> Pinot is an open source project with a broad user base, and the community
> >>> is also very active.
> >>>
> >>> On Fri, Jun 11, 2021 at 6:29 PM Jim Jagielski  wrote:
> >>>
>  +1 (binding)
> 
> > On Jun 10, 2021, at 7:12 PM, Mayank Shrivastava 
>  wrote:
> >
> > Hi all,
> >
> > After a discussion with the community [1], voting [2], and a positive
>  vote result [3],
> > we believe Apache Pinot (Incubating) is ready for graduation to a TLP,
> > and we'd like to bring it up in discussion with the IPMC.
> >
> > To list a few of the community's achievements:
> >
> > 7800+ contributions from 168 contributors
> > 7 releases by various release managers
> > 6 new committers and 2 new PPMCs invited (all accepted)
> > Diverse committers and PPMCs (from 7 companies/institutes)
> > Apache website setup [4]
> > Dev conversations at d...@pinot.apache.org  >> d...@pinot.apache.org>
> > Assessed ourselves against the Apache Project maturity matrix [5]
> > We have built a meritocratic and open collaborative process (the
> >> Apache
>  way)
> >
> > [1] Community Discussion for Graduation <
> 
> >> https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E
> >
> > [2] Voting Thread <
> 
> >> https://lists.apache.org/thread.html/r9ca0b2ccc9b0fbdbee6a09aaf06b36ffd3a20e9cc1b810cdbe7c65d6%40%3Cdev.pinot.apache.org%3E
> >
> > [3] Voting Result <
> 
> >> https://lists.apache.org/thread.html/rc371ca50ce8ff2d6c0b068165195526cfdbd08d915105573e17042d2%40%3Cdev.pinot.apache.org%3E
> >
> > [4] https://pinot.incubator.apache.org/ <
>  https://pinot.incubator.apache.org/>
> > [5] Maturity Model Assessment <
> 
> >> https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot
> >
> > Please see the proposed board resolution below and let us know what
> >> you
> > think.
> >
> > The discussion will remain open for at least 72 hours.
> >
> > ---
> >
> > Establish the Apache Pinot Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests
> >> of
>  the Foundation and consistent with the Foundation's purpose to
> >> establish a
>  Project Management Committee charged with the creation and maintenance
> >> of
>  open-source software, for distribution at no charge to the public,
> >> related
>  to a distributed data integration framework that simplifies common
> >> aspects
>  of big data integration such as data ingestion, replication,
> >> organization
>  and lifecycle management for both streaming and batch data ecosystems.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>  (PMC), to be known as the "Apache Pinot Project", be and hereby is
>  established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Pinot Project be and hereby is responsible
>  for the creation and maintenance of software related to distributed OLAP
>  data store to provide Real-time Analytics to power wide variety of
>  analytical use case; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Pinot" be and
>  hereby is created, the person holding such office to serve at the
> >> direction
>  of the Board of Directors as the chair of the Apache Pinot Project, and
> >> to
>  have primary responsibility for management of the projects within the
> >> scope
>  of responsibility of the Apache Pinot Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
>  appointed to serve as the initial members of the Apache Pinot Project:
> > Felix Cheung mailto:felixche...@apache.org>>
> > Jackie Jiang mailto:jac...@apache.org>>
> > Jim Jagielski mailto:j...@apache.org>>
> > Kishore G mailto:kisho...@apache.org>>
> > Mayank Shrivastava mailto:maya...@apache.org>>
> > Neha Pawar mailto:nehapa...@apache.org>>
> > Olivier Lamy 

Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

2021-06-11 Thread Jean-Baptiste Onofre
+1 (binding)

Regards
JB

> Le 11 juin 2021 à 17:57, Felix Cheung  a écrit :
> 
> +1
> 
> On Fri, Jun 11, 2021 at 4:18 AM Xun Liu  wrote:
> 
>> +1
>> Pinot is an open source project with a broad user base, and the community
>> is also very active.
>> 
>> Best regards
>> Xun Liu
>> 
>> On Fri, Jun 11, 2021 at 7:16 PM Xun Liu  wrote:
>> 
>>> Pinot is an open source project with a broad user base, and the community
>>> is also very active.
>>> 
>>> On Fri, Jun 11, 2021 at 6:29 PM Jim Jagielski  wrote:
>>> 
 +1 (binding)
 
> On Jun 10, 2021, at 7:12 PM, Mayank Shrivastava 
 wrote:
> 
> Hi all,
> 
> After a discussion with the community [1], voting [2], and a positive
 vote result [3],
> we believe Apache Pinot (Incubating) is ready for graduation to a TLP,
> and we'd like to bring it up in discussion with the IPMC.
> 
> To list a few of the community's achievements:
> 
> 7800+ contributions from 168 contributors
> 7 releases by various release managers
> 6 new committers and 2 new PPMCs invited (all accepted)
> Diverse committers and PPMCs (from 7 companies/institutes)
> Apache website setup [4]
> Dev conversations at d...@pinot.apache.org > d...@pinot.apache.org>
> Assessed ourselves against the Apache Project maturity matrix [5]
> We have built a meritocratic and open collaborative process (the
>> Apache
 way)
> 
> [1] Community Discussion for Graduation <
 
>> https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E
> 
> [2] Voting Thread <
 
>> https://lists.apache.org/thread.html/r9ca0b2ccc9b0fbdbee6a09aaf06b36ffd3a20e9cc1b810cdbe7c65d6%40%3Cdev.pinot.apache.org%3E
> 
> [3] Voting Result <
 
>> https://lists.apache.org/thread.html/rc371ca50ce8ff2d6c0b068165195526cfdbd08d915105573e17042d2%40%3Cdev.pinot.apache.org%3E
> 
> [4] https://pinot.incubator.apache.org/ <
 https://pinot.incubator.apache.org/>
> [5] Maturity Model Assessment <
 
>> https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot
> 
> Please see the proposed board resolution below and let us know what
>> you
> think.
> 
> The discussion will remain open for at least 72 hours.
> 
> ---
> 
> Establish the Apache Pinot Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests
>> of
 the Foundation and consistent with the Foundation's purpose to
>> establish a
 Project Management Committee charged with the creation and maintenance
>> of
 open-source software, for distribution at no charge to the public,
>> related
 to a distributed data integration framework that simplifies common
>> aspects
 of big data integration such as data ingestion, replication,
>> organization
 and lifecycle management for both streaming and batch data ecosystems.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
 (PMC), to be known as the "Apache Pinot Project", be and hereby is
 established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache Pinot Project be and hereby is responsible
 for the creation and maintenance of software related to distributed OLAP
 data store to provide Real-time Analytics to power wide variety of
 analytical use case; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Pinot" be and
 hereby is created, the person holding such office to serve at the
>> direction
 of the Board of Directors as the chair of the Apache Pinot Project, and
>> to
 have primary responsibility for management of the projects within the
>> scope
 of responsibility of the Apache Pinot Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are
 appointed to serve as the initial members of the Apache Pinot Project:
> Felix Cheung mailto:felixche...@apache.org>>
> Jackie Jiang mailto:jac...@apache.org>>
> Jim Jagielski mailto:j...@apache.org>>
> Kishore G mailto:kisho...@apache.org>>
> Mayank Shrivastava mailto:maya...@apache.org>>
> Neha Pawar mailto:nehapa...@apache.org>>
> Olivier Lamy mailto:ol...@apache.org>>
> Seunghyun Lee mailto:sn...@apache.org>>
> Siddharth Teotia mailto:siddteo...@apache.org
 
> Subbu Subramaniam mailto:mcvsu...@apache.org>>
> Xiang Fu mailto:xian...@apache.org>>
> 
> 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
 appointed to the office of Vice President, Apache Pinot, to serve in
 accordance with and subject to the direction of the Board of Directors
>> and
 the Bylaws of the Foundation until death, resignation, retirement,
>> removal
 of disqualification, or until a successor is appointed; 

Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-11 Thread Justin Mclean
Hi,’

Perhaps this will help: A software grant / initial donation consists of a set 
of files, their 3rd party headers will be replaced with ASF ones and that noted 
in the NOTICE file. If any other files 3rd party files, were then copied into 
the same ASF repo they should retain their original 3rd party header and their 
details mention in LICENSE. This may also requires some changes to NOTICE but 
these would be different to changed needed from the initial donation.

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



Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-11 Thread Justin Mclean
Hi,

> Well Justin, these files are typically generated by our software.  It would
> not be OK to force the license into all files since that wouldn't be
> appropriate and right since we don't force Apache copyright on the work of
> others.

The ASF header doesn’t include a copyright line and the ALv2 license doesn’t 
ask to transfer copyright so I’m not sure what you mean by the above. If those 
files are in an ASF repo they they need to be (in general) covered by a 
software grant, ICLA, CCLA etc or be 3rd party file with a compatible license. 
What you say above suggests they are actually 3rd party files, the work of 
others outside the project?  If they are 3rd party files then that should be 
made clear. [2]

>  Without that possibility we're down to manually editing the files
> every time they are created or modified in the slightest.  I don't see that
> as a valid option.

I would assume whatever generates them can generate them with a header? Are all 
of these files generated or not?

> That evaluation was made before.  Now it just feels like one more rule we
> have to deal with that just comes out of the blue.

Can you please point me to this conversation on your mailing list as I was 
unable to find it. I did find this [1]

Thanks,
Justin

1. 
https://lists.apache.org/thread.html/rdb61e0df4ac921dc3af3e71b7971a20e9222016d9c02244bccfb3892%40%3Cdev.hop.apache.org%3E
2. https://www.apache.org/legal/src-headers.html#3party
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-11 Thread Justin Mclean
Hi,

> It wasn't part of the software grant so we were just following the bundling
> apache licensed 2.0 code route as explained here [1].

See [1] "However, for completeness it is useful to list the products and their 
versions, as is done for products under other licenses.” Common practice is 
that you list any ALv2 licensed code in your LICENSE file. Also if the code 
base if came from has a NOTICE file you may need to alter your NOTICE file as 
well. Can you point to the code base / repository it come from?

It still seems odd to me that only this one file has come across in this 
fashion, all of those files in that directory didn’t exist in the previous 
release where did they come from? Have their headers been altered?

Thanks,
Justin

1. https://infra.apache.org/licensing-howto.html#alv2-dep


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



[RESULT] [VOTE] Release Apache NLPCraft (incubating) v 0.8.0

2021-06-11 Thread Aaron Radzinski
Hi,
The vote to release Apache NLPCraft (incubating) 0.8.0 has passed with
3 +1 binding votes.

[2] +1 Non-binding votes:
 - Xun Liu
 - Chao Zhang

[3] +1 Binding votes:
- Paul King
- Furkan KAMACI
- Juan Pan

[ 0 ] +0  Binding votes
[ 0 ] -1  Binding votes

The vote was successful.

Thank you to the above IPMC members for taking the time to review and
provide guidance on our release!

We will proceed with publishing the approved artifacts and sending out the
appropriate announcements in the coming days.

On behalf of the NLPCraft community,
--
Aaron.


On Wed, Jun 9, 2021 at 6:37 AM Paul King  wrote:
>
> +1 (binding) carrying over my dev vote
>
> 
> Virus-free.
> www.avast.com
> 
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Wed, Jun 9, 2021 at 2:39 AM Aaron Radzinski 
> wrote:
>
> > Hello all,
> > This is a call for a vote to release Apache NLPCraft (incubating)
> > version 0.8.0. Apache NLPCraft is a library for adding a natural
> > language interface to any application.
> >
> > The Apache NLPCraft community has voted on and approved a proposal to
> > release Apache NLPCraft (Incubating) version 0.8.0. We would like to
> > request the Incubator PMC members review and vote on this incubator
> > release.
> >
> > Release information:
> > 1. PPMC vote result thread:
> > https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202106.mbox/
> > 
> > 2. Release location:
> > https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/0.8.0/
> > 3. Git tag: https://github.com/apache/incubator-nlpcraft/tree/v0.8.0
> > 4. JIRA issues fixed in release:
> > https://issues.apache.org/jira/projects/NLPCRAFT/versions/12350193
> > 5. KEYS file:
> > https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
> >
> > PPMC vote has already provided a required majority approval and
> > therefore this vote is a lazy consensus vote open for 72 hours.
> >
> > Please vote accordingly:
> > +1 approve
> > +0 no opinion
> > -1 disapprove with the reason
> >
> > Thank you,
> > Aaron.
> > ---
> > On behalf of NLPCraft community
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

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



Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

2021-06-11 Thread Atri Sharma
+1 (binding)

On Fri, Jun 11, 2021 at 4:42 AM Mayank Shrivastava  wrote:
>
> Hi all,
>
> After a discussion with the community [1], voting [2], and a positive vote
> result [3],
>
> we believe Apache Pinot (Incubating) is ready for graduation to a TLP,
>
> and we'd like to bring it up in discussion with the IPMC.
>
> To list a few of the community's achievements:
>
>
>-
>
>7800+ contributions from 168 contributors
>-
>
>7 releases by various release managers
>-
>
>6 new committers and 2 new PPMCs invited (all accepted)
>-
>
>Diverse committers and PPMCs (from 7 companies/institutes)
>-
>
>Apache website setup [4]
>-
>
>Dev conversations at d...@pinot.apache.org
>-
>
>Assessed ourselves against the Apache Project maturity matrix [5]
>-
>
>We have built a meritocratic and open collaborative process (the Apache
>way)
>
>
> [1] Community Discussion for Graduation
> 
>
> [2] Voting Thread
> 
>
> [3] Voting Result
> 
>
> [4] https://pinot.incubator.apache.org/
>
> [5] Maturity Model Assessment
> 
>
> Please see the proposed board resolution below and let us know what you
>
> think.
>
> The discussion will remain open for at least 72 hours.
>
> ---
>
> Establish the Apache Pinot Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of the
> Foundation and consistent with the Foundation's purpose to establish a
> Project Management Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the public, related
> to a distributed data integration framework that simplifies common aspects
> of big data integration such as data ingestion, replication, organization
> and lifecycle management for both streaming and batch data ecosystems.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Pinot Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Pinot Project be and hereby is responsible for
> the creation and maintenance of software related to distributed OLAP data
> store to provide Real-time Analytics to power wide variety of analytical
> use case; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Pinot" be and hereby
> is created, the person holding such office to serve at the direction of the
> Board of Directors as the chair of the Apache Pinot Project, and to have
> primary responsibility for management of the projects within the scope of
> responsibility of the Apache Pinot Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Pinot Project:
>
>-
>
>Felix Cheung 
>-
>
>Jackie Jiang 
>-
>
>Jim Jagielski 
>-
>
>Kishore G 
>-
>
>Mayank Shrivastava 
>-
>
>Neha Pawar 
>-
>
>Olivier Lamy 
>-
>
>Seunghyun Lee 
>-
>
>Siddharth Teotia 
>-
>
>Subbu Subramaniam 
>-
>
>Xiang Fu 
>
>
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
> appointed to the office of Vice President, Apache Pinot, to serve in
> accordance with and subject to the direction of the Board of Directors and
> the Bylaws of the Foundation until death, resignation, retirement, removal
> of disqualification, or until a successor is appointed; and be it further
>
> RESOLVED, that the Apache Pinot Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Pinot podling; and be
> it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pinot podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
>
> ---
>
>
> Thanks,
> Mayank

-- 
Regards,

Atri
Apache Concerted

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



Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

2021-06-11 Thread Felix Cheung
+1

On Fri, Jun 11, 2021 at 4:18 AM Xun Liu  wrote:

> +1
> Pinot is an open source project with a broad user base, and the community
> is also very active.
>
> Best regards
> Xun Liu
>
> On Fri, Jun 11, 2021 at 7:16 PM Xun Liu  wrote:
>
> > Pinot is an open source project with a broad user base, and the community
> > is also very active.
> >
> > On Fri, Jun 11, 2021 at 6:29 PM Jim Jagielski  wrote:
> >
> >> +1 (binding)
> >>
> >> > On Jun 10, 2021, at 7:12 PM, Mayank Shrivastava 
> >> wrote:
> >> >
> >> > Hi all,
> >> >
> >> > After a discussion with the community [1], voting [2], and a positive
> >> vote result [3],
> >> > we believe Apache Pinot (Incubating) is ready for graduation to a TLP,
> >> > and we'd like to bring it up in discussion with the IPMC.
> >> >
> >> > To list a few of the community's achievements:
> >> >
> >> > 7800+ contributions from 168 contributors
> >> > 7 releases by various release managers
> >> > 6 new committers and 2 new PPMCs invited (all accepted)
> >> > Diverse committers and PPMCs (from 7 companies/institutes)
> >> > Apache website setup [4]
> >> > Dev conversations at d...@pinot.apache.org  d...@pinot.apache.org>
> >> > Assessed ourselves against the Apache Project maturity matrix [5]
> >> > We have built a meritocratic and open collaborative process (the
> Apache
> >> way)
> >> >
> >> > [1] Community Discussion for Graduation <
> >>
> https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E
> >> >
> >> > [2] Voting Thread <
> >>
> https://lists.apache.org/thread.html/r9ca0b2ccc9b0fbdbee6a09aaf06b36ffd3a20e9cc1b810cdbe7c65d6%40%3Cdev.pinot.apache.org%3E
> >> >
> >> > [3] Voting Result <
> >>
> https://lists.apache.org/thread.html/rc371ca50ce8ff2d6c0b068165195526cfdbd08d915105573e17042d2%40%3Cdev.pinot.apache.org%3E
> >> >
> >> > [4] https://pinot.incubator.apache.org/ <
> >> https://pinot.incubator.apache.org/>
> >> > [5] Maturity Model Assessment <
> >>
> https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot
> >> >
> >> > Please see the proposed board resolution below and let us know what
> you
> >> > think.
> >> >
> >> > The discussion will remain open for at least 72 hours.
> >> >
> >> > ---
> >> >
> >> > Establish the Apache Pinot Project
> >> >
> >> > WHEREAS, the Board of Directors deems it to be in the best interests
> of
> >> the Foundation and consistent with the Foundation's purpose to
> establish a
> >> Project Management Committee charged with the creation and maintenance
> of
> >> open-source software, for distribution at no charge to the public,
> related
> >> to a distributed data integration framework that simplifies common
> aspects
> >> of big data integration such as data ingestion, replication,
> organization
> >> and lifecycle management for both streaming and batch data ecosystems.
> >> >
> >> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >> (PMC), to be known as the "Apache Pinot Project", be and hereby is
> >> established pursuant to Bylaws of the Foundation; and be it further
> >> >
> >> > RESOLVED, that the Apache Pinot Project be and hereby is responsible
> >> for the creation and maintenance of software related to distributed OLAP
> >> data store to provide Real-time Analytics to power wide variety of
> >> analytical use case; and be it further
> >> >
> >> > RESOLVED, that the office of "Vice President, Apache Pinot" be and
> >> hereby is created, the person holding such office to serve at the
> direction
> >> of the Board of Directors as the chair of the Apache Pinot Project, and
> to
> >> have primary responsibility for management of the projects within the
> scope
> >> of responsibility of the Apache Pinot Project; and be it further
> >> >
> >> > RESOLVED, that the persons listed immediately below be and hereby are
> >> appointed to serve as the initial members of the Apache Pinot Project:
> >> > Felix Cheung mailto:felixche...@apache.org>>
> >> > Jackie Jiang mailto:jac...@apache.org>>
> >> > Jim Jagielski mailto:j...@apache.org>>
> >> > Kishore G mailto:kisho...@apache.org>>
> >> > Mayank Shrivastava mailto:maya...@apache.org>>
> >> > Neha Pawar mailto:nehapa...@apache.org>>
> >> > Olivier Lamy mailto:ol...@apache.org>>
> >> > Seunghyun Lee mailto:sn...@apache.org>>
> >> > Siddharth Teotia mailto:siddteo...@apache.org
> >>
> >> > Subbu Subramaniam mailto:mcvsu...@apache.org>>
> >> > Xiang Fu mailto:xian...@apache.org>>
> >> >
> >> >
> >> >
> >> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
> >> appointed to the office of Vice President, Apache Pinot, to serve in
> >> accordance with and subject to the direction of the Board of Directors
> and
> >> the Bylaws of the Foundation until death, resignation, retirement,
> removal
> >> of disqualification, or until a successor is appointed; and be it
> further
> >> >
> >> > RESOLVED, that the Apache Pinot Project be and 

Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-11 Thread Hans Van Akelyen
Hi Justin,

It wasn't part of the software grant so we were just following the bundling
apache licensed 2.0 code route as explained here [1].
No addition to the LICENSE was needed as the code already was Apache 2
licensed. As the necessary mentions already are in our notice file, no
change was needed there either.
Can you elaborate on what isn't done correctly as described in [1]?

Kind Regards,
Hans

[1] https://infra.apache.org/licensing-howto.html

On Fri, 11 Jun 2021 at 14:51, Justin Mclean 
wrote:

> HI,
>
> > That file should be switched to the standard ASF header and is part of
> the
> > original code and covered by the notice file.
>
> Except it wasn’t in the previous release and I assume wasn’t part of the
> original software grant.
>
> Thanks,
> Justin
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-11 Thread Matt Casters
Well Justin, these files are typically generated by our software.  It would
not be OK to force the license into all files since that wouldn't be
appropriate and right since we don't force Apache copyright on the work of
others.  Without that possibility we're down to manually editing the files
every time they are created or modified in the slightest.  I don't see that
as a valid option.
So I guess those are good reasons why.
That evaluation was made before.  Now it just feels like one more rule we
have to deal with that just comes out of the blue.

If you (=the wonderful people in this list) really want us to script some
process on Jenkins that force-feeds the header into the .hpl/.hwf files
we'll do so though. It's just a bit frustrating to be honest.


On Fri, Jun 11, 2021 at 2:54 PM Justin Mclean 
wrote:

> Hi,
>
> > We see integration tests as an even more important and integral part of
> the
> > source code compared to unit tests since they offer so much more value in
> > ensuring that functionality and compatibility remain the same when we
> push
> > our software forward.
>
> So in that case they should have ASF header on them. I don’t see why
> integration tests shod be excused from this and it make the release hard to
> review.
>
> Kind Regards,
> Justin



-- 
Neo4j Chief Solutions Architect
*✉   *matt.cast...@neo4j.com
☎  +32486972937


Re: Champion and Mentors wanted for new potential Apache SST incubator project

2021-06-11 Thread Lothar Klein
Hello Chris,

Just before I responded about STEP geometry.
Another potential application is about assembly structures. Today likely all 
reasonable CAD systems can generate STEP files with assembly information. SST 
can already import XML files with assemblies (but not yet p21 files with 
assemblies). A potential application might e.g. reads in a STEP assembly for a 
machine and then analyses all the parts the machine is made up from and their 
transformation/placement in space. A future SST application might e.g.:

a) try to find vendors on the Internet that offer suitable parts and link to 
them - e.g. link to their more detailed STEP models they provide on the 
Internet (many do so already)

b) collect how many pieces of the same parts are needed (e.g. number of screws 
of a certain type) and from this derive a BOM (Bill Of Material), containing a 
summary of the more detailed assembly information.

c) Develop a tool to simulate how the assembly could be best build up; the 
sequence of operations that are needed. The result could be similar to what you 
see is coming with a LEGO(tm) toy with all the single steps on how to put 
things together.

The result of all three examples could be again stored in SST and be used by 
further tools.

Lothar

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



Re: Champion and Mentors wanted for new potential Apache SST incubator project

2021-06-11 Thread Lothar Klein
Hello Nathan,

Right, STEP geometry is one of the things we could do with SST. We are just 
finishing with a higher level ontology that is directly derived from STEP 
geometry models (written in the Express modelling language) and that is 
directly integrated in SST as "early binding". So an application can directly 
operate on objects such an Ellipse, a BSplineSurfaceWithKnots,a Torus or to 
take advantage of the new triangulated data capabilities.
The next thing to do is to write a STEP p21-file parser that can transform the 
data in a p21 file into RDF using the higher level ontology. After this we 
might look for ways how to display the geometry in a browser ... there are 
several approached that could be taken for this.

Cheers

Lothar

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



Re: Champion and Mentors wanted for new potential Apache SST incubator project

2021-06-11 Thread Nathan Hartman
On Fri, Jun 11, 2021 at 6:39 AM Christofer Dutz 
wrote:

> Hi Lothar,
>
> after a call with you and comparing that to the proposal, I think it
> would be great if you could explain a little bit more on a concrete
> example what SST does, which problem it solves and how it differs from
> existing solutions.
>
> For me at first the proposal was pretty lengthy but stayed so vague with
> WHAT it actually is, that this didn't trigger my interest at first.
> Perhaps being a little more concrete will help get some responses here.
>
> Chris



I had a bit of trouble understanding it as well, but from what I picked up
it sounds like an API and library to read and write industry-standard file
formats used in CAD/CAE/CAM systems, with ability to version control those
files or at least provide meaningful diffing of these formats.

STEP was mentioned several times. Not sure if that refers to the 3D file
format that's used as a data interchange between CAD systems, or is an
acronym for something else.

Should be interesting to hear more about it.

Cheers,
Nathan


Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-11 Thread Justin Mclean
Hi,

> We see integration tests as an even more important and integral part of the
> source code compared to unit tests since they offer so much more value in
> ensuring that functionality and compatibility remain the same when we push
> our software forward. 

So in that case they should have ASF header on them. I don’t see why 
integration tests shod be excused from this and it make the release hard to 
review.

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 Hop (incubating) 0.99-rc1

2021-06-11 Thread Justin Mclean
HI,

> That file should be switched to the standard ASF header and is part of the
> original code and covered by the notice file.

Except it wasn’t in the previous release and I assume wasn’t part of the 
original software grant.

Thanks,
Justin



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



Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

2021-06-11 Thread Xun Liu
+1
Pinot is an open source project with a broad user base, and the community
is also very active.

Best regards
Xun Liu

On Fri, Jun 11, 2021 at 7:16 PM Xun Liu  wrote:

> Pinot is an open source project with a broad user base, and the community
> is also very active.
>
> On Fri, Jun 11, 2021 at 6:29 PM Jim Jagielski  wrote:
>
>> +1 (binding)
>>
>> > On Jun 10, 2021, at 7:12 PM, Mayank Shrivastava 
>> wrote:
>> >
>> > Hi all,
>> >
>> > After a discussion with the community [1], voting [2], and a positive
>> vote result [3],
>> > we believe Apache Pinot (Incubating) is ready for graduation to a TLP,
>> > and we'd like to bring it up in discussion with the IPMC.
>> >
>> > To list a few of the community's achievements:
>> >
>> > 7800+ contributions from 168 contributors
>> > 7 releases by various release managers
>> > 6 new committers and 2 new PPMCs invited (all accepted)
>> > Diverse committers and PPMCs (from 7 companies/institutes)
>> > Apache website setup [4]
>> > Dev conversations at d...@pinot.apache.org 
>> > Assessed ourselves against the Apache Project maturity matrix [5]
>> > We have built a meritocratic and open collaborative process (the Apache
>> way)
>> >
>> > [1] Community Discussion for Graduation <
>> https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E
>> >
>> > [2] Voting Thread <
>> https://lists.apache.org/thread.html/r9ca0b2ccc9b0fbdbee6a09aaf06b36ffd3a20e9cc1b810cdbe7c65d6%40%3Cdev.pinot.apache.org%3E
>> >
>> > [3] Voting Result <
>> https://lists.apache.org/thread.html/rc371ca50ce8ff2d6c0b068165195526cfdbd08d915105573e17042d2%40%3Cdev.pinot.apache.org%3E
>> >
>> > [4] https://pinot.incubator.apache.org/ <
>> https://pinot.incubator.apache.org/>
>> > [5] Maturity Model Assessment <
>> https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot
>> >
>> > Please see the proposed board resolution below and let us know what you
>> > think.
>> >
>> > The discussion will remain open for at least 72 hours.
>> >
>> > ---
>> >
>> > Establish the Apache Pinot Project
>> >
>> > WHEREAS, the Board of Directors deems it to be in the best interests of
>> the Foundation and consistent with the Foundation's purpose to establish a
>> Project Management Committee charged with the creation and maintenance of
>> open-source software, for distribution at no charge to the public, related
>> to a distributed data integration framework that simplifies common aspects
>> of big data integration such as data ingestion, replication, organization
>> and lifecycle management for both streaming and batch data ecosystems.
>> >
>> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> (PMC), to be known as the "Apache Pinot Project", be and hereby is
>> established pursuant to Bylaws of the Foundation; and be it further
>> >
>> > RESOLVED, that the Apache Pinot Project be and hereby is responsible
>> for the creation and maintenance of software related to distributed OLAP
>> data store to provide Real-time Analytics to power wide variety of
>> analytical use case; and be it further
>> >
>> > RESOLVED, that the office of "Vice President, Apache Pinot" be and
>> hereby is created, the person holding such office to serve at the direction
>> of the Board of Directors as the chair of the Apache Pinot Project, and to
>> have primary responsibility for management of the projects within the scope
>> of responsibility of the Apache Pinot Project; and be it further
>> >
>> > RESOLVED, that the persons listed immediately below be and hereby are
>> appointed to serve as the initial members of the Apache Pinot Project:
>> > Felix Cheung mailto:felixche...@apache.org>>
>> > Jackie Jiang mailto:jac...@apache.org>>
>> > Jim Jagielski mailto:j...@apache.org>>
>> > Kishore G mailto:kisho...@apache.org>>
>> > Mayank Shrivastava mailto:maya...@apache.org>>
>> > Neha Pawar mailto:nehapa...@apache.org>>
>> > Olivier Lamy mailto:ol...@apache.org>>
>> > Seunghyun Lee mailto:sn...@apache.org>>
>> > Siddharth Teotia mailto:siddteo...@apache.org>>
>> > Subbu Subramaniam mailto:mcvsu...@apache.org>>
>> > Xiang Fu mailto:xian...@apache.org>>
>> >
>> >
>> >
>> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
>> appointed to the office of Vice President, Apache Pinot, to serve in
>> accordance with and subject to the direction of the Board of Directors and
>> the Bylaws of the Foundation until death, resignation, retirement, removal
>> of disqualification, or until a successor is appointed; and be it further
>> >
>> > RESOLVED, that the Apache Pinot Project be and hereby is tasked with
>> the migration and rationalization of the Apache Incubator Pinot podling;
>> and be it further
>> >
>> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> Pinot podling encumbered upon the Apache Incubator PMC are hereafter
>> discharged.
>> >
>> >
>> 

Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

2021-06-11 Thread Xun Liu
Pinot is an open source project with a broad user base, and the community
is also very active.

On Fri, Jun 11, 2021 at 6:29 PM Jim Jagielski  wrote:

> +1 (binding)
>
> > On Jun 10, 2021, at 7:12 PM, Mayank Shrivastava 
> wrote:
> >
> > Hi all,
> >
> > After a discussion with the community [1], voting [2], and a positive
> vote result [3],
> > we believe Apache Pinot (Incubating) is ready for graduation to a TLP,
> > and we'd like to bring it up in discussion with the IPMC.
> >
> > To list a few of the community's achievements:
> >
> > 7800+ contributions from 168 contributors
> > 7 releases by various release managers
> > 6 new committers and 2 new PPMCs invited (all accepted)
> > Diverse committers and PPMCs (from 7 companies/institutes)
> > Apache website setup [4]
> > Dev conversations at d...@pinot.apache.org 
> > Assessed ourselves against the Apache Project maturity matrix [5]
> > We have built a meritocratic and open collaborative process (the Apache
> way)
> >
> > [1] Community Discussion for Graduation <
> https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E
> >
> > [2] Voting Thread <
> https://lists.apache.org/thread.html/r9ca0b2ccc9b0fbdbee6a09aaf06b36ffd3a20e9cc1b810cdbe7c65d6%40%3Cdev.pinot.apache.org%3E
> >
> > [3] Voting Result <
> https://lists.apache.org/thread.html/rc371ca50ce8ff2d6c0b068165195526cfdbd08d915105573e17042d2%40%3Cdev.pinot.apache.org%3E
> >
> > [4] https://pinot.incubator.apache.org/ <
> https://pinot.incubator.apache.org/>
> > [5] Maturity Model Assessment <
> https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot
> >
> > Please see the proposed board resolution below and let us know what you
> > think.
> >
> > The discussion will remain open for at least 72 hours.
> >
> > ---
> >
> > Establish the Apache Pinot Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish a
> Project Management Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the public, related
> to a distributed data integration framework that simplifies common aspects
> of big data integration such as data ingestion, replication, organization
> and lifecycle management for both streaming and batch data ecosystems.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pinot Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Pinot Project be and hereby is responsible for
> the creation and maintenance of software related to distributed OLAP data
> store to provide Real-time Analytics to power wide variety of analytical
> use case; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Pinot" be and
> hereby is created, the person holding such office to serve at the direction
> of the Board of Directors as the chair of the Apache Pinot Project, and to
> have primary responsibility for management of the projects within the scope
> of responsibility of the Apache Pinot Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Pinot Project:
> > Felix Cheung mailto:felixche...@apache.org>>
> > Jackie Jiang mailto:jac...@apache.org>>
> > Jim Jagielski mailto:j...@apache.org>>
> > Kishore G mailto:kisho...@apache.org>>
> > Mayank Shrivastava mailto:maya...@apache.org>>
> > Neha Pawar mailto:nehapa...@apache.org>>
> > Olivier Lamy mailto:ol...@apache.org>>
> > Seunghyun Lee mailto:sn...@apache.org>>
> > Siddharth Teotia mailto:siddteo...@apache.org>>
> > Subbu Subramaniam mailto:mcvsu...@apache.org>>
> > Xiang Fu mailto:xian...@apache.org>>
> >
> >
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
> appointed to the office of Vice President, Apache Pinot, to serve in
> accordance with and subject to the direction of the Board of Directors and
> the Bylaws of the Foundation until death, resignation, retirement, removal
> of disqualification, or until a successor is appointed; and be it further
> >
> > RESOLVED, that the Apache Pinot Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Pinot podling; and be
> it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pinot podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
> >
> >
> > ---
> >
> > Thanks,
> > Mayank
> >
>
>


Re: Champion and Mentors wanted for new potential Apache SST incubator project

2021-06-11 Thread Christofer Dutz
Hi Lothar,

after a call with you and comparing that to the proposal, I think it 
would be great if you could explain a little bit more on a concrete 
example what SST does, which problem it solves and how it differs from 
existing solutions.

For me at first the proposal was pretty lengthy but stayed so vague with 
WHAT it actually is, that this didn't trigger my interest at first. 
Perhaps being a little more concrete will help get some responses here.

Chris










On 09.06.21 14:07, Lothar Klein wrote:
> Dear IPMC members,
> 
> We are looking for a Champion and Mentors for the new SST incubator 
> project proposal; see below.
> So far I contacted Justin Mclean and Christofer Dutz and they are 
> considering to become mentors.
> 
> Best Regards
> Lothar
> 
> 
> === Abstract ===
> 
> SST (Semantic STEP Technology) is an optimized RDF/OWL API with
> GIT like revision control capabilities as an enabler for a new
> comprehensive CAD/CAx data model derived from ISO 10303 (STEP)
> and ISO 15926 (Oil & Gas) standards.
> 
> === Rationale: The Problem to solve ===
> 
> There are many different kinds of Computer-aided technology
> (CAx) systems around. Some are listed here:
> => https://en.wikipedia.org/wiki/Computer-aided_technologies
> 
> For all organizations that are involved in the design,
> production, maintenance and commercial use of industrial
> products a smooth exchange of data between these tools would be
> needed. Also please have in mind that for most industrial
> production a big supply network has be coordinated; each with
> it’s own specific tools.
> 
> The reality is that data exchange between these system is often
> not possible and if available the interface tools are
> incomplete as they exchange only some, but not all needed data.
> The problem get even worse as often the systems have to be used
> in a cyclic iterative way to deal with design changes. The
> truth is also that for all CAx systems a big part of the
> software development power (if not the biggest part) is spent
> on the interfaces to other system, not on the core
> functionality the system provides.
> 
> STEP is a big attempt to address this issue. In the
> introduction of ISO 10303-1:1994 "Overview and fundamental
> principles" and extended in the 2021 edition we can read:
> 
> "ISO 10303 is an International Standard for the
> computer-interpretable representation of product information
> and for the exchange of product data. The objective is to
> provide a neutral mechanism capable of describing products
> throughout their life cycle. This mechanism is suitable not
> only for neutral file exchange, but also as a basis for
> implementing and sharing product databases, and as a basis for
> archiving. The information generated about a product during its
> design, manufacture, use, maintenance, and disposal is used for
> many purposes. The use can involve many computer systems,
> including some that can be located in different organizations.
> In order to support such uses, organizations need to be able to
> represent their product information in a common
> computer-interpretable form that is required to remain complete
> and consistent when exchanged among different computer
> systems."
> => https://www.iso.org/obp/ui/#iso:std:iso:10303:-1:ed-2:v1:en
> 
> In the introduction of ISO 15926-1:2004 "Overview and
> fundamental principles" we can see slightly different but
> highly overlapping goals:
> => https://www.iso.org/obp/ui/#iso:std:iso:15926:-1:ed-1:v1:en
> 
> The goals of the ISO 10303 and 15926 series of standards are
> only very partially achieved in practice today.
> 
> The aim of the SST project is to make the visions of these
> standards a reality by providing an open source environment
> that is suitable to directly operate on distributed data on servers
> managed by different organizations.
> 
> === Background ===
> 
> ISO 10303 and ISO 15926 and other series of standards are
> developed by the ISO Technical Committee 184: Automation
> Systems and Integration, Subcommittee 4: Industrial data. In
> its resolution number 9 from March 1985 the overall goal was
> expressed as: "To develop as soon as possible a single
> international standard for the exchange of product definition
> data to be called the standard for the exchange of product
> model data (STEP)." It took almost 10 years (1994/95) till the
> publication of the first set of standards. The geometric data
> models and assembly structures developed back then are today
> widely implemented by CAD and other systems. Since then the
> STEP standard grew constantly with lots of new application
> areas and layers of abstraction; but with only a few of the new
> capabilities really implemented and widely used. For upward
> compatibility reasons the originals data models where kept in
> place with only minor extensions.
> 
> In parallel to the development of STEP, the process industry
> was searching for ways to capture the life-cycle data for their
> process 

Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

2021-06-11 Thread Jim Jagielski
+1 (binding)

> On Jun 10, 2021, at 7:12 PM, Mayank Shrivastava  wrote:
> 
> Hi all,
> 
> After a discussion with the community [1], voting [2], and a positive vote 
> result [3],
> we believe Apache Pinot (Incubating) is ready for graduation to a TLP,
> and we'd like to bring it up in discussion with the IPMC.
> 
> To list a few of the community's achievements: 
> 
> 7800+ contributions from 168 contributors
> 7 releases by various release managers
> 6 new committers and 2 new PPMCs invited (all accepted)
> Diverse committers and PPMCs (from 7 companies/institutes)
> Apache website setup [4]
> Dev conversations at d...@pinot.apache.org 
> Assessed ourselves against the Apache Project maturity matrix [5]
> We have built a meritocratic and open collaborative process (the Apache way)
> 
> [1] Community Discussion for Graduation 
> 
> [2] Voting Thread 
> 
> [3] Voting Result 
> 
> [4] https://pinot.incubator.apache.org/ 
> [5] Maturity Model Assessment 
> 
> Please see the proposed board resolution below and let us know what you
> think.
> 
> The discussion will remain open for at least 72 hours.
> 
> ---
> 
> Establish the Apache Pinot Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of the 
> Foundation and consistent with the Foundation's purpose to establish a 
> Project Management Committee charged with the creation and maintenance of 
> open-source software, for distribution at no charge to the public, related to 
> a distributed data integration framework that simplifies common aspects of 
> big data integration such as data ingestion, replication, organization and 
> lifecycle management for both streaming and batch data ecosystems.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to 
> be known as the "Apache Pinot Project", be and hereby is established pursuant 
> to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache Pinot Project be and hereby is responsible for the 
> creation and maintenance of software related to distributed OLAP data store 
> to provide Real-time Analytics to power wide variety of analytical use case; 
> and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Pinot" be and hereby is 
> created, the person holding such office to serve at the direction of the 
> Board of Directors as the chair of the Apache Pinot Project, and to have 
> primary responsibility for management of the projects within the scope of 
> responsibility of the Apache Pinot Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are 
> appointed to serve as the initial members of the Apache Pinot Project:
> Felix Cheung mailto:felixche...@apache.org>>
> Jackie Jiang mailto:jac...@apache.org>>
> Jim Jagielski mailto:j...@apache.org>>
> Kishore G mailto:kisho...@apache.org>>
> Mayank Shrivastava mailto:maya...@apache.org>>
> Neha Pawar mailto:nehapa...@apache.org>>
> Olivier Lamy mailto:ol...@apache.org>>
> Seunghyun Lee mailto:sn...@apache.org>>
> Siddharth Teotia mailto:siddteo...@apache.org>>
> Subbu Subramaniam mailto:mcvsu...@apache.org>>
> Xiang Fu mailto:xian...@apache.org>>
> 
> 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be 
> appointed to the office of Vice President, Apache Pinot, to serve in 
> accordance with and subject to the direction of the Board of Directors and 
> the Bylaws of the Foundation until death, resignation, retirement, removal of 
> disqualification, or until a successor is appointed; and be it further
> 
> RESOLVED, that the Apache Pinot Project be and hereby is tasked with the 
> migration and rationalization of the Apache Incubator Pinot podling; and be 
> it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator Pinot 
> podling encumbered upon the Apache Incubator PMC are hereafter discharged.
> 
> 
> ---
> 
> Thanks,
> Mayank
> 



Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-11 Thread Matt Casters
We see integration tests as an even more important and integral part of the
source code compared to unit tests since they offer so much more value in
ensuring that functionality and compatibility remain the same when we push
our software forward.  It gives us the freedom to continue progressing in a
safe way.  That is why I think that splitting these tests off into another
repository is a bad idea and the same goes for documentation and the
samples really.  We really want and need to keep everything in sync with
code changes.
We hope to have hundreds of extra .hpl/.hwf files for testing and samples
in the future.
Our mentors in the past thought it was not required to add license headers
for these "user-files" hence their exclusion from the RAT checks.

On Fri, Jun 11, 2021 at 10:51 AM Hans Van Akelyen <
hans.van.akel...@gmail.com> wrote:

> Hi Justin,
>
> That file should be switched to the standard ASF header and is part of the
> original code and covered by the notice file.
>
> As for the no header in hpl and hwf files, these are files created using
> the application and are used for samples and for our integration testing
> framework. This framework is an extension on our unit tests mainly used to
> see if all functionality is working and that we have no regressions.
> As they are created using the application no header is included, they are
> not manually created files.
>
> Cheers,
> Hans
>
> On Fri, 11 Jun 2021 at 09:36, Justin Mclean 
> wrote:
>
> > Hi,
> >
> > -1 (binding)
> >
> > This 3rd party file [1] is not mentioned in LICENSE. While this is just
> > one file my concern is that that this may indicate a bigger issue where
> > headers of 3rd party files have been changed.
> >
> > I checked:
> > - incubating in name
> > - signatures and hash are fine
> > - LICENSE is missing a mention from a 3rd party file
> > - No unexpected binary files
> > - There is quite a number of files without ASF headers I assume it could
> > be added to some of these (e.g. .hpl or .hwf files)
> > - Didn't compile from source
> >
> > Kind Regards,
> > Justin
> >
> > 1. ./core/src/test/java/org/apache/hop/core/sql/SqlFieldsUnitTest.java
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>


-- 
Neo4j Chief Solutions Architect
*✉   *matt.cast...@neo4j.com
☎  +32486972937


Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-11 Thread Hans Van Akelyen
Hi Justin,

That file should be switched to the standard ASF header and is part of the
original code and covered by the notice file.

As for the no header in hpl and hwf files, these are files created using
the application and are used for samples and for our integration testing
framework. This framework is an extension on our unit tests mainly used to
see if all functionality is working and that we have no regressions.
As they are created using the application no header is included, they are
not manually created files.

Cheers,
Hans

On Fri, 11 Jun 2021 at 09:36, Justin Mclean 
wrote:

> Hi,
>
> -1 (binding)
>
> This 3rd party file [1] is not mentioned in LICENSE. While this is just
> one file my concern is that that this may indicate a bigger issue where
> headers of 3rd party files have been changed.
>
> I checked:
> - incubating in name
> - signatures and hash are fine
> - LICENSE is missing a mention from a 3rd party file
> - No unexpected binary files
> - There is quite a number of files without ASF headers I assume it could
> be added to some of these (e.g. .hpl or .hwf files)
> - Didn't compile from source
>
> Kind Regards,
> Justin
>
> 1. ./core/src/test/java/org/apache/hop/core/sql/SqlFieldsUnitTest.java
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-11 Thread Justin Mclean
Hi,

-1 (binding)

This 3rd party file [1] is not mentioned in LICENSE. While this is just one 
file my concern is that that this may indicate a bigger issue where headers of 
3rd party files have been changed.

I checked:
- incubating in name
- signatures and hash are fine
- LICENSE is missing a mention from a 3rd party file
- No unexpected binary files
- There is quite a number of files without ASF headers I assume it could be 
added to some of these (e.g. .hpl or .hwf files)
- Didn't compile from source

Kind Regards,
Justin

1. ./core/src/test/java/org/apache/hop/core/sql/SqlFieldsUnitTest.java
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [DISCUSS] Incubating Proposal of Kyuubi

2021-06-11 Thread Kent Yao
Hello everyone,

It's been 12 days since this discussion started on May 31, 2021. After June
6, there are no more new questions arising. So I'd like to summarize the
results of this discussion so we can move forward.

Thank you very much to everyone at the Apache IPMC for suggesting changes
to our proposal and everyone else who participated in the discussion. We
have corrected some sections and content of the proposal during this
discussion, such as Orphaned products, Core Developers, Initial Committers,
SGA, etc., based on your recommendations.

In addition, we had a discussion with our mentors and all former candidates
about the composition of Initial Committers. Based on the Apache Way,
considering the current status of the Kyuubi community, the contribution of
each contributor, the current Initial Committers were adjusted as follows
with the consensus of everyone.

Kent Yao (y...@apache.org)
Fei Wang (cn.feiw...@gmail.com)
Ulysses You (ulyssesyo...@gmail.com)
Cheng Pan (pan3...@gmail.com)
Hongxiang Jiang (jhx1...@gmail.com)

Thank you all again.
Bests

Kent Yao

Kent Yao  于2021年6月6日周日 下午10:44写道:

> Hi Ming,
>
> Thanks for your question.
>
> As mentioned in the proposal, Kyuubi was first developed and applied in
> NetEase in 2018. The early scenario we wanted to address was
> straightforward - to provide data analysts with a Spark-based analytics
> platform. This platform needed to support multi-tenancy [1] and
> authentication and authorization [2]. From the project's perspective, it
> was just an alternative implementation of Apache Spark Thrift Server. And
> for the workloads and users that it serves are not very big in NetEase. So
> at that time, I was the only one who was maintaining the project.
>
> Another reason for this problem should be the limited usage scenario
> caused by its architecture. It was implemented based on
> *spark.driver.allowMultipleContexts*, which was not good judging from the
> dismal feedback after we open-sourced it. Many people have found Kyuubi or
> me through GitHub, hoping that Kyuubi could solve a problem they were
> having in their scenario. From all of these things, I remember most and
> feel sorry for is when they said they were using Kyuubi to help medical
> staff fight COVID-19 [9]. Limited by design, there was very little that
> could be done at the time.
>
> Starting with Spark 3.0.0, the Spark community also removed this feature
> [3] for Kyuubi's old architecture. This allowed us to rethink and redesign
> Kyuubi architecture. A prototype was quickly designed, but we did not start
> it in a hurry. As Kyuubi relies heavily on Spark, we decided to actively
> and deeply participate in the Spark community beginning around September
> 2019 [4][5][6], both to help the Spark community and to verify that the
> design of the new Kyuubi architecture [7] was future-proofing enough. In
> the process of implementing the new architecture, Zen Jin became a
> contributor to the project and contributed several great ideas, which made
> Kyuubi's architecture and the scenarios it can cover more general and
> comprehensive. This has made Kyuubi's architecture and the scenarios it can
> cover more general. This advancement has made Kyuubi more attractive than
> older architecture projects.
>
> As a result, many like-minded people [6] started to gather around the
> project and the new architecture, and some of them have already become our
> contributors. There are also many people who have encouraged us to
> contribute to this project to Apache, which will be very beneficial for
> them to be more directly involved in the project.
>
> In addition, we've learned a lot about community operations while
> contributing to other Apache projects like Spark, Submarine, and Hudi. Some
> of these communities are new to Apache, and some are ten years out of
> school. We also actively participated in some online and offline
> conferences or meetups, published technical articles in different media to
> promote Kyuubi.
>
> From our practical experience, we have learned that promoting a project is
> not an easy task. We want to donate Kyuubi to the community and bring in
> potentially willing people to help the Kyuubi community grow.
>
> Bests
> Kent Yao
>
> [1] https://issues.apache.org/jira/browse/SPARK-2243
> [2] https://issues.apache.org/jira/browse/SPARK-5159
> [3] https://issues.apache.org/jira/browse/SPARK-26362
> [4] https://github.com/apache/spark/commits?author=yaooqinn
> [5] https://github.com/apache/spark/commits?author=turboFei
> [6] https://github.com/apache/spark/commits?author=ulysses-you
> [7] https://github.com/NetEase/kyuubi/releases/tag/v1.0.0
> [8]
> https://github.com/NetEase/kyuubi/graphs/contributors?from=2021-01-01=2021-06-06=c
> [9] https://github.com/NetEase/kyuubi/issues/228
>
> Ming Wen  于2021年6月6日周日 上午7:37写道:
>
>> You can see the trend chart from
>>
>> https://www.apiseven.com/zh/contributor-graph?chart=contributorMonthlyActivity=NetEase/kyuubi
>>
>>
>> Ming Wen 

Re: [VOTE] Release Apache Hop (incubating) 0.99-rc1

2021-06-11 Thread fpapon
Forwarding my PPMC vote

+1 (binding)

Good job to all the Hop team!

regards,

François
fpa...@apache.org

Le 09/06/2021 à 10:47, Hans Van Akelyen a écrit :
> Hi All,
>
> This will be our preview 1.0 release, this release contains both the source
> code and binary to run the client. This will also be our first release
> without DISCLAIMER-WIP but the regular disclaimer.
>
> This release aims to get as much feedback as possible so we can remove some
> final bugs before releasing 1.0.
>
> Build instructions can be found in the README included.
>
> Hop community vote and result threads:
> Vote:
>
> https://lists.apache.org/thread.html/ra0cb8d9286e3cabf3348f3544a6dc0e60dcdd87a58918a7c1a413d36%40%3Cdev.hop.apache.org%3E
> Result:
> https://lists.apache.org/thread.html/ra6e1e447f5611bea927e8b41558d5ff790e8475e8e44629b7e872a14%40%3Cdev.hop.apache.org%3E
>
> The tag to be voted on is 0.99-rc1 (commit a29e5a7)
> https://github.com/apache/incubator-hop/tree/0.99-rc1
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/hop/apache-hop-0.99-incubating-rc1/
>
> The SHA512 Checksum for these artifacts is:
> code:
> ab62b90b311097fde622884cbcd3c67ccec75cfe0be2c70c7dd773528f34290994a0c3a166a1cecb04a5342d5eccb6953f258b87c0497e90e2ffd2c5f31723a3
>
> client:
> 99f28e78d4795c19ae686094bcef6e75e875fcd213c967c868108afcf3fc0bcd83a268e2566aee122ae74c0dc54cffdd1a7e43bfcf7fcf23f3dda50487d5b644
>
> Release artifacts are signed with the following key:
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x9a8a628dd4f4aa1e
>
> For more information about the contents of this release, see:
> https://issues.apache.org/jira/projects/HOP/versions/12350036
>
> Please vote on releasing this package as Apache Hop (incubating) 0.99!
>
> The vote is open for 72 hours and passes if
> a majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Hop (incubating) 0.99
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
> Best Regards,
> Hans
>

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