[VOTE] Release Apache Ratis (incubating) 0.2.0 (rc2)

[Elek, Marton]

Hi All,

The Apache Ratis community has voted on and approved a proposal to 
release Apache Ratis 0.2.0-rc2.


We now kindly request that the Incubator PMC members review and vote on 
this incubator release candidate.


The problems from the previous vote are fixed 
(https://mail-archives.apache.org/mod_mbox/incubator-general/201805.mbox/%3C8BB8FABD-E3F7-4DB3-9417-DDB552675416%40classsoftware.com%3E)


• The name contains incubating (not incubator)
• Separated LICENSE and NOTICE for bin/source releases
• The missing BSD license (for Crc32 files) is added to the LICENSE

Apache Ratis is a highly customizable Raft protocol implementation in Java.

The vote thread is at:

https://mail-archives.apache.org/mod_mbox/ratis-dev/201806.mbox/%3C7ddfb4cd-4501-e15a-4bc2-d9a86b9d0d9d%40apache.org%3E

and the result is at:

https://mail-archives.apache.org/mod_mbox/ratis-dev/201807.mbox/%3Cde45e7c7-d2b0-935e-6595-870f87bf1a51%40apache.org%3E

This is the second incubator release and it includes more than 120 
improvements and fixes since the previous 0.1.0-alpha release. This is 
the first release

which includes a binary package with ready to use examples.

All distribution packages, including signatures, digests, etc. can be
found at:

https://dist.apache.org/repos/dist/dev/incubator/ratis/0.2.0/rc2

Staged artifacts can be found at:

https://repository.apache.org/content/repositories/orgapacheratis-1005

This release has been signed with PGP key 0EE79B28, corresponding to
e...@apache.org, which is included in the repository's KEYS file
(https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS).

This key can be found on keyservers, such as:

http://pgp.mit.edu/pks/lookup?op=get=0x0EE79B28

Or in the apache phonebook:

https://people.apache.org/keys/committer/elek.asc

The release candidate has been tagged in git with ratis-0.2.0-rc2 (4d14160)

https://github.com/apache/incubator-ratis/releases/tag/ratis-0.2.0-rc2

Please review and vote. The vote will be open for at least 72 hours or 
until necessary number of votes are reached.


# Review/testing

 You can build the project from the source code package with

```
mvn clean install  assembly:single -DskipTests=true
```

The binary papckage can be smoketested with:

./examples/bin/start-all.sh
./examples/bin/client.sh assign --name a --value 2
./examples/bin/client.sh get --name a

Thank you very much,
Marton Elek


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

[DISCUSS] Graduate Apache HAWQ (incubating) as a TLP

[Roman Shaposhnik]

Hi!

HAWQ community seems to be ready to graduate. What
do fellow IPMC members think?

Details on the community are below and here's a link to
the DISCUSS thread:

https://lists.apache.org/thread.html/67a2d52ef29cbf9e93d8050ed0193cc110a919962dd92f8436b343b7@%3Cdev.hawq.apache.org%3E

Thanks,
Roman.

-- Forwarded message --
From: Radar Lei 
Date: Tue, Jun 19, 2018 at 2:40 AM
Subject: [DISCUSS] Graduate Apache HAWQ (incubating) as a TLP
To: dev 


Hi All,

With the 2.3.0.0-incubating release officially out, the Apache HAWQ
community and its mentors believe it is time to consider graduation to the
TLP:
https://lists.apache.org/thread.html/b4a0b5671ce377b3d51c9b7
ab00496a1eebfcbf1696ce8b67e078c64@%3Cdev.hawq.apache.org%3E

Apache HAWQ entered incubation in September of 2015, since then, the HAWQ
community learned a lot about how to do things in Apache ways. Now we have
a healthy and engaged community, ready to help with all questions from the
HAWQ community. We delivered four releases including two binary releases,
now we can do self-driving releases in good cadence. The PPMC has
demonstrated a good understanding of growing the community by electing 12
individuals as committers and PPMC members. The PPMC addressed the maturity
issues one by one followed by Apache Project Maturity Model, currently all
the License and IP issues are resolved. This demonstrated our understanding
of ASF's IP policies.

All in all, I believe this project is qualified as a true TLP and we should
recognize this fact by formally awarding it such a status. This thread
means to open up the very same discussion that we had among the mentors and
HAWQ community to the rest of the IPMC. It is a DISCUSS thread so feel free
to ask questions.

To get you all going, here are a few data points which may help:

Project status:
 http://incubator.apache.org/projects/hawq.html

Project website:
  http://hawq.incubator.apache.org/

Project documentation:
   http://hawq.incubator.apache.org/docs/userguide/2.3.0.0-inc
ubating/overview/HAWQOverview.html
   http://hawq.apache.org/#download

Maturity assessment:
https://cwiki.apache.org/confluence/display/HAWQ/ASF+Maturity+Evaluation

DRAFT of the board resolution is at the bottom of this email

Proposed PMC size: 45 members

Total number of committers: 45 members

PMC affiliation (* indicated chair):
   Pivotal (20)
 * Oushu (7)
   Amazon (3)
   Hashdata (2)
   Autonomic (1)
   Confluent (1)
   Datometry (1)
   Hortonworks (1)
   Microsoft (1)
   PETUUM (1)
   Privacera (1)
   Qubole (1)
   Snowflake (1)
   State Street (1)
   Unifi (1)
   Visa (1)
   ZEDEDA (1)

1549 commits on develop
1375 PR”s on GitHub
63 contributors across all branches

1624 issues created
1350 issues resolved

dev list averaged ~53 msgs/month over last 12 months
user list averaged ~6 msgs/month over last 12 months
129 unique posters


committer affiliations:
active
  pivotal.io
  oushu.io
  hashdata.cn
occasional
  amazon.com
  autonomic.ai
  confluent.io
  datometry.com
  hortonworks.com
  microsoft.com
  petuum.com
  privacera.com
  qubole.com
  snowflake.net
  statestreet.com
  unifisoftware.com
  visa.com
  zededa.com


Thanks,
Radar



## Resolution to create a TLP from graduating Incubator podling

X. Establish the Apache HAWQ 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 Hadoop native SQL query engine that
   combines the key technological advantages of MPP database
   with the scalability and convenience of Hadoop.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the "Apache HAWQ Project",
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache HAWQ Project be and hereby is
   responsible for the creation and maintenance of software
   related to Hadoop native SQL query engine that
   combines the key technological advantages of MPP database
   with the scalability and convenience of Hadoop;
   and be it further

   RESOLVED, that the office of "Vice President, Apache HAWQ" 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 HAWQ Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache HAWQ Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed 

Re: [VOTE] Accept Doris into the Apache Incubator

[Xin Wang]

+1

Charith Elvitigala  于2018年7月6日周五 上午9:37写道：

> +1
>
> On Fri, 6 Jul 2018 at 06:21, Tan,Zhongyi  wrote:
>
> > +1 （no binding）
> >
> > 发件人: Dave Fisher mailto:dave2w...@comcast.net>>
> > 答复: mailto:general@incubator.apache.org>>
> > 日期: 2018年7月6日 星期五 上午3:22
> > 至: mailto:general@incubator.apache.org>>
> > 主题: [VOTE] Accept Doris into the Apache Incubator
> >
> > Hi All,
> >
> > I would like to start a VOTE to bring the Doris project as an Apache
> > incubator podling.
> >
> > 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 Doris into the Apache Incubator
> > [] +0 Abstain.
> > [] -1 Do not accept Doris into the Apache Incubator because ...
> >
> > The proposal is listed below, but you can also access it on the wiki:
> >
> > https://wiki.apache.org/incubator/DorisProposal
> >
> > Best regards,
> > Dave
> >
> > = Apache Doris =
> >
> > == Abstract ==
> >
> > Doris is a MPP-based interactive SQL data warehousing for reporting and
> > analysis.
> >
> > == Proposal ==
> >
> > We propose to contribute the Doris codebase and associated artifacts
> (e.g.
> > documentation, web-site content etc.) to the Apache Software Foundation,
> > and aim to build an open community around Doris’s continued development
> in
> > the ‘Apache Way’.
> >
> > === Overview of Doris ===
> >
> > Doris’s implementation consists of two daemons: Frontend (FE) and Backend
> > (BE).
> >
> > **Frontend daemon** consists of query coordinator and catalog manager.
> > Query coordinator is responsible for receiving users’ sql queries,
> > compiling queries and managing queries execution. Catalog manager is
> > responsible for managing metadata such as databases, tables, partitions,
> > replicas and etc. Several frontend daemons could be deployed to guarantee
> > fault-tolerance, and load balancing.
> >
> > **Backend daemon** stores the data and executes the query fragments. Many
> > backend daemons could also be deployed to provide scalability and
> > fault-tolerance.
> >
> > A typical Doris cluster generally composes of several frontend daemons
> and
> > dozens to hundreds of backend daemons.
> >
> > Users can use MySQL client tools to connect any frontend daemon to submit
> > SQL query. Frontend receives the query and compiles it into query plans
> > executable by the Backend. Then Frontend sends the query plan fragments
> to
> > Backend. Backend will build a query execution DAG. Data is fetched and
> > pipelined into the DAG. The final result response is sent to client via
> > Frontend. The distribution of query fragment execution takes minimizing
> > data movement and maximizing scan locality as the main goal.
> >
> > == Background ==
> >
> > At Baidu, Prior to Doris, different tools were deployed to solve diverse
> > requirements in many ways. And when a use case requires the simultaneous
> > availability of capabilities that cannot all be provided by a single
> tool,
> > users were forced to build hybrid architectures that stitch multiple
> tools
> > together, but we believe that they shouldn’t need to accept such inherent
> > complexity. A storage system built to provide great performance across a
> > broad range of workloads provides a more elegant solution to the problems
> > that hybrid architectures aim to solve. Doris is the solution.
> >
> > Doris is designed to be a simple and single tightly coupled system, not
> > depending on other systems. Doris provides high concurrent low latency
> > point query performance, but also provides high throughput queries of
> > ad-hoc analysis. Doris provides bulk-batch data loading, but also
> provides
> > near real-time mini-batch data loading. Doris also provides high
> > availability, reliability, fault tolerance, and scalability.
> >
> > == Rationale ==
> >
> > Doris mainly integrates the technology of Google Mesa and Apache Impala.
> >
> > Mesa is a highly scalable analytic data storage system that stores
> > critical measurement data related to Google's Internet advertising
> > business. Mesa is designed to satisfy complex and challenging set of
> users’
> > and systems’ requirements, including near real-time data ingestion and
> > query ability, as well as high availability, reliability, fault
> tolerance,
> > and scalability for large data and query volumes.
> >
> > Impala is a modern, open-source MPP SQL engine architected from the
> ground
> > up for the Hadoop data processing environment. At present, by virtue of
> its
> > superior performance and rich functionality， Impala has been comparable
> to
> > many commercial MPP database query engine. Mesa can satisfy the needs of
> > many of our storage requirements, however Mesa itself does not provide a
> > SQL query engine; Impala is a very good MPP SQL query engine, but 

Re: [VOTE] Accept Doris into the Apache Incubator

[Charith Elvitigala]

+1

On Fri, 6 Jul 2018 at 06:21, Tan,Zhongyi  wrote:

> +1 （no binding）
>
> 发件人: Dave Fisher mailto:dave2w...@comcast.net>>
> 答复: mailto:general@incubator.apache.org>>
> 日期: 2018年7月6日 星期五 上午3:22
> 至: mailto:general@incubator.apache.org>>
> 主题: [VOTE] Accept Doris into the Apache Incubator
>
> Hi All,
>
> I would like to start a VOTE to bring the Doris project as an Apache
> incubator podling.
>
> 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 Doris into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Doris into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
>
> https://wiki.apache.org/incubator/DorisProposal
>
> Best regards,
> Dave
>
> = Apache Doris =
>
> == Abstract ==
>
> Doris is a MPP-based interactive SQL data warehousing for reporting and
> analysis.
>
> == Proposal ==
>
> We propose to contribute the Doris codebase and associated artifacts (e.g.
> documentation, web-site content etc.) to the Apache Software Foundation,
> and aim to build an open community around Doris’s continued development in
> the ‘Apache Way’.
>
> === Overview of Doris ===
>
> Doris’s implementation consists of two daemons: Frontend (FE) and Backend
> (BE).
>
> **Frontend daemon** consists of query coordinator and catalog manager.
> Query coordinator is responsible for receiving users’ sql queries,
> compiling queries and managing queries execution. Catalog manager is
> responsible for managing metadata such as databases, tables, partitions,
> replicas and etc. Several frontend daemons could be deployed to guarantee
> fault-tolerance, and load balancing.
>
> **Backend daemon** stores the data and executes the query fragments. Many
> backend daemons could also be deployed to provide scalability and
> fault-tolerance.
>
> A typical Doris cluster generally composes of several frontend daemons and
> dozens to hundreds of backend daemons.
>
> Users can use MySQL client tools to connect any frontend daemon to submit
> SQL query. Frontend receives the query and compiles it into query plans
> executable by the Backend. Then Frontend sends the query plan fragments to
> Backend. Backend will build a query execution DAG. Data is fetched and
> pipelined into the DAG. The final result response is sent to client via
> Frontend. The distribution of query fragment execution takes minimizing
> data movement and maximizing scan locality as the main goal.
>
> == Background ==
>
> At Baidu, Prior to Doris, different tools were deployed to solve diverse
> requirements in many ways. And when a use case requires the simultaneous
> availability of capabilities that cannot all be provided by a single tool,
> users were forced to build hybrid architectures that stitch multiple tools
> together, but we believe that they shouldn’t need to accept such inherent
> complexity. A storage system built to provide great performance across a
> broad range of workloads provides a more elegant solution to the problems
> that hybrid architectures aim to solve. Doris is the solution.
>
> Doris is designed to be a simple and single tightly coupled system, not
> depending on other systems. Doris provides high concurrent low latency
> point query performance, but also provides high throughput queries of
> ad-hoc analysis. Doris provides bulk-batch data loading, but also provides
> near real-time mini-batch data loading. Doris also provides high
> availability, reliability, fault tolerance, and scalability.
>
> == Rationale ==
>
> Doris mainly integrates the technology of Google Mesa and Apache Impala.
>
> Mesa is a highly scalable analytic data storage system that stores
> critical measurement data related to Google's Internet advertising
> business. Mesa is designed to satisfy complex and challenging set of users’
> and systems’ requirements, including near real-time data ingestion and
> query ability, as well as high availability, reliability, fault tolerance,
> and scalability for large data and query volumes.
>
> Impala is a modern, open-source MPP SQL engine architected from the ground
> up for the Hadoop data processing environment. At present, by virtue of its
> superior performance and rich functionality， Impala has been comparable to
> many commercial MPP database query engine. Mesa can satisfy the needs of
> many of our storage requirements, however Mesa itself does not provide a
> SQL query engine; Impala is a very good MPP SQL query engine, but the lack
> of a perfect distributed storage engine. So in the end we chose the
> combination of these two technologies.
>
> Learning from Mesa’s data model, we developed a distributed storage
> engine. Unlike Mesa, this storage engine does not rely on any distributed
> file system. Then we deeply 

Re: [VOTE] Accept Doris into the Apache Incubator

[Tan,Zhongyi]

+1 （no binding）

发件人: Dave Fisher mailto:dave2w...@comcast.net>>
答复: mailto:general@incubator.apache.org>>
日期: 2018年7月6日 星期五 上午3:22
至: mailto:general@incubator.apache.org>>
主题: [VOTE] Accept Doris into the Apache Incubator

Hi All,

I would like to start a VOTE to bring the Doris project as an Apache incubator 
podling.

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 Doris into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept Doris into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/DorisProposal

Best regards,
Dave

= Apache Doris =

== Abstract ==

Doris is a MPP-based interactive SQL data warehousing for reporting and 
analysis.

== Proposal ==

We propose to contribute the Doris codebase and associated artifacts (e.g. 
documentation, web-site content etc.) to the Apache Software Foundation, and 
aim to build an open community around Doris’s continued development in the 
‘Apache Way’.

=== Overview of Doris ===

Doris’s implementation consists of two daemons: Frontend (FE) and Backend (BE).

**Frontend daemon** consists of query coordinator and catalog manager. Query 
coordinator is responsible for receiving users’ sql queries, compiling queries 
and managing queries execution. Catalog manager is responsible for managing 
metadata such as databases, tables, partitions, replicas and etc. Several 
frontend daemons could be deployed to guarantee fault-tolerance, and load 
balancing.

**Backend daemon** stores the data and executes the query fragments. Many 
backend daemons could also be deployed to provide scalability and 
fault-tolerance.

A typical Doris cluster generally composes of several frontend daemons and 
dozens to hundreds of backend daemons.

Users can use MySQL client tools to connect any frontend daemon to submit SQL 
query. Frontend receives the query and compiles it into query plans executable 
by the Backend. Then Frontend sends the query plan fragments to Backend. 
Backend will build a query execution DAG. Data is fetched and pipelined into 
the DAG. The final result response is sent to client via Frontend. The 
distribution of query fragment execution takes minimizing data movement and 
maximizing scan locality as the main goal.

== Background ==

At Baidu, Prior to Doris, different tools were deployed to solve diverse 
requirements in many ways. And when a use case requires the simultaneous 
availability of capabilities that cannot all be provided by a single tool, 
users were forced to build hybrid architectures that stitch multiple tools 
together, but we believe that they shouldn’t need to accept such inherent 
complexity. A storage system built to provide great performance across a broad 
range of workloads provides a more elegant solution to the problems that hybrid 
architectures aim to solve. Doris is the solution.

Doris is designed to be a simple and single tightly coupled system, not 
depending on other systems. Doris provides high concurrent low latency point 
query performance, but also provides high throughput queries of ad-hoc 
analysis. Doris provides bulk-batch data loading, but also provides near 
real-time mini-batch data loading. Doris also provides high availability, 
reliability, fault tolerance, and scalability.

== Rationale ==

Doris mainly integrates the technology of Google Mesa and Apache Impala.

Mesa is a highly scalable analytic data storage system that stores critical 
measurement data related to Google's Internet advertising business. Mesa is 
designed to satisfy complex and challenging set of users’ and systems’ 
requirements, including near real-time data ingestion and query ability, as 
well as high availability, reliability, fault tolerance, and scalability for 
large data and query volumes.

Impala is a modern, open-source MPP SQL engine architected from the ground up 
for the Hadoop data processing environment. At present, by virtue of its 
superior performance and rich functionality， Impala has been comparable to many 
commercial MPP database query engine. Mesa can satisfy the needs of many of our 
storage requirements, however Mesa itself does not provide a SQL query engine; 
Impala is a very good MPP SQL query engine, but the lack of a perfect 
distributed storage engine. So in the end we chose the combination of these two 
technologies.

Learning from Mesa’s data model, we developed a distributed storage engine. 
Unlike Mesa, this storage engine does not rely on any distributed file system. 
Then we deeply integrate this storage engine with Impala query engine. Query 
compiling, query execution coordination and catalog management of storage 
engine are integrated to be frontend daemon; query execution and 

Re: [VOTE] Accept Doris into the Apache Incubator

[Sijie Guo]

+1 (non-binding)

It is a good project to incubate in the ASF. Doris (Palo) team was very
responsive to the questions raised in the discussion. I believe with the
help from Mentors, it can become a great project in the ASF.

- Sijie

On Thu, Jul 5, 2018 at 12:22 PM Dave Fisher  wrote:

> Hi All,
>
> I would like to start a VOTE to bring the Doris project as an Apache
> incubator podling.
>
> 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 Doris into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Doris into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
>
> https://wiki.apache.org/incubator/DorisProposal
>
> Best regards,
> Dave
>
> = Apache Doris =
>
> == Abstract ==
>
> Doris is a MPP-based interactive SQL data warehousing for reporting and
> analysis.
>
> == Proposal ==
>
> We propose to contribute the Doris codebase and associated artifacts (e.g.
> documentation, web-site content etc.) to the Apache Software Foundation,
> and aim to build an open community around Doris’s continued development in
> the ‘Apache Way’.
>
> === Overview of Doris ===
>
> Doris’s implementation consists of two daemons: Frontend (FE) and Backend
> (BE).
>
> **Frontend daemon** consists of query coordinator and catalog manager.
> Query coordinator is responsible for receiving users’ sql queries,
> compiling queries and managing queries execution. Catalog manager is
> responsible for managing metadata such as databases, tables, partitions,
> replicas and etc. Several frontend daemons could be deployed to guarantee
> fault-tolerance, and load balancing.
>
> **Backend daemon** stores the data and executes the query fragments. Many
> backend daemons could also be deployed to provide scalability and
> fault-tolerance.
>
> A typical Doris cluster generally composes of several frontend daemons and
> dozens to hundreds of backend daemons.
>
> Users can use MySQL client tools to connect any frontend daemon to submit
> SQL query. Frontend receives the query and compiles it into query plans
> executable by the Backend. Then Frontend sends the query plan fragments to
> Backend. Backend will build a query execution DAG. Data is fetched and
> pipelined into the DAG. The final result response is sent to client via
> Frontend. The distribution of query fragment execution takes minimizing
> data movement and maximizing scan locality as the main goal.
>
> == Background ==
>
> At Baidu, Prior to Doris, different tools were deployed to solve diverse
> requirements in many ways. And when a use case requires the simultaneous
> availability of capabilities that cannot all be provided by a single tool,
> users were forced to build hybrid architectures that stitch multiple tools
> together, but we believe that they shouldn’t need to accept such inherent
> complexity. A storage system built to provide great performance across a
> broad range of workloads provides a more elegant solution to the problems
> that hybrid architectures aim to solve. Doris is the solution.
>
> Doris is designed to be a simple and single tightly coupled system, not
> depending on other systems. Doris provides high concurrent low latency
> point query performance, but also provides high throughput queries of
> ad-hoc analysis. Doris provides bulk-batch data loading, but also provides
> near real-time mini-batch data loading. Doris also provides high
> availability, reliability, fault tolerance, and scalability.
>
> == Rationale ==
>
> Doris mainly integrates the technology of Google Mesa and Apache Impala.
>
> Mesa is a highly scalable analytic data storage system that stores
> critical measurement data related to Google's Internet advertising
> business. Mesa is designed to satisfy complex and challenging set of users’
> and systems’ requirements, including near real-time data ingestion and
> query ability, as well as high availability, reliability, fault tolerance,
> and scalability for large data and query volumes.
>
> Impala is a modern, open-source MPP SQL engine architected from the ground
> up for the Hadoop data processing environment. At present, by virtue of its
> superior performance and rich functionality， Impala has been comparable to
> many commercial MPP database query engine. Mesa can satisfy the needs of
> many of our storage requirements, however Mesa itself does not provide a
> SQL query engine; Impala is a very good MPP SQL query engine, but the lack
> of a perfect distributed storage engine. So in the end we chose the
> combination of these two technologies.
>
> Learning from Mesa’s data model, we developed a distributed storage
> engine. Unlike Mesa, this storage engine does not rely on any distributed
> file system. Then we deeply 

Re: Podling Report Reminder - July 2018

[Dave Fisher]

Hi -

It’s not too late to report.

Regards,
Dave

> On Jul 5, 2018, at 4:09 PM, Edward Capriolo  wrote:
> 
> Pointed this out on the Gossip list:
> 
> AirflowAmaterasuAnnotatorBatchEEGobblinGossipHAWQLivyMilagroMXNetNetBeansODF
> ToolkitPLC4XRyaS2GraphSensSoftServiceCombTraffic ControlWeex
> 
> Pointing out of this list 10 failed to report in July.
> 
> On Thu, Jul 5, 2018 at 2:35 PM, Dave Fisher  wrote:
> 
>> Hi -
>> 
>>> On Jul 5, 2018, at 4:45 AM, Edward Capriolo 
>> wrote:
>>> 
>>> Also at one point the project was assigned a "shepard" who never signed
>> off
>>> on a single report even when the project was active. His first
>> interaction
>>> for the project was vote to moth ball it.
>> 
>> There is a difference between Mentors and Shepherds. A shepherd is
>> assigned for a reporting cycle to look into the podling to see how things
>> are going. I was assigned as shepherd this month and have left my comments
>> along with an email. Your mentors are supposed to provide guidance in the
>> Apache Way. If your mentors are absent then that is a different matter. If
>> you would like new mentors then please ask here on this list.
>> 
>> If on the other hand the Gossip community feels that the Apache Way and
>> particularly the release process is too much process and not enough coding
>> then that is your choice.
>> 
>> Regards,
>> Dave
>> 
>>> 
>>> 
>>> On Thu, Jul 5, 2018 at 7:35 AM, Edward Capriolo 
>>> wrote:
>>> 
 I want to get this out there. I do not know why everyone is stuck on
 gossip. There are some TLP that do not have activity for years and
>> podlings
 much older then gossip. I can give numerous examples.
 
 On Thu, Jun 28, 2018 at 1:10 PM, John D. Ament 
 wrote:
 
> That sounds like retirement to me.  The way I've always seen it is that
> podlings don't fail, the people behind them simply had a change in
> priorities.
> 
> Gossip is a great toolkit that I believe people will continue to use.
> 
> John
> 
> 
> On Thu, Jun 28, 2018, 12:44 PM Josh Elser  wrote:
> 
>> I've been trying to be patient around this, but I think this month's
>> incubator report must be "Gossip is going to exit incubation" (I'm not
>> sure what the proper verb is here; I only know that "retire" is wrong)
>> 
>> We've gone through many months where the only traffic I've seen on the
>> mailing list are the report reminders.
>> 
>> This doesn't need to be interpreted as "Gossip is a failure at the
>> ASF"
>> or anything of the such. It just means "It's not the right time for
>> Gossip at the ASF incubator". By all means, we can bring it back into
>> incubation if we get some more community traction behind the project.
>> 
>> On 6/27/18 5:41 PM, jmcl...@apache.org wrote:
>>> Dear podling,
>>> 
>>> This email was sent by an automated system on behalf of the Apache
>>> Incubator PMC. It is an initial reminder to give you plenty of time
>> to
>>> prepare your quarterly board report.
>>> 
>>> The board meeting is scheduled for Wed, 18 July 2018, 10:30 am PDT.
>>> The report for your podling will form a part of the Incubator PMC
>>> report. The Incubator PMC requires your report to be submitted 2
>> weeks
>>> before the board meeting, to allow sufficient time for review and
>>> submission (Wed, July 04).
>>> 
>>> Please submit your report with sufficient time to allow the Incubator
>>> PMC, and subsequently board members to review and digest. Again, the
>>> very latest you should submit your report is 2 weeks prior to the
> board
>>> meeting.
>>> 
>>> Candidate names should not be made public before people are actually
>>> elected, so please do not include the names of potential committers
>> or
>>> PPMC members in your report.
>>> 
>>> Thanks,
>>> 
>>> The Apache Incubator PMC
>>> 
>>> Submitting your Report
>>> 
>>> --
>>> 
>>> Your report should contain the following:
>>> 
>>> *   Your project name
>>> *   A brief description of your project, which assumes no knowledge
>> of
>>>the project or necessarily of its field
>>> *   A list of the three most important issues to address in the move
>>>towards graduation.
>>> *   Any issues that the Incubator PMC or ASF Board might wish/need to
> be
>>>aware of
>>> *   How has the community developed since the last report
>>> *   How has the project developed since the last report.
>>> *   How does the podling rate their own maturity.
>>> 
>>> This should be appended to the Incubator Wiki page at:
>>> 
>>> https://wiki.apache.org/incubator/July2018
>>> 
>>> Note: This is manually populated. You may need to wait a little
>> before
>>> this page is created from a template.
>>> 
>>> Mentors
>>> ---
>>> 
>>> Mentors 

Re: Podling Report Reminder - July 2018

[Edward Capriolo]

Pointed this out on the Gossip list:

AirflowAmaterasuAnnotatorBatchEEGobblinGossipHAWQLivyMilagroMXNetNetBeansODF
ToolkitPLC4XRyaS2GraphSensSoftServiceCombTraffic ControlWeex

Pointing out of this list 10 failed to report in July.

On Thu, Jul 5, 2018 at 2:35 PM, Dave Fisher  wrote:

> Hi -
>
> > On Jul 5, 2018, at 4:45 AM, Edward Capriolo 
> wrote:
> >
> > Also at one point the project was assigned a "shepard" who never signed
> off
> > on a single report even when the project was active. His first
> interaction
> > for the project was vote to moth ball it.
>
> There is a difference between Mentors and Shepherds. A shepherd is
> assigned for a reporting cycle to look into the podling to see how things
> are going. I was assigned as shepherd this month and have left my comments
> along with an email. Your mentors are supposed to provide guidance in the
> Apache Way. If your mentors are absent then that is a different matter. If
> you would like new mentors then please ask here on this list.
>
> If on the other hand the Gossip community feels that the Apache Way and
> particularly the release process is too much process and not enough coding
> then that is your choice.
>
> Regards,
> Dave
>
> >
> >
> > On Thu, Jul 5, 2018 at 7:35 AM, Edward Capriolo 
> > wrote:
> >
> >> I want to get this out there. I do not know why everyone is stuck on
> >> gossip. There are some TLP that do not have activity for years and
> podlings
> >> much older then gossip. I can give numerous examples.
> >>
> >> On Thu, Jun 28, 2018 at 1:10 PM, John D. Ament 
> >> wrote:
> >>
> >>> That sounds like retirement to me.  The way I've always seen it is that
> >>> podlings don't fail, the people behind them simply had a change in
> >>> priorities.
> >>>
> >>> Gossip is a great toolkit that I believe people will continue to use.
> >>>
> >>> John
> >>>
> >>>
> >>> On Thu, Jun 28, 2018, 12:44 PM Josh Elser  wrote:
> >>>
>  I've been trying to be patient around this, but I think this month's
>  incubator report must be "Gossip is going to exit incubation" (I'm not
>  sure what the proper verb is here; I only know that "retire" is wrong)
> 
>  We've gone through many months where the only traffic I've seen on the
>  mailing list are the report reminders.
> 
>  This doesn't need to be interpreted as "Gossip is a failure at the
> ASF"
>  or anything of the such. It just means "It's not the right time for
>  Gossip at the ASF incubator". By all means, we can bring it back into
>  incubation if we get some more community traction behind the project.
> 
>  On 6/27/18 5:41 PM, jmcl...@apache.org wrote:
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time
> to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 18 July 2018, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2
> weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, July 04).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the
> >>> board
> > meeting.
> >
> > Candidate names should not be made public before people are actually
> > elected, so please do not include the names of potential committers
> or
> > PPMC members in your report.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge
> of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to
> >>> be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> > *   How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://wiki.apache.org/incubator/July2018
> >
> > Note: This is manually populated. You may need to wait a little
> before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off
> >>> on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects 

