Re: Suggestion for podling reminder report emails.

[Emilian Bold]

+1

Maybe the script just BCCs all the podlings, otherwise it should be a small 
change to make.

--emi

‐‐‐ Original Message ‐‐‐

On 10 June 2018 12:28 AM, Edward Capriolo  wrote:

> Hey all,
> 
> I have been personally slacking a bit, but I wanted to point something out.
> 
> I subscribe to the mailing lists of 4 podlings. The email I get has a
> 
> subject of
> 
> "Podling Report Reminder - June 2018"
> 
> The email is addressed to dev@gossip But with gmail you actually do not
> 
> see that until you click into the email and expand the to:
> 
> Again, I know I have been slacking, but it would be easier if the email
> 
> said: "gossip podling reminder"
> 
> Thanks,
> 
> Edward



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

Suggestion for podling reminder report emails.

[Edward Capriolo]

Hey all,

I have been personally slacking a bit, but I wanted to point something out.

I subscribe to the mailing lists of 4 podlings. The email I get has a
subject of
"Podling Report Reminder - June 2018"

The email is addressed to dev@gossip But with gmail you actually do not
see that until you click into the email and expand the to:

Again, I know I have been slacking, but it would be easier if the email
said: "gossip podling reminder"

Thanks,
Edward

Re: [VOTE] Accept Warble into the Apache Incubator

[Timothy Chen]

+1

Tim

On Sat, Jun 9, 2018 at 10:15 AM Daniel Takamori  wrote:

> +1
>
> On 2018/06/08 14:43:53, Chris Thistlethwaite  wrote:
> > Hi All (again),
> >
> > I'd like to start a vote on accepting Warble into the Apache Incubator.
> >
> > https://lists.apache.org/thread.html/1d62a2948d047cea38e6f01f92d5f138f8
> > 3acd2c9d86349023fb28e4@%3Cgeneral.incubator.apache.org%3E
> >
> > The ASF voting rules are described:
> >
> > https://www.apache.org/foundation/voting.html
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote
> > for which only Incubator PMC member votes are binding.
> >
> > This vote will run for at least 72 hours. Please VOTE as follows
> > [ ] +1 Accept Warble into the Apache Incubator
> > [ ] +0 Abstain.
> > [ ] -1 Do not accept Warble into the Incubator
> >
> > The proposal is listed below, but you can also access it on the wiki:
> > https://wiki.apache.org/incubator/WarbleProposal
> >
> >
> > Thank you,
> > Chris T.
> >
> >
> >
> > = Apache Warble Proposal =
> >
> > == Abstract ==
> >
> > Apache Warble is a distributed endpoint monitoring solution where
> > the agent is hosted on your own hardware. The aim of Warble is to
> > produce a more balanced and less binary view of services and
> > systems, lowering the rates of false positives while also providing
> > greater insight into possible peering issues and proactive trend
> > analysis.
> >
> > ==Proposal ==
> >
> > The goal of Warble will be to bring internal control of
> > distributed monitoring back to the end user. Warble can be used as
> > an independent service running on your own infrastructure
> > monitoring other services in your infrastructure.
> >
> > == Background and Rationale ==
> >
> > The beginning of this project was prompted by the service
> > pingmybox.com (PMB) going end of life. This brought up
> > conversation about FOSS services that can monitor internal and
> > external services. PMB offered a unique code base to build this
> > service upon a known infrastructure.
> >
> > ===Initial Goals ===
> >
> > Bring PMB code into the ASF, refactor the client/server into
> > a more reusable structure. Further reuse of code gives us the a
> > great starting point to build a starting point.
> >
> > ==Current Status ==
> >
> > The software exists as a proprietary service. We wish to convert
> > this to a FLOSS solution.
> >
> > ==Meritocracy ==
> >
> > The initial PMC list covers new folks coming into the ASF.
> >
> > ==Community ==
> >
> > There exists a large user-base of software like Warble, as well
> > as existing users of the old propietary service. It is our hope
> > that we can convert a great deal of these to contributors and
> > testers for the new open source product.
> >
> > ==Core Developers ==
> >
> > The initial set of developers are a lot of newcomers:
> >
> > * Daniel Gruno 
> > * Chris Thistlethwaite 
> > * Haig Didizian 
> > * Andrew Karetas 
> > * Chandler Claxton 
> > * Luke Stevens 
> > * Mike Andescavage 
> > * Chris Lambertus 
> >
> > ==Known Risks ==
> >
> > There are many existing services that provide external
> > monitoring. They are well established and have large user bases.
> >
> > ===Orphaned Products ===
> >
> > The initial PMC has great interest in open source projects, though
> > no formal projects have been run.
> >
> >
> > ===Inexperience with Open Source ===
> >
> > Most of the initial PPMC members are new to the ASF and some are
> > new to open source projects. However, all are very interested in
> > giving back to the community and projects.  Having said that, there
> > are several people involved with extensive experience in the
> > Apache Way and our procedures and processes.
> >
> > ===Homogenous Developers ===
> >
> > The initial set of developers are employed by a variety of
> > companies, located across the world, and used to working on a
> > variety of distributed projects.
> >
> > ===Reliance on Salaried Developers ===
> >
> > We do not expect the interest of the proposed initial PMC to be
> > directly tied to current employment, but will actively seek to
> > grow our volunteer base regardless.
> >
> > ===Relationships with Other Apache Products ===
> >
> > Not much to say here. Many ASF projects make use of the proprietary
> > offering, we wish to open source it and have people engage in the
> > development of the project. There are, at present, indirect
> > relationships in that some dependencies are built on Apache
> > software, but these are generally by proxy and does not merit
> > considering Warble as a sub-project of an existing TLP.
> >
> >
> > ==Initial Source ==
> >
> > The initial task of the PMC will be assessing what we wish the
> > project to contain. The proprietary 

