hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lei Chang <chang.lei...@gmail.com>
Subject Re: Podling Report Reminder - July 2018
Date Wed, 04 Jul 2018 01:44:17 GMT
Hi Guys,

The following is the podling report draft. Please feel free to give your
comments and suggestions.



HAWQ is an advanced enterprise SQL on Hadoop analytic engine built around a
robust and high-performance massively-parallel processing (MPP) SQL engine
evolved from Greenplum Database.

HAWQ has been incubating since 2015-09-04.

Three most important issues to address in the move towards graduation:

    Nothing at this time.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware

     Nothing urgent at this time.

How has the community developed since the last report?

1. Conference Talks :

* HAWQ for data scientists,  Shanghai CIO forum (Speaker: Lei Chang,  June
23, 2018)

2.  "Graduate Apache HAWQ (incubating) as a TLP" discussion was started:

With the release officially out, the Apache HAWQ
community and its mentors believe it is time to consider graduation to the

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/

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)
Privacera (1)
Qubole (1)
Snowflake (1)
State Street (1)
Unifi (1)
Visa (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:

How has the project developed since the last report?

1. HAWQ 2.4.0 Plan finalized. It includes the following features.

   - New Feature: Pluggable Vectorized Execution Engine on HAWQ.
   - New Feature: Support Runtime Filter for HAWQ local hash join.
   - Bug fixes.

Project page link: https://cwiki.apache.org/confluence/display/HAWQ/

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [X] Nearing graduation
  [ ] Other:

Date of last release:

2018-03-12, Apache HAWQ

When were the last committers or PPMC members elected?

1) Lav Jain: April 5, 2018
2) Shubham Sharma: April 5, 2018


  [ ](hawq) Alan Gates Comments:
  [ ](hawq) Justin Erenkrantz Comments:
  [ ](hawq) Thejas Nair Comments:
  [ ](hawq) Roman Shaposhnik Comments:

On Thu, Jun 28, 2018 at 5:41 AM, <jmclean@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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message