Re: [VOTE] Accept Doris into the Apache Incubator

[Dave Fisher]

Here is my +1 (binding)

> On Jul 5, 2018, at 12:22 PM, Dave Fisher  wrote:
> 
> Hi All,
> 
> I would like to start a VOTE to bring the Doris project as an Apache 
> incubator podling.
> 
> 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 Doris into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Doris into the Apache Incubator because ...
> 
> The proposal is listed below, but you can also access it on the wiki:
> 
> https://wiki.apache.org/incubator/DorisProposal 
> 
> 
> Best regards,
> Dave
> 
> = Apache Doris =
> 
> == Abstract ==
> 
> Doris is a MPP-based interactive SQL data warehousing for reporting and 
> analysis.
> 
> == Proposal ==
> 
> We propose to contribute the Doris codebase and associated artifacts (e.g. 
> documentation, web-site content etc.) to the Apache Software Foundation, and 
> aim to build an open community around Doris’s continued development in the 
> ‘Apache Way’.
> 
> === Overview of Doris ===
> 
> Doris’s implementation consists of two daemons: Frontend (FE) and Backend 
> (BE).
> 
> **Frontend daemon** consists of query coordinator and catalog manager. Query 
> coordinator is responsible for receiving users’ sql queries, compiling 
> queries and managing queries execution. Catalog manager is responsible for 
> managing metadata such as databases, tables, partitions, replicas and etc. 
> Several frontend daemons could be deployed to guarantee fault-tolerance, and 
> load balancing.
> 
> **Backend daemon** stores the data and executes the query fragments. Many 
> backend daemons could also be deployed to provide scalability and 
> fault-tolerance.
> 
> A typical Doris cluster generally composes of several frontend daemons and 
> dozens to hundreds of backend daemons.
> 
> Users can use MySQL client tools to connect any frontend daemon to submit SQL 
> query. Frontend receives the query and compiles it into query plans 
> executable by the Backend. Then Frontend sends the query plan fragments to 
> Backend. Backend will build a query execution DAG. Data is fetched and 
> pipelined into the DAG. The final result response is sent to client via 
> Frontend. The distribution of query fragment execution takes minimizing data 
> movement and maximizing scan locality as the main goal.
> 
> == Background ==
> 
> At Baidu, Prior to Doris, different tools were deployed to solve diverse 
> requirements in many ways. And when a use case requires the simultaneous 
> availability of capabilities that cannot all be provided by a single tool, 
> users were forced to build hybrid architectures that stitch multiple tools 
> together, but we believe that they shouldn’t need to accept such inherent 
> complexity. A storage system built to provide great performance across a 
> broad range of workloads provides a more elegant solution to the problems 
> that hybrid architectures aim to solve. Doris is the solution.
> 
> Doris is designed to be a simple and single tightly coupled system, not 
> depending on other systems. Doris provides high concurrent low latency point 
> query performance, but also provides high throughput queries of ad-hoc 
> analysis. Doris provides bulk-batch data loading, but also provides near 
> real-time mini-batch data loading. Doris also provides high availability, 
> reliability, fault tolerance, and scalability.
> 
> == Rationale ==
> 
> Doris mainly integrates the technology of Google Mesa and Apache Impala.
> 
> Mesa is a highly scalable analytic data storage system that stores critical 
> measurement data related to Google's Internet advertising business. Mesa is 
> designed to satisfy complex and challenging set of users’ and systems’ 
> requirements, including near real-time data ingestion and query ability, as 
> well as high availability, reliability, fault tolerance, and scalability for 
> large data and query volumes.
> 
> Impala is a modern, open-source MPP SQL engine architected from the ground up 
> for the Hadoop data processing environment. At present, by virtue of its 
> superior performance and rich functionality， Impala has been comparable to 
> many commercial MPP database query engine. Mesa can satisfy the needs of many 
> of our storage requirements, however Mesa itself does not provide a SQL query 
> engine; Impala is a very good MPP SQL query engine, but the lack of a perfect 
> distributed storage engine. So in the end we chose the combination of these 
> two technologies.
> 
> Learning from Mesa’s data model, we developed a distributed storage engine. 
> Unlike Mesa, this storage engine does not rely on any distributed file 
> system. Then we deeply integrate this storage engine with 