Re: [VOTE] Accept Warble into the Apache Incubator

[Daniel Takamori]

+1

On 2018/06/08 14:43:53, Chris Thistlethwaite  wrote: 
> Hi All (again),
> 
> I'd like to start a vote on accepting Warble into the Apache Incubator.
> 
> https://lists.apache.org/thread.html/1d62a2948d047cea38e6f01f92d5f138f8
> 3acd2c9d86349023fb28e4@%3Cgeneral.incubator.apache.org%3E
> 
> The ASF voting rules are described:
> 
> https://www.apache.org/foundation/voting.html
> 
> A vote for accepting a new Apache Incubator podling is a majority vote
> for which only Incubator PMC member votes are binding.
> 
> This vote will run for at least 72 hours. Please VOTE as follows
> [ ] +1 Accept Warble into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept Warble into the Incubator
> 
> The proposal is listed below, but you can also access it on the wiki:
> https://wiki.apache.org/incubator/WarbleProposal
> 
> 
> Thank you,
> Chris T.
> 
> 
> 
> = Apache Warble Proposal =
> 
> == Abstract ==
> 
> Apache Warble is a distributed endpoint monitoring solution where
> the agent is hosted on your own hardware. The aim of Warble is to
> produce a more balanced and less binary view of services and
> systems, lowering the rates of false positives while also providing
> greater insight into possible peering issues and proactive trend
> analysis.
>  
> ==Proposal ==
>  
> The goal of Warble will be to bring internal control of
> distributed monitoring back to the end user. Warble can be used as
> an independent service running on your own infrastructure
> monitoring other services in your infrastructure. 
>  
> == Background and Rationale ==
>  
> The beginning of this project was prompted by the service
> pingmybox.com (PMB) going end of life. This brought up
> conversation about FOSS services that can monitor internal and
> external services. PMB offered a unique code base to build this
> service upon a known infrastructure.
>  
> ===Initial Goals ===
> 
> Bring PMB code into the ASF, refactor the client/server into 
> a more reusable structure. Further reuse of code gives us the a
> great starting point to build a starting point. 
>  
> ==Current Status ==
>  
> The software exists as a proprietary service. We wish to convert
> this to a FLOSS solution.
>  
> ==Meritocracy ==
>  
> The initial PMC list covers new folks coming into the ASF. 
> 
> ==Community ==
>  
> There exists a large user-base of software like Warble, as well 
> as existing users of the old propietary service. It is our hope
> that we can convert a great deal of these to contributors and
> testers for the new open source product.
>  
> ==Core Developers ==
>  
> The initial set of developers are a lot of newcomers:
> 
> * Daniel Gruno 
> * Chris Thistlethwaite 
> * Haig Didizian 
> * Andrew Karetas 
> * Chandler Claxton 
> * Luke Stevens 
> * Mike Andescavage 
> * Chris Lambertus 
>  
> ==Known Risks ==
> 
> There are many existing services that provide external 
> monitoring. They are well established and have large user bases.
>  
> ===Orphaned Products ===
>  
> The initial PMC has great interest in open source projects, though
> no formal projects have been run.
>  
>  
> ===Inexperience with Open Source ===
>  
> Most of the initial PPMC members are new to the ASF and some are
> new to open source projects. However, all are very interested in
> giving back to the community and projects.  Having said that, there
> are several people involved with extensive experience in the
> Apache Way and our procedures and processes.
>  
> ===Homogenous Developers ===
>  
> The initial set of developers are employed by a variety of
> companies, located across the world, and used to working on a
> variety of distributed projects.
>  
> ===Reliance on Salaried Developers ===
>  
> We do not expect the interest of the proposed initial PMC to be
> directly tied to current employment, but will actively seek to
> grow our volunteer base regardless.
>  
> ===Relationships with Other Apache Products ===
>  
> Not much to say here. Many ASF projects make use of the proprietary
> offering, we wish to open source it and have people engage in the
> development of the project. There are, at present, indirect
> relationships in that some dependencies are built on Apache
> software, but these are generally by proxy and does not merit
> considering Warble as a sub-project of an existing TLP.
> 
>  
> ==Initial Source ==
>  
> The initial task of the PMC will be assessing what we wish the
> project to contain. The proprietary vendor is willing to donate the
> software, but considerable rewriting and relicensing will have to
> take place. This will likely 

