You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by Roman Shaposhnik <ro...@shaposhnik.org> on 2016/07/01 22:44:03 UTC
Re: Podling Report Reminder - July 2016
Looks good to me, but please include a quick summary of the trademark
issue that is now being discussed on private.
Here's the text I'd suggest: "The PPMC was made aware of an erroneous
use of Apache HAWQ (incubating)
trademark by a vendor doing research with an older, eponymous Pivotal
product. The PPMC is working with
a vendor and ASF's VP of Branding to resolve the issue"
Also, please include a mention of the update you just did to the
website based on the podling branding guidelines.
Thanks,
Roman.
On Wed, Jun 29, 2016 at 10:31 PM, Vineet Goel <vv...@apache.org> wrote:
> looks good to me.
> Thanks
>
> -Vineet
>
> On Wed, Jun 29, 2016 at 2:49 AM, Lei Chang <le...@apache.org> wrote:
>
>> Hi Guys,
>>
>> Please see the following report. Looking forwards to your comments &
>> suggestions!
>>
>> ---------------------------------------------------------------
>> Apache HAWQ is a Hadoop native SQL query engine that combines the key
>> technological advantages of MPP database with the scalability and
>> convenience of Hadoop. HAWQ reads data from and writes data to HDFS
>> natively. HAWQ delivers industry-leading performance and linear
>> scalability. It provides users the tools to confidently and successfully
>> interact with petabyte range data sets. HAWQ provides users with a
>> complete, standards compliant SQL interface.
>>
>> HAWQ has been incubating since 2015-09-04.
>>
>> Three most important issues to address in the move towards graduation:
>>
>> 1. Produce our first Apache Release
>> 2. Expand the community, by adding new contributors and focusing on
>> making sure that there's a much more robust level of conversations and
>> discussions happening around roadmaps and feature development on the public
>> dev mailing list
>> 3. Infrastructure migration: create Jenkins projects that build HAWQ
>> binary, source tarballs, and run feature tests including at least
>> installcheck-good tests for each commit (HAWQ-127).
>>
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>>
>> Everything seems to be smooth, nothing urgent at this time.
>>
>> How has the community developed since the last report?
>>
>> 1. we have seen significant increase of communication and collaboration
>> across the whole community from last several weeks. The community becomes
>> more open for discussion around the roadmap, various features that
>> committers are working on, infrastructure enhancements for the project.
>>
>> 2. One meetup: Zeppelin meets MADlib & HAWQ (
>>
>> https://www.youtube.com/watch?v=p8V10IukBes&list=PL62pIycqXx-Qf6EXu5FDxUgXW23BHOtcQ&index=6
>> )
>>
>>
>> How has the project developed since the last report?
>>
>> 1. The first release candidate has been proposed and it is under the voting
>> process on the dev mailing list
>>
>> 2. New features added include snappy compression for AO tables, HAWQ
>> register feature for registering data into HAWQ native tables
>>
>> 3. The build system has been simplified a lot by making some components as
>> optional (for example, pl/r, orca et al)
>>
>> 4. The community is consolidating the testing frameworks including
>> installcheck tests and gtest into gtest based framework.
>>
>>
>> Date of last release:
>>
>> We have not had a release yet.
>>
>>
>> When were the last committers or PMC members elected?
>>
>> No new committers/members from initial.
>>
>>
>> Signed-off-by:
>>
>> [ ](hawq) Alan Gates
>> [ ](hawq) Konstantin Boudnik
>> [ ](hawq) Justin Erenkrantz
>> [ ](hawq) Thejas Nair
>> [ ](hawq) Roman Shaposhnik
>>
>> Shepherd/Mentor notes:
>>
>>
>>
>> On Wed, Jun 29, 2016 at 11:12 AM, <jo...@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, 20 July 2016, 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 06).
>> >
>> > 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.
>> >
>> > 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.
>> >
>> > This should be appended to the Incubator Wiki page at:
>> >
>> > http://wiki.apache.org/incubator/July2016
>> >
>> > 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
>> >
>>
Re: Podling Report Reminder - July 2016
Posted by Lei Chang <le...@apache.org>.
Thanks for the suggestion. Please see the revised one.
------------------------------------
Hi Guys,
Please see the following report. Looking forwards to your comments &
suggestions!
---------------------------------------------------------------
Apache HAWQ is a Hadoop native SQL query engine that combines the key
technological advantages of MPP database with the scalability and
convenience of Hadoop. HAWQ reads data from and writes data to HDFS
natively. HAWQ delivers industry-leading performance and linear
scalability. It provides users the tools to confidently and successfully
interact with petabyte range data sets. HAWQ provides users with a
complete, standards compliant SQL interface.
HAWQ has been incubating since 2015-09-04.
Three most important issues to address in the move towards graduation:
1. Produce our first Apache Release
2. Expand the community, by adding new contributors and focusing on
making sure that there's a much more robust level of conversations and
discussions happening around roadmaps and feature development on the public
dev mailing list
3. Infrastructure migration: create Jenkins projects that build HAWQ
binary, source tarballs, and run feature tests including at least
installcheck-good tests for each commit (HAWQ-127).
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Everything seems to be smooth, nothing urgent at this time.
How has the community developed since the last report?
1. we have seen significant increase of communication and collaboration
across the whole community from last several weeks. The community becomes
more open for discussion around the roadmap, various features that
committers are working on, infrastructure enhancements for the project.
2. One meetup: Zeppelin meets MADlib & HAWQ (
https://www.youtube.com/watch?v=p8V10IukBes&list=PL62pIycqXx-Qf6EXu5FDxUgXW23BHOtcQ&index=6
)
3. The PPMC was made aware of an erroneous use of Apache HAWQ
(incubating) trademark
by a vendor doing research with an older, eponymous Pivotal product. The
PPMC is working with a vendor and ASF's VP of Branding to resolve the issue
How has the project developed since the last report?
1. The first release candidate has been proposed and it is under the voting
process on the dev mailing list
2. New features added include snappy compression for AO tables, HAWQ
register feature for registering data into HAWQ native tables
3. The build system has been simplified a lot by making some components as
optional (for example, pl/r, orca et al)
4. The community is consolidating the testing frameworks including
installcheck tests and gtest into gtest based framework.
5. Including the incubating disclaimer on Apache HAWQ website based on the
podling branding guidelines
Date of last release:
We have not had a release yet.
When were the last committers or PMC members elected?
No new committers/members from initial.
Signed-off-by:
[ ](hawq) Alan Gates
[ ](hawq) Konstantin Boudnik
[ ](hawq) Justin Erenkrantz
[ ](hawq) Thejas Nair
[ ](hawq) Roman Shaposhnik
Shepherd/Mentor notes:
On Sat, Jul 2, 2016 at 6:44 AM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> Looks good to me, but please include a quick summary of the trademark
> issue that is now being discussed on private.
>
> Here's the text I'd suggest: "The PPMC was made aware of an erroneous
> use of Apache HAWQ (incubating)
> trademark by a vendor doing research with an older, eponymous Pivotal
> product. The PPMC is working with
> a vendor and ASF's VP of Branding to resolve the issue"
>
> Also, please include a mention of the update you just did to the
> website based on the podling branding guidelines.
>
> Thanks,
> Roman.
>
> On Wed, Jun 29, 2016 at 10:31 PM, Vineet Goel <vv...@apache.org> wrote:
> > looks good to me.
> > Thanks
> >
> > -Vineet
> >
> > On Wed, Jun 29, 2016 at 2:49 AM, Lei Chang <le...@apache.org> wrote:
> >
> >> Hi Guys,
> >>
> >> Please see the following report. Looking forwards to your comments &
> >> suggestions!
> >>
> >> ---------------------------------------------------------------
> >> Apache HAWQ is a Hadoop native SQL query engine that combines the key
> >> technological advantages of MPP database with the scalability and
> >> convenience of Hadoop. HAWQ reads data from and writes data to HDFS
> >> natively. HAWQ delivers industry-leading performance and linear
> >> scalability. It provides users the tools to confidently and successfully
> >> interact with petabyte range data sets. HAWQ provides users with a
> >> complete, standards compliant SQL interface.
> >>
> >> HAWQ has been incubating since 2015-09-04.
> >>
> >> Three most important issues to address in the move towards graduation:
> >>
> >> 1. Produce our first Apache Release
> >> 2. Expand the community, by adding new contributors and focusing on
> >> making sure that there's a much more robust level of conversations and
> >> discussions happening around roadmaps and feature development on the
> public
> >> dev mailing list
> >> 3. Infrastructure migration: create Jenkins projects that build HAWQ
> >> binary, source tarballs, and run feature tests including at least
> >> installcheck-good tests for each commit (HAWQ-127).
> >>
> >> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> >> aware of?
> >>
> >> Everything seems to be smooth, nothing urgent at this time.
> >>
> >> How has the community developed since the last report?
> >>
> >> 1. we have seen significant increase of communication and collaboration
> >> across the whole community from last several weeks. The community
> becomes
> >> more open for discussion around the roadmap, various features that
> >> committers are working on, infrastructure enhancements for the project.
> >>
> >> 2. One meetup: Zeppelin meets MADlib & HAWQ (
> >>
> >>
> https://www.youtube.com/watch?v=p8V10IukBes&list=PL62pIycqXx-Qf6EXu5FDxUgXW23BHOtcQ&index=6
> >> )
> >>
> >>
> >> How has the project developed since the last report?
> >>
> >> 1. The first release candidate has been proposed and it is under the
> voting
> >> process on the dev mailing list
> >>
> >> 2. New features added include snappy compression for AO tables, HAWQ
> >> register feature for registering data into HAWQ native tables
> >>
> >> 3. The build system has been simplified a lot by making some components
> as
> >> optional (for example, pl/r, orca et al)
> >>
> >> 4. The community is consolidating the testing frameworks including
> >> installcheck tests and gtest into gtest based framework.
> >>
> >>
> >> Date of last release:
> >>
> >> We have not had a release yet.
> >>
> >>
> >> When were the last committers or PMC members elected?
> >>
> >> No new committers/members from initial.
> >>
> >>
> >> Signed-off-by:
> >>
> >> [ ](hawq) Alan Gates
> >> [ ](hawq) Konstantin Boudnik
> >> [ ](hawq) Justin Erenkrantz
> >> [ ](hawq) Thejas Nair
> >> [ ](hawq) Roman Shaposhnik
> >>
> >> Shepherd/Mentor notes:
> >>
> >>
> >>
> >> On Wed, Jun 29, 2016 at 11:12 AM, <jo...@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, 20 July 2016, 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 06).
> >> >
> >> > 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.
> >> >
> >> > 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.
> >> >
> >> > This should be appended to the Incubator Wiki page at:
> >> >
> >> > http://wiki.apache.org/incubator/July2016
> >> >
> >> > 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
> >> >
> >>
>