[VOTE] Accept Doris into the Apache Incubator

[Dave Fisher]

Hi All,

I would like to start a VOTE to bring the Doris project as an Apache incubator 
podling.

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 Doris into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept Doris into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/DorisProposal

Best regards,
Dave

= Apache Doris =

== Abstract ==

Doris is a MPP-based interactive SQL data warehousing for reporting and 
analysis.

== Proposal ==

We propose to contribute the Doris codebase and associated artifacts (e.g. 
documentation, web-site content etc.) to the Apache Software Foundation, and 
aim to build an open community around Doris’s continued development in the 
‘Apache Way’.

=== Overview of Doris ===

Doris’s implementation consists of two daemons: Frontend (FE) and Backend (BE).

**Frontend daemon** consists of query coordinator and catalog manager. Query 
coordinator is responsible for receiving users’ sql queries, compiling queries 
and managing queries execution. Catalog manager is responsible for managing 
metadata such as databases, tables, partitions, replicas and etc. Several 
frontend daemons could be deployed to guarantee fault-tolerance, and load 
balancing.

**Backend daemon** stores the data and executes the query fragments. Many 
backend daemons could also be deployed to provide scalability and 
fault-tolerance.

A typical Doris cluster generally composes of several frontend daemons and 
dozens to hundreds of backend daemons.