Re: Looking for Champion

[Li,De(BDG)]

Hi Tim, Todd,

Thank you for your response.

We are so sorry that we have not contribute any improvements to Impala so
far.
I think we will do that as soon, it is a good opportuniy to us to
participate
in open source community and learn to do things in Apache way.

One of causes is that We think most of our patches may not been accept by
Impala.
Because there is a big difference between Palo and Impala, our patch just
could
apply to Palo.

Firstly, as a query engine for Hadoop, Impala deeply depend on HDFS and
HBase 
(At least several years ago it was like this)
but Palo is just the opposite. We struggle to build a single tool which do
not 
depend on any other system.
The simplicity (of developing, deploying and using) and meeting many data
serving requirements in single system are the main feature of Palo.
So we just want a query engine from Impala rather than others such as
read/write Hive data.

Secondly, due to introduced Mesa data model. The Catalog is different from
Impala.
We developped a In-Memory Catalog and also support Rollup, aggregation
data 
model. As a consequnce, we have to change sql grammar based on Impala.

Thirdly, it is a big difference in Cluster manager and node deployment.
Contrast Impala, Query compiling, query execution coordination and catalog
management of storage engine are integrated to be frontend daemon.
Query execution and data storage are integrated to be backend daemon.

Now, as you mentioned, regarding Impala's goal is to be a full featured
data 
warehouse engine as well, maybe some of Palo's feature also usefull to
Impala. 
If it is possible, we are very happy to contribute code for Impala.
We are very appreciate for Impala community and we are looking forward to
corporate with Impala community in whatever way.

Best Regards,
Reed



在 2018/6/9 上午12:18， "Tim Armstrong"  写入:

>> Meanwhile we found Impala is a very good MPP SQL query engine, so we
>>integrated
>them together.
>
>Palo didn't integrate with Impala, it forked Impala's codebase and
>embedded
>it in its own repository. I don't remember any attempts from the Palo team
>to engage with the Impala community or attempt to work with us to
>contribute any improvements.
>
>It looks like Palo is still pulling in new code from Impala.  E.g. this
>commit includes a bunch of code I wrote as part of IMPALA-3200:
>https://github.com/baidu/palo/commit/2419384e8a211f10e7636afc6d3423700ba22
>b5a#diff-1c501d9a8b5c3d1d1cce48d5e1fb0edf
>
>The code isn't owned by any individual, I contributed it to Apache and
>it's
>free for anyone to do what they want to do with it, but pulling in
>improvements from other projects without any attempt to attribute it or
>contribute improvements back seems contrary to the Apache way.
>
>Anyway, maybe incubation is an opportunity for us to work together, but
>I'd
>hope that if Palo does go into incubation that it will rethink some of the
>practices it's been following.
>
>On Fri, Jun 8, 2018 at 9:12 AM, Todd Lipcon  wrote:
>
>> On Thu, Jun 7, 2018 at 11:55 PM, Li,De(BDG)  wrote:
>>
>> > Hi, Jim
>> >
>> > Thank you for your response.
>> > Actually, we start Palo in several years ago, and that time we
>>developed
>> > the storage engine based on Mesa technology.
>> > Meanwhile we found Impala is a very good MPP SQL query engine, so we
>> > integrated them together.
>> >
>>
>> From what I can tell of the Palo source, it's not so much an
>>integration as
>> a copied-and-modified codebase, right? i.e Palo does not use Impala as a
>> dependency, but rather shares a lot of code from the Impala project that
>> has since diverged.
>>
>>
>> >
>> > With this integration, the goal of Palo is to implement a single,
>> > full-featured, mysql protocol compatible data warehousing.
>> >
>>
>> That sounds pretty similar to the goals of the Impala project. Impala
>>isn't
>> MySQL-compatible at the moment but that seems more like a particular
>> feature that could be added rather than a distinct identity of the
>>project.
>> Otherwise, Impala's goal is to be a full featured data warehouse engine
>>as
>> well.
>>
>> Generally Apache has no rules against multiple projects fulfilling
>>similar
>> goals or use cases, even when those projects might compete. However I
>>think
>> it would be relatively unusual to incubate a project that appears to be
>> derived from a fork of an existing project, at least without first
>> considering whether the additional feature set could be contributed
>>back to
>> the existing community.
>>
>> -Todd
>>
>>
>> > 在 2018/6/8 下午1:55， "Jim Apple"  写入:
>> >
>> > >Hello! As a contributor to Impala, I’d be interested in hearing
>>thoughts
>> > >from the Palo community about integration between Impala and Palo.
>> > >
>> > >For instance, are there any apparent design goals of Impala that the
>> Palo
>> > >community thinks are fundamentally incompatible with Palo?
>> > >
>> > >Thanks,
>> > >Jim
>> > >
>> > >On 2018/06/08 04:45:32, "Li,De(BDG)"  wrote:
>> > >> Hi all,
>> > >>
>> > >> I am Reed, as a 

Re: Looking for Champion

[Li,De(BDG)]

Hi Dave,

Thank you for your response.

As you mentioned that mongoose.h, it is serious mistake to replace license when 
updating Apache
license with a automatic script.

I have fixed it as following:
https://github.com/baidu/palo/commit/611afcd125dc136c58d7feb5552c26e9b215878a

By the way, I wonder Palo just use OpenLdap with binary way, is it still have 
license issue?

Best Regards,
Reed

发件人: Dave Fisher mailto:dave2w...@comcast.net>>
答复: mailto:general@incubator.apache.org>>
日期: 2018年6月9日 星期六 上午2:10
至: mailto:general@incubator.apache.org>>
主题: Re: Looking for Champion

Yuck. That’s a mess. That is one very large diff.

I see a few files related to AES the were GPL converted to Apache which not 
allowed.
Copyrights were changed too which is also incorrect.

Changes to this file 
be/src/http/mongoose.h
 violate license and copyright of Sergey Lyubka

GitHub makes you expand each diff after awhile.

There are dependency licenses that might be issues too.

These licenses have not been evaluated by LEGAL.
* OpenLdap (OpenLDAP Software License)
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=blob;f=LICENSE;hb=e5f8117f0ce088d0bd7a8e18ddf37eaa40eb09b1
* rapidjson (Tencent)
Unknown
* cyrus-sasl (CMU License)
https://spdx.org/licenses/MIT-CMU.html
AKA MIT-CMU

Lots of work in evaluating licenses.

On Jun 8, 2018, at 9:46 AM, Ted Dunning 
mailto:ted.dunn...@gmail.com>> wrote:

Ouch.

The copyright in question was attached to code from the source code for
mySQL. There is no way that code can be in an Apache project.

Given the cut and paste history, it seems like it will require a very
detailed audit of code history or web searches to find where the original
code came from. The my_aes.c and .h files, for instance, have no hint in
their history that they came from GPL'ed code.

Yeah. Lot’s of oversight.

If we accept this proposal we need a Mentor who has time to help with this mess.

I don’t know that I have the time to lead that effort. Anyone?

Regards,
Dave


On Fri, Jun 8, 2018 at 5:37 PM Todd Lipcon 
mailto:t...@cloudera.com>> wrote:

...

+1. Also briefly browsing the code I found suspicious commits like this
one:

https://github.com/baidu/palo/commit/6486be64c319fe0beb8c6b4430c1662de54f182e

... in which a GPL license copyright by Oracle was "fixed" to be an Apache
license copyright Baidu.

So if this project does enter incubation I think we should be extra careful
to audit the origins of all of the source code.

Re: Looking for Champion

[Li,De(BDG)]

   Copyrights were changed too which is also incorrect.

Yes, we know that, I have fixed this mistake as following.
https://github.com/baidu/palo/commit/ac770c33d445a4c18a0b74f56b28a4180b30bf
b7

As you mentioned, we will recheck and make sure if Open LDAP is necessary
for Palo. 

Best Regards,
Reed


在 2018/6/9 上午4:13， "Ted Dunning"  写入:

>Open LDAP is a form of copy-left. It requires source code distribution of
>binary packaged versions.
>
>
>
>On Fri, Jun 8, 2018 at 7:10 PM Dave Fisher  wrote:
>
>> Yuck. That’s a mess. That is one very large diff.
>>
>> I see a few files related to AES the were GPL converted to Apache which
>> not allowed.
>> Copyrights were changed too which is also incorrect.
>>
>> Changes to this file be/src/http/mongoose.h
>> 
>>>f182e#diff-586168bd25cfbf3bc8bc1b52abc4206c> violate
>> license and copyright of Sergey Lyubka
>>
>> GitHub makes you expand each diff after awhile.
>>
>> There are dependency licenses that might be issues too.
>>
>> These licenses have not been evaluated by LEGAL.
>> * OpenLdap (OpenLDAP Software License)
>>
>> 
>>http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=blob;f=LICENSE;
>>hb=e5f8117f0ce088d0bd7a8e18ddf37eaa40eb09b1
>> * rapidjson (Tencent)
>> Unknown
>> * cyrus-sasl (CMU License)
>> https://spdx.org/licenses/MIT-CMU.html
>> AKA MIT-CMU
>>
>> Lots of work in evaluating licenses.
>>
>> On Jun 8, 2018, at 9:46 AM, Ted Dunning  wrote:
>>
>> Ouch.
>>
>> The copyright in question was attached to code from the source code for
>> mySQL. There is no way that code can be in an Apache project.
>>
>> Given the cut and paste history, it seems like it will require a very
>> detailed audit of code history or web searches to find where the
>>original
>> code came from. The my_aes.c and .h files, for instance, have no hint in
>> their history that they came from GPL'ed code.
>>
>>
>> Yeah. Lot’s of oversight.
>>
>> If we accept this proposal we need a Mentor who has time to help with
>>this
>> mess.
>>
>> I don’t know that I have the time to lead that effort. Anyone?
>>
>> Regards,
>> Dave
>>
>>
>> On Fri, Jun 8, 2018 at 5:37 PM Todd Lipcon  wrote:
>>
>> ...
>>
>> +1. Also briefly browsing the code I found suspicious commits like this
>> one:
>>
>>
>> 
>>https://github.com/baidu/palo/commit/6486be64c319fe0beb8c6b4430c1662de54f
>>182e
>>
>> ... in which a GPL license copyright by Oracle was "fixed" to be an
>>Apache
>> license copyright Baidu.
>>
>> So if this project does enter incubation I think we should be extra
>>careful
>> to audit the origins of all of the source code.
>>
>>
>>
>>

Re: Looking for Champion

[Li,De(BDG)]

Hi Todd,

Thank you for your response.

It is serious mistake to replace Oracle license to Apache when updating
license with a script.

We have not check carefully, actually, those file no longer been used.
So I removed them and made a new commit.

https://github.com/baidu/palo/commit/ac770c33d445a4c18a0b74f56b28a4180b30bf
b7

Best Regards,
Reed


在 2018/6/9 上午12:37， "Todd Lipcon"  写入:

>On Fri, Jun 8, 2018 at 9:18 AM, Tim Armstrong 
>wrote:
>
>> > Meanwhile we found Impala is a very good MPP SQL query engine, so we
>> integrated
>> them together.
>>
>> Palo didn't integrate with Impala, it forked Impala's codebase and
>>embedded
>> it in its own repository. I don't remember any attempts from the Palo
>>team
>> to engage with the Impala community or attempt to work with us to
>> contribute any improvements.
>>
>> It looks like Palo is still pulling in new code from Impala.  E.g. this
>> commit includes a bunch of code I wrote as part of IMPALA-3200:
>> https://github.com/baidu/palo/commit/2419384e8a211f10e7636afc6d3423
>> 700ba22b5a#diff-1c501d9a8b5c3d1d1cce48d5e1fb0edf
>>
>> The code isn't owned by any individual, I contributed it to Apache and
>>it's
>> free for anyone to do what they want to do with it, but pulling in
>> improvements from other projects without any attempt to attribute it or
>> contribute improvements back seems contrary to the Apache way.
>>
>
>+1. Also briefly browsing the code I found suspicious commits like this
>one:
>https://github.com/baidu/palo/commit/6486be64c319fe0beb8c6b4430c1662de54f1
>82e
>
>... in which a GPL license copyright by Oracle was "fixed" to be an Apache
>license copyright Baidu.
>
>So if this project does enter incubation I think we should be extra
>careful
>to audit the origins of all of the source code.
>
>-Todd
>
>
>> On Fri, Jun 8, 2018 at 9:12 AM, Todd Lipcon  wrote:
>>
>> > On Thu, Jun 7, 2018 at 11:55 PM, Li,De(BDG)  wrote:
>> >
>> > > Hi, Jim
>> > >
>> > > Thank you for your response.
>> > > Actually, we start Palo in several years ago, and that time we
>> developed
>> > > the storage engine based on Mesa technology.
>> > > Meanwhile we found Impala is a very good MPP SQL query engine, so we
>> > > integrated them together.
>> > >
>> >
>> > From what I can tell of the Palo source, it's not so much an
>>integration
>> as
>> > a copied-and-modified codebase, right? i.e Palo does not use Impala
>>as a
>> > dependency, but rather shares a lot of code from the Impala project
>>that
>> > has since diverged.
>> >
>> >
>> > >
>> > > With this integration, the goal of Palo is to implement a single,
>> > > full-featured, mysql protocol compatible data warehousing.
>> > >
>> >
>> > That sounds pretty similar to the goals of the Impala project. Impala
>> isn't
>> > MySQL-compatible at the moment but that seems more like a particular
>> > feature that could be added rather than a distinct identity of the
>> project.
>> > Otherwise, Impala's goal is to be a full featured data warehouse
>>engine
>> as
>> > well.
>> >
>> > Generally Apache has no rules against multiple projects fulfilling
>> similar
>> > goals or use cases, even when those projects might compete. However I
>> think
>> > it would be relatively unusual to incubate a project that appears to
>>be
>> > derived from a fork of an existing project, at least without first
>> > considering whether the additional feature set could be contributed
>>back
>> to
>> > the existing community.
>> >
>> > -Todd
>> >
>> >
>> > > 在 2018/6/8 下午1:55， "Jim Apple"  写入:
>> > >
>> > > >Hello! As a contributor to Impala, I’d be interested in hearing
>> thoughts
>> > > >from the Palo community about integration between Impala and Palo.
>> > > >
>> > > >For instance, are there any apparent design goals of Impala that
>>the
>> > Palo
>> > > >community thinks are fundamentally incompatible with Palo?
>> > > >
>> > > >Thanks,
>> > > >Jim
>> > > >
>> > > >On 2018/06/08 04:45:32, "Li,De(BDG)"  wrote:
>> > > >> Hi all,
>> > > >>
>> > > >> I am Reed, as a developer worked with the team for Palo (a
>>MPP-based
>> > > >>interactive SQL data warehousing).
>> > > >> https://github.com/baidu/palo/wiki/Palo-Overview
>> > > >>
>> > > >> We propose to contribute Palo as an Apache Incubator project, and
>> > > >> we are still looking for possible Champion if anyone would like
>>to
>> > > >>volunteer. Thanks a lot.
>> > > >>
>> > > >> Best Regards,
>> > > >> Reed
>> > > >>
>> > > >> ===
>> > > >> The draft of the proposal as below:
>> > > >>
>> > > >> #Apache Palo
>> > > >>
>> > > >> ##Abstract
>> > > >>
>> > > >> Palo is a MPP-based interactive SQL data warehousing for
>>reporting
>> and
>> > > >>analysis.
>> > > >>
>> > > >> ##Proposal
>> > > >>
>> > > >> We propose to contribute the Palo codebase and associated
>>artifacts
>> > > >>(e.g. documentation, web-site content etc.) to the Apache Software
>> > > >>Foundation with the intent of forming a productive, meritocratic
>>and
>> > > >>open community around Palo’s continued 