Users can use MySQL client tools to connect any frontend daemon to submit SQL 
query. Frontend receives the query and compiles it into query plans executable 
by the Backend. Then Frontend sends the query plan fragments to Backend. 
Backend will build a query execution DAG. Data is fetched and pipelined into 
the DAG. The final result response is sent to client via Frontend. The 
distribution of query fragment execution takes minimizing data movement and 
maximizing scan locality as the main goal.

== Background ==

At Baidu, Prior to Doris, different tools were deployed to solve diverse 
requirements in many ways. And when a use case requires the simultaneous 
availability of capabilities that cannot all be provided by a single tool, 
users were forced to build hybrid architectures that stitch multiple tools 
together, but we believe that they shouldn’t need to accept such inherent 
complexity. A storage system built to provide great performance across a broad 
range of workloads provides a more elegant solution to the problems that hybrid 
architectures aim to solve. Doris is the solution.

Doris is designed to be a simple and single tightly coupled system, not 
depending on other systems. Doris provides high concurrent low latency point 
query performance, but also provides high throughput queries of ad-hoc 
analysis. Doris provides bulk-batch data loading, but also provides near 
real-time mini-batch data loading. Doris also provides high availability, 
reliability, fault tolerance, and scalability.

== Rationale ==

Doris mainly integrates the technology of Google Mesa and Apache Impala.