Re: Looking for Champion

[Li,De(BDG)]

Regarding Licence's question, we will complete the repair as soon as possible 
before voting.

发件人: Dave Fisher mailto:dave2w...@comcast.net>>
答复: mailto:general@incubator.apache.org>>
日期: 2018年6月9日 星期六 上午2:10
至: mailto:general@incubator.apache.org>>
主题: Re: Looking for Champion

Yuck. That’s a mess. That is one very large diff.

I see a few files related to AES the were GPL converted to Apache which not 
allowed.
Copyrights were changed too which is also incorrect.

Changes to this file 
be/src/http/mongoose.h
 violate license and copyright of Sergey Lyubka

GitHub makes you expand each diff after awhile.

There are dependency licenses that might be issues too.

These licenses have not been evaluated by LEGAL.
* OpenLdap (OpenLDAP Software License)
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=blob;f=LICENSE;hb=e5f8117f0ce088d0bd7a8e18ddf37eaa40eb09b1
* rapidjson (Tencent)
Unknown
* cyrus-sasl (CMU License)
https://spdx.org/licenses/MIT-CMU.html
AKA MIT-CMU

Lots of work in evaluating licenses.

On Jun 8, 2018, at 9:46 AM, Ted Dunning 
mailto:ted.dunn...@gmail.com>> wrote:

Ouch.

The copyright in question was attached to code from the source code for
mySQL. There is no way that code can be in an Apache project.

Given the cut and paste history, it seems like it will require a very
detailed audit of code history or web searches to find where the original
code came from. The my_aes.c and .h files, for instance, have no hint in
their history that they came from GPL'ed code.

Yeah. Lot’s of oversight.

If we accept this proposal we need a Mentor who has time to help with this mess.

I don’t know that I have the time to lead that effort. Anyone?

Regards,
Dave


On Fri, Jun 8, 2018 at 5:37 PM Todd Lipcon 
mailto:t...@cloudera.com>> wrote:

...

+1. Also briefly browsing the code I found suspicious commits like this
one:

https://github.com/baidu/palo/commit/6486be64c319fe0beb8c6b4430c1662de54f182e

... in which a GPL license copyright by Oracle was "fixed" to be an Apache
license copyright Baidu.

So if this project does enter incubation I think we should be extra careful
to audit the origins of all of the source code.

Re: Looking for Champion

[Li,De(BDG)]

Thanks to Jim's suggestion. We will seriously consider this proposal.
Also, for some of the opinions given by everyone,
the Palo development team will seriously discuss and then give
everyone a unified reply next week.



在 2018/6/9 上午7:41， "Jim Apple"  写入:

>>
>> Generally Apache has no rules against multiple projects fulfilling
>>similar
>> goals or use cases, even when those projects might compete. However I
>>think
>> it would be relatively unusual to incubate a project that appears to be
>> derived from a fork of an existing project, at least without first
>> considering whether the additional feature set could be contributed
>>back to
>> the existing community.
>>
>
>And this is something I'm really excited about. If only the storage system
>part of Palo were contributed to the ASF, and simultaneously the Palo
>community and the Impala community worked together to integrate the query
>engine work of Palo into Impala, then this could provide a lot of benefit
>to users, I think. My hope is that it would eliminate the toil the Palo
>community is engaged in by rebasing Impala changes (as Tim noticed).
>Impala, meanwhile, might benefit from some changes Palo has made, like
>SIMD
>filtering.
>
>This could be a lot of work, but the current system seems to already
>include quite a lot of inefficiency from the duplication.