Mesa is a highly scalable analytic data storage system that stores critical 
measurement data related to Google's Internet advertising business. Mesa is 
designed to satisfy complex and challenging set of users’ and systems’ 
requirements, including near real-time data ingestion and query ability, as 
well as high availability, reliability, fault tolerance, and scalability for 
large data and query volumes.

Impala is a modern, open-source MPP SQL engine architected from the ground up 
for the Hadoop data processing environment. At present, by virtue of its 
superior performance and rich functionality， Impala has been comparable to many 
commercial MPP database query engine. Mesa can satisfy the needs of many of our 
storage requirements, however Mesa itself does not provide a SQL query engine; 
Impala is a very good MPP SQL query engine, but the lack of a perfect 
distributed storage engine. So in the end we chose the combination of these two 
technologies.

Learning from Mesa’s data model, we developed a distributed storage engine. 
Unlike Mesa, this storage engine does not rely on any distributed file system. 
Then we deeply integrate this storage engine with Impala query engine. 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. With this integration, we implemented a 
single, full-featured, high performance state the art of MPP database, as well 
as 

Re: Podling Report Reminder - July 2018

[Dave Fisher]

Hi -

> On Jul 5, 2018, at 4:45 AM, Edward Capriolo  wrote:
> 
> Also at one point the project was assigned a "shepard" who never signed off
> on a single report even when the project was active. His first interaction
> for the project was vote to moth ball it.

There is a difference between Mentors and Shepherds. A shepherd is assigned for 
a reporting cycle to look into the podling to see how things are going. I was 
assigned as shepherd this month and have left my comments along with an email. 
Your mentors are supposed to provide guidance in the Apache Way. If your 
mentors are absent then that is a different matter. If you would like new 
mentors then please ask here on this list.

If on the other hand the Gossip community feels that the Apache Way and 
particularly the release process is too much process and not enough coding then 
that is your choice.

Regards,
Dave

> 
> 
> On Thu, Jul 5, 2018 at 7:35 AM, Edward Capriolo 
> wrote:
> 
>> I want to get this out there. I do not know why everyone is stuck on
>> gossip. There are some TLP that do not have activity for years and podlings
>> much older then gossip. I can give numerous examples.
>> 
>> On Thu, Jun 28, 2018 at 1:10 PM, John D. Ament 
>> wrote:
>> 
>>> That sounds like retirement to me.  The way I've always seen it is that
>>> podlings don't fail, the people behind them simply had a change in
>>> priorities.
>>> 
>>> Gossip is a great toolkit that I believe people will continue to use.
>>> 
>>> John
>>> 
>>> 
>>> On Thu, Jun 28, 2018, 12:44 PM Josh Elser  wrote:
>>> 
 I've been trying to be patient around this, but I think this month's
 incubator report must be "Gossip is going to exit incubation" (I'm not
 sure what the proper verb is here; I only know that "retire" is wrong)
 
 We've gone through many months where the only traffic I've seen on the
 mailing list are the report reminders.
 
 This doesn't need to be interpreted as "Gossip is a failure at the ASF"
 or anything of the such. It just means "It's not the right time for
 Gossip at the ASF incubator". By all means, we can bring it back into
 incubation if we get some more community traction behind the project.
 
 On 6/27/18 5:41 PM, jmcl...@apache.org wrote:
> Dear podling,
> 
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
> 
> The board meeting is scheduled for Wed, 18 July 2018, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, July 04).
> 
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the
>>> board
> meeting.
> 
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
> 
> Thanks,
> 
> The Apache Incubator PMC
> 
> Submitting your Report
> 
> --
> 
> Your report should contain the following:
> 
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to
>>> be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://wiki.apache.org/incubator/July2018
> 
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
> 
> Mentors
> ---
> 
> Mentors should review reports for their project(s) and sign them off
>>> on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
> 
> Incubator PMC
> 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>>> 
>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: Podling Report Reminder - July 2018

[Ted Dunning]

On Thu, Jul 5, 2018 at 5:02 AM Edward Capriolo 
wrote:

> Also what is the point of forcing us into this monthly reporting cycle? It
> is kinda stressing me out. Is this a new thing just to harass me into
> retirement.
>

That is a common step if a project doesn't produce reports reliably or
seems to have a significant disfunction.

It isn't usually a stressor at the level it appears to be in this case.

It is definitely not harassment aimed at you.



>
> Also I asked about this:
>
> http://apache-incubator-general.996316.n3.nabble.com/Suggestion-for-podling-reminder-report-emails-td59035.html
> . Whats up with that? I mean its so worth wild to start this close down the
> podling convo like every month, but no one can go out and fix the email.
>

I think that would be great to have fixed. It bugs me when I get emails and
have to drill in to figure out what's up. Of course, I haven't found time
to contribute a fix, so I try to be circumspect in my frustration.

My guess is that it would be the work of a moment to do the fix but many
hours to figure out how. Sounds like you are are as time crunched as I, so
it isn't happening based on your efforts or mine.

In any case, the fact that an email subject line doesn't get augmented
isn't actually a good reason to keep a project alive if it has really
should retire. Two completely separate issues.

Re: Podling Report Reminder - July 2018

[Ted Dunning]

On Thu, Jul 5, 2018 at 4:35 AM Edward Capriolo 
wrote:

> I want to get this out there. I do not know why everyone is stuck on
> gossip. There are some TLP that do not have activity for years and podlings
> much older then gossip. I can give numerous examples.


Please do give these examples. They may need to retire as well.

Closing down projects that have no activity and no ability to respond to
security reports is an ongoing effort. It isn't focussed just on gossip by
any means.

The real problem arises when a project is clearly inert but one or more
people pop up when retirement is mentioned. Then nothing happens.  Letting
go is good in those cases.

Re: [DISCUSS] Doris Proposal

[Jim Apple]

Looks good to me. Thanks!

On Thu, Jul 5, 2018 at 9:17 AM, Dave Fisher  wrote:

> Hi -
>
> There was no reply yet. I made a change to the proposal.
>
> > On Jul 2, 2018, at 9:51 AM, Dave Fisher  wrote:
> >
> > Hi Jim,
> >
> >> On Jun 30, 2018, at 8:58 AM, Jim Apple 
> wrote:
> >>
> >> Can you help me understand which portion of this document addresses the
> >> discussions that occurred on the thread? The thread included discussion
> of
> >>
> >> 1. The name
> >> 2. Licence and copyright
> >
> > The remaining license and copyright issues are a natural part of
> Incubation and should be handled with the Mentor’s help.
> >
> >> 3. Attribution (Tim's Impala patch that was copied without attribution)
> >
> > Would additional text in the Impala part of the rationale help explain?
> Or, should a specific paragraph be added elsewhere?
> >
> >> 4. Impala integration
> >
> > The Doris team has a plan to handle this. Do you want it incorporated in
> the proposal? Or acknowledged along with (3)?
>
> I added the following to Community:
>
> "Doris makes use of Apache Impala. It was identified during early review
> of the proposal that the Doris community will need to work with Impala to
> define a suitable API."
>
> Regards,
> Dave
>
> >
> >> 5. Mentors and committer choices
> >>
> >> I only see #1 and #5 addressed in the wiki page, with no discussion on
> #2,
> >> #3, and #4. Am I missing something?
> >
> > Thanks,
> > Dave
> >
> >>
> >>
> >> On Fri, Jun 29, 2018 at 4:27 PM, Dave Fisher 
> wrote:
> >>
> >>> Hi -
> >>>
> >>> The Doris Proposal is available at https://wiki.apache.org/
> >>> incubator/DorisProposal
> >>>
> >>> It was updated to reflect the discussions that occurred under the
> thread
> >>> https://lists.apache.org/thread.html/74a3f3f945403b50515c658047d328
> >>> 4955288a637207e4f97ecc15d1@%3Cgeneral.incubator.apache.org%3E
> >>>
> >>> Please provide any necessary updates.
> >>>
> >>> We would like to start the VOTE on Monday.
> >>>
> >>> Regards,
> >>> Dave
> >>>
> >
>
>

Re: [DISCUSS] Doris Proposal

[Dave Fisher]

Hi -

There was no reply yet. I made a change to the proposal.

> On Jul 2, 2018, at 9:51 AM, Dave Fisher  wrote:
> 
> Hi Jim,
> 
>> On Jun 30, 2018, at 8:58 AM, Jim Apple  wrote:
>> 
>> Can you help me understand which portion of this document addresses the
>> discussions that occurred on the thread? The thread included discussion of
>> 
>> 1. The name
>> 2. Licence and copyright
> 
> The remaining license and copyright issues are a natural part of Incubation 
> and should be handled with the Mentor’s help.
> 
>> 3. Attribution (Tim's Impala patch that was copied without attribution)
> 
> Would additional text in the Impala part of the rationale help explain? Or, 
> should a specific paragraph be added elsewhere?
> 
>> 4. Impala integration
> 
> The Doris team has a plan to handle this. Do you want it incorporated in the 
> proposal? Or acknowledged along with (3)?

I added the following to Community:

"Doris makes use of Apache Impala. It was identified during early review of the 
proposal that the Doris community will need to work with Impala to define a 
suitable API."

Regards,
Dave

> 
>> 5. Mentors and committer choices
>> 
>> I only see #1 and #5 addressed in the wiki page, with no discussion on #2,
>> #3, and #4. Am I missing something?
> 
> Thanks,
> Dave
> 
>> 
>> 
>> On Fri, Jun 29, 2018 at 4:27 PM, Dave Fisher  wrote:
>> 
>>> Hi -
>>> 
>>> The Doris Proposal is available at https://wiki.apache.org/
>>> incubator/DorisProposal
>>> 
>>> It was updated to reflect the discussions that occurred under the thread
>>> https://lists.apache.org/thread.html/74a3f3f945403b50515c658047d328
>>> 4955288a637207e4f97ecc15d1@%3Cgeneral.incubator.apache.org%3E
>>> 
>>> Please provide any necessary updates.
>>> 
>>> We would like to start the VOTE on Monday.
>>> 
>>> Regards,
>>> Dave
>>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: Podling Report Reminder - July 2018

[Edward Capriolo]

Also what is the point of forcing us into this monthly reporting cycle? It
is kinda stressing me out. Is this a new thing just to harass me into
retirement.

Also I asked about this:
http://apache-incubator-general.996316.n3.nabble.com/Suggestion-for-podling-reminder-report-emails-td59035.html
. Whats up with that? I mean its so worth wild to start this close down the
podling convo like every month, but no one can go out and fix the email.



On Thu, Jun 28, 2018 at 2:42 PM, Ted Dunning  wrote:

> We have been working for quite some time to desensitize people so that they
> don't have a strong emotional cost associated with different ways to leave
> incubation. That animus just gets people to avoid the right decision for
> far too long.
>
>
> On Thu, Jun 28, 2018, 10:22 Josh Elser  wrote:
>
> > Ah, maybe "moving to the Attic" is the phrase I was trying to avoid then
> > :). Thanks, John.
> >
> > Agreed on the software still being great and going to receive love.
> >
> > On 6/28/18 1:10 PM, John D. Ament wrote:
> > > That sounds like retirement to me.  The way I've always seen it is that
> > > podlings don't fail, the people behind them simply had a change in
> > > priorities.
> > >
> > > Gossip is a great toolkit that I believe people will continue to use.
> > >
> > > John
> > >
> > >
> > > On Thu, Jun 28, 2018, 12:44 PM Josh Elser  wrote:
> > >
> > >> I've been trying to be patient around this, but I think this month's
> > >> incubator report must be "Gossip is going to exit incubation" (I'm not
> > >> sure what the proper verb is here; I only know that "retire" is wrong)
> > >>
> > >> We've gone through many months where the only traffic I've seen on the
> > >> mailing list are the report reminders.
> > >>
> > >> This doesn't need to be interpreted as "Gossip is a failure at the
> ASF"
> > >> or anything of the such. It just means "It's not the right time for
> > >> Gossip at the ASF incubator". By all means, we can bring it back into
> > >> incubation if we get some more community traction behind the project.
> > >>
> > >> On 6/27/18 5:41 PM, jmcl...@apache.org wrote:
> > >>> Dear podling,
> > >>>
> > >>> This email was sent by an automated system on behalf of the Apache
> > >>> Incubator PMC. It is an initial reminder to give you plenty of time
> to
> > >>> prepare your quarterly board report.
> > >>>
> > >>> The board meeting is scheduled for Wed, 18 July 2018, 10:30 am PDT.
> > >>> The report for your podling will form a part of the Incubator PMC
> > >>> report. The Incubator PMC requires your report to be submitted 2
> weeks
> > >>> before the board meeting, to allow sufficient time for review and
> > >>> submission (Wed, July 04).
> > >>>
> > >>> Please submit your report with sufficient time to allow the Incubator
> > >>> PMC, and subsequently board members to review and digest. Again, the
> > >>> very latest you should submit your report is 2 weeks prior to the
> board
> > >>> meeting.
> > >>>
> > >>> Candidate names should not be made public before people are actually
> > >>> elected, so please do not include the names of potential committers
> or
> > >>> PPMC members in your report.
> > >>>
> > >>> Thanks,
> > >>>
> > >>> The Apache Incubator PMC
> > >>>
> > >>> Submitting your Report
> > >>>
> > >>> --
> > >>>
> > >>> Your report should contain the following:
> > >>>
> > >>> *   Your project name
> > >>> *   A brief description of your project, which assumes no knowledge
> of
> > >>>   the project or necessarily of its field
> > >>> *   A list of the three most important issues to address in the move
> > >>>   towards graduation.
> > >>> *   Any issues that the Incubator PMC or ASF Board might wish/need to
> > be
> > >>>   aware of
> > >>> *   How has the community developed since the last report
> > >>> *   How has the project developed since the last report.
> > >>> *   How does the podling rate their own maturity.
> > >>>
> > >>> This should be appended to the Incubator Wiki page at:
> > >>>
> > >>> https://wiki.apache.org/incubator/July2018
> > >>>
> > >>> Note: This is manually populated. You may need to wait a little
> before
> > >>> this page is created from a template.
> > >>>
> > >>> Mentors
> > >>> ---
> > >>>
> > >>> Mentors should review reports for their project(s) and sign them off
> on
> > >>> the Incubator wiki page. Signing off reports shows that you are
> > >>> following the project - projects that are not signed may raise alarms
> > >>> for the Incubator PMC.
> > >>>
> > >>> Incubator PMC
> > >>>
> > >>
> > >> -
> > >> 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: 

Re: Podling Report Reminder - July 2018

[Edward Capriolo]

Also at one point the project was assigned a "shepard" who never signed off
on a single report even when the project was active. His first interaction
for the project was vote to moth ball it.


On Thu, Jul 5, 2018 at 7:35 AM, Edward Capriolo 
wrote:

> I want to get this out there. I do not know why everyone is stuck on
> gossip. There are some TLP that do not have activity for years and podlings
> much older then gossip. I can give numerous examples.
>
> On Thu, Jun 28, 2018 at 1:10 PM, John D. Ament 
> wrote:
>
>> That sounds like retirement to me.  The way I've always seen it is that
>> podlings don't fail, the people behind them simply had a change in
>> priorities.
>>
>> Gossip is a great toolkit that I believe people will continue to use.
>>
>> John
>>
>>
>> On Thu, Jun 28, 2018, 12:44 PM Josh Elser  wrote:
>>
>> > I've been trying to be patient around this, but I think this month's
>> > incubator report must be "Gossip is going to exit incubation" (I'm not
>> > sure what the proper verb is here; I only know that "retire" is wrong)
>> >
>> > We've gone through many months where the only traffic I've seen on the
>> > mailing list are the report reminders.
>> >
>> > This doesn't need to be interpreted as "Gossip is a failure at the ASF"
>> > or anything of the such. It just means "It's not the right time for
>> > Gossip at the ASF incubator". By all means, we can bring it back into
>> > incubation if we get some more community traction behind the project.
>> >
>> > On 6/27/18 5:41 PM, jmcl...@apache.org wrote:
>> > > Dear podling,
>> > >
>> > > This email was sent by an automated system on behalf of the Apache
>> > > Incubator PMC. It is an initial reminder to give you plenty of time to
>> > > prepare your quarterly board report.
>> > >
>> > > The board meeting is scheduled for Wed, 18 July 2018, 10:30 am PDT.
>> > > The report for your podling will form a part of the Incubator PMC
>> > > report. The Incubator PMC requires your report to be submitted 2 weeks
>> > > before the board meeting, to allow sufficient time for review and
>> > > submission (Wed, July 04).
>> > >
>> > > Please submit your report with sufficient time to allow the Incubator
>> > > PMC, and subsequently board members to review and digest. Again, the
>> > > very latest you should submit your report is 2 weeks prior to the
>> board
>> > > meeting.
>> > >
>> > > Candidate names should not be made public before people are actually
>> > > elected, so please do not include the names of potential committers or
>> > > PPMC members in your report.
>> > >
>> > > Thanks,
>> > >
>> > > The Apache Incubator PMC
>> > >
>> > > Submitting your Report
>> > >
>> > > --
>> > >
>> > > Your report should contain the following:
>> > >
>> > > *   Your project name
>> > > *   A brief description of your project, which assumes no knowledge of
>> > >  the project or necessarily of its field
>> > > *   A list of the three most important issues to address in the move
>> > >  towards graduation.
>> > > *   Any issues that the Incubator PMC or ASF Board might wish/need to
>> be
>> > >  aware of
>> > > *   How has the community developed since the last report
>> > > *   How has the project developed since the last report.
>> > > *   How does the podling rate their own maturity.
>> > >
>> > > This should be appended to the Incubator Wiki page at:
>> > >
>> > > https://wiki.apache.org/incubator/July2018
>> > >
>> > > Note: This is manually populated. You may need to wait a little before
>> > > this page is created from a template.
>> > >
>> > > Mentors
>> > > ---
>> > >
>> > > Mentors should review reports for their project(s) and sign them off
>> on
>> > > the Incubator wiki page. Signing off reports shows that you are
>> > > following the project - projects that are not signed may raise alarms
>> > > for the Incubator PMC.
>> > >
>> > > Incubator PMC
>> > >
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>> >
>>
>
>

Re: Podling Report Reminder - July 2018

[Edward Capriolo]

I want to get this out there. I do not know why everyone is stuck on
gossip. There are some TLP that do not have activity for years and podlings
much older then gossip. I can give numerous examples.

On Thu, Jun 28, 2018 at 1:10 PM, John D. Ament 
wrote:

> That sounds like retirement to me.  The way I've always seen it is that
> podlings don't fail, the people behind them simply had a change in
> priorities.
>
> Gossip is a great toolkit that I believe people will continue to use.
>
> John
>
>
> On Thu, Jun 28, 2018, 12:44 PM Josh Elser  wrote:
>
> > I've been trying to be patient around this, but I think this month's
> > incubator report must be "Gossip is going to exit incubation" (I'm not
> > sure what the proper verb is here; I only know that "retire" is wrong)
> >
> > We've gone through many months where the only traffic I've seen on the
> > mailing list are the report reminders.
> >
> > This doesn't need to be interpreted as "Gossip is a failure at the ASF"
> > or anything of the such. It just means "It's not the right time for
> > Gossip at the ASF incubator". By all means, we can bring it back into
> > incubation if we get some more community traction behind the project.
> >
> > On 6/27/18 5:41 PM, jmcl...@apache.org wrote:
> > > Dear podling,
> > >
> > > This email was sent by an automated system on behalf of the Apache
> > > Incubator PMC. It is an initial reminder to give you plenty of time to
> > > prepare your quarterly board report.
> > >
> > > The board meeting is scheduled for Wed, 18 July 2018, 10:30 am PDT.
> > > The report for your podling will form a part of the Incubator PMC
> > > report. The Incubator PMC requires your report to be submitted 2 weeks
> > > before the board meeting, to allow sufficient time for review and
> > > submission (Wed, July 04).
> > >
> > > Please submit your report with sufficient time to allow the Incubator
> > > PMC, and subsequently board members to review and digest. Again, the
> > > very latest you should submit your report is 2 weeks prior to the board
> > > meeting.
> > >
> > > Candidate names should not be made public before people are actually
> > > elected, so please do not include the names of potential committers or
> > > PPMC members in your report.
> > >
> > > Thanks,
> > >
> > > The Apache Incubator PMC
> > >
> > > Submitting your Report
> > >
> > > --
> > >
> > > Your report should contain the following:
> > >
> > > *   Your project name
> > > *   A brief description of your project, which assumes no knowledge of
> > >  the project or necessarily of its field
> > > *   A list of the three most important issues to address in the move
> > >  towards graduation.
> > > *   Any issues that the Incubator PMC or ASF Board might wish/need to
> be
> > >  aware of
> > > *   How has the community developed since the last report
> > > *   How has the project developed since the last report.
> > > *   How does the podling rate their own maturity.
> > >
> > > This should be appended to the Incubator Wiki page at:
> > >
> > > https://wiki.apache.org/incubator/July2018
> > >
> > > Note: This is manually populated. You may need to wait a little before
> > > this page is created from a template.
> > >
> > > Mentors
> > > ---
> > >
> > > Mentors should review reports for their project(s) and sign them off on
> > > the Incubator wiki page. Signing off reports shows that you are
> > > following the project - projects that are not signed may raise alarms
> > > for the Incubator PMC.
> > >
> > > Incubator PMC
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>