Re: Podling Report Reminder - September 2018

[Julian Hyde]

Thanks, I have signed off.

As I noted in the report, I have some concerns about Quickstep’s activity and 
community building. Activity seems to be focused on the needs of Madison 
researchers, and commits occur without discussion on list. (The three “ongoing 
objectives” mentioned in the report were not discussed on the dev list, unless 
I am mistaken. Where were they decided?)

The project does not seem to be attracting contributors outside of Madison, and 
the committers are acting as if all stakeholders are in Madison. I’m not sure 
which is the cause and which is the effect, but it is not how a successful 
Apache project operates.

The lists were deathly quiet over the summer, and there is a question on the 
dev list from a week ago that has still not been answered.

The last release was almost 18 months ago. Is it time for a new release?

Julian



> On Sep 5, 2018, at 7:34 AM, Harshad Deshmukh  wrote:
> 
> Hi Julian,
> 
> 
> Apologies for the delay. The report is now up on the wiki.
> 
> 
> Thanks,
> 
> Harshad
> 
> ________
> From: Julian Hyde 
> Sent: Tuesday, August 28, 2018 12:56:28 PM
> To: dev@quickstep.incubator.apache.org
> Subject: Re: Podling Report Reminder - September 2018
> 
> Can someone please volunteer to write this report?
> 
>> On Aug 25, 2018, at 3:17 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, 19 September 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, September 05).
>> 
>> 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/September2018
>> 
>> 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 - September 2018

[Julian Hyde]

The podling report is due tomorrow. Who is picking this up?

Julian

> On Sep 3, 2018, at 3:22 PM, Justin Mclean  wrote:
> 
> Hi,
> The incubator PMC would appreciated if you could complete the podling report 
> on time. It takes time to prepare the incubator report, have your mentors 
> sign off the report and for the board to review it, in order for all that to 
> happen the report is due in the next two days.
> Thanks,
> Justin

Re: Podling Report Reminder - September 2018

[Julian Hyde]

Can someone please volunteer to write this report?

> On Aug 25, 2018, at 3:17 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, 19 September 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, September 05).
> 
> 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/September2018
> 
> 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 - June 2018

[Julian Hyde]

I saw that you filed the report[1] - thank you! I have signed off.

I made the following comments on the report:

   The project seems to have slowed somewhat. Development activity
   is about the same, but there has not been a release for over a
   year, and I do not sense any real efforts at community building
   outside of the core group. I will be concerned if things don't
   change soon.

Any reactions to this?

Julian

[1] https://wiki.apache.org/incubator/June2018 
 


> On Jun 3, 2018, at 5:06 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, 20 June 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, June 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.
> 
> 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/June2018
> 
> 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 - April 2018

[Julian Hyde]

Thanks Harshad, I signed off.


> On Apr 3, 2018, at 9:21 AM, Harshad Deshmukh  wrote:
> 
> Hello all,
> 
> 
> Please find the report posted at 
> https://wiki.apache.org/incubator/April2018
> 
> 
> Thanks,
> 
> Harshad
> 
> 
> From: johndam...@apache.org 
> Sent: Monday, April 2, 2018 5:50:31 PM
> To: dev@quickstep.incubator.apache.org
> Subject: Podling Report Reminder - April 2018
> 
> 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 April 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, April 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.
> 
> 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/April2018
> 
> 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: subscribe instructions

[Julian Hyde]

Per https://mail-archives.apache.org/mod_mbox/quickstep-dev/ 
 send an email to 
dev-subscr...@quickstep.incubator.apache.org 
. 

> On Apr 4, 2018, at 7:20 PM, Yusong Yang  wrote:
> 
> 

Re: Quickstep paper

[Julian Hyde]

ApacheCon is for the community, so keynotes are chosen entirely on merit. 
Bigger audience than the regular talks, but fewer minutes, and it would be good 
if there are larger themes than simply what the project does.

I recommend that you submit a keynote and a regular talk. If people enjoy the 
keynote they will come to the regular talk to hear more details. Writing an 
abstract doesn’t take very long.

Julian


> On Mar 17, 2018, at 4:59 PM, J. M. Patel  wrote:
> 
> Hi Team: I'm starting to work on the abstract for this (will circulate it 
> soon). 
> 
> Apache Con has two options for talk submission: Keynote and Standard. I'm 
> thinking of submitting to the Keynote category. Any comments? I figured 
> go-big-or-go-home.
> 
> Not sure if ApacheCon is like some of the other industry-style conferences in 
> which keynotes are favored from sponsors. 
> 
> Also, what do folks think of working on a release sometime early summer? We 
> can try to see if Marc can help if he has settled down from the recent 
> excitement 
> (https://techcrunch.com/2018/01/25/ford-acquires-autonomic-and-transloc-as-it-evolves-its-mobility-business/).
>  
> 
> Cheers,
> Jignesh 
> 
> On 2/13/18, 10:09 PM, "J. M. Patel"  wrote:
> 
>    Good tips Julian! 
> 
>Cheers,
>Jignesh  
> 
>On 2/9/18, 6:00 PM, "Julian Hyde"  wrote:
> 
>ApacheCon is a good opportunity to attract community, so I suggest you 
> think of the talk as a sales pitch. You need to convince members of the 
> audience to use Quickstep in their application or data engine, and then to 
> start contributing. The fact that the Quickstep is high-performance is 
> necessary but not sufficient. You also need to demonstrate that it is easy to 
> use Quickstep in their project. From your talk by all means reference your 
> research and experiments to back up your assertions about speed etc.
> 
>Julian
> 
> 
>> On Feb 8, 2018, at 5:00 PM, J. M. Patel  wrote:
>> 
>> Hello Quicksteppers: VLDB (research track) has accepted a paper on 
>> Quickstep. The current (temporary) version of the paper is at: 
>> http://pages.cs.wisc.edu/~jignesh/publ/quickstep.pdf If any of you have 
>> feedback, please reply to this email. 
>> 
>> 
>> 
>> Perhaps this can also serve as material that we can use for the ApacheCon 
>> submission?
>> 
>> 
>> 
>> Cheers,
>> 
>> Jignesh
>> 
>> 
>> 
> 
> 
> 
> 
> 
> 

Re: Podling Report Reminder - March 2018

[Julian Hyde]

Hi Quickstep PPMC,

This report is due tomorrow (March 7th). Who is going to write it?

Julian

> On Mar 6, 2018, at 5:32 PM, johndam...@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, 21 March 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, March 07).
> 
> 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.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://wiki.apache.org/incubator/March2018
> 
> 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: Question about using Intel TBB

[Julian Hyde]

Apache license is fine.


> On Feb 26, 2018, at 9:11 AM, Harshad Deshmukh  wrote:
> 
> Hello,
> 
> 
> I am planning to incorporate Intel's TBB library 
> (https://www.threadingbuildingblocks.org/) in the Quickstep source code as a 
> third party module. TBB provides fast and parallel data structures such as 
> concurrent hash map. Its licence looks alright to me but I want to run it 
> through the licensing experts on the dev list. Here's the licensing header I 
> found in their source code:
> 
> 
> 
> 
>Copyright (c) 2005-2017 Intel Corporation
> 
>Licensed under the Apache License, Version 2.0 (the "License");
>you may not use this file except in compliance with the License.
>You may obtain a copy of the License at
>http://www.apache.org/licenses/LICENSE-2.0
>Unless required by applicable law or agreed to in writing, software
>distributed under the License is distributed on an "AS IS" BASIS,
>WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>See the License for the specific language governing permissions and
>limitations under the License.
> 
> 
> 
> Thanks,
> 
> Harshad

Re: Quickstep paper

[Julian Hyde]

ApacheCon is a good opportunity to attract community, so I suggest you think of 
the talk as a sales pitch. You need to convince members of the audience to use 
Quickstep in their application or data engine, and then to start contributing. 
The fact that the Quickstep is high-performance is necessary but not 
sufficient. You also need to demonstrate that it is easy to use Quickstep in 
their project. From your talk by all means reference your research and 
experiments to back up your assertions about speed etc.

Julian


> On Feb 8, 2018, at 5:00 PM, J. M. Patel  wrote:
> 
> Hello Quicksteppers: VLDB (research track) has accepted a paper on Quickstep. 
> The current (temporary) version of the paper is at: 
> http://pages.cs.wisc.edu/~jignesh/publ/quickstep.pdf If any of you have 
> feedback, please reply to this email. 
> 
> 
> 
> Perhaps this can also serve as material that we can use for the ApacheCon 
> submission?
> 
> 
> 
> Cheers,
> 
> Jignesh
> 
> 
> 

ApacheCon

[Julian Hyde]

Hi Quicksteppers,

ApacheCon North America is being held in Montreal in September. CFP is open 
until March 30. It is a great place for projects (especially incubator 
projects) to connect with smart folks in the ecosystem. It is straightforward 
to get a paper accepted, so I encourage you to apply.

http://apachecon.com/acna18/ 

Julian

Re: Podling Report Reminder - December 2017

[Julian Hyde]

I’ve signed off the report. Thanks for filing!

I just checked http://quickstep.apache.org/about/ 
<http://quickstep.apache.org/about/> and I see Robert has not been added. I 
think it would be more welcoming to outsiders if that page was a simple list of 
committers, not mentioning organizational affiliations. What do you all think?

Julian


> On Dec 6, 2017, at 12:12 PM, Harshad Deshmukh  wrote:
> 
> Hi Jignesh,
> 
> 
> Robert Claus is the latest committer. I have added that in the report.
> 
> 
> Thanks,
> 
> Harshad
> 
> 
> From: J. M. Patel 
> Sent: Wednesday, December 6, 2017 2:05:07 PM
> To: dev@quickstep.incubator.apache.org
> Subject: Re: Podling Report Reminder - December 2017
> 
> Hi everyone: I've added an initial report (see below). Feedback?
> 
> 
> Quickstep is a high-performance database engine.
> 
> Quickstep has been incubating since 2016-03-29.
> 
> Three most important issues to address in the move towards graduation:
> 
>  1. Work on adoption of the Quickstep technology.
>  2. Continue building a developer community.
>  3. Work towards a second release.
> 
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
> 
> None.
> 
> How has the community developed since the last report?
> 
> There are a number of active developers working with the code base, who may 
> become committers in the near future.
> 
> 
> How has the project developed since the last report?
> 
> A number of bug reports have been filed and features added to move the 
> single-node version of the system forward.
> 
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
> 
>  [ ] Initial setup
>  [ ] Working towards first release
>  [X] Community building
>  [ ] Nearing graduation
>  [ ] Other:
> 
> Date of last release:
> 
>  2017-03-25
> 
> When were the last committers or PPMC members elected?
> 
>  2017-05-12 Tianrun Lee (committer)
> 
> 
> On 12/6/17, 12:32 PM, "Julian Hyde"  wrote:
> 
>Hi Quicksteppers,
> 
>The report is due TODAY. Can someone write it please?
> 
>Julian
> 
> 
>> On Nov 26, 2017, at 7:48 PM, johndam...@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 December 2017, 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, December 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.
>> *   How does the podling rate their own maturity.
>> 
>> This should be appended to the Incubator Wiki page at:
>> 
>> https://wiki.apache.org/incubator/December2017
>> 
>> 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 - December 2017

[Julian Hyde]

Hi Quicksteppers,

The report is due TODAY. Can someone write it please?

Julian


> On Nov 26, 2017, at 7:48 PM, johndam...@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 December 2017, 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, December 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.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://wiki.apache.org/incubator/December2017
> 
> 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

Instructions for subscribing to the email list

[Julian Hyde]

I just received (as dev-ow...@quickstep.apache.org 
) a request to join 
d...@quickstep.apache.org . I wondered why 
the person had not figured out how to subscribe, so I checked:

1. The instructions on the page 
http://mail-archives.apache.org/mod_mbox/quickstep-dev/ 
 are correct; however

2. When I google “subscribe apache quickstep” that page doesn’t come up in the 
top 10, and

3. That page is not listed as the official archive at 
http://quickstep.apache.org/ . Rather, that page 
lists https://www.mail-archive.com/dev@quickstep.incubator.apache.org/ 
 as the 
archive, but the official apache archives 
https://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/ 
 or 
https://lists.apache.org/list.html?d...@quickstep.apache.org 
 would probably 
be better.

4. The instructions on http://quickstep.apache.org/ 
, "Send a blank email to [ 
d...@quickstep.apache.org  ]  for subscribe 
instructions” are wrong.

Can someone make a pass over the doc and make it easier to join the community?

Julian

Re: Podling Report Reminder - September 2017

[Julian Hyde]

Thanks. I have signed off.

Roman & Cos, please sign off.

Julian


> On Sep 11, 2017, at 9:16 AM, Harshad Deshmukh  wrote:
> 
> Notes are posted on the wiki. Apologies for the delay.
> 
> Link: https://wiki.apache.org/incubator/September2017
> 
> 
> On 09/09/2017 07:52 PM, J. M. Patel wrote:
>> This looks good to me Harshad. Thanks!
>> 
>> On 9/6/17, 7:52 PM, "Harshad Deshmukh"  wrote:
>> 
>> Dear mentors,
>>  Can you please take a look at the report below?
>>  Jignesh: Did I miss something in the development activity overview?
>>  Get Outlook for Android<https://aka.ms/ghei36>
>>  
>> From: Harshad Deshmukh
>> Sent: Sunday, September 3, 2017 11:50:40 AM
>> To: dev@quickstep.incubator.apache.org
>> Subject: Re: Podling Report Reminder - September 2017
>>   Hello,
>>  I drafted the Quickstep podling report below. Please take a look 
>> and let me know if there are any changes.
>>  ---
>> Quickstep is a high-performance database engine.
>>  Quickstep has been incubating since 2016-03-29.
>>  Three most important issues to address in the move towards 
>> graduation:
>>1. Building a Quickstep community
>>   2. More adoption of the Quickstep technology
>>   3. More releases
>>  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to 
>> be
>> aware of?
>>  None
>>  How has the community developed since the last report?
>>  In the summer of 2017, we took efforts to spread awareness about 
>> the Quickstep project and technology. We had many talks, particularly in the 
>> San Francisco Bay Area. The talks/venues are listed here:
>>1.  SRI International in Menlo Park
>>   2.  A meetup hosted by H2O.ai in Mountain View (Link: 
>> https://www.meetup.com/H2O-AI-Deep-Learning/events/241576643/?_cookie-check=en9PvHYSsw_N1Bf_)
>>   3.  Hortonworks in Santa Clara (Thanks to our mentor Julian Hyde for 
>> hosting)
>>  We had also applied for a talk at BigDataWisconsin meetup but the 
>> proposal was not selected.
>>  How has the project developed since the last report?
>>  During the summer, the development activity was slow. There are 
>> ongoing efforts to build a distributed version of Quickstep.
>>  How would you assess the podling's maturity?
>> Please feel free to add your own commentary.
>>[ ] Initial setup
>>   [ ] Working towards first release
>>   [ ] Community building
>>   [ ] Nearing graduation
>>   [ ] Other:
>>  Date of last release:
>>2017-03-25
>>  When were the last committers or PPMC members elected?
>>2017-05-12
>>   ---
>>   Thanks,
>>  Harshad
>>  
>> From: johndam...@apache.org 
>> Sent: Saturday, September 2, 2017 1:13:27 PM
>> To: dev@quickstep.incubator.apache.org
>> Subject: Podling Report Reminder - September 2017
>>  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 September 2017, 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, September 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 Bo

Re: Podling Report Reminder - September 2017

[Julian Hyde]

I don’t know how to do that.

Can you please post to general@incubator, and someone will help.

Julian

> On Sep 7, 2017, at 5:48 PM, Harshad Deshmukh  wrote:
> 
> Thanks Julian for your comments. Would you mind giving me the editing rights 
> to the wiki?
> 
> Harshad
> -Original Message-
> From: Julian Hyde [mailto:jh...@apache.org] 
> Sent: Thursday, September 7, 2017 6:39 PM
> To: dev@quickstep.incubator.apache.org
> Subject: Re: Podling Report Reminder - September 2017
> 
>> A meetup hosted by H2O.ai in Mountain View (Link: 
>> https://www.meetup.com/H2O-AI-Deep-Learning/events/241576643/?_cookie-
>> check=en9PvHYSsw_N1Bf_)
> 
> I would remove the link. The Board trusts you, so doesn't need proof.
> 
>> Hortonworks in Santa Clara (Thanks to our mentor Julian Hyde for 
>> hosting)
> 
> You're welcome.
> 
>> How would you assess the podling's maturity?
> 
> Can you check one of the boxes.
> 
>> When were the last committers or PPMC members elected?
>> 
>>  2017-05-12
> 
> I would expand to
> 
>  2017-05-12 Tianrun Lee (committer)
> 
> I don't recall any PPMC members being appointed since incubation started 
> (correct me if I am wrong).
> 
> Julian
> 
> 
> 
> On Wed, Sep 6, 2017 at 5:51 PM, Harshad Deshmukh  wrote:
>> Dear mentors,
>> 
>> Can you please take a look at the report below?
>> 
>> Jignesh: Did I miss something in the development activity overview?
>> 
>> Get Outlook for Android<https://aka.ms/ghei36>
>> 
>> 
>> From: Harshad Deshmukh
>> Sent: Sunday, September 3, 2017 11:50:40 AM
>> To: dev@quickstep.incubator.apache.org
>> Subject: Re: Podling Report Reminder - September 2017
>> 
>> 
>> Hello,
>> 
>> I drafted the Quickstep podling report below. Please take a look and let me 
>> know if there are any changes.
>> 
>> ---
>> Quickstep is a high-performance database engine.
>> 
>> Quickstep has been incubating since 2016-03-29.
>> 
>> Three most important issues to address in the move towards graduation:
>> 
>>  1. Building a Quickstep community
>>  2. More adoption of the Quickstep technology
>>  3. More releases
>> 
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be 
>> aware of?
>> 
>> None
>> 
>> How has the community developed since the last report?
>> 
>> In the summer of 2017, we took efforts to spread awareness about the 
>> Quickstep project and technology. We had many talks, particularly in the San 
>> Francisco Bay Area. The talks/venues are listed here:
>> 
>>  1.  SRI International in Menlo Park
>>  2.  A meetup hosted by H2O.ai in Mountain View (Link: 
>> https://www.meetup.com/H2O-AI-Deep-Learning/events/241576643/?_cookie-check=en9PvHYSsw_N1Bf_)
>>  3.  Hortonworks in Santa Clara (Thanks to our mentor Julian Hyde for 
>> hosting)
>> 
>> We had also applied for a talk at BigDataWisconsin meetup but the proposal 
>> was not selected.
>> 
>> How has the project developed since the last report?
>> 
>> During the summer, the development activity was slow. There are ongoing 
>> efforts to build a distributed version of Quickstep.
>> 
>> How would you assess the podling's maturity?
>> Please feel free to add your own commentary.
>> 
>>  [ ] Initial setup
>>  [ ] Working towards first release
>>  [ ] Community building
>>  [ ] Nearing graduation
>>  [ ] Other:
>> 
>> Date of last release:
>> 
>>  2017-03-25
>> 
>> When were the last committers or PPMC members elected?
>> 
>>  2017-05-12
>> 
>> 
>> ---
>> 
>> 
>> Thanks,
>> 
>> Harshad
>> 
>> 
>> From: johndam...@apache.org 
>> Sent: Saturday, September 2, 2017 1:13:27 PM
>> To: dev@quickstep.incubator.apache.org
>> Subject: Podling Report Reminder - September 2017
>> 
>> 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 September 2017, 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, S

Re: Podling Report Reminder - September 2017

[Julian Hyde]

> A meetup hosted by H2O.ai in Mountain View (Link: 
> https://www.meetup.com/H2O-AI-Deep-Learning/events/241576643/?_cookie-check=en9PvHYSsw_N1Bf_)

I would remove the link. The Board trusts you, so doesn't need proof.

> Hortonworks in Santa Clara (Thanks to our mentor Julian Hyde for hosting)

You're welcome.

> How would you assess the podling's maturity?

Can you check one of the boxes.

> When were the last committers or PPMC members elected?
>
>   2017-05-12

I would expand to

  2017-05-12 Tianrun Lee (committer)

I don't recall any PPMC members being appointed since incubation
started (correct me if I am wrong).

Julian



On Wed, Sep 6, 2017 at 5:51 PM, Harshad Deshmukh  wrote:
> Dear mentors,
>
> Can you please take a look at the report below?
>
> Jignesh: Did I miss something in the development activity overview?
>
> Get Outlook for Android<https://aka.ms/ghei36>
>
> 
> From: Harshad Deshmukh
> Sent: Sunday, September 3, 2017 11:50:40 AM
> To: dev@quickstep.incubator.apache.org
> Subject: Re: Podling Report Reminder - September 2017
>
>
> Hello,
>
> I drafted the Quickstep podling report below. Please take a look and let me 
> know if there are any changes.
>
> ---
> Quickstep is a high-performance database engine.
>
> Quickstep has been incubating since 2016-03-29.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Building a Quickstep community
>   2. More adoption of the Quickstep technology
>   3. More releases
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None
>
> How has the community developed since the last report?
>
> In the summer of 2017, we took efforts to spread awareness about the 
> Quickstep project and technology. We had many talks, particularly in the San 
> Francisco Bay Area. The talks/venues are listed here:
>
>   1.  SRI International in Menlo Park
>   2.  A meetup hosted by H2O.ai in Mountain View (Link: 
> https://www.meetup.com/H2O-AI-Deep-Learning/events/241576643/?_cookie-check=en9PvHYSsw_N1Bf_)
>   3.  Hortonworks in Santa Clara (Thanks to our mentor Julian Hyde for 
> hosting)
>
> We had also applied for a talk at BigDataWisconsin meetup but the proposal 
> was not selected.
>
> How has the project developed since the last report?
>
> During the summer, the development activity was slow. There are ongoing 
> efforts to build a distributed version of Quickstep.
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   [ ] Initial setup
>   [ ] Working towards first release
>   [ ] Community building
>   [ ] Nearing graduation
>   [ ] Other:
>
> Date of last release:
>
>   2017-03-25
>
> When were the last committers or PPMC members elected?
>
>   2017-05-12
>
>
> ---
>
>
> Thanks,
>
> Harshad
>
> 
> From: johndam...@apache.org 
> Sent: Saturday, September 2, 2017 1:13:27 PM
> To: dev@quickstep.incubator.apache.org
> Subject: Podling Report Reminder - September 2017
>
> 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 September 2017, 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, September 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.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/September2017
>
> 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: Upcoming Quickstep talks

[Julian Hyde]

I won’t make it to the talk today, I’m afraid. I have signed up for the meet up 
on August 1st. See you then, and good luck with the talk today.

Julian


> On Jul 12, 2017, at 7:10 PM, Harshad Deshmukh  wrote:
> 
> Hello Julian,
> 
> The abstract for H2O.ai is corrected, thanks for pointing it out! 
> 
> I asked the organizers at SRI about the talk being public and also if you can 
> attend. The talk doesn't seem to be open for all, but they mentioned that you 
> (as our Apache mentor) are most welcome to attend. 
> 
> The talk is from 1.30 PM to 3.00 PM (including the time for some interaction 
> after the talk). I am planning to reach there by around 1 PM. If you would 
> like to come, please let me know. It would be nice to interact with you in 
> person!
> 
> Here's the address of SRI: 
> 333 Ravenswood Avenue, Menlo Park, CA 94025-3493
> 
> I am supposed to go to the main lobby. 
> 
> Thanks,
> Harshad
> 
> -Original Message-
> From: Julian Hyde [mailto:jh...@apache.org] 
> Sent: Tuesday, July 11, 2017 1:37 PM
> To: dev@quickstep.incubator.apache.org
> Subject: Re: Upcoming Quickstep talks
> 
> Well done landing a couple of talks. Is the SRI talk open to the public? I 
> haven't seen any tweets yet about it - I'd like to retweet them.
> 
> On Mon, Jul 10, 2017 at 7:25 PM, Harshad Deshmukh  wrote:
>> Hello everyone,
>> 
>> I would like to spread the word about some upcoming Quickstep talks that I 
>> will be giving in the San Francisco Bay Area.
>> 
>>  1.  Computer Science Laboratory at SRI 
>> International<http://www.csl.sri.com/> on July 13th
>>  2.  A meetup sponsored by H2O.ai on August 1st (Link: 
>> https://www.meetup.com/Silicon-Valley-Big-Data-Science/events/24157648
>> 0/)
>> 
>> Additionally we have submitted an abstract for a talk to BigData Madison, 
>> that's going to happen in late August. Thanks to Julian for suggesting the 
>> meetup options.
>> 
>> I will use our twitter account to publicize these talks, please retweet!
>> 
>> Thanks,
>> Harshad

Re: Upcoming Quickstep talks

[Julian Hyde]

Well done landing a couple of talks. Is the SRI talk open to the
public? I haven't seen any tweets yet about it - I'd like to retweet
them.

On Mon, Jul 10, 2017 at 7:25 PM, Harshad Deshmukh  wrote:
> Hello everyone,
>
> I would like to spread the word about some upcoming Quickstep talks that I 
> will be giving in the San Francisco Bay Area.
>
>   1.  Computer Science Laboratory at SRI 
> International on July 13th
>   2.  A meetup sponsored by H2O.ai on August 1st (Link: 
> https://www.meetup.com/Silicon-Valley-Big-Data-Science/events/241576480/)
>
> Additionally we have submitted an abstract for a talk to BigData Madison, 
> that's going to happen in late August. Thanks to Julian for suggesting the 
> meetup options.
>
> I will use our twitter account to publicize these talks, please retweet!
>
> Thanks,
> Harshad

Re: Upcoming Quickstep talks

[Julian Hyde]

In the H20.ai summary, you refer to the project as "Quickstep". It
needs to be "Apache Quickstep". Can you change it please?

On Tue, Jul 11, 2017 at 1:36 PM, Julian Hyde  wrote:
> Well done landing a couple of talks. Is the SRI talk open to the
> public? I haven't seen any tweets yet about it - I'd like to retweet
> them.
>
> On Mon, Jul 10, 2017 at 7:25 PM, Harshad Deshmukh  wrote:
>> Hello everyone,
>>
>> I would like to spread the word about some upcoming Quickstep talks that I 
>> will be giving in the San Francisco Bay Area.
>>
>>   1.  Computer Science Laboratory at SRI 
>> International<http://www.csl.sri.com/> on July 13th
>>   2.  A meetup sponsored by H2O.ai on August 1st (Link: 
>> https://www.meetup.com/Silicon-Valley-Big-Data-Science/events/241576480/)
>>
>> Additionally we have submitted an abstract for a talk to BigData Madison, 
>> that's going to happen in late August. Thanks to Julian for suggesting the 
>> meetup options.
>>
>> I will use our twitter account to publicize these talks, please retweet!
>>
>> Thanks,
>> Harshad

Re: Podling Report Reminder - June 2017

[Julian Hyde]

Approved - thanks Jignesh!

Roman & Cos, please sign off.

Julian


> On Jun 1, 2017, at 2:43 PM, Jignesh Patel  wrote:
> 
> A starting point for the podling report is now at: 
> https://wiki.apache.org/incubator/June2017#preview. Feel free to make any 
> changes or suggest them. 
> 
> Cheers,
> Jignesh 
> 
> On 6/1/17, 6:43 AM, "johndam...@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, 21 June 2017, 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, June 07).
> 
>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.
>*   How does the podling rate their own maturity.
> 
>This should be appended to the Incubator Wiki page at:
> 
>https://wiki.apache.org/incubator/June2017
> 
>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 - June 2017

[Julian Hyde]

By the way, if you had submitted an abstract for Data Works summit you probably 
would have been accepted. There’s always interest in new Apache data 
technologies in Hadoop conferences. Same goes for Strata. Those conferences 
each have east coast, west coast, europe and one or two other locations 
(asia/pacific) per year.

And of course the open source conferences: ApacheCon, OSCON, FOSDEM, Berlin 
Buzzwords.

Julian


> On Jun 5, 2017, at 8:55 AM, Julian Hyde  wrote:
> 
> Harshad,
> 
> A good venue for reaching out to folks from industry would be meet ups. For 
> example, my company, Hortonworks, regularly organizes them. In fact there are 
> several happening next week in San Jose during Data works summit[1] (same 
> city, but you don’t need to be an attendee of the conference to attend the 
> meet ups).
> 
> I’ll introduce you to the folks at Hortonworks who organize these meet ups. 
> Even though it’s short notice, maybe they can find a slot for you to speak.
> 
> Mentors,
> 
> Do you know of folks who organize meet ups in the bay area?
> 
> Julian
> 
> [1] https://dataworkssummit.com/san-jose-2017/meetups/ 
> <https://dataworkssummit.com/san-jose-2017/meetups/>
> 
>> On Jun 2, 2017, at 9:21 PM, Harshad Deshmukh > <mailto:hars...@cs.wisc.edu>> wrote:
>> 
>> Hi Jignesh,
>> 
>> I am in the Bay area right now and I can give a talk.
>> 
>> 
>> On 06/02/2017 03:53 PM, Jignesh Patel wrote:
>>> I’ve been thinking of other ways to get the word out.
>>> 
>>> There are few current and ex-Wisconsin folks in the Bay area this summer.
>>> 
>>> Question for all: Are there any forums in the Bay area that may be good to 
>>> think about presenting this summer? IMHO, it would also be good to target 
>>> specific meetups and companies that might be potential synergistic partners.
>>> 
>>> I can prepare the slides.
>>> 
>>> Any Bay area residents who want to volunteer to give a talk? I think I can 
>>> find $s for incidental reimbursements and conference costs (if they are not 
>>> outrageously high).
>>> 
>>> Cheers,
>>> Jignesh
>>> 
>>> On 6/1/17, 10:28 AM, "Julian Hyde" >> <mailto:jh...@apache.org>> wrote:
>>> 
>>> Quickstep community,
>>>  Now we have a first release, it is clear to me — and I hope to you 
>>> — that the big challenge for Quickstep is growing a community outside of 
>>> Madison. I think we need to come up with a plan to address this so that it 
>>> can be in this quarter’s report, and we can measure progress at the time of 
>>> the next quarterly report. What do you think?
>>>  Julian
>>>  > On Jun 1, 2017, at 4:43 AM, johndam...@apache.org 
>>> <mailto:johndam...@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, 21 June 2017, 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, June 07).
>>> >
>>> > 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 
>>>

Re: Podling Report Reminder - June 2017

[Julian Hyde]

Harshad,

A good venue for reaching out to folks from industry would be meet ups. For 
example, my company, Hortonworks, regularly organizes them. In fact there are 
several happening next week in San Jose during Data works summit[1] (same city, 
but you don’t need to be an attendee of the conference to attend the meet ups).

I’ll introduce you to the folks at Hortonworks who organize these meet ups. 
Even though it’s short notice, maybe they can find a slot for you to speak.

Mentors,

Do you know of folks who organize meet ups in the bay area?

Julian

[1] https://dataworkssummit.com/san-jose-2017/meetups/ 
<https://dataworkssummit.com/san-jose-2017/meetups/>

> On Jun 2, 2017, at 9:21 PM, Harshad Deshmukh  wrote:
> 
> Hi Jignesh,
> 
> I am in the Bay area right now and I can give a talk.
> 
> 
> On 06/02/2017 03:53 PM, Jignesh Patel wrote:
>> I’ve been thinking of other ways to get the word out.
>> 
>> There are few current and ex-Wisconsin folks in the Bay area this summer.
>> 
>> Question for all: Are there any forums in the Bay area that may be good to 
>> think about presenting this summer? IMHO, it would also be good to target 
>> specific meetups and companies that might be potential synergistic partners.
>> 
>> I can prepare the slides.
>> 
>> Any Bay area residents who want to volunteer to give a talk? I think I can 
>> find $s for incidental reimbursements and conference costs (if they are not 
>> outrageously high).
>> 
>> Cheers,
>> Jignesh
>> 
>> On 6/1/17, 10:28 AM, "Julian Hyde"  wrote:
>> 
>> Quickstep community,
>>  Now we have a first release, it is clear to me — and I hope to you 
>> — that the big challenge for Quickstep is growing a community outside of 
>> Madison. I think we need to come up with a plan to address this so that it 
>> can be in this quarter’s report, and we can measure progress at the time of 
>> the next quarterly report. What do you think?
>>  Julian
>>  > On Jun 1, 2017, at 4:43 AM, johndam...@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, 21 June 2017, 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, June 07).
>> >
>> > 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.
>> > *   How does the podling rate their own maturity.
>> >
>> > This should be appended to the Incubator Wiki page at:
>> >
>> > https://wiki.apache.org/incubator/June2017
>> >
>> > 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
>>  
>> 
> 
> -- 
> Thanks,
> Harshad
> 

Re: Podling Report Reminder - June 2017

[Julian Hyde]

Quickstep community,

Now we have a first release, it is clear to me — and I hope to you — that the 
big challenge for Quickstep is growing a community outside of Madison. I think 
we need to come up with a plan to address this so that it can be in this 
quarter’s report, and we can measure progress at the time of the next quarterly 
report. What do you think?

Julian

> On Jun 1, 2017, at 4:43 AM, johndam...@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, 21 June 2017, 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, June 07).
> 
> 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.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://wiki.apache.org/incubator/June2017
> 
> 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 - June 2017

[Julian Hyde]

PS Here are the board minutes, containing the Quickstep report:
https://www.apache.org/foundation/records/minutes/2017/board_minutes_2017_03_15.txt

On Tue, May 23, 2017 at 10:36 AM, Julian Hyde  wrote:
> The previous report, 3 months ago, was all about making the release.
> Now we have a release, well done! (The next release will be easy in
> comparison.)
>
> Now the major issue that needs to be solved before graduation is
> growing a diverse community. By which I mean attracting contributors
> from outside Madison who in due course become committers and PPMC
> members.
>
> How can we achieve that?
>
> I'd like to come up with some concrete steps to put in this board
> report, so we can measure progress in the next board report
> (September).
>
>
> On Tue, May 23, 2017 at 3:00 AM,   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, 21 June 2017, 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, June 07).
>>
>> 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.
>> *   How does the podling rate their own maturity.
>>
>> This should be appended to the Incubator Wiki page at:
>>
>> https://wiki.apache.org/incubator/June2017
>>
>> 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 - June 2017

[Julian Hyde]

The previous report, 3 months ago, was all about making the release.
Now we have a release, well done! (The next release will be easy in
comparison.)

Now the major issue that needs to be solved before graduation is
growing a diverse community. By which I mean attracting contributors
from outside Madison who in due course become committers and PPMC
members.

How can we achieve that?

I'd like to come up with some concrete steps to put in this board
report, so we can measure progress in the next board report
(September).


On Tue, May 23, 2017 at 3:00 AM,   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, 21 June 2017, 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, June 07).
>
> 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.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/June2017
>
> 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: New Committer: Tianrun Li

[Julian Hyde]

Congratulations Tianrun, and welcome!

> On May 12, 2017, at 8:27 AM, Jignesh Patel  wrote:
> 
> The Project Management Committee (PMC) for Apache (incubating) Qucikstep
> 
> has invited Tianrun Li to become a committer and we are pleased 
> 
> to announce that he has accepted.
> 
> 
> 
> Welcome Tianrun! 
> 
> 
> 
> Being a committer enables easier contribution to the
> 
> project since there is no need to go via the patch
> 
> submission process. This should enable better productivity.
> 
> Being a PMC member enables assistance with the management
> 
> and to guide the direction of the project.
> 
> 
> 
> Cheers,
> 
> Jignesh 
> 

Re: [DISCUSS] Need for standard driver?

[Julian Hyde]

Thanks for bringing this up for discussion, Marc. 

If you have any questions about Avatica (which is part of the Calcite project, 
but may be spun off as a top-level project at some point in the future), I and 
Josh Elser will be happy to answer them.

Julian

> On Apr 20, 2017, at 9:03 AM, Marc Spehlmann  wrote:
> 
> I have a PR out for a CLI which interfaces with the network over gRPC [1].
> Julian recommended using a package called Avantica which wraps over a
> standard JDBC+ODBC drivers and takes care the protocol.
> 
> The question I have for /dev is if we have a need right now for a standard
> driver. I could see a use case being that for demoing QS and trying to find
> users, it would be valuable.
> 
> Does anyone have comments about how to do interaction with QS?
> 
> --Marc
> 
> [1] https://issues.apache.org/jira/browse/QUICKSTEP-87

Re: Blog post on storage formats

[Julian Hyde]

Very nice! And pictures too!

One suggestion (take it or leave it) - use colors to indicate which values 
belong to which columns. If will make the difference between row- and 
column-oriented format more apparent.

At some point those 3 graphics, plus the table with the data set, could be 
boiled down to one slide for presentations. Similar to the one that Arrow 
use[1].
 
Julian


[1] https://arrow.apache.org/img/simd.png 
 

> On Mar 31, 2017, at 3:33 PM, Jignesh Patel  wrote:
> 
> Very nice Harshad! I made minor edits in the PR 
> https://github.com/hbdeshmukh/incubator-quickstep-site/pull/1 
> 
> Cheers,
> Jignesh 
> 
> On 3/31/17, 2:29 PM, "Harshad Deshmukh"  wrote:
> 
>Hello all,
> 
>I have written a blog post on various storage formats implemented in 
>Quickstep. Please review the pull request - 
>https://github.com/apache/incubator-quickstep-site/pull/2 and provide 
>your feedback. If you don't have jekyll set up on your machine, you can 
>use this link to read the post: 
>
> https://github.com/hbdeshmukh/incubator-quickstep-site/blob/storage-formats-post/_posts/2017-03-30-storage-formats-quickstep.markdown
> 
>The SQL formatting doesn't look well on GitHub, but I think it shows up 
>alright on the actual website.
> 
>-- 
> 
>Thanks,
>Harshad
> 
> 
> 
> 

Re: Release publicity

[Julian Hyde]

Here’s my 2 cents on publicity: do a little and often, and use lots of pictures.

Very few people are tuned into the first broadcast of a new radio station, but 
more people tune in over time if there is regular good content. So, don’t bust 
a gut trying to make huge splash for the release. Make a short factual post 
about the release. Then work on some more content (say a demo, or a brief video 
of a demo).

In both tweets and blog posts, a graphic helps get your message across. So, aim 
to have an architecture slide ready to tweet in 1 or 2 weeks. And a slide about 
Quickstep’s memory format (or whatever) in a week after that.

Also, do a tweet and a blog post each time a significant feature lands in 
Quickstep (hopefully at least 2 or 3 per release).

Julian



> On Mar 27, 2017, at 8:25 PM, Harshad Deshmukh  wrote:
> 
> Hello folks,
> 
> I am making some noise (a.k.a publicity) about our release on various forums. 
> Please help us spread the word:
> 
> Hacker news: https://news.ycombinator.com/item?id=13962876 Honestly, this is 
> my first post on HN, so I am not sure how it works. I guess you need to 
> upvote it to make it more visible?
> 
> Twitter: https://twitter.com/ApacheQuickstep There are a couple of new 
> tweets. We should probably have a better twitter bio for the project. Right 
> now it is very brief "Democratizing Data Analytics". Any suggestions?
> 
> I am also writing a blog post on the various storage formats in Quickstep and 
> how to create them through CREATE statements. I somehow couldn't get jekyll 
> working on my machine.
> 
> -- 
> Thanks,
> Harshad
> 

Re: release announcement

[Julian Hyde]

Send it to the announce list. You can see other announcements and get some 
ideas here: 
http://mail-archives.apache.org/mod_mbox/www-announce/201703.mbox/browser 
 

Yes, it’s an opportunity to describe your mission (and unique technology) in a 
bit more detail. The list has a wide audience (e.g. I get pings from analysts 
after announcing a calcite release there) so use the exposure widely.

Also, it can be the first tweet on that long-neglected 
https://twitter.com/ApacheQuickstep  
account.

On the downloads page I would include the date of the release and a link to the 
release notes/history. You will want to describe the baseline functionality 
that is in this release so that next release you can describe what is new. At 
this point some projects have a “status” page describing in bullet points what 
is working and what is not working.

Julian

> On Mar 25, 2017, at 8:07 AM, Harshad Deshmukh  wrote:
> 
> Hi Marc,
> 
> I don't know about the Apache protocol, so may be the mentors may have 
> something to say about that.
> 
> How about saying high performance,  relational data processing engine 
> developed in C++?
> 
> The release is very exciting! I will start another thread regarding publicity 
> of the release.
> 
> Sent from Outlook for Android
> 
> 
> From: Marc Spehlmann
> Sent: Saturday, March 25, 9:57 AM
> Subject: release announcement
> To: dev@quickstep.incubator.apache.org
> 
> Hello quickstep, I am going to send an announce email to a few of the other 
> apache lists later today. Is there anything special about this release that 
> we want to mention (besides that it's our first release)? If not, that's 
> fine, I will send this email: ___ The Apache Quickstep (incubating) team is 
> pleased to announce the release of Quickstep 0.1.0 (our very first release!) 
> Quickstep is a high-performance C++ SQL database. The release is available 
> at: https://quickstep.incubator.apache.org/release Thank you, The Apache 
> Quickstep (incubating) team ___ --Marc

Re: [VOTE] Apache Incubating Quickstep 0.1.0 RC7

[Julian Hyde]

+1 (binding)

Downloaded, checked hashes, checked L&N, disclaimer, ran rat.

For next release, please add headers on all .md, .git*, .sh and .patch files. 
That will reduce the number of rat exceptions.

Julian


> On Mar 20, 2017, at 9:42 AM, Harshad Deshmukh  wrote:
> 
> +1 from me.
> 
> Apart from release metadata:
> 
> Build passes on Ubuntu 14.04 using gcc 4.9.4
> 
> All tests pass.
> 
> No style issues.
> 
> Thanks Marc for putting together RC7!
> 
> 
> On 03/20/2017 10:26 AM, Josh Elser wrote:
>> +1
>> 
>> * Verified commits since rc6
>> * sigs/xsums still OK
>> 
>> For your $release.next:
>>  - gflags still listed in LICENSE unnecessarily (I don't see it bundled)
>> 
>> Thanks for including sha256/512 hashes as well!
>> 
>> - Josh
>> 
>> On 2017-03-19 18:57 (-0400), Marc Spehlmann  wrote:
>>> This vote is for approval of the Quickstep-0.1.0 RC7.
>>> 
>>> We had a few minor changes since RC6. They were changes to the LICENSE and
>>> NOTICE
>>> file, as well as updating some headers. These should not have made
>>> functional changes.
>>> 
>>> Voters should download, unpack, build, and test the package before voting.
>>> 
>>> A +1 vote means that the package passes all tests and meets Apache
>>> guidelines.
>>> A -1 vote should be accompanied with a short reason.
>>> 
>>> Votes will remain open for 2 days in light of this being a very similar
>>> candidate
>>> to the last one.
>>> 
>>> ___
>>> 
>>> The commit to be voted upon:
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-quickstep.git;a=shortlog;h=refs/tags/v0.1.0-rc7
>>>  
>>> 
>>> The artifacts to be voted on are located here:
>>> https://dist.apache.org/repos/dist/dev/incubator/quickstep/0.1.0/RC7/
>>> 
>>> Release artifacts are signed with the following key:
>>> https://people.apache.org/keys/committer/spehl
>>> 
>>> Please vote on releasing this package as Apache Incubating Quickstep 0.1.0.
>>> 
> 
> -- 
> Thanks,
> Harshad
> 

Re: [VOTE] Apache Incubating Quickstep 0.1.0 RC6

[Julian Hyde]

+1 (binding)

Download tar-ball, checked KEYS, checked hashes, ran Rat, checked for
LICENSE, NOTICE, DISCLAIMER.

Rat had several exceptions (listed below) but no show-stoppers.

Thanks for fixing the important issues that I noted in RC5. Next
release please carry on down that list of issues, put some content
into HISTORY.md, and make sure Doxyfle each .patch, .md and .sh file
has a header.

Julian

---

Rat output:

*
Summary
---
Generated at: 2017-03-08T17:39:21-08:00

Notes: 17
Binaries: 20
Archives: 0
Standards: 2890

Apache Licensed: 1251
Generated Documents: 0

JavaDocs are generated, thus a license header is optional.
Generated files do not require license headers.

1601 Unknown Licenses

*

Files with unapproved licenses:

  ./.gitattributes
  ./.gitignore
  ./.gitmodules
  ./BUILDING.md
  ./CREDITS.md
  ./DEV_README.md
  ./Doxyfile
  ./GENERATOR_FUNCTIONS.md
  ./HISTORY.md
  ./README.md
  ./WORKING_WITH_AN_IDE.md
  ./build/vagrant/README.md
  ./parser/preprocessed/SqlLexer_gen.hpp
  ./parser/preprocessed/genfiles.sh
  ./query_execution/README.md
  ./relational_operators/tests/text_scan_faulty_golden_output.txt
  ./relational_operators/tests/text_scan_faulty_input.txt
  ./relational_operators/tests/text_scan_golden_output.txt
  ./relational_operators/tests/text_scan_input.txt
  ./third_party/README.md
  ./third_party/patches/benchmark/benchmarkCMake.patch
  ./third_party/patches/benchmark/benchmarkSrcCMakeLists.patch
  ./third_party/patches/gflags/CMakeLists.patch
  ./third_party/patches/gflags/gflags_reporting.cc.patch
  ./third_party/patches/linenoise/CMakeLists.txt
  ./third_party/patches/linenoise/linenoise.c.patch
  ./third_party/patches/linenoise/linenoise.h.patch
  ./third_party/patches/re2/re2CMake.patch
  ./third_party/src/cpplint/cpplint.py
 (and many more files under third_party/src).




On Wed, Mar 8, 2017 at 2:16 PM, Marc Spehlmann  wrote:
> This vote is for approval of the Quickstep-0.1.0 RC6.
>
> Voters should download, unpack, build, and test the package before voting.
>
> +1 vote should be accompanied with what you did with the release.
> -1 vote should be accompanied with a short reason.
>
> Votes will remain open for 3 days.
>
> ___
>
> Changes since RC5:
> - Vote email has been refactored. Added a template on the confluence wiki.
> - Removed KEYS file from the main github repo. It now exists as a single
> source of truth in the SVN repo for release artifacts. I updated the KEYS
> file to conform to the apache standard.
> - We'll now use sha256, sha512, and md5 to hash the artifacts
> - Created History.md file
> - Added additional headers based on RAT's output
> - Removed references to Pivotal
>
> SHA512
> c0cfffb701680ab3a8277f9e1c64f0a91a53e6eb6c32321c67a10aaed65557651d2495ed9503b845d41ab02a1bfb8f4d1481c5bbe270240a4ca702687a87e860
>  apache-quickstep-incubating-0.1.0.tar.gz
>
> ___
>
> The commit to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-quickstep.git;a=commit;h=f8cf7fba51db3748c1c241c7e8880d499634213b
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/quickstep/0.1.0/RC6/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/spehl
>
> Please vote on releasing this package as Apache Incubating Quickstep 0.1.0.

Re: [VOTE] incubator-quickstep-0.1.0RC5

[Julian Hyde]

-1 (binding)

Sorry my review is so late; I know that you’ve already closed the vote; but I 
figured my feedback would be more useful now than waiting for RC6.

The release is actually in good shape; well done. My formal “-1” vote is due to 
issue 0 (content of the vote email) and 5 (copyright year). Please fix these 
show-stoppers in the next RC. Other issues are well worth looking into, because 
others may raise them in the IPMC vote.

Julian


0. I found the release candidate at 
https://dist.apache.org/repos/dist/dev/incubator/quickstep/0.1.0/RC5/ 
. Please 
include its URL and its hashes (the URLs of the hashes AND the actual hash 
values) in the vote email next time. The proposition to be voted upon  needs to 
be self-contained and immutable.

1. KEYS [ https://dist.apache.org/repos/dist/dev/incubator/quickstep/KEYS 
 ] looks a bit 
strange — usually the user & signers are at the top of each block (see for 
example http://www.apache.org/dist/calcite/KEYS 
) but import succeeded:

$ gpg --import KEYS
gpg: key A3C29E12: public key "Jignesh Patel " imported
gpg: key 5A29899A: public key "Marc Spehlmann (apache) " 
imported
gpg: Total number processed: 2
gpg:   imported: 2  (RSA: 2)

2. Checked hashes and keys. (Let’s move to something stronger than MD5 and SHA1 
soon. Also, let’s do a key signing party so that Marc & Jignesh are in the web 
of trust.)

3. The tar-ball contains KEYS. Not much point in that (because if someone 
compromised the tar-ball they would undoubtedly insert their a compromised KEYS 
file!), but no harm either.

4. I didn’t try to build (I’m not on a machine with sufficient horse-power), 
but it’s good to see clear build instructions in the tar-ball.

5. Checked that LICENSE, DISCLAIMER, NOTICE. The year in NOTICE must be 2017.

6. Are all of the lines in NOTICE *required*? People tend to put lines into a 
NOTICE out of *courtesy*. But it is mis-placed courtesy because the consumers 
of your software are *required* to reproduce your NOTICE verbatim. If Quickstep 
Technologies and Pivotal Software contributed under the ASL, then I don’t 
believe their copyright notices are required.

In NOTICE, by “third_party/benchmark”, do you mean 
“third_party/src/tmb/benchmarks”?

third_party/src/tmb/README.md says "TMB is part of the Quickstep project 
(copyright Pivotal Software, Inc.) and is distributed under the same license 
terms.” This statement is confusing now that Quickstep is now Apache Quickstep. 
If TMB has been contributed to Apache Quickstep can we just move it out of 
third_party?

third_party/linenoise and third_party/gpertools don’t seem to be included in 
the tar-ball, so the entry can be removed from NOTICE.

7. It is useful (not required) to include release notes, including changes 
since the previous release. Some projects include a HISTORY.md file.

8. There are pivotalsoftware.com URLs in README.md and DEV_README.md. Can you 
change these to apache.org .

9. Apache Rat found the following files without headers (ignoring files under 
third_party/src):

  ./.gitattributes
  ./.gitignore
  ./.gitmodules
  ./.travis.yml
  ./BUILDING.md
  ./CREDITS.md
  ./DEV_README.md
  ./Doxyfile
  ./GENERATOR_FUNCTIONS.md
  ./README.md
  ./WORKING_WITH_AN_IDE.md
  ./build/vagrant/README.md
  ./parser/preprocessed/SqlLexer_gen.hpp
  ./parser/preprocessed/genfiles.sh
  ./query_execution/README.md
  ./relational_operators/tests/text_scan_faulty_golden_output.txt
  ./relational_operators/tests/text_scan_faulty_input.txt
  ./relational_operators/tests/text_scan_golden_output.txt
  ./relational_operators/tests/text_scan_input.txt
  ./third_party/README.md
  ./third_party/download_and_patch_prerequisites.sh
  ./third_party/reset_third_party_dir.sh
  ./third_party/patches/benchmark/benchmarkCMake.patch
  ./third_party/patches/benchmark/benchmarkSrcCMakeLists.patch
  ./third_party/patches/gflags/CMakeLists.patch
  ./third_party/patches/gflags/gflags_reporting.cc.patch
  ./third_party/patches/linenoise/CMakeLists.txt
  ./third_party/patches/linenoise/linenoise.c.patch
  ./third_party/patches/linenoise/linenoise.h.patch
  ./third_party/patches/re2/re2CMake.patch
  ./types/README.md

Add headers to as many of these as you can.

10. Apache Rat found 2 files that it considered to be GPL3:

  GPL3  ./parser/preprocessed/SqlParser_gen.cpp
  GPL3  ./parser/preprocessed/SqlParser_gen.hpp

But according to https://issues.apache.org/jira/browse/LEGAL-291 
 these files can be 
distributed under ASL. So we’re good.


Julian



> On Mar 2, 2017, at 12:25 PM, Harshad Deshmukh  wrote:
> 
> Hi Marc,
> 
> +1 from me. Here's a brief summary of what I tested -
> 
> 1. Download the source code - OK
> 
> 2. Download the third party libraries (dependencies) - OK
> 
> 

Re: Podling Report - Seeking feedback

[Julian Hyde]

Thanks for writing the report.

I replaced #3 with "No releases so far." and signed off.

Julian



On Fri, Mar 3, 2017 at 12:31 PM, Roman Shaposhnik  wrote:
> I still think that #3 on the graduation blockers list should be "Lack
> of releases so far"
>
> If there's no disagreement -- I'll change it.
>
> Thanks,
> Roman.
>
> On Thu, Mar 2, 2017 at 5:44 PM, Jignesh Patel  wrote:
>> Thanks Harshad for taking the lead on this!
>>
>> I have also uploaded this on: https://wiki.apache.org/incubator/March2017. 
>> We can make changes to the wiki if there is feedback from the mentors. Let 
>> us know.
>>
>> Cheers,
>> Jignesh
>>
>> On 3/2/17, 5:36 PM, "Harshad Deshmukh"  wrote:
>>
>> Hello mentors,
>>
>> May I request you to review the following podling report? Thanks for
>> your time.
>>
>> *   Your project name
>> Apache (incubating) Quickstep
>>
>> *   A brief description of your project, which assumes no knowledge of
>>  the project or necessarily of its field
>> Apache Quickstep is high-performance database engine designed to exploit
>> the full potential
>> of hardware that is packed in modern computing boxes (servers and 
>> laptops).
>> The initial version targets single-node in-memory environments.
>>
>> *   A list of the three most important issues to address in the move
>>  towards graduation.
>> 1) Building a Quickstep community
>> 2) More adoption of the Quickstep technology
>> 3) Making the technology easier to understand and use
>>
>> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>>  aware of
>> None
>>
>> *   How has the community developed since the last report
>>
>> Members of the community have become more aware about the release 
>> process.
>>
>> The details about the release process are well documented so that future
>> releases will be smooth and more frequent.
>>
>> *   How has the project developed since the last report.
>>
>> We will have our first release this month. Since the last report,
>>
>> 1) We have made several changes to the code base.
>> Some highlights are: Cleaning up the third party library code as per the
>> Apache hygiene, improve the code performance by adding several novel
>> features.
>>
>> 2) Preparation for release -
>> Created scripts and step by step procedural documentation for how to
>> make a Quickstep release.
>>
>> Scripts have been added to the main repo while documentation is on
>> confluence.
>>
>> We went through several release candidates.
>>
>> During this period, we identified some usability issues on our supported
>> platforms and fixed them.
>>
>> *   How does the podling rate their own maturity.
>>
>> Preparation for the first release is under way and the release is
>> expected to happen in this month.
>>
>> --
>>
>> Thanks,
>> Harshad
>>
>>
>>
>>

Re: We really need to get going with the podling report

[Julian Hyde]

Ah, I didn’t notice the artifacts because they weren’t listed in the email. The 
vote thread needs to list the URLs of the artifacts and include (in the body of 
the email) the checksums. (Why? Because people voting on the release must 
download those artifacts and check them against the checksums. And the 
checksums need to be in the email thread so that no one can later deny that 
they voted on these exact artifacts.)

As an example, here’s a fragment from a recent Calcite vote:

(begin)

The commit to be voted upon:
http://git-wip-us.apache.org/repos/asf/calcite/commit/f8ba670de4e283d1532f288de53fdb67fa4dea67

Its hash is f8ba670de4e283d1532f288de53fdb67fa4dea67.

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.11.0-rc0

The hashes of the artifacts are as follows:
apache-calcite-1.11.0-src.tar.gz:MD5 = 88 FF 46 FC 13 A6 AE 98  BB 53 7D 8C
  24 73 D7 12
apache-calcite-1.11.0-src.tar.gz:   SHA1 = 7CDE F906 0665 44F4 6CCA  4021 D515
  935A 6243 A869
apache-calcite-1.11.0-src.tar.gz: RMD160 = 0783 C9BD 5397 B045 45AB  F750 7541
  611F A78A D31C
apache-calcite-1.11.0-src.tar.gz: SHA224 = 024B9857 29EA0FCD 0315E10C C75DD1F1
  A50A1611 93ED3577 C91F5E3A
apache-calcite-1.11.0-src.tar.gz: SHA256 = 10976E10 3C420300 AFC7AD83 810755CA
  6DE31081 DDFB3325 7721A204 ACDA0D26
apache-calcite-1.11.0-src.tar.gz: SHA384 = 178FC2CC 9064A51B 30AE7454 BA7A2507
  7A555E05 CB758FE0 642C4877 622BE539
  DAF7BCC2 CB9D2244 335FF0C7 5513DA7B
apache-calcite-1.11.0-src.tar.gz: SHA512 = E539EE3C 39DF3358 DABC4216 861C88D3
  4F7030F3 34C7D759 21CC47B9 8D4E5B09
  124AEA8D F5AC3B3D 29BFAADB A027102C
  795F0DAF 778AFAC2 93F1D902 E2D62B2A
apache-calcite-1.11.0-src.zip:MD5 = F0 FD C7 7F A0 32 E4 95  E3 E5 3D 47 B7
   B2 C4 8D
apache-calcite-1.11.0-src.zip:   SHA1 = 1347 67F0 1D70 4AB9 FBB2  7EEF 61F1 1A8A
   86E9 E26B
apache-calcite-1.11.0-src.zip: RMD160 = EE4D 5C2F 4396 2758 9DF0  C5CA 961A 0631
   64A8 E060
apache-calcite-1.11.0-src.zip: SHA224 = 28A18665 3695592E A15C2CF1 0A684A15
   D5A53243 CB712249 FDBEBF65
apache-calcite-1.11.0-src.zip: SHA256 = 7AEF77DE EF34612D 3AA6BF72 F02163A2
   D8808658 CAB8980B B35D454D AC3A5BB7
apache-calcite-1.11.0-src.zip: SHA384 = E6EDFAFD 8E2C55B9 9F19B75F F276A2AF
   82E4DC6B 8788D143 BAB42CEC D029ACD1
   E315C857 9645DF30 E41DEA8D 8A2767AA
apache-calcite-1.11.0-src.zip: SHA512 = F2BEEBB4 649DAA40 B73EBE51 D22242D8
   6250B27E 94F4C100 5915E6D5 8A2EF1A5
   1BFBB37E C1670D68 C0427FB4 85785CE4
   504BC1A5 DFEFE2EE 288323C7 DCD5DEF4

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/jhyde.asc

Please vote on releasing this package as Apache Calcite 1.11.0.

(end)

I recommend that Quickstep adopt similar boilerplate, because a release vote is 
actually a rather formal protocol. The full thread is here:  
https://mail-archives.apache.org/mod_mbox/calcite-dev/201701.mbox/%3C5C408E13-C276-4902-A0FC-802736574168%40apache.org%3E
 
<https://mail-archives.apache.org/mod_mbox/calcite-dev/201701.mbox/%3c5c408e13-c276-4902-a0fc-802736574...@apache.org%3E>

Julian



> On Mar 2, 2017, at 1:09 PM, Marc Spehlmann  wrote:
> 
> We have been publishing to the dev/ svn
> 
> https://dist.apache.org/repos/dist/dev/incubator/quickstep/0.1.0/RC5/
> 
> Maybe we missed something. Is there a better way to announce this?
> 
> On Thu, Mar 2, 2017 at 2:49 PM, Julian Hyde  wrote:
> 
>> I haven’t been voting on the RCs because I haven’t yet seen a “release
>> candidate” — a signed artifact (tarball) and its checksums. It seems that
>> while the code is in good shape, release packaging needs some work. I’ll
>> weigh in on the latest RC vote thread.
>> 
>> Julian
>> 
>> 
>>> On Mar 2, 2017, at 12:33 PM, Harshad Deshmukh 
>> wrote:
>>> 
>>> Hi Julian,
>>> 
>>> Thanks for your inputs. I will modify the report accordingly and send it
>> out for review.
>>> 
>>> Just an update on the release progress - Marc floated a vote for RC5
>> (yesterday evening CST) on the dev list, which has gotten more than 3 +1s
>> so fa

Re: We really need to get going with the podling report

[Julian Hyde]

I haven’t been voting on the RCs because I haven’t yet seen a “release 
candidate” — a signed artifact (tarball) and its checksums. It seems that while 
the code is in good shape, release packaging needs some work. I’ll weigh in on 
the latest RC vote thread.

Julian


> On Mar 2, 2017, at 12:33 PM, Harshad Deshmukh  wrote:
> 
> Hi Julian,
> 
> Thanks for your inputs. I will modify the report accordingly and send it out 
> for review.
> 
> Just an update on the release progress - Marc floated a vote for RC5 
> (yesterday evening CST) on the dev list, which has gotten more than 3 +1s so 
> far. It appears that this release candidate (RC5) should be the final one, 
> therefore I thought this week should be a realistic target for the release. 
> Marc should have an idea about the next steps, so if I misunderstood 
> something w.r.t the release estimates, please let me know.
> 
> 
> On 03/02/2017 02:12 PM, Marc Spehlmann wrote:
>> Hi Julian,
>> 
>> I agree that 'this week' is optimistic. Though, we have been going through
>> the voting process on @dev, it's likely that the current RC will not pass,
>> meaning that we'll need to restart the whole process, as you said.
>> 
>> Considering, 'this month' is probably a more realistic wording.
>> 
>> On Thu, Mar 2, 2017 at 2:08 PM, Julian Hyde  wrote:
>> 
>>> In answer to the “How does the podling rate their maturity?”. The
>>> incubator report used to have categories "Ready to Graduate", “Some
>>> Community Growth", "No Release" and "Still Getting Started.” Out of these,
>>> I think “No release” fits best. You can add that the first release is well
>>> under way.
>>> 
>>> "We will have our first release this week” is a bit optimistic. Remember
>>> you need to create a release candidate, pass a vote on the Quickstep list
>>> (which takes 3 working days), repeat if there is a problem with the RC, and
>>> then pass a vote on the incubator list (which takes 3 working days). Again,
>>> the incubator vote might fail, and in fact probably will the first or
>>> second time.
>>> 
>>> A true statement is “we are almost ready to start a vote on our first
>>> release candidate”.
>>> 
>>> Julian
>>> 
>>> 
>>>> On Mar 2, 2017, at 11:04 AM, Harshad Deshmukh 
>>> wrote:
>>>> Hi Roman,
>>>> 
>>>> Apologies for the delay. I am not sure how to address two of these
>>> questions, hence left them blank. Any inputs in that regard should be
>>> helpful. Can you please review the following report?
>>>> *   Your project name
>>>> Apache (incubating) Quickstep
>>>> 
>>>> *   A brief description of your project, which assumes no knowledge of
>>>>the project or necessarily of its field
>>>> Apache Quickstep is high-performance database engine designed to exploit
>>> the full potential
>>>> of hardware that is packed in modern computing boxes (servers and
>>> laptops).
>>>> The initial version targets single-node in-memory environments.
>>>> 
>>>> *   A list of the three most important issues to address in the move
>>>>towards graduation.
>>>> 1) Building a Quickstep community
>>>> 2) More adoption of the Quickstep technology
>>>> 3) Making the technology easier to understand and use
>>>> 
>>>> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>>>>aware of
>>>> None
>>>> 
>>>> *   How has the community developed since the last report
>>>> 
>>>> *   How has the project developed since the last report.
>>>> 
>>>> We will have our first release this week. Since the last report,
>>>> 
>>>> 1) We have made several changes to the code base.
>>>> Some highlights are: Cleaning up the third party library code as per the
>>> Apache hygiene, improve the code performance by adding several novel
>>> features.
>>>> 2) Preparation for release -
>>>> Created scripts and step by step procedural documentation for how to
>>> make a Quickstep release. Scripts have been added to the main repo while
>>> documentation is on confluence.
>>>> We went through several release candidates. During this period, we
>>> identified some usability issues on our supported platforms and fixed them.
>>> Quickstep is now on schedule for a release later this week.
>>>> *   How does the podling rate their own maturity.
>>>> 
>>>> 
>>>> On 02/28/2017 10:23 PM, Roman Shaposhnik wrote:
>>>>> Bueller? Bueller? Bueller?
>>>> --
>>>> Thanks,
>>>> Harshad
>>>> 
>>> 
> 
> -- 
> Thanks,
> Harshad
> 

Re: We really need to get going with the podling report

[Julian Hyde]

In answer to the “How does the podling rate their maturity?”. The incubator 
report used to have categories "Ready to Graduate", “Some Community Growth", 
"No Release" and "Still Getting Started.” Out of these, I think “No release” 
fits best. You can add that the first release is well under way.

"We will have our first release this week” is a bit optimistic. Remember you 
need to create a release candidate, pass a vote on the Quickstep list (which 
takes 3 working days), repeat if there is a problem with the RC, and then pass 
a vote on the incubator list (which takes 3 working days). Again, the incubator 
vote might fail, and in fact probably will the first or second time.

A true statement is “we are almost ready to start a vote on our first release 
candidate”.

Julian


> On Mar 2, 2017, at 11:04 AM, Harshad Deshmukh  wrote:
> 
> Hi Roman,
> 
> Apologies for the delay. I am not sure how to address two of these questions, 
> hence left them blank. Any inputs in that regard should be helpful. Can you 
> please review the following report?
> 
> *   Your project name
> Apache (incubating) Quickstep
> 
> *   A brief description of your project, which assumes no knowledge of
>the project or necessarily of its field
> Apache Quickstep is high-performance database engine designed to exploit the 
> full potential
> of hardware that is packed in modern computing boxes (servers and laptops).
> The initial version targets single-node in-memory environments.
> 
> *   A list of the three most important issues to address in the move
>towards graduation.
> 1) Building a Quickstep community
> 2) More adoption of the Quickstep technology
> 3) Making the technology easier to understand and use
> 
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>aware of
> None
> 
> *   How has the community developed since the last report
> 
> *   How has the project developed since the last report.
> 
> We will have our first release this week. Since the last report,
> 
> 1) We have made several changes to the code base.
> Some highlights are: Cleaning up the third party library code as per the 
> Apache hygiene, improve the code performance by adding several novel features.
> 
> 2) Preparation for release -
> Created scripts and step by step procedural documentation for how to make a 
> Quickstep release. Scripts have been added to the main repo while 
> documentation is on confluence.
> We went through several release candidates. During this period, we identified 
> some usability issues on our supported platforms and fixed them. Quickstep is 
> now on schedule for a release later this week.
> 
> *   How does the podling rate their own maturity.
> 
> 
> On 02/28/2017 10:23 PM, Roman Shaposhnik wrote:
>> Bueller? Bueller? Bueller?
> 
> -- 
> Thanks,
> Harshad
> 

Re: release candidate svn repo

[Julian Hyde]

Yes, it probably is. I believe that as a committer of an incubator
project, you have karma to commit to any incubator project (not that
you should use that power!).

See if you can create the corresponding
https://dist.apache.org/repos/dist/release/incubator/quickstep
directory and copy the KEYS file into it. (That's where releases will
go, when you've passed all the votes. But the KEYS can go there
already.)

On Tue, Feb 14, 2017 at 2:25 PM, Marc Spehlmann  wrote:
> Awesome, thank you so much! Is creating a directory in svn on
> dist.apache.org something which is in our power as apache members?
>
> On Tue, Feb 14, 2017 at 4:24 PM, Julian Hyde  wrote:
>
>> I've just created the quickstep directory in svn. Now if you're a
>> committer, you should be able to do this:
>>
>>   svn co https://dist.apache.org/repos/dist/dev/incubator/quickstep
>>
>>
>> Julian
>>
>>
>> On Tue, Feb 14, 2017 at 2:12 PM, Marc Spehlmann  wrote:
>> > I'm looking through the impala guide to releases and they have an svm
>> repo
>> > where they store their release candidate tarballs, hashes plus an svn for
>> > the final releases.
>> >
>> > https://cwiki.apache.org/confluence/display/IMPALA/
>> DRAFT%3A+How+to+Release
>> >
>> > repo is
>> >
>> > svn checkout https://dist.apache.org/repos/dist/dev/incubator/impala/
>> >
>> > Anyone know how to make an svm repo on apache.org?
>>

Re: release candidate svn repo

[Julian Hyde]

I've just created the quickstep directory in svn. Now if you're a
committer, you should be able to do this:

  svn co https://dist.apache.org/repos/dist/dev/incubator/quickstep


Julian


On Tue, Feb 14, 2017 at 2:12 PM, Marc Spehlmann  wrote:
> I'm looking through the impala guide to releases and they have an svm repo
> where they store their release candidate tarballs, hashes plus an svn for
> the final releases.
>
> https://cwiki.apache.org/confluence/display/IMPALA/DRAFT%3A+How+to+Release
>
> repo is
>
> svn checkout https://dist.apache.org/repos/dist/dev/incubator/impala/
>
> Anyone know how to make an svm repo on apache.org?

Re: Release Managers?

[Julian Hyde]

I don't know whether it's even possible for more than one person to sign the 
release.

The way to make the release more "trustworthy" is to strengthen the release 
manager's web of trust. Have a key signing party [1] and sign each other's 
keys. 

If the one person who signs the release is well established in the Apache web 
of trust then the release is clearly a genuine product of the Apache Software 
Foundation. 

Regarding the report. It's possible that you're now scheduled to report only 
once per quarter. Projects are only monthly when they start out. 

Julian

[1] https://en.m.wikipedia.org/wiki/Key_signing_party



Sent from my iPad
> On Feb 11, 2017, at 2:04 PM, Jignesh Patel  wrote:
> 
> Hi folks: We are nearly ready to do a release. Anyone else wants to sign the 
> release along with me? 
> 
> 
> 
> Also, I haven’t seen an email about providing input for the usual Podling 
> report? Anyone else has seen this? I hope I haven’t missed it.
> 
> 
> 
> Cheers,
> 
> Jignesh  
> 

Re: Release Signing

[Julian Hyde]

Yes, only the release manager needs to sign.

The KEYS file contains all the people who have EVER signed a release.

> On Feb 1, 2017, at 6:20 PM, Jignesh Patel  wrote:
> 
> That would be nice if that were the case. We are nearly there then!
> 
> Cheers,
> Jignesh 
> 
> On 2/1/17, 7:47 PM, "Marc Spehlmann"  wrote:
> 
>It sounds like only one release manager needs to sign it then?
> 
> 
> 
> 

Re: release: third_party/

[Julian Hyde]

Well done! I know this wasn’t easy.

> On Jan 31, 2017, at 3:41 PM, Harshad Deshmukh  wrote:
> 
> Hello all,
> 
> At long last, we have dealt with the third party issue. Some highlights:
> 
> 1. Most of the libraries are now downloaded through a shell script.
> 
> 2. The download links point to the release versions of the libraries.
> 
> 3. After downloading the source code, we apply appropriate patches.
> 
> Some libraries don't have an official release yet, so we will wait until they 
> have a release. Until then, we have copied their entire source code to our 
> third party directory. I have updated the build instructions based on these 
> changes.
> 
> Thanks Julian, Marc and Zuyu for your help.
> 
> On 01/23/2017 09:57 PM, Jignesh Patel wrote:
>> Thanks Zuyu for the nice summary! For this release, I’d support going with 
>> Harshad’s lead, which is a single script to download the third party 
>> libraries.
>> 
>> Dear Harshad: If your life is simpler with any of the other option (e.g. the 
>> issue you are having with an old version of Ubuntu in Travis), when feel 
>> free to go with the Mesos approach.
>> 
>> Cheers,
>> Jignesh
>> 
>> On 1/23/17, 12:26 AM, "Zuyu Zhang" > z...@cs.wisc.edu> wrote:
>> 
>> FYI, there are some Apache projects in C++ (
>> https://projects.apache.org/projects.html?language), and more in github (
>> https://github.com/apache?language=c%2B%2B), including incubator 
>> projects.
>>  I summaries how typically they deal with the third parties and the 
>> release.
>> - Apache Mesos (https://github.com/apache/mesos) has most third 
>> parties
>>in release tar balls, along with patches.
>>- Apache Kudu (https://github.com/apache/kudu) has multiple scripts to
>>download and build third parties.
>>- Apache NiFi - MiNiFi (https://github.com/apache/nifi-minifi-cpp)
>>includes the whole codebase of third parties.
>>  Cheers,
>> Zuyu
>> 
>> 
> 
> -- 
> Thanks,
> Harshad
> 

Re: Release Signing

[Julian Hyde]

It does say so in the instructions, but I’ll reiterate: be sure to use your 
apache.org  email address for your key. People get spooked 
if they get a release that is not signed by someone who is not obviously an 
Apache committer.

Generally the release manager will either build the release on their own 
machine or download a build to their machine. Then they will sign it on their 
machine (where their private key is present). Lastly they will upload it (which 
happens by means of a “svn commit”).

At the same time they will make sure that their key is in KEYS, and if not they 
will edit KEYS and do another “svn commit”.

Julian




> On Jan 31, 2017, at 3:35 PM, Marc Spehlmann  wrote:
> 
> One of the steps that must take place before releasing a release tarball is
> to have the release managers digitally sign the tarball.
> 
> Hakan, Jignesh, Harshad I think you all are the release managers. Please
> follow this guide
> 
> http://quickstep.apache.org/release-signing/
> 
> to
> 1) create a key pair
> 2) upload the public key to a public keyserver
> 3) (bonus for now) add the public key to a KEYS file in the root of
> quickstep.
> 
> When the release tarball is ready, we can sign it.
> 
> To be fair, I'm not totally sure how this works because it seems to me that
> everyone has to sign the release with their private key, meaning that it
> must be uploaded to each PC where the private key is held, then signed?
> That seems cumbersome.
> 
> Anyways, steps 1,2 are straightforward and need to be done before we
> resolve that last problem.
> 
> Cheers,
> Marc

Re: Fixing git submodule commits to a release

[Julian Hyde]

And by the way, I might be giving you completely bad advice here. The general 
advice is that a release should work standalone and be robust when other 
projects change. But I don’t know how you should achieve it. I’ve never made a 
release of a project in any language other than java. You guys should see what 
similar Apache projects do, and consider asking a question on general@incubator.

> On Jan 8, 2017, at 12:22 PM, Marc Spehlmann  wrote:
> 
> Julian mentioned that it's unsafe to have submodules track from the head of
> their respective repo because things can break unexpectedly.
> 
> I'm thinking a small change we can do is simply fix the submodules to a
> release commit.
> 
> Google Test: release 1.8.0
> https://github.com/google/googletest/releases/tag/release-1.8.0
> 
> Google RE: release 2017-1-1
> https://github.com/google/re2/releases/tag/2017-01-01
> 
> Google Protobuf2: 2.6.1
> https://github.com/google/protobuf/releases/tag/v2.6.1
> 
> Zuyu, I know there's some work you did switching to proto3, can you comment
> on this?
> 
> Thanks,
> Marc

Re: release: third_party/

[Julian Hyde]

Better still, make a release depend only releases. Snapshots and even
commit IDs can disappear.

And consider the state of the IP. In Apache and many other open source
projects, the IP is only guaranteed "clean" when it has been formally
released.

Sorry this is all painful. But conversely, this is the value-add of
making a release.

On Thu, Jan 5, 2017 at 11:57 AM, Harshad Deshmukh  wrote:
>> Also, since you’re relying on the latest googletest, protobuf and re2 your
>> release will work today and will break at some point in the future. That’s
>> not OK. A release can depend only on releases, not snapshots or live
>> repositories.
>
> Thanks for pointing that. It is possible to fetch a particular release
> (based on its commit ID) of the submodule. We will add the release commit ID
> to the git submodule file.
>
>
>
> On 01/05/2017 01:44 PM, Julian Hyde wrote:
>>
>> Git sub-modules are useful, I agree. But for a source release, the goal is
>> that someone should be able to download the source tar-ball and go:
>>
>> $ curl -O …/apache-quickstep-x.x-incubating.tar.gz
>> $ tar xvfz apache-quickstep-x.x-incubating.tar.gz
>> $ cd apache-quickstep-x.x-incubating/build
>> $ ./download-thirdparty.sh
>> $ cmake etc.
>>
>> I tried to find other Apache projects that use git submodules and see what
>> they do for source releases. Not much luck. Maybe someone else can find
>> something.
>>
>> Also, since you’re relying on the latest googletest, protobuf and re2 your
>> release will work today and will break at some point in the future. That’s
>> not OK. A release can depend only on releases, not snapshots or live
>> repositories.
>>
>> Julian
>>
>>
>>
>>> On Jan 5, 2017, at 11:03 AM, Harshad Deshmukh 
>>> wrote:
>>>
>>> Thanks for the review Julian.
>>>
>>> For some of the third party libraries used in Quickstep (e.g. googletest,
>>> protobuf and re2) we use the submodules feature of git. For such libraries,
>>> the developer has to initialize the submodule only once, which pulls code
>>> from the third party repo to the Quickstep third party directory.
>>>
>>> I don't know of a centralized repo for C++ projects. Does the git
>>> submodule method sound similar to the maven central approach you mentioned?
>>>
>>> On 01/05/2017 12:43 PM, Julian Hyde wrote:
>>>>
>>>> I took a quick look at third_party and there don’t seem to be any
>>>> binaries in there. That’s good. You definitely cannot include binaries in a
>>>> source release.
>>>>
>>>> The more you can remove from third_party, the better. It doesn’t have to
>>>> be done this release, but the less IP there is to review, the easier for
>>>> everyone.
>>>>
>>>> Consider pulling from an external source the first time the developer
>>>> builds in a sandbox, then apply patches. The patches will be the only thing
>>>> checked in to quickstep. (My expertise is in Java projects, which these 
>>>> days
>>>> get their dependencies from a Maven repo such as Maven central; I don’t 
>>>> know
>>>> whether there is an equivalent place to pull C and C++ source code. Might 
>>>> be
>>>> worth a review of what other C and C++ based Apache projects do for their
>>>> third-party dependencies.)
>>>>
>>>> Julian
>>>>
>>>>
>>>>> On Jan 5, 2017, at 9:43 AM, Marc Spehlmann 
>>>>> wrote:
>>>>>
>>>>> That seems to be the repo with the LLVM code for implementing IWYU. I
>>>>> think
>>>>> what we have in our repo is scripts ontop of that library. I'm
>>>>> wondering
>>>>> where the scripts came from.
>>>>>
>>>>> Thanks,
>>>>> Marc
>>>>>
>>>>> On Thu, Jan 5, 2017 at 10:50 AM, Harshad Deshmukh 
>>>>> wrote:
>>>>>
>>>>>> Hi Marc,
>>>>>>
>>>>>> How about this one for IWYU?
>>>>>>
>>>>>> https://github.com/include-what-you-use/include-what-you-use
>>>>>> /blob/master/LICENSE.TXT
>>>>>>
>>>>>>
>>>>>> On 01/05/2017 10:43 AM, Marc Spehlmann wrote:
>>>>>>
>>>>>>> I double checked the libraries in thirdy_party. They adhere to
>>>>>>> Apache's
>>>>

Re: release: third_party/

[Julian Hyde]

Git sub-modules are useful, I agree. But for a source release, the goal is that 
someone should be able to download the source tar-ball and go:

$ curl -O …/apache-quickstep-x.x-incubating.tar.gz
$ tar xvfz apache-quickstep-x.x-incubating.tar.gz
$ cd apache-quickstep-x.x-incubating/build
$ ./download-thirdparty.sh
$ cmake etc.

I tried to find other Apache projects that use git submodules and see what they 
do for source releases. Not much luck. Maybe someone else can find something.

Also, since you’re relying on the latest googletest, protobuf and re2 your 
release will work today and will break at some point in the future. That’s not 
OK. A release can depend only on releases, not snapshots or live repositories.

Julian



> On Jan 5, 2017, at 11:03 AM, Harshad Deshmukh  wrote:
> 
> Thanks for the review Julian.
> 
> For some of the third party libraries used in Quickstep (e.g. googletest, 
> protobuf and re2) we use the submodules feature of git. For such libraries, 
> the developer has to initialize the submodule only once, which pulls code 
> from the third party repo to the Quickstep third party directory.
> 
> I don't know of a centralized repo for C++ projects. Does the git submodule 
> method sound similar to the maven central approach you mentioned?
> 
> On 01/05/2017 12:43 PM, Julian Hyde wrote:
>> I took a quick look at third_party and there don’t seem to be any binaries 
>> in there. That’s good. You definitely cannot include binaries in a source 
>> release.
>> 
>> The more you can remove from third_party, the better. It doesn’t have to be 
>> done this release, but the less IP there is to review, the easier for 
>> everyone.
>> 
>> Consider pulling from an external source the first time the developer builds 
>> in a sandbox, then apply patches. The patches will be the only thing checked 
>> in to quickstep. (My expertise is in Java projects, which these days get 
>> their dependencies from a Maven repo such as Maven central; I don’t know 
>> whether there is an equivalent place to pull C and C++ source code. Might be 
>> worth a review of what other C and C++ based Apache projects do for their 
>> third-party dependencies.)
>> 
>> Julian
>> 
>> 
>>> On Jan 5, 2017, at 9:43 AM, Marc Spehlmann  wrote:
>>> 
>>> That seems to be the repo with the LLVM code for implementing IWYU. I think
>>> what we have in our repo is scripts ontop of that library. I'm wondering
>>> where the scripts came from.
>>> 
>>> Thanks,
>>> Marc
>>> 
>>> On Thu, Jan 5, 2017 at 10:50 AM, Harshad Deshmukh 
>>> wrote:
>>> 
>>>> Hi Marc,
>>>> 
>>>> How about this one for IWYU?
>>>> 
>>>> https://github.com/include-what-you-use/include-what-you-use
>>>> /blob/master/LICENSE.TXT
>>>> 
>>>> 
>>>> On 01/05/2017 10:43 AM, Marc Spehlmann wrote:
>>>> 
>>>>> I double checked the libraries in thirdy_party. They adhere to Apache's
>>>>> 3rd
>>>>> party requirement as they are all apache 2 or opensourced by Google. The
>>>>> only issue I saw was that IWYU has no documentation. Anyone know of its
>>>>> source?
>>>>> 
>>>>> Library
>>>>> 
>>>>> Ver
>>>>> 
>>>>> License
>>>>> 
>>>>> Notes
>>>>> 
>>>>> benchmark
>>>>> 
>>>>> Apache 2.0
>>>>> 
>>>>> cpplint
>>>>> 
>>>>> Google
>>>>> 
>>>>> Header states that reuse is unconditional so long as the copyright header
>>>>> stays intact.
>>>>> 
>>>>> Farmhash
>>>>> 
>>>>> Google
>>>>> 
>>>>> No restrictions so long as COPYING file is preserved. See COPYING
>>>>> 
>>>>> gflags
>>>>> 
>>>>> Google
>>>>> 
>>>>> No restrictions so long as COPYING file is preserved. See COPYING
>>>>> 
>>>>> glog
>>>>> 
>>>>> Google
>>>>> 
>>>>> No restrictions so long as COPYING file is preserved. See COPYING
>>>>> 
>>>>> gtest
>>>>> 
>>>>> Google
>>>>> 
>>>>> No restrictions so long as COPYING file is preserved. See COPYING in
>>>>> subprojects.
>>>>> 
>>>>> gperftools
>>>>> 
>>>>> Google
>>>>> 
>>>>> No restrictions so long as COPYING file is preserved.
>>>>> 
>>>>> iwyu
>>>>> 
>>>>> 
>>>>> No license present
>>>>> 
>>>>> linenoise
>>>>> 
>>>>> Google
>>>>> 
>>>>> No restrictions so long as LICENSE file is preserved.
>>>>> 
>>>>> protobuf
>>>>> 
>>>>> Google
>>>>> 
>>>>> No restrictions so long as LICENSE file is preserved.
>>>>> 
>>>>> RE2
>>>>> 
>>>>> Google
>>>>> 
>>>>> No restrictions so long as LICENSE file is preserved.
>>>>> 
>>>>> tmb
>>>>> 
>>>>> Apache 2.0
>>>>> 
>>>>> README: TMB is part of the Quickstep project (copyright Pivotal Software,
>>>>> Inc.) and is distributed under the same license terms.
>>>>> 
>>>>> 
>>>> --
>>>> Thanks,
>>>> Harshad
>>>> 
>>>> 
> 
> -- 
> Thanks,
> Harshad
> 

Re: release: third_party/

[Julian Hyde]

I took a quick look at third_party and there don’t seem to be any binaries in 
there. That’s good. You definitely cannot include binaries in a source release.

The more you can remove from third_party, the better. It doesn’t have to be 
done this release, but the less IP there is to review, the easier for everyone.

Consider pulling from an external source the first time the developer builds in 
a sandbox, then apply patches. The patches will be the only thing checked in to 
quickstep. (My expertise is in Java projects, which these days get their 
dependencies from a Maven repo such as Maven central; I don’t know whether 
there is an equivalent place to pull C and C++ source code. Might be worth a 
review of what other C and C++ based Apache projects do for their third-party 
dependencies.)

Julian


> On Jan 5, 2017, at 9:43 AM, Marc Spehlmann  wrote:
> 
> That seems to be the repo with the LLVM code for implementing IWYU. I think
> what we have in our repo is scripts ontop of that library. I'm wondering
> where the scripts came from.
> 
> Thanks,
> Marc
> 
> On Thu, Jan 5, 2017 at 10:50 AM, Harshad Deshmukh 
> wrote:
> 
>> Hi Marc,
>> 
>> How about this one for IWYU?
>> 
>> https://github.com/include-what-you-use/include-what-you-use
>> /blob/master/LICENSE.TXT
>> 
>> 
>> On 01/05/2017 10:43 AM, Marc Spehlmann wrote:
>> 
>>> I double checked the libraries in thirdy_party. They adhere to Apache's
>>> 3rd
>>> party requirement as they are all apache 2 or opensourced by Google. The
>>> only issue I saw was that IWYU has no documentation. Anyone know of its
>>> source?
>>> 
>>> Library
>>> 
>>> Ver
>>> 
>>> License
>>> 
>>> Notes
>>> 
>>> benchmark
>>> 
>>> Apache 2.0
>>> 
>>> cpplint
>>> 
>>> Google
>>> 
>>> Header states that reuse is unconditional so long as the copyright header
>>> stays intact.
>>> 
>>> Farmhash
>>> 
>>> Google
>>> 
>>> No restrictions so long as COPYING file is preserved. See COPYING
>>> 
>>> gflags
>>> 
>>> Google
>>> 
>>> No restrictions so long as COPYING file is preserved. See COPYING
>>> 
>>> glog
>>> 
>>> Google
>>> 
>>> No restrictions so long as COPYING file is preserved. See COPYING
>>> 
>>> gtest
>>> 
>>> Google
>>> 
>>> No restrictions so long as COPYING file is preserved. See COPYING in
>>> subprojects.
>>> 
>>> gperftools
>>> 
>>> Google
>>> 
>>> No restrictions so long as COPYING file is preserved.
>>> 
>>> iwyu
>>> 
>>> 
>>> No license present
>>> 
>>> linenoise
>>> 
>>> Google
>>> 
>>> No restrictions so long as LICENSE file is preserved.
>>> 
>>> protobuf
>>> 
>>> Google
>>> 
>>> No restrictions so long as LICENSE file is preserved.
>>> 
>>> RE2
>>> 
>>> Google
>>> 
>>> No restrictions so long as LICENSE file is preserved.
>>> 
>>> tmb
>>> 
>>> Apache 2.0
>>> 
>>> README: TMB is part of the Quickstep project (copyright Pivotal Software,
>>> Inc.) and is distributed under the same license terms.
>>> 
>>> 
>> --
>> Thanks,
>> Harshad
>> 
>> 

Re: blog

[Julian Hyde]

Correct. The site (and the publishing process) don't do anything clever.

On Tue, Dec 13, 2016 at 8:39 AM, Marc Spehlmann  wrote:
> Whoops, looks like the content was pushed OK, but the mechanism which is
> supposed to trigger Jekyll compilation was not tripped- we just see a
> directory listing when going to http://quickstep.apache.org/.
>
> Possibly the automatic jekyll publishing isn't built into this framework.
> The instructions for https://github.com/apache/calcite/tree/master/site
> suggest that the site must be compiled locally and then pushed into the
> pubsub svn repo.
>
> If that's the case, then maybe we will have to compile the jekyll files
> locally and push them along with the markdown/config/scss/etc
>
> On Tue, Dec 13, 2016 at 10:10 AM, Marc Spehlmann 
> wrote:
>
>> Harshad pointed out the directory is
>> https://git-wip-us.apache.org/repos/asf?p=incubator-quickstep-site.git
>>
>> He found it by modifying the address found in
>> https://cwiki.apache.org/confluence/display/QUICKSTEP/
>> Workflow+For+Committers
>>
>> On Tue, Dec 13, 2016 at 10:02 AM, Marc Spehlmann 
>> wrote:
>>
>>> Thanks for looking into that! I actually took the majority of the written
>>> content from the old website and converted it into markdown to create the
>>> content for the new site, so I think we can keep the structure as Jekyll
>>> has automatically made it. Once we get some more posts, we might want to
>>> move to a separate /blog directory for the posts and have it paginate the
>>> blog index- that's not too hard to do, but unneeded right now.
>>>
>>> One question about the quickstep-site repo...
>>>
>>> Any idea how to get access? Or will I need to submit a pull request?
>>>
>>> cramja@wifi-780 ~/workspace/incubator-quickstep-site $ git remote -v
>>> origin https://github.com/cramja/incubator-quickstep-site.git (fetch)
>>> origin https://github.com/cramja/incubator-quickstep-site.git (push)
>>> source https://github.com/apache/incubator-quickstep-site (fetch)
>>> source https://github.com/apache/incubator-quickstep-site (push)
>>> cramja@wifi-780 ~/workspace/incubator-quickstep-site $ git push source
>>> remote: Permission to apache/incubator-quickstep-site.git denied to
>>> cramja.
>>> fatal: unable to access 'https://github.com/apache/inc
>>> ubator-quickstep-site/': The requested URL returned error: 403
>>>
>>> On Mon, Dec 12, 2016 at 5:24 PM, Roman Shaposhnik 
>>> wrote:
>>>
>>>> Yes. But note you have to push to a branch called asf-site.
>>>>
>>>> Thanks,
>>>> Roman.
>>>>
>>>> On Mon, Dec 12, 2016 at 1:14 PM, Julian Hyde  wrote:
>>>> > INFRA tell me that Quickstep is already using gitpubsub. So, if you
>>>> push to https://github.com/apache/incubator-quickstep-site <
>>>> https://github.com/apache/incubator-quickstep-site> it will
>>>> automatically appear at http://quickstep.apache.org/ <
>>>> http://quickstep.apache.org/>.
>>>> >
>>>> > I think you should consider merging the content you just created into
>>>> that site (maybe under http://quickstep.apache.org/blog <
>>>> http://quickstep.apache.org/blog> ?), and them turn off apache.github.io.
>>>> I can help with the Jekyll if you can’t figure it out.
>>>> >
>>>> > Julian
>>>> >
>>>> >
>>>> >
>>>> >> On Dec 12, 2016, at 10:58 AM, Julian Hyde  wrote:
>>>> >>
>>>> >> I got part way through the process and logged
>>>> https://issues.apache.org/jira/browse/INFRA-13079 <
>>>> https://issues.apache.org/jira/browse/INFRA-13079> for the rest. Please
>>>> watch that case if you want to be updated.
>>>> >>
>>>> >>> On Dec 12, 2016, at 10:38 AM, Julian Hyde >>> jh...@apache.org>> wrote:
>>>> >>>
>>>> >>> The SVN URL should be https://svn.apache.org/repos/a
>>>> sf/incubator/quickstep/site/ <https://svn.apache.org/repos/
>>>> asf/incubator/quickstep/site/> (see for instance
>>>> https://svn.apache.org/repos/asf/incubator/tephra/site/ <
>>>> https://svn.apache.org/repos/asf/incubator/tephra/site/>) but doesn’t
>>>> exist currently.
>>>> >>>
>>>> >>> Per http://incubator.apache.org/guides/mentor.html#Set+Up+SVN+Re
>

Re: blog

[Julian Hyde]

INFRA tell me that Quickstep is already using gitpubsub. So, if you push to 
https://github.com/apache/incubator-quickstep-site 
<https://github.com/apache/incubator-quickstep-site> it will automatically 
appear at http://quickstep.apache.org/ <http://quickstep.apache.org/>.

I think you should consider merging the content you just created into that site 
(maybe under http://quickstep.apache.org/blog 
<http://quickstep.apache.org/blog> ?), and them turn off apache.github.io. I 
can help with the Jekyll if you can’t figure it out.

Julian



> On Dec 12, 2016, at 10:58 AM, Julian Hyde  wrote:
> 
> I got part way through the process and logged 
> https://issues.apache.org/jira/browse/INFRA-13079 
> <https://issues.apache.org/jira/browse/INFRA-13079> for the rest. Please 
> watch that case if you want to be updated.
> 
>> On Dec 12, 2016, at 10:38 AM, Julian Hyde > <mailto:jh...@apache.org>> wrote:
>> 
>> The SVN URL should be 
>> https://svn.apache.org/repos/asf/incubator/quickstep/site/ 
>> <https://svn.apache.org/repos/asf/incubator/quickstep/site/> (see for 
>> instance https://svn.apache.org/repos/asf/incubator/tephra/site/ 
>> <https://svn.apache.org/repos/asf/incubator/tephra/site/>) but doesn’t exist 
>> currently.
>> 
>> Per http://incubator.apache.org/guides/mentor.html#Set+Up+SVN+Repository 
>> <http://incubator.apache.org/guides/mentor.html#Set+Up+SVN+Repository> I 
>> think this means I need to create the repository and authorize committers. 
>> (Don’t worry, Quickstep will continue to use git for its source code, and 
>> for the source of the web site; SVN is just for the generated web site.)
>> 
>> And I think we need to tell INFRA to enable svnpubsub. I don’t recall how to 
>> do that, and I can’t find online doc. Any mentors know?
>> 
>> Julian
>> 
>> 
>>> On Dec 12, 2016, at 9:56 AM, Marc Spehlmann >> <mailto:spehl.apa...@gmail.com>> wrote:
>>> 
>>> SVN pubsub sounds simple enough... but I cannot seem to find the url for
>>> quickstep.
>>> 
>>> I tried
>>> svn co https://svn.apache.org/repos/asf/quickstep 
>>> <https://svn.apache.org/repos/asf/quickstep> target
>>> svn co https://svn.apache.org/repos/asf/quickstep 
>>> <https://svn.apache.org/repos/asf/quickstep> target
>>> svn co https://svn.apache.org/repos/asf/incubator-quickstep 
>>> <https://svn.apache.org/repos/asf/incubator-quickstep> target
>>> svn co https://svn.apache.org/repos/asf/incubator-quickstep/site 
>>> <https://svn.apache.org/repos/asf/incubator-quickstep/site> target
>>> __
>>> svn: E17: URL 'https://svn.apache.org/[ <https://svn.apache.org/[>...]' 
>>> doesn't exist
>>> 
>>> On Mon, Dec 12, 2016 at 9:41 AM, Jignesh Patel >> <mailto:jmp.quicks...@gmail.com>>
>>> wrote:
>>> 
>>>> Nice. Thanks Marc!
>>>> 
>>>> On 12/11/16, 11:54 AM, "Marc Spehlmann" >>> <mailto:spehl.apa...@gmail.com>> wrote:
>>>> 
>>>>Hey, we have a jekyll blog and a first blog article now! It can be
>>>> viewed
>>>> 
>>>>here http://apache.github.io/incubator-quickstep/ 
>>>> <http://apache.github.io/incubator-quickstep/>
>>>> 
>>>>It's a page automatically generated by github. We can probably change
>>>> the
>>>>URL somehow, not sure off hand though.
>>>> 
>>>>Editting instructions are included in the readme here
>>>> 
>>>>https://github.com/apache/incubator-quickstep/tree/gh-pages 
>>>> <https://github.com/apache/incubator-quickstep/tree/gh-pages>
>>>> 
>>>>If anyone wants to touch up the css or layout, have at it. I'm no web
>>>>design expert, I rely on the pre-built themes.
>>>> 
>>>>Anyone can write a post, all you need to know is markdown.
>>>> 
>>>>Happy blogging!
>>>> 
>>>> 
>>>> 
>>>> 
>> 
> 

Re: blog

[Julian Hyde]

I got part way through the process and logged 
https://issues.apache.org/jira/browse/INFRA-13079 
<https://issues.apache.org/jira/browse/INFRA-13079> for the rest. Please watch 
that case if you want to be updated.

> On Dec 12, 2016, at 10:38 AM, Julian Hyde  wrote:
> 
> The SVN URL should be 
> https://svn.apache.org/repos/asf/incubator/quickstep/site/ 
> <https://svn.apache.org/repos/asf/incubator/quickstep/site/> (see for 
> instance https://svn.apache.org/repos/asf/incubator/tephra/site/ 
> <https://svn.apache.org/repos/asf/incubator/tephra/site/>) but doesn’t exist 
> currently.
> 
> Per http://incubator.apache.org/guides/mentor.html#Set+Up+SVN+Repository 
> <http://incubator.apache.org/guides/mentor.html#Set+Up+SVN+Repository> I 
> think this means I need to create the repository and authorize committers. 
> (Don’t worry, Quickstep will continue to use git for its source code, and for 
> the source of the web site; SVN is just for the generated web site.)
> 
> And I think we need to tell INFRA to enable svnpubsub. I don’t recall how to 
> do that, and I can’t find online doc. Any mentors know?
> 
> Julian
> 
> 
>> On Dec 12, 2016, at 9:56 AM, Marc Spehlmann > <mailto:spehl.apa...@gmail.com>> wrote:
>> 
>> SVN pubsub sounds simple enough... but I cannot seem to find the url for
>> quickstep.
>> 
>> I tried
>> svn co https://svn.apache.org/repos/asf/quickstep 
>> <https://svn.apache.org/repos/asf/quickstep> target
>> svn co https://svn.apache.org/repos/asf/quickstep 
>> <https://svn.apache.org/repos/asf/quickstep> target
>> svn co https://svn.apache.org/repos/asf/incubator-quickstep 
>> <https://svn.apache.org/repos/asf/incubator-quickstep> target
>> svn co https://svn.apache.org/repos/asf/incubator-quickstep/site 
>> <https://svn.apache.org/repos/asf/incubator-quickstep/site> target
>> __
>> svn: E17: URL 'https://svn.apache.org/[ <https://svn.apache.org/[>...]' 
>> doesn't exist
>> 
>> On Mon, Dec 12, 2016 at 9:41 AM, Jignesh Patel > <mailto:jmp.quicks...@gmail.com>>
>> wrote:
>> 
>>> Nice. Thanks Marc!
>>> 
>>> On 12/11/16, 11:54 AM, "Marc Spehlmann" >> <mailto:spehl.apa...@gmail.com>> wrote:
>>> 
>>>Hey, we have a jekyll blog and a first blog article now! It can be
>>> viewed
>>> 
>>>here http://apache.github.io/incubator-quickstep/ 
>>> <http://apache.github.io/incubator-quickstep/>
>>> 
>>>It's a page automatically generated by github. We can probably change
>>> the
>>>URL somehow, not sure off hand though.
>>> 
>>>Editting instructions are included in the readme here
>>> 
>>>https://github.com/apache/incubator-quickstep/tree/gh-pages 
>>> <https://github.com/apache/incubator-quickstep/tree/gh-pages>
>>> 
>>>If anyone wants to touch up the css or layout, have at it. I'm no web
>>>design expert, I rely on the pre-built themes.
>>> 
>>>Anyone can write a post, all you need to know is markdown.
>>> 
>>>Happy blogging!
>>> 
>>> 
>>> 
>>> 
> 

Re: blog

[Julian Hyde]

The SVN URL should be 
https://svn.apache.org/repos/asf/incubator/quickstep/site/ 
 (see for instance 
https://svn.apache.org/repos/asf/incubator/tephra/site/ 
) but doesn’t exist 
currently.

Per http://incubator.apache.org/guides/mentor.html#Set+Up+SVN+Repository 
 I think 
this means I need to create the repository and authorize committers. (Don’t 
worry, Quickstep will continue to use git for its source code, and for the 
source of the web site; SVN is just for the generated web site.)

And I think we need to tell INFRA to enable svnpubsub. I don’t recall how to do 
that, and I can’t find online doc. Any mentors know?

Julian


> On Dec 12, 2016, at 9:56 AM, Marc Spehlmann  wrote:
> 
> SVN pubsub sounds simple enough... but I cannot seem to find the url for
> quickstep.
> 
> I tried
> svn co https://svn.apache.org/repos/asf/quickstep target
> svn co https://svn.apache.org/repos/asf/quickstep target
> svn co https://svn.apache.org/repos/asf/incubator-quickstep target
> svn co https://svn.apache.org/repos/asf/incubator-quickstep/site target
> __
> svn: E17: URL 'https://svn.apache.org/[...]' doesn't exist
> 
> On Mon, Dec 12, 2016 at 9:41 AM, Jignesh Patel 
> wrote:
> 
>> Nice. Thanks Marc!
>> 
>> On 12/11/16, 11:54 AM, "Marc Spehlmann"  wrote:
>> 
>>Hey, we have a jekyll blog and a first blog article now! It can be
>> viewed
>> 
>>here http://apache.github.io/incubator-quickstep/
>> 
>>It's a page automatically generated by github. We can probably change
>> the
>>URL somehow, not sure off hand though.
>> 
>>Editting instructions are included in the readme here
>> 
>>https://github.com/apache/incubator-quickstep/tree/gh-pages
>> 
>>If anyone wants to touch up the css or layout, have at it. I'm no web
>>design expert, I rely on the pre-built themes.
>> 
>>Anyone can write a post, all you need to know is markdown.
>> 
>>Happy blogging!
>> 
>> 
>> 
>> 

Re: blog

[Julian Hyde]

I don’t believe that Apache infra allows projects to change DNS. So you need to 
move your content onto quickstep.apache.org <http://quickstep.apache.org/>, not 
move the DNS record to point to your content. That isn’t too hard.

There are a few options[1], but I’m most familiar with svnpubsub and would 
recommend it, Basically you commit the contents of your web site into a 
subversion repository, and it immediately appears on Apache. Very 
straightforward.

It’s entirely up to you how you author the contents of the site. You can do it 
manually, or use a maven site generator, or write your own generator. As I 
said, at Calcite we use Jekyll, so the effect is very similar to GitHub pages, 
and as a bonus it handles large generated content like javadoc or doxygen 
better.

There is an Apache project which provides a template[2]. Give it a try.

Julian

[1] https://www.apache.org/dev/project-site.html 
<https://www.apache.org/dev/project-site.html>

[2] https://github.com/apache/apache-website-template 
<https://github.com/apache/apache-website-template>

> On Dec 11, 2016, at 6:39 PM, Marc Spehlmann  wrote:
> 
> Hi Julian, I'm sure that we will be!
> 
> And in an effort to consolidate the number of quickstep pages, I'm
> wondering if you'd know where the switch is that tells the DNS servers
> where to point traffic to quickstep.apache.org 
> <http://quickstep.apache.org/>? Right now I think it's
> pointing to this (https://github.com/apache/incubator-quickstep-site 
> <https://github.com/apache/incubator-quickstep-site>)
> github repo, which is obsolete now that all the info has been copied over
> to quickstep's gh-pages branch.
> 
> Best,
> Marc
> 
> On Sun, Dec 11, 2016 at 4:54 PM, Julian Hyde  <mailto:jh...@apache.org>> wrote:
> 
>> By the way, I think for now publishing to GitHub.io is just fine. The blog
>> post is great — content like this is great outreach.
>> 
>> Speaking of outreach, the ApacheQuickstep twitter account has been very
>> quiet. How about tweeting a link to the blog post? I think you could find a
>> couple of newsworthy events every week to tweet about.
>> 
>> Julian
>> 
>> 
>>> On Dec 11, 2016, at 2:40 PM, Julian Hyde  wrote:
>>> 
>>> I’m a fan of Jekyll too. Note that you can use the same markup to write
>> pages and then deploy them to Apache. In fact Calcite’s web site does
>> exactly that[1]. You need to install Jekyll but that isn’t too difficult.
>>> 
>>> Julian
>>> 
>>> [1] https://github.com/apache/calcite/blob/master/site/README.md <
>> https://github.com/apache/calcite/blob/master/site/README.md 
>> <https://github.com/apache/calcite/blob/master/site/README.md>>
>>> 
>>>> On Dec 11, 2016, at 12:36 PM, Hakan Memisoglu <
>> hakanmemiso...@apache.org <mailto:hakanmemiso...@apache.org> 
>> <mailto:hakanmemiso...@apache.org <mailto:hakanmemiso...@apache.org>>> wrote:
>>>> 
>>>> Thanks Marc for the effort!
>>>> 
>>>> 
>>>> On 12/11/2016 11:54 AM, Marc Spehlmann wrote:
>>>>> Hey, we have a jekyll blog and a first blog article now! It can be
>> viewed
>>>>> 
>>>>> here http://apache.github.io/incubator-quickstep/ 
>>>>> <http://apache.github.io/incubator-quickstep/> <
>> http://apache.github.io/incubator-quickstep/ 
>> <http://apache.github.io/incubator-quickstep/>>
>>>>> 
>>>>> It's a page automatically generated by github. We can probably change
>> the
>>>>> URL somehow, not sure off hand though.
>>>>> 
>>>>> Editting instructions are included in the readme here
>>>>> 
>>>>> https://github.com/apache/incubator-quickstep/tree/gh-pages 
>>>>> <https://github.com/apache/incubator-quickstep/tree/gh-pages> <
>> https://github.com/apache/incubator-quickstep/tree/gh-pages 
>> <https://github.com/apache/incubator-quickstep/tree/gh-pages>>
>>>>> 
>>>>> If anyone wants to touch up the css or layout, have at it. I'm no web
>>>>> design expert, I rely on the pre-built themes.
>>>>> 
>>>>> Anyone can write a post, all you need to know is markdown.
>>>>> 
>>>>> Happy blogging!

Re: blog

[Julian Hyde]

By the way, I think for now publishing to GitHub.io is just fine. The blog post 
is great — content like this is great outreach.

Speaking of outreach, the ApacheQuickstep twitter account has been very quiet. 
How about tweeting a link to the blog post? I think you could find a couple of 
newsworthy events every week to tweet about.

Julian


> On Dec 11, 2016, at 2:40 PM, Julian Hyde  wrote:
> 
> I’m a fan of Jekyll too. Note that you can use the same markup to write pages 
> and then deploy them to Apache. In fact Calcite’s web site does exactly 
> that[1]. You need to install Jekyll but that isn’t too difficult.
> 
> Julian
> 
> [1] https://github.com/apache/calcite/blob/master/site/README.md 
> <https://github.com/apache/calcite/blob/master/site/README.md>
> 
>> On Dec 11, 2016, at 12:36 PM, Hakan Memisoglu > <mailto:hakanmemiso...@apache.org>> wrote:
>> 
>> Thanks Marc for the effort!
>> 
>> 
>> On 12/11/2016 11:54 AM, Marc Spehlmann wrote:
>>> Hey, we have a jekyll blog and a first blog article now! It can be viewed
>>> 
>>> here http://apache.github.io/incubator-quickstep/ 
>>> <http://apache.github.io/incubator-quickstep/>
>>> 
>>> It's a page automatically generated by github. We can probably change the
>>> URL somehow, not sure off hand though.
>>> 
>>> Editting instructions are included in the readme here
>>> 
>>> https://github.com/apache/incubator-quickstep/tree/gh-pages 
>>> <https://github.com/apache/incubator-quickstep/tree/gh-pages>
>>> 
>>> If anyone wants to touch up the css or layout, have at it. I'm no web
>>> design expert, I rely on the pre-built themes.
>>> 
>>> Anyone can write a post, all you need to know is markdown.
>>> 
>>> Happy blogging!
>>> 
>> 
> 

Re: blog

[Julian Hyde]

I’m a fan of Jekyll too. Note that you can use the same markup to write pages 
and then deploy them to Apache. In fact Calcite’s web site does exactly 
that[1]. You need to install Jekyll but that isn’t too difficult.

Julian

[1] https://github.com/apache/calcite/blob/master/site/README.md 


> On Dec 11, 2016, at 12:36 PM, Hakan Memisoglu  
> wrote:
> 
> Thanks Marc for the effort!
> 
> 
> On 12/11/2016 11:54 AM, Marc Spehlmann wrote:
>> Hey, we have a jekyll blog and a first blog article now! It can be viewed
>> 
>> here http://apache.github.io/incubator-quickstep/
>> 
>> It's a page automatically generated by github. We can probably change the
>> URL somehow, not sure off hand though.
>> 
>> Editting instructions are included in the readme here
>> 
>> https://github.com/apache/incubator-quickstep/tree/gh-pages
>> 
>> If anyone wants to touch up the css or layout, have at it. I'm no web
>> design expert, I rely on the pre-built themes.
>> 
>> Anyone can write a post, all you need to know is markdown.
>> 
>> Happy blogging!
>> 
> 

Re: Podling Report Reminder - December 2016

[Julian Hyde]

Thanks for filing in a timely fashion, Jignesh. It is accurate (though of 
course I wish there had been a release and some talks/blog posts by now) and I 
have signed off.

Julian

> On Nov 29, 2016, at 4:30 AM, Jignesh Patel  wrote:
> 
> I have entered an initial podling report. Please let this group know if you 
> have comments on the initial report. 
> 
> Cheers,
> Jignesh 
> 
> On 11/28/16, 6:06 AM, "johndam...@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, 21 December 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, December 07).
> 
>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:
> 
>https://wiki.apache.org/incubator/December2016
> 
>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: Quickstep Feedback

[Julian Hyde]

Yes, JIRA is the place to log issues. I believe that anyone (not just 
committers) can log issues at https://issues.apache.org/jira/browse/QUICKSTEP 
.

Julian


> On Nov 14, 2016, at 12:54 PM, HAKAN MEMISOGLU  wrote:
> 
> 
> Hi Quickstep Devs,
> 
> 
> This is a feedback mail for Quickstep. The users cannot submit an issue 
> request for Quickstep on Github.
> 
> So I have couple of questions.
> 
> - Is Apache JIRA the only place where we can submit issues?
> 
> - How can non-Apache contributors access the JIRA page?
> 
> 
> 
> From: x
> Sent: Wednesday, November 9, 2016 2:58 PM
> To: HAKAN MEMISOGLU
> Cc: x
> Subject: Quickstep Feedback
> 
> 
> Hello Hakan,
> 
> 
> As discussed today, below are the missing quickstep features and bugs we 
> encountered with respect to https://github.com/apache/incubator-quickstep
> 
> [https://avatars1.githubusercontent.com/u/47359?v=3&s=400]
> 
> GitHub - apache/incubator-quickstep: Mirror of Apache 
> ...
> github.com
> README.md Apache Quickstep (Incubating) What is Quickstep? Apache Quickstep 
> is high-performance database engine designed to exploit the full potential of 
> hardware ...
> 
> [Adding it here as we the repo does not have settings to accept github issues]
> 
>  *   Missing - Union operator
>  *   Missing - Intersect operator
>  *   Missing - Distinct operator
>  *   Missing - Drop index
>  *   Missing - Create Simple index [currently it expects bloomfilter / sma / 
> csbtree]
>  *   Missing - Boolean data type
>  *   Bug - describe table command \dt does not seem to support table names 
> with underscore
>  *   Bug -  limit query result returns more than expected number of rows, 
> also order by does not produce correct ordering
> 
> Thanks,
> 
> 

Re: Delay in showing a branch on GitHub mirror

[Julian Hyde]

What do other folks think? There's nothing in Apache policy that prevents you 
from taking pull requests from the Apache account, so that can definitely be an 
option, if you want. What do you think works best for you and the community?

Julian

PS If you agree, Apache custom is to reply "+1". Silence doesn't indicate 
assent, it indicates apathy :)

> On Nov 5, 2016, at 12:15 PM, Harshad Deshmukh  wrote:
> 
> Hi Julian,
> 
> No, there's no such policy. I think majority of the contributors use their 
> individual GitHub accounts and also initiate pull request from the same. Some 
> of us started with the practice of using Apache repo and continue to do so. 
> If using individual GitHub accounts is preferred we all can switch to that 
> mode.
> 
>> On 11/05/2016 12:45 PM, Julian Hyde wrote:
>> Regarding my other point: does Quickstep have a policy that pull requests 
>> should, or must, come from the Apache github account? If so, can you see how 
>> that would tend to discourage people from joining the community? Because 
>> only committers are able to push to Apache.
>> 
>> Several projects use "feature branches", where multiple developers need to 
>> collaborate over a long period, and of course a branch or tag per release, 
>> but other than that, branches in the Apache repo are quite unusual.
>> 
>> Julian
>> 
>>> On Nov 4, 2016, at 11:25 AM, Harshad Deshmukh  wrote:
>>> 
>>> Thanks Julian, your suggestion worked!
>>> 
>>> 
>>>> On 11/04/2016 11:29 AM, Julian Hyde wrote:
>>>> If I recall, there is an issue with Apache-github integration that a 
>>>> branch only shows up when you make a commit on it. So maybe make a trivial 
>>>> commit.
>>>> 
>>>> That said, you don’t need to push a branch to Apache in order to make a 
>>>> pull request. You can make a pull request from your own personal GitHub 
>>>> fork. That’s usually the right thing to do.
>>>> 
>>>> Julian
>>>> 
>>>>> On Nov 4, 2016, at 8:42 AM, Harshad Deshmukh  wrote:
>>>>> 
>>>>> Hello,
>>>>> 
>>>>> I pushed a branch (named auto-worker-pinning) to the apache repository 11 
>>>>> hours ago. That branch is still not showing up on the GitHub mirror. Has 
>>>>> any one else experienced similar issue? Without the branch showing up on 
>>>>> GitHub, I can't create a pull request for it.
>>>>> 
>>>>> -- 
>>>>> 
>>>>> Thanks,
>>>>> Harshad
>>>>> 
>>> -- 
>>> Thanks,
>>> Harshad
>>> 
> 
> -- 
> Thanks,
> Harshad
> 

Re: Delay in showing a branch on GitHub mirror

[Julian Hyde]

Regarding my other point: does Quickstep have a policy that pull requests 
should, or must, come from the Apache github account? If so, can you see how 
that would tend to discourage people from joining the community? Because only 
committers are able to push to Apache. 

Several projects use "feature branches", where multiple developers need to 
collaborate over a long period, and of course a branch or tag per release, but 
other than that, branches in the Apache repo are quite unusual. 

Julian

> On Nov 4, 2016, at 11:25 AM, Harshad Deshmukh  wrote:
> 
> Thanks Julian, your suggestion worked!
> 
> 
>> On 11/04/2016 11:29 AM, Julian Hyde wrote:
>> If I recall, there is an issue with Apache-github integration that a branch 
>> only shows up when you make a commit on it. So maybe make a trivial commit.
>> 
>> That said, you don’t need to push a branch to Apache in order to make a pull 
>> request. You can make a pull request from your own personal GitHub fork. 
>> That’s usually the right thing to do.
>> 
>> Julian
>> 
>>> On Nov 4, 2016, at 8:42 AM, Harshad Deshmukh  wrote:
>>> 
>>> Hello,
>>> 
>>> I pushed a branch (named auto-worker-pinning) to the apache repository 11 
>>> hours ago. That branch is still not showing up on the GitHub mirror. Has 
>>> any one else experienced similar issue? Without the branch showing up on 
>>> GitHub, I can't create a pull request for it.
>>> 
>>> -- 
>>> 
>>> Thanks,
>>> Harshad
>>> 
> 
> -- 
> Thanks,
> Harshad
> 

Re: Delay in showing a branch on GitHub mirror

[Julian Hyde]

If I recall, there is an issue with Apache-github integration that a branch 
only shows up when you make a commit on it. So maybe make a trivial commit.

That said, you don’t need to push a branch to Apache in order to make a pull 
request. You can make a pull request from your own personal GitHub fork. That’s 
usually the right thing to do. 

Julian

> On Nov 4, 2016, at 8:42 AM, Harshad Deshmukh  wrote:
> 
> Hello,
> 
> I pushed a branch (named auto-worker-pinning) to the apache repository 11 
> hours ago. That branch is still not showing up on the GitHub mirror. Has any 
> one else experienced similar issue? Without the branch showing up on GitHub, 
> I can't create a pull request for it.
> 
> -- 
> 
> Thanks,
> Harshad
> 

Re: Accidental Push to Master

[Julian Hyde]

Yes, ASF Git is not Github. But the master branch is “protected”, in the sense 
that if you do a force-push, it will send an email to the commits list noting 
that it was a force push. (At least, the Calcite git repo works this way. I 
think this is standard behavior. I might be mistaken.)

Here’s a tip I find useful: I store the username and password of my GitHub 
fork, but I don’t store the username and password of the Apache remote. When I 
push to Apache (force or otherwise), git prompts me for username and password, 
and that makes me think twice before pressing return.

Julian




> On Sep 28, 2016, at 1:36 PM, J Patel  wrote:
> 
> I don't think so :-( ASF, I think, is plain old Git.
> 
> On Friday, September 23, 2016, Navneet Potti  wrote:
> 
>> Github has a new feature called protected branches <
>> https://help.github.com/articles/about-protected-branches/> that
>> automatically requires a PR acceptance before code can be merged into a
>> branch. Is there a similar functionality for ASF repo?
>> 
>> 
>> 
>>> On Sep 23, 2016, at 15:49, Hakan Memisoglu > > wrote:
>>> 
>>> I accidentally pushed my changes to master directly, then I revert the
>> changes with forced push. In original ASF repo, everything seems alright.
>> In Github, the changes have not been reflected yet.
>>> 
>>> Again sorry for the inconvenience.
>>> 
>> 
>> 

Missing report

[Julian Hyde]

Hi everyone,

Quickstep didn’t file a report for the Board meeting this month. Can you please 
be sure to file one next month?

Julian

Re: Mentor concerns

[Julian Hyde]

+1 what Roman said about dev traffic. It seems to me that features come out of 
nowhere and I can only surmise that significant discussion is happening 
back-channel. The dev list should be the “front door” of the project and I 
think that to would-be contributors it looks pretty tightly shut.

Another instance: I tried to kick off a discussion on the dev list about the 
future of the project. IIRC, no one chimed in except Jignesh and mentors. That 
is not what would happen on a project that is being effective in governing 
itself.

Julian


> On Aug 15, 2016, at 5:51 PM, Harshad Deshmukh  wrote:
> 
> Hello Roman and Jignesh,
> 
> The website is updated with the said changes.
> 
> http://quickstep.incubator.apache.org/
> 
> 
> On 08/15/2016 11:20 AM, J Patel wrote:
>> I'm on vacation - can someone take care of the website? Else, I'll do it on
>> Thursday.
>> 
>> I believe we have Jira tickets for all the main features. I'll check when
>> I'm back. Agreed would be good to have Jira tickets for visibility to the
>> community.
>> 
>> On a related note to perhaps clear some misconception: Some of the changes
>> come around when someone sees a problem and is inspired to fix it. I think
>> JQs plan visualization is a good example - he did it over a few days on his
>> own. I love that feature (I think we all do!), and discovered it when the
>> PR showed up. He had a great writeup in his PR (IMHO a good model for all
>> of us). Agreed if that didn't have a Jira ticket would be good to get in
>> the habit of opening one when inspiration strikes for an idea, and close it
>> with the final commit. But please do keep such inspiration driven features
>> going! I think no one wants to stop doing that.
>> 
>> And I very much would love for existing folks to take the lead like JQ did!
>> 
>> 
>> On Sunday, August 14, 2016, Roman Shaposhnik  wrote:
>> 
>>> Hi!
>>> 
>>> Quickstep community is coming along fine, but,
>>> with my mentor hat on, I still have a few concerns:
>>>   1. The Download button needs to be removed from
>>>   the website until there's a first official release
>>> 
>>>   2. Website has to have an Incubator disclaimer:
>>>  http://incubator.apache.org/guides/branding.html#disclaimers
>>> 
>>>3. I see tons of GitHub commits and yet I see pretty much
>>>no dev@ list or JIRA traffic. Why is this code being commited?
>>>Where is it discussed? This all is a mystery to me and I suspect
>>>anybody else who's not on-site with those who commit.
>>> 
>>> I'd like to ask that the community quickly takes care of #1 and #2
>>> and comes up with an explanation for #3
>>> 
>>> Thanks,
>>> Roman.
>>> 
> 
> -- 
> Thanks,
> Harshad
> 

Re: 5 things

[Julian Hyde]

See below, comments on specific points.

> On Aug 3, 2016, at 1:35 PM, J Patel  wrote:
> 
> All: Would love to hear your thoughts on a release. I'd like to propose mid
> to late November, which likely works out best given the semester cadence
> (yeah -- I know we are far skewed in the Committer to that, at least for
> now).

November seems a very long way off. Remember, a release is a good way to 
attract contributors, and does not need to be “perfect” or a big splash in 
terms of marketing.

> In general, it is expected that to maintain
> membership in the Committer group, the developer must be active in the
> project in the preceding 6-month period.

Procedures to allow committers and PMC members to “go emeritus” do exist[1] but 
in my opinion they are solving a non-problem.

> PMC members can commit code directly to the main repository, but are
> generally advised to open a PR and allow another Committer to close the PR.

The role of the PMC (actually PPMC while Quickstep is incubating) is solely 
governance. PPMC members should not have more rights than committers where it 
comes to code. We don’t want to create two tiers of committers.

> A Contributor can become a Committer by getting support from at least two
> existing Committers. It is expected that a Contributor will have
> demonstrated proficiency in understanding and working with the core engine
> to become part of the Committer group.

Per Apache rules committers are appointed by achieving consensus (typically a 
vote) in the PMC[2].


> The PMC meets at least annually. Meetings are announced at least two weeks
> in advance on the project developer list. Any Committer is welcome to
> propose agenda items for the meeting. The PMC chair consults the overall
> PMC to finalize the agenda. The meeting agenda must be finalized two days
> before the meeting and communicated on the project developer list. Agenda
> items can include, but is not limited to, voting for changes to the PMC,
> changes to the Committers group, and changes to the community governance
> document. Only existing PMC members can vote on motions. For a motion to
> carry, a majority of the votes that are cast must be in favor of the
> motion. Ties are broken by the PMC Chair. Proxies are permitted, and must
> be communicated to the PMC Chair prior to the meeting.

Per Apache, the PMC meets continually… via email. I suppose the PMC could have 
an annual meeting, but business such as appointing members does not have to 
wait for that.

Apache has a procedure for appointing members to the PMC[3]. You need to follow 
this.

Jignesh, As I said in a previous email, it’s good that you are thinking about 
governance. But we are going to be at odds until you read & understand the 
existing Apache governance. I think you need to take the time to do this before 
proposing alternatives. The Apache governance is well established and is 
proven. And considerable parts of it are mandatory.

Julian

[1] http://www.apache.org/dev/pmc.html#pmc-removal 


[2] http://www.apache.org/dev/pmc.html#newcommitter 


[3] http://www.apache.org/dev/pmc.html#newpmc 
 

Re: Podling Report Reminder - August 2016

[Julian Hyde]

Today is the deadline for the report. If you miss the deadline, this will be 
the second consecutive month that you have failed to report. The IPMC and Board 
do not appreciate multiple missed reports.

Julian


> On Jul 27, 2016, at 10:18 AM, Julian Hyde  wrote:
> 
> Quickstep missed its report last month, so it is very important to file this 
> month.
> 
> Who is going to write the report?
> 
> Julian
> 
> 
>> On Jul 27, 2016, at 4:47 AM, johndam...@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, 17 August 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, August 03).
>> 
>> 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/August2016
>> 
>> 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: 5 things

[Julian Hyde]

Did you see my reply[1] and Roman’s reply[2] to your message?

I think it’s great that you are thinking about governance, review process, and 
a path for people to become members of the project. But before you invent 
concepts like “core contributor”, are you familiar with the Apache concepts 
such as “committer”?[3]

Since Quickstep is in incubation, your goal must be to understand the Apache 
Way and craft the project’s governance model within that.

Julian

[1] 
http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/201607.mbox/%3C0B87BE6C-93F4-4959-BD9A-D9E89E0A3835%40apache.org%3E
 
<http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/201607.mbox/%3c0b87be6c-93f4-4959-bd9a-d9e89e0a3...@apache.org%3E>
 

[2] 
http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/201607.mbox/%3CCA%2BULb%2BtWAA_c4e-YYAitXfDMAz60Y_XVZMSN4QUPvOgNE7dojA%40mail.gmail.com%3E
 
<http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/201607.mbox/%3cca+ulb+twaa_c4e-yyaitxfdmaz60y_xvzmsn4qupvogne7d...@mail.gmail.com%3E>

[3] http://www.apache.org/foundation/how-it-works.html#roles 
<http://www.apache.org/foundation/how-it-works.html#roles>


> On Aug 3, 2016, at 11:59 AM, J Patel  wrote:
> 
> Hello everyone,
> 
> Since no objections have been raised to the developer community governance
> as outlined below, I'd like to move forward with adopting the version
> below.  *Does anyone know if we need to vote for it? *
> 
> Note: I made a few changes from the previous draft. The key ones are:
> 
> #1: Adding Caleb Welton to the general contributors' list.  (Thanks Caleb
> for your contribution, which has now been merged to the master!).
> 
> #2: Sorted both lists by the last name.
> 
> I'd love to put it on our web page before the end of the week.
> 
> Thanks!
> 
> Cheers,
> Jignesh
> 
> QUICKSTEP DEVELOPER COMMUNITY GOVERNANCE
> 
> Quickstep is a data platform that is written in C++ and uses advanced C++
> techniques including template meta-programming and various abstractions to
> balance high-performance with extensibility. Thus, a good grasp over C++
> concepts is essential for a Quickstep developer.
> 
> 
> 
> Quickstep has a set of *core contributors* who are collectively the
> stewards of the project. In addition, there is a set of *general
> contributors* who contribute individual changes. The initial list of core
> and general contributors is listed below.
> 
> 
> 
> Core contributors can close pull requests, except pull requests that they
> have created (which must be examined and closed by another core
> contributor). Anyone can open a pull request and once a pull request has
> been accepted that committer becomes part of the general contributors
> group.
> 
> 
> 
> A general contributor can become a core contributor by getting support from
> at least two core contributors. It is expected that a general contributor
> will have demonstrated proficiency in understanding and working with the
> core engine to become part of the core contributors group.
> 
> 
> 
> To maintain membership in the core contributors group, the contributor must
> be active in the project in the preceding 6-month period. Membership of the
> core contributors is examined and determined bi-annually by the Apache
> Quickstep PPMC.
> 
> 
> 
> *Core Contributors (as of August 5, 2016:*
> Harshad Deshmukh
> Rogers Jeffrey Leo John
> Hakan Memisoglu
> Jignesh M. Patel
> Navneet Potti
> Saket Saurabh
> Marc Spehlmann
> Zuyu Zhang
> 
> Jianqiao Zhu
> 
> *Core Collaborators (as of August 5, 2016):*
> Shoban Chandrabose
> Craig Chasseur
> Julian Hyde
> Yinan Li
> Rathijit Sen
> Roman Shaposhnik
> Adalbert Gerald Soosai Raj
> Siddharth Suresh
> Caleb Welton
> 
>> Qiang Zeng

Re: Question about using github as the main repo

[Julian Hyde]

This question comes up a lot when it comes to Apache’s github policy. The short 
answer, unfortunately, is no.

In order to ensure the integrity of the IP, Apache needs to host the source 
code through its entire lifecycle. When a committer pushes to 
git-wip-us.apache.org, Apache is able to record who is doing the pushing. The 
commit(s) being pushed might be by a different person, but the committer is 
vouching for them (checking IP integrity is one of the core responsibilities of 
a committer).

Those records are available for inspection if the provenance of the code were 
ever questioned.

When someone creates a pull request against github.com/apache/foo, this serves 
as a record that the contributor intended to make the contribution under ASL.

I know it’s inconvenient to close PRs. (You’ve discovered the trick of adding a 
‘Close #NNN’ comment, I assume.) There’s actually quite a lot going on, in a 
legal sense, when a committer accepts code contribution to an Apache project, 
so I think it’s OK that there is a little extra overhead.

By the way, it’s up to each project whether they do CTR (commit-then-review) or 
RTC (review-then-commit), but in Calcite we allow committers to commit code 
that have authored themselves. (They generally ask for a review first if it is 
non-trivial, and they always make sure that the test suite passes first.) So in 
that case, no pull request is required. Quickstep should decide whether they 
require pull requests for every commit, and how code should be reviewed.

Julian



> On Jul 28, 2016, at 1:40 PM, Jignesh Patel  wrote:
> 
> Currently we use the git-wip-us.apache.org as the main repo for Quickstep. 
> This works, but has limitations compared to doing development on github. One 
> key limitation is closing PRs on github is far easier.
> 
> 
> 
> Question: Is it possible for us to use github instead of ASF git server to 
> host the main code base? I know we have a mirror on github, but is it 
> possible to also have the main repo on github?
> 
> 
> 
> Thanks!
> 
> Jignesh
> 

Re: Podling Report Reminder - August 2016

[Julian Hyde]

Quickstep missed its report last month, so it is very important to file this 
month.

Who is going to write the report?

Julian


> On Jul 27, 2016, at 4:47 AM, johndam...@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, 17 August 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, August 03).
> 
> 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/August2016
> 
> 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: 5 things

[Julian Hyde]

The web site is great. It’ll be good enough for several months!

Can you add a link to the mailing list. e.g. “To get involved…” 
http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/ 
<http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/> and to JIRA 
https://issues.apache.org/jira/browse/QUICKSTEP 
<https://issues.apache.org/jira/browse/QUICKSTEP>.

Also please add an incubation disclaimer, same as in 
https://issues.apache.org/jira/browse/QUICKSTEP-1 
<https://issues.apache.org/jira/browse/QUICKSTEP-1>.

I agree with the other things on your TODO list but let’s also add making a 
release to the list.

Can you use apache terminology (PPMC, committers, contributors) rather than 
“core contributors” / “collaborators”.

Julian


> On Jul 14, 2016, at 10:41 AM, Jignesh Patel  wrote:
> 
> Dear Quickstep-pers:
> 
> 
> 
> A bunch of comments/updates.
> 
> 
> 
> #1: The initial project website is up at 
> http://quickstep.incubator.apache.org. It is really early and still needs a 
> lot of work.
> 
> 
> 
> #2: There is now a quickstart guide in the main repo: 
> https://github.com/apache/incubator-quickstep/blob/master/README.md Again 
> lots of work to do, but it is a start. 
> 
> 
> 
> #3: We need a more pages/writeup to cover more of the basics, which includes 
> at least a “Supported SQL surface” and additional examples. Will work on this 
> as I can steal time. Volunteers are of course welcome! 
> 
> 
> 
> #4: We need to write a better developer guide; i.e. improve the intro to dev 
> at https://github.com/apache/incubator-quickstep/blob/master/DEV_README.md. I 
> know the code is well-commented, but we should be making it easier to welcome 
> new developers. We can also provide a list of relatively simple projects that 
> new developers could take on. Ideas here are welcome.
> 
> 
> 
> #5: We need a guide for the developer community governance. Below is a 
> starting point. 
> 
> 
> 
> As usual comments welcome!
> 
> 
> 
> Cheers,
> 
> Jignesh 
> 
> 
> 
> Quickstep is a data platform that is written in C++ and uses advanced C++ 
> techniques including template meta-programming and various abstractions to 
> balance high-performance with extensibility. Thus, a good grasp over C++ 
> concepts is essential for a Quickstep developer.
> 
> 
> 
> Quickstep has a set of core contributors who are collectively the stewards of 
> the project. In addition, there is a set of general contributors who 
> contribute individual changes. The initial list of core and general 
> contributors is listed below.
> 
> 
> 
> Core contributors can close pull requests, except pull requests that they 
> have created (which must be examined and closed by another core contributor). 
> Anyone can open a pull request and once a pull request has been accepted that 
> committer becomes part of the general contributors group. 
> 
> 
> 
> A general contributor can become a core contributor by getting support from 
> at least two core contributors. It is expected that a general contributor 
> will have demonstrated proficiency in understanding and working with the core 
> engine to become part of the core contributors group.
> 
> 
> 
> To maintain membership in the core contributors group, the contributor must 
> be active in the project in the preceding 6-month period. Membership of the 
> core contributors is examined and determined bi-annually by the Apache 
> Quickstep PPMC. 
> 
> 
> 
> Core Contributors (as of July 14, 2016):
> 
> ·   Jignesh M. Patel
> 
> ·   Harshad Deshmukh
> 
> ·   Jianqiao Zhu
> 
> ·   Zuyu Zhang
> 
> ·   Marc Spehlmann
> 
> ·   Saket Saurabh
> 
> ·   Hakan Memisoglu
> 
> ·   Rogers Jeffrey Leo John
> 
> ·   Navneet Potti
> 
> 
> 
> Core Collaborators (as of June 18, 2016):
> 
> ·   Adalbert Gerald Soosai Raj
> 
> ·   Siddharth Suresh
> 
> ·   Rathijit Sen
> 
> ·   Craig Chasseur
> 
> ·   Yinan Li
> 
> ·   Qiang Zeng
> 
> ·   Shoban Chandrabose
> 
> ·   Roman Shaposhnik
> 
> ·   Julian Hyde
> 
> ·   Jesse Zhang
> 
> 
> 

Re: [DISCUSS] Building a community

[Julian Hyde]

I can think of a few concrete steps.

First, generate more activity on this list. I am worried by statements
like "Website is being worked on". If work is going on, why is it not
being discussed on the list? Who is working on the web site? A
community member, presumably? Everything on list, please.

Look at it from the perspective of those of us outside Wisconsin. To
most of the world, the dev list *is* the project. By working on
private lists, or face-to-face meetings, you are excluding your
potential community.

I am also worried about "getting some funding stability in place to
gather resources". Look, I know developers have to eat. But if Jignesh
is the rainmaker, it creates a particular social dynamic that could be
damaging if it carries into the Apache community.

I'd love to see the folks who are working on code -- Harshad Deshmukh,
Navneet Potti, Craig Chasseur, Zuyu Zhang, Jianqiao Zhu --
participating in these kinds of discussions, and picking up the tasks
to build the project. At Apache we say "community over code" and my
sense is that this project is just heads down, building code, right
now.

As for those tasks. A web site is absolutely essential. A quick start
guide is also a great idea.

Talks are a great way to reach new people. Project members should be
giving talks at meetups, conferences (especially
open-source/business-oriented conferences, such as Hadoop Summit and
ApacheCon). The lead time for conferences is 4-6 months, so you should
be applying now. If project members are geographically distributed,
ask them to give talks in their own area.

A video talk or demo is also useful. Also, a single slide or graphic
explaining what QuickStep is. And start generating one piece of
content a week to put into the twitter feed.

Lastly, the release. Releases are central to what Apache projects do.
They involve community more than they involve code.

The biggest misconception is that you have to fix bugs and make
features before you release. A release is just a blob of intellectual
property. There is considerable effort in making the first release,
but it is all about the legal packaging.

I think you should start working on the release right now. That means
discussing goals, timescales, and assigning tasks, all of it on this
list. You have enough features already. Keep your goals extremely
limited, and you might be able to release in two months.

Julian



On Fri, Jun 17, 2016 at 3:02 PM, Jignesh Patel  wrote:
> Great questions Julian and neat comments Greg.
>
> Website is being worked on, but need a bit more work before putting it up.
>
> Agreed — need to work on all this. The key question that we have to solve as 
> a group is getting some funding stability in place to gather resources to 
> work on things that you outline below, which is often hard to pull is as part 
> of student thesis (as you may know most of the initial developer community is 
> students).
>
> BTW — the goals were changes as one of the mentors objected to it :-) I think 
> it was a valid objection.
>
> I am actively developing guidelines to make it easier to allow developers 
> outside the core group to join. You may have seen the wiki pages that went up 
> recently. There is still a lot more to do there. Am also working on an quick 
> start guide.
>
> If anyone on this list sees opportunities for early actual users to try us 
> out, please point this group toward that. That would allow us to solve a lot 
> of problems!
>
> Cheers,
> Jignesh
>
>> On Jun 17, 2016, at 12:04 PM, Gregory Chase  wrote:
>>
>> A few questions:
>>
>> 1. Who should be in Quickstep's Community?
>>
>> 2. Why  should they join?
>>
>> 3. What do you want them to do?
>>
>> I'd change your goals as follows:
>>
>> 1. Create an ASF release
>> 2. Acquire Early Adopters
>> 3. Build a Community
>>
>> It's hard to attract people to a community when there is little to offer.
>>
>> Now, you can acquire some "early contributors" before the first ASF release
>> if you provide a bread crumb trail for them to contribute:
>> 1. Try out our daily snapshot
>> 2. Test instructions to help provide feedback in the Jira
>> 3. List of simple Jiras any first time contributor can solve (don't fix
>> them yourself, make it easy for others to join)
>>
>> I'd also recommend posting a more informative website so that people know
>> what it is that Quickstep offers and why it might interest them as a
>> product and a community.
>>
>> -Greg
>>
>> On Fri, Jun 17, 2016 at 9:55 AM, Julian Hyde  wrote:
>>
>>> Hi Quickstep developers and community,
>>>
>>> Let’s have a discussion about how to build a community aroun

[DISCUSS] Building a community

[Julian Hyde]

Hi Quickstep developers and community,

Let’s have a discussion about how to build a community around Quickstep.

In the last report, Quickstep’s goals were listed as

  1. Acquire early adopters
  2. Acquire early adopters
  3. Acquire early adopters

then changed to

  1. Acquire early adopters
  2. Build a community.
  3. Create an ASF release.

I’d like to see progress toward those goals. The main activity I see right now 
is people checking in code; that’s important, but it isn’t very effective at 
building community.

What concrete steps can we take to acquire early adopters and help build a 
community?

Please don’t be shy. I’d like to hear from as many people as possible — initial 
committers, mentors, and people who are on this list just because they want to 
kick the tires. Tell us what you want from this project.

Julian

Re: [jira] [Commented] (QUICKSTEP-20) Add parser support for SQL window aggregation function

[Julian Hyde]

If you’re going to build a full database, go for it, best of luck to you, but 
you’re going to need a large community.

But in my opinion, you should focus on your strengths. The community should ask 
itself what is the one thing that it can do better than anyone else. If you 
build library that can be embedded in other projects and in commercial 
products, you will gain adoption. If you try to solve the whole problem, 
everyone (including other Apache projects) will be against you.

Research projects and companies have an interest in “going big”. But projects, 
in my experience, work better if you go small.

That said, it does help to build community if you allow people to contribute 
stuff that interests them. But make sure you know what your goal is, and how 
those contributions contribute to that goal.

Julian


> On Jun 15, 2016, at 8:15 AM, Jignesh Patel  wrote:
> 
> Great points Julian, especially about algebra. Couldn’t agree more.
> 
> In fact, we have been strong advocates of the viewpoint that it is all about 
> the algebraic framework. Furthermore, we have argued that the relational 
> algebraic framework is the right “core” to build a platform. With it you can 
> go well beyond warehousing/SQL but also (with small extensions) build:
> 
> #1: JSON document stores (see Argo 
> <http://pages.cs.wisc.edu/~chasseur/pubs/argo-short.pdf>), 
> 
> #2: Iterative graph analytics (see Grail 
> <http://www.cs.wisc.edu/~jignesh/publ/Grail.pdf>), 
> 
> #3: Relational learning (see QuickFOIL 
> <http://www.cs.wisc.edu/~jignesh/publ/QuickFoil.pdf>), and
> 
> #4: Biological data management (see Periscope/SQ 
> <http://www.vldb.org/conf/2007/papers/demo/p1406-tata.pdf> and Periscope/GQ 
> <http://www.vldb.org/pvldb/1/1454184.pdf>).
> 
> If all of that is not enough, there are nice synergies between deeper 
> integration of common classes of machine learning and relational data 
> representation. A key idea here is factorized learning, which my student Arun 
> Kumar (co-advised with Naughton) introduced last year 
> <http://pages.cs.wisc.edu/~arun/orion/LearningOverJoinsSIGMOD.pdf>. Arun will 
> present a far deeper follow-on paper 
> <http://pages.cs.wisc.edu/~arun/hamlet/OptFSSIGMOD.pdf> on this topic at 
> SIGMOD in a few weeks. Interestingly, many other papers are starting to build 
> on these initial ideas. There is still a bunch of theory to figure out, as a 
> research community, we are collectively getting very close to nailing that.
> 
> In my keynote @ SIGMOD last year 
> <http://dl.acm.org/citation.cfm?doid=2723372.2723374>, I talked about how 
> theory (see papers above) has shown that with an extended relational 
> algebraic core these seemingly different applications converge to a platform 
> that is powered by a relational core. This converged platform is the 
> long-term vision for Quickstep. Yup — I hear you, I need to write this up for 
> the community. You are right and I’m adding it to my list :-) 
> 
> We have shown prototypes for all of the above, but haven’t put it all 
> together. That is the hard part, and we are at the start of that journey. 
> That effort is also revealing all kinds of interesting systems research 
> issues — so good for the students on the project. Potentially exciting times 
> ahead!
> 
> Cheers,
> Jignesh 
> 
>> On Jun 14, 2016, at 2:32 PM, Julian Hyde  wrote:
>> 
>> Having that representation reduces coupling in your architecture, so is 
>> useful even if you don’t decide to use a library for SQL parsing/planning. 
>> But I think once you have it you will realize that all of the interesting 
>> problems for the project happen after the query has been converted to 
>> algebra.
>> 
>> Julian

Re: Guideline To Update Copyright Header

[Julian Hyde]

If the code in third_party is merely “copied” into the project and not part of 
it, and in particular if have not forked it and intend to copy in a more recent 
version in the future, maybe you shouldn’t be applying Apache headers to those 
files. They could be just included in the source distribution (including 
appropriate licenses and notices).

Other mentors, what do you think?

Julian

> On Jun 14, 2016, at 4:08 PM, Jignesh Patel  wrote:
> 
> Following up on Roman’s excellent comment, I took all the copyright notices 
> under third_party and collected them into a new NOTICE file (see below). 
> 
> Notice that there are comments within [Square Braces]. This will make it 
> easier for us to update the NOTICE file if we chose to upgrade some of these 
> third-party packages in the future. 
> 
> Also, the copyright file in the third_party/benchmark does not have year, so 
> I  simply reproduced it as they state in their AUTHORS  file 
> .
> 
> Comments? 
> 
> Cheers,
> Jignesh 
> 
> Apache Quickstep (incubating)
> Copyright 2016 The Apache Software Foundation.
> 
> This product includes software developed at
> The Apache Software Foundation (http://www.apache.org/).
> 
> Portions Copyright (c) 2011-2015, Quickstep Technologies, LLC.
> Portions Copyright (c) 2015-2016, Pivotal Software, Inc.
> 
> [Copyright for third_party/benchmark]
> Portions Copyright (c) Arne Beer 
> Portions Copyright (c) Christopher Seymour 
> Portions Copyright (c) David Coeurjolly 
> Portions Copyright (c) Dominic Hamon 
> Portions Copyright (c) Eugene Zhuk 
> Portions Copyright (c) Evgeny Safronov 
> Portions Copyright (c) Felix Homann 
> Portions Copyright (c) Google Inc.
> Portions Copyright (c) JianXiong Zhou 
> Portions Copyright (c) Lei Xu 
> Portions Copyright (c) Matt Clarkson 
> Portions Copyright (c) Oleksandr Sochka 
> Portions Copyright (c) Paul Redmond 
> Portions Copyright (c) Shuo Chen 
> Portions Copyright (c) Yusuke Suzuki 
> 
> [Copyright for third_party/cpplint]
> Portions Copyright (c) 2009 Google Inc 
> 
> [Copyright for third_party/farmhash]
> Copyright (c) 2014 Google, Inc.
> 
> [Copyright for third_party/gflags]
> Copyright (c) 2006, Google Inc.
> 
> [Copyright for third_party/glog]
> Copyright (c) 2008, Google Inc.
> 
> [Copyright for third_party/gpertools]
> Copyright (c) 2005, Google Inc.
> 
> [Copyright for third_party/linenoise]
> Copyright (c) 2010-2014, Salvatore Sanfilippo 
> Copyright (c) 2010-2013, Pieter Noordhuis 

Re: [jira] [Commented] (QUICKSTEP-20) Add parser support for SQL window aggregation function

[Julian Hyde]

The prerequisite for integrating a SQL parsing and/or planning front-end would 
be to have a lower-level interface than SQL. Imagine a text representation (in 
say JSON or XML) of a queries in logical or physical relational algebra. 
(Logical would have the logical operators, e.g. Join, and physical would have, 
say, QuickstepHashJoin and QuickstepSortMergeJoin).

Having that representation reduces coupling in your architecture, so is useful 
even if you don’t decide to use a library for SQL parsing/planning. But I think 
once you have it you will realize that all of the interesting problems for the 
project happen after the query has been converted to algebra.

Julian

> On Jun 14, 2016, at 12:22 PM, Jignesh Patel  wrote:
> 
> Great point Julian and something that I have been thinking about too. 
> 
> I’d love to kick off a discussion to see how we can find a way to make this 
> work. I’d love to give a talk to the Calcite team sometime later on this 
> summer (July?) on Quickstep and explore this very synergy. 
> 
> Some of the ORCA guys have also been thinking about this. But, in the end it 
> boils down to two things: a) Synergy and b) Some commitment from the two 
> projects to make this work.
> 
> For Quickstep, the goal is quite clear: we want to focus on the key aspects 
> of our platform that relate to fast query execution and flexible scheduling. 
> But, need to do this in a way that is trivially easy for users to use. 
> 
> Cheers,
> Jignesh  
> 
>> Julian Hyde commented on QUICKSTEP-20:
>> --
>> 
>> It sounds as if Quickstep is going down the route of building a full SQL 
>> parser, validator, planner. This is fine, but it is a huge amount of work to 
>> produce something that is high quality. Have you considered using Apache 
>> Calcite? Calcite is written in Java but that shouldn't be too much of an 
>> issue because Calcite can work as a pre-processor, producing a physical plan 
>> that can be run without any Java in the runtime.
>> 
>>> Add parser support for SQL window aggregation function
>>> --
>>> 
>>>   Key: QUICKSTEP-20
>>>   URL: https://issues.apache.org/jira/browse/QUICKSTEP-20
>>>   Project: Apache Quickstep
>>>Issue Type: New Feature
>>>Components: Parser
>>>  Reporter: Shixuan Fan
>>>Labels: features, newbie
>>> 
>>> The first part of window aggregation function. There will be new grammar 
>>> introduced to the parser so that the parser could understand a window 
>>> aggregation query.
>> 
>> 
>> 
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)
> 

Re: Guideline To Update Copyright Header

[Julian Hyde]

> On Jun 13, 2016, at 8:01 AM, Jignesh Patel  wrote:
> 
> Please note it is my understanding that we don’t need to add our individual 
> names or organization names to the NOTICE file, so don’t need to grow the 
> list in the NOTICE file. 

+1 to keeping the NOTICE file as short as possible. Some projects get into the 
habit of adding copyrights & notices merely out of “courtesy” but that imposes 
a burden on downstream projects (who are obliged by the ASL to pass on the 
NOTICE file intact).

Julian

Re: Where are design discussions happening?

[Julian Hyde]

And by the way, Harshad and Zuyu are JIRA administrators, so they could 
potentially do this too.

> On Jun 7, 2016, at 10:53 AM, Julian Hyde  wrote:
> 
> Yes, happy to do that. Can you make sure that jign...@apache.org is a JIRA 
> user and tell me the JIRA id.
> 
> 
>> On Jun 7, 2016, at 10:48 AM, Jignesh Patel  wrote:
>> 
>> Dear Julian,
>> 
>> I believe that is not me. I tried to see if I created that account and 
>> forgot the password, but it does not appear that way. After a bit of chasing 
>> down, I think that email belongs to 
>> https://plus.google.com/108466782913065225351/posts 
>> <https://plus.google.com/108466782913065225351/posts>. That is not me. 
>> 
>> Any chance we could make jign...@apache.org <mailto:jign...@apache.org> be 
>> the administrator for the JIRA? 
>> 
>> Yup — I agree using jign...@apache.org <mailto:jign...@apache.org> in every 
>> ASF asset would be a good idea. I have just realized that of late and am 
>> trying to switch to that whenever I can. 
>> 
>> Sorry for leaning so heavily on you so heavily on you Julian — thank you so 
>> much for all your help through this especially as the ASF infrastructure 
>> needs some patience :-) 
>> 
>> Cheers,
>> Jignesh 
>> 
>>> On Jun 7, 2016, at 11:28 AM, Julian Hyde  wrote:
>>> 
>>> Jignesh,
>>> 
>>> It looks as if you have Administrator access to the QUICKSTEP component in 
>>> JIRA. The user who is administrator is “jigneshmpatel" user (jignashmpatel 
>>> at gmail dot com).
>>> 
>>> So, you should be able to create issues (as, in fact should anyone with 
>>> committer or contributor access) and you should also see an 
>>> “Administration” tab at top-left where you can give rights to other people. 
>>> JIRA is in lockdown because of recent spam attacks, so regular users cannot 
>>> create JIRA cases.
>>> 
>>> Yeah, there are too many logins. I recommend that you try to use your 
>>> apache ID for as many as possible. JIRA makes it too easy to create new 
>>> users.
>>> 
>>> Julian
>>> 
>>> 
>>>> On Jun 7, 2016, at 6:03 AM, Jignesh Patel  wrote:
>>>> 
>>>> Anyone know how to file a Jira for Quickstep? My Jira login is “jignesh” — 
>>>> I can’t find a “create button”
>>>> 
>>>> Another question — there appears to be too many different logins. Not sure 
>>>> if I am doing something wrong, and not finding a way to have a unified way 
>>>> of managing my identity across git, Jira, and Wiki. Does slow things down. 
>>>> Anyone have a better way to manage all these across the different portions 
>>>> of the infrastructure? 
>>>> 
>>>> Cheers,
>>>> Jignesh 
>>>> 
>>>> 
>>>>> On Jun 6, 2016, at 7:47 PM, Julian Hyde  wrote:
>>>>> 
>>>>> There seems to be quite a lot of work happening on Quickstep, but I can’t 
>>>>> figure out where the design discussions and decisions are being made. 
>>>>> Very few JIRA cases have been logged so far[1], some github pull-requests 
>>>>> get a lot of review comments[2] but the pull-requests themselves seem to 
>>>>> come out of the blue, and the traffic on the dev list is mainly either 
>>>>> code commits of people like me nagging you to produce reports[3].
>>>>> 
>>>>> Where are design discussions happening? Does the team have a weekly or 
>>>>> daily meeting?
>>>>> 
>>>>> I ask because if discussions are happening off-list, and in particular if 
>>>>> decisions are being made off-list, the project is not attractive to 
>>>>> outsiders. People won’t be able to find tasks to work on, and will assume 
>>>>> (rightly or wrongly) that any contribution they might make would be 
>>>>> rejected.
>>>>> 
>>>>> Julian
>>>>> 
>>>>> [1] https://issues.apache.org/jira/browse/QUICKSTEP 
>>>>> <https://issues.apache.org/jira/browse/QUICKSTEP>
>>>>> 
>>>>> [2] https://github.com/apache/incubator-quickstep/pull/8 
>>>>> <https://github.com/apache/incubator-quickstep/pull/8>
>>>>> 
>>>>> [3] 
>>>>> http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/201606.mbox/browser
>>>>>  
>>>>> <http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/201606.mbox/browser>
>>>> 
>>> 
>> 
> 

Re: Where are design discussions happening?

[Julian Hyde]

Yes, happy to do that. Can you make sure that jign...@apache.org is a JIRA user 
and tell me the JIRA id.


> On Jun 7, 2016, at 10:48 AM, Jignesh Patel  wrote:
> 
> Dear Julian,
> 
> I believe that is not me. I tried to see if I created that account and forgot 
> the password, but it does not appear that way. After a bit of chasing down, I 
> think that email belongs to 
> https://plus.google.com/108466782913065225351/posts 
> <https://plus.google.com/108466782913065225351/posts>. That is not me. 
> 
> Any chance we could make jign...@apache.org <mailto:jign...@apache.org> be 
> the administrator for the JIRA? 
> 
> Yup — I agree using jign...@apache.org <mailto:jign...@apache.org> in every 
> ASF asset would be a good idea. I have just realized that of late and am 
> trying to switch to that whenever I can. 
> 
> Sorry for leaning so heavily on you so heavily on you Julian — thank you so 
> much for all your help through this especially as the ASF infrastructure 
> needs some patience :-) 
> 
> Cheers,
> Jignesh 
> 
>> On Jun 7, 2016, at 11:28 AM, Julian Hyde  wrote:
>> 
>> Jignesh,
>> 
>> It looks as if you have Administrator access to the QUICKSTEP component in 
>> JIRA. The user who is administrator is “jigneshmpatel" user (jignashmpatel 
>> at gmail dot com).
>> 
>> So, you should be able to create issues (as, in fact should anyone with 
>> committer or contributor access) and you should also see an “Administration” 
>> tab at top-left where you can give rights to other people. JIRA is in 
>> lockdown because of recent spam attacks, so regular users cannot create JIRA 
>> cases.
>> 
>> Yeah, there are too many logins. I recommend that you try to use your apache 
>> ID for as many as possible. JIRA makes it too easy to create new users.
>> 
>> Julian
>> 
>> 
>>> On Jun 7, 2016, at 6:03 AM, Jignesh Patel  wrote:
>>> 
>>> Anyone know how to file a Jira for Quickstep? My Jira login is “jignesh” — 
>>> I can’t find a “create button”
>>> 
>>> Another question — there appears to be too many different logins. Not sure 
>>> if I am doing something wrong, and not finding a way to have a unified way 
>>> of managing my identity across git, Jira, and Wiki. Does slow things down. 
>>> Anyone have a better way to manage all these across the different portions 
>>> of the infrastructure? 
>>> 
>>> Cheers,
>>> Jignesh 
>>> 
>>> 
>>>> On Jun 6, 2016, at 7:47 PM, Julian Hyde  wrote:
>>>> 
>>>> There seems to be quite a lot of work happening on Quickstep, but I can’t 
>>>> figure out where the design discussions and decisions are being made. Very 
>>>> few JIRA cases have been logged so far[1], some github pull-requests get a 
>>>> lot of review comments[2] but the pull-requests themselves seem to come 
>>>> out of the blue, and the traffic on the dev list is mainly either code 
>>>> commits of people like me nagging you to produce reports[3].
>>>> 
>>>> Where are design discussions happening? Does the team have a weekly or 
>>>> daily meeting?
>>>> 
>>>> I ask because if discussions are happening off-list, and in particular if 
>>>> decisions are being made off-list, the project is not attractive to 
>>>> outsiders. People won’t be able to find tasks to work on, and will assume 
>>>> (rightly or wrongly) that any contribution they might make would be 
>>>> rejected.
>>>> 
>>>> Julian
>>>> 
>>>> [1] https://issues.apache.org/jira/browse/QUICKSTEP 
>>>> <https://issues.apache.org/jira/browse/QUICKSTEP>
>>>> 
>>>> [2] https://github.com/apache/incubator-quickstep/pull/8 
>>>> <https://github.com/apache/incubator-quickstep/pull/8>
>>>> 
>>>> [3] 
>>>> http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/201606.mbox/browser
>>>>  
>>>> <http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/201606.mbox/browser>
>>> 
>> 
> 

Re: Where are design discussions happening?

[Julian Hyde]

Jignesh,

It looks as if you have Administrator access to the QUICKSTEP component in 
JIRA. The user who is administrator is “jigneshmpatel" user (jignashmpatel at 
gmail dot com).

So, you should be able to create issues (as, in fact should anyone with 
committer or contributor access) and you should also see an “Administration” 
tab at top-left where you can give rights to other people. JIRA is in lockdown 
because of recent spam attacks, so regular users cannot create JIRA cases.

Yeah, there are too many logins. I recommend that you try to use your apache ID 
for as many as possible. JIRA makes it too easy to create new users.

Julian


> On Jun 7, 2016, at 6:03 AM, Jignesh Patel  wrote:
> 
> Anyone know how to file a Jira for Quickstep? My Jira login is “jignesh” — I 
> can’t find a “create button”
> 
> Another question — there appears to be too many different logins. Not sure if 
> I am doing something wrong, and not finding a way to have a unified way of 
> managing my identity across git, Jira, and Wiki. Does slow things down. 
> Anyone have a better way to manage all these across the different portions of 
> the infrastructure? 
> 
> Cheers,
> Jignesh 
> 
> 
>> On Jun 6, 2016, at 7:47 PM, Julian Hyde  wrote:
>> 
>> There seems to be quite a lot of work happening on Quickstep, but I can’t 
>> figure out where the design discussions and decisions are being made. Very 
>> few JIRA cases have been logged so far[1], some github pull-requests get a 
>> lot of review comments[2] but the pull-requests themselves seem to come out 
>> of the blue, and the traffic on the dev list is mainly either code commits 
>> of people like me nagging you to produce reports[3].
>> 
>> Where are design discussions happening? Does the team have a weekly or daily 
>> meeting?
>> 
>> I ask because if discussions are happening off-list, and in particular if 
>> decisions are being made off-list, the project is not attractive to 
>> outsiders. People won’t be able to find tasks to work on, and will assume 
>> (rightly or wrongly) that any contribution they might make would be rejected.
>> 
>> Julian
>> 
>> [1] https://issues.apache.org/jira/browse/QUICKSTEP 
>> <https://issues.apache.org/jira/browse/QUICKSTEP>
>> 
>> [2] https://github.com/apache/incubator-quickstep/pull/8 
>> <https://github.com/apache/incubator-quickstep/pull/8>
>> 
>> [3] 
>> http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/201606.mbox/browser
>>  
>> <http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/201606.mbox/browser>
> 

Re: [FINAL DRAFT] Incubator PMC Board Report - June 2016 -- feedback

[Julian Hyde]

Some background on formatting. The Board uses plain text for its agenda and 
minutes. The Wiki is just a convenient tool that allows several podlings to 
edit their reports, which are then combined into an Incubator report and 
incorporated in the agenda. The minutes of the last meeting are online[1] and 
you can see the various podlings’ reports if you search for “Attachment Y”.

Sorry it wasn’t clear what the format & content of the report should be. No one 
is upset that you didn’t know — we’re just giving feedback. I don’t expect 
we'll be changing the wiki interface, because other content in the wiki does 
allow markup and links, but my best suggestion is to take a look at other 
podling reports, and also look through the board minutes.

Julian

[1] 
https://www.apache.org/foundation/records/minutes/2016/board_minutes_2016_04_20.txt
 
<https://www.apache.org/foundation/records/minutes/2016/board_minutes_2016_04_20.txt>

> On Jun 7, 2016, at 6:15 AM, Jignesh Patel  wrote:
> 
> Hi Julian and Marvin: Changes made to 
> https://wiki.apache.org/incubator/June2016 
> <https://wiki.apache.org/incubator/June2016>. Thanks for the feedback!
> 
> Good to know about not using wiki markup. The wiki edit page is confusing as 
> it shows in the bottom pane the markup syntax. That seems to encourage 
> writers to consider using makeup to make it easier to read the report. If it 
> is not too hard, may be worth mentioning that writers should not use markup 
> perhaps right upfront in the wiki (and that can be taken out just before the 
> final report is filed), or simply not showing the hints for markup. Just a 
> thought in case it helps other incubators. 
> 
> Cheers,
> Jignesh 
> 
>> On Jun 6, 2016, at 9:01 PM, Julian Hyde  wrote:
>> 
>> For those of you not on general@incubator, forwarding Marvin Humphrey’s 
>> comments on Quickstep’s report.
>> 
>> (I recommend that PPMC members join general@incubator… you will learn a lot 
>> about incubation & the Apache way.)
>> 
>> Julian
>> 
>> 
>>> On Jun 6, 2016, at 6:40 PM, Marvin Humphrey  wrote:
>>> 
>>>> 
>>>> Quickstep
>>>> 
>>>> Modern servers pack enough storage and computing power that just a decade
>>>> ago was spread across a modest-sized cluster. Given that we are on a
>>>> technological path to continue to increase the storage and compute 
>>>> densities
>>>> of individual server nodes, we must complement methods that focus on
>>>> '''scaling-out''' by also developing methods to '''scale-in''' to fully
>>>> exploit the hardware capabilities that is packed in each server node. The
>>>> initial phase of the Quickstep project focuses on this scaling-in aspect.
>>>> Quickstep uses novel methods for organizing data (including columnar and
>>>> hybrid storage organization), template metaprogramming for vectorized query
>>>> execution, and a query execution paradigm that separate control-flow from
>>>> data-flow. Collectively, these methods achieve high performance on
>>>> contemporary servers with multi-socket, multi-core processors and large 
>>>> main
>>>> memory configurations. To keep the project focused, the project’s initial
>>>> target is interactive in-memory data warehousing workloads in single-node
>>>> settings. In the near future we plan to expand from this initial 
>>>> single-node
>>>> focus to a distributed setting. Early results indicate that Quickstep is
>>>> over an order-of-magnitude faster than existing platforms including Spark
>>>> 2.0 and PostgreSQL 9.6 Beta1 (that now has parallel query processing).
>>> 
>>> The description of Quickstep is longer than it needs to be and shouldn't
>>> contain wiki markup.  Please edit podlings.xml.
>>> 
>>>> Three most important issues to address in the move towards graduation:
>>>> 
>>>> 1. Acquire early adopters
>>>> 2. Acquire early adopters
>>>> 3. Acquire early adopters
>>>>  (We know it is that important!)
>>> 
>>>> Roman Shaposhnik (rvs):
>>>> 
>>>>  Really, at least goal #2 should be "make a first ASF release". Hopefully
>>>>  we can work with the community to get a sense how important it is in
>>>>  addition to growing a community (all 3 goals in this report).
>>> 
>>> +1 to this excellent comment of Roman's on the Quickstep report.  "Release
>>> early, release often" is a technique for acquiring early adopters!
>> 
>> 
> 

Re: [FINAL DRAFT] Incubator PMC Board Report - June 2016 -- feedback

[Julian Hyde]

For those of you not on general@incubator, forwarding Marvin Humphrey’s 
comments on Quickstep’s report.

(I recommend that PPMC members join general@incubator… you will learn a lot 
about incubation & the Apache way.)

Julian


> On Jun 6, 2016, at 6:40 PM, Marvin Humphrey  wrote:
> 
>> 
>> Quickstep
>> 
>> Modern servers pack enough storage and computing power that just a decade
>> ago was spread across a modest-sized cluster. Given that we are on a
>> technological path to continue to increase the storage and compute densities
>> of individual server nodes, we must complement methods that focus on
>> '''scaling-out''' by also developing methods to '''scale-in''' to fully
>> exploit the hardware capabilities that is packed in each server node. The
>> initial phase of the Quickstep project focuses on this scaling-in aspect.
>> Quickstep uses novel methods for organizing data (including columnar and
>> hybrid storage organization), template metaprogramming for vectorized query
>> execution, and a query execution paradigm that separate control-flow from
>> data-flow. Collectively, these methods achieve high performance on
>> contemporary servers with multi-socket, multi-core processors and large main
>> memory configurations. To keep the project focused, the project’s initial
>> target is interactive in-memory data warehousing workloads in single-node
>> settings. In the near future we plan to expand from this initial single-node
>> focus to a distributed setting. Early results indicate that Quickstep is
>> over an order-of-magnitude faster than existing platforms including Spark
>> 2.0 and PostgreSQL 9.6 Beta1 (that now has parallel query processing).
> 
> The description of Quickstep is longer than it needs to be and shouldn't
> contain wiki markup.  Please edit podlings.xml.
> 
>> Three most important issues to address in the move towards graduation:
>> 
>>  1. Acquire early adopters
>>  2. Acquire early adopters
>>  3. Acquire early adopters
>>(We know it is that important!)
> 
>>  Roman Shaposhnik (rvs):
>> 
>>Really, at least goal #2 should be "make a first ASF release". Hopefully
>>we can work with the community to get a sense how important it is in
>>addition to growing a community (all 3 goals in this report).
> 
> +1 to this excellent comment of Roman's on the Quickstep report.  "Release
> early, release often" is a technique for acquiring early adopters!

Where are design discussions happening?

[Julian Hyde]

There seems to be quite a lot of work happening on Quickstep, but I can’t 
figure out where the design discussions and decisions are being made. Very few 
JIRA cases have been logged so far[1], some github pull-requests get a lot of 
review comments[2] but the pull-requests themselves seem to come out of the 
blue, and the traffic on the dev list is mainly either code commits of people 
like me nagging you to produce reports[3].

Where are design discussions happening? Does the team have a weekly or daily 
meeting?

I ask because if discussions are happening off-list, and in particular if 
decisions are being made off-list, the project is not attractive to outsiders. 
People won’t be able to find tasks to work on, and will assume (rightly or 
wrongly) that any contribution they might make would be rejected.

Julian

[1] https://issues.apache.org/jira/browse/QUICKSTEP 


[2] https://github.com/apache/incubator-quickstep/pull/8 


[3] 
http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/201606.mbox/browser
 

Re: Logo?

[Julian Hyde]

Word art + cute animal mascot has worked well for a lot of Apache projects.

This guy (a Basilisk lizard) seems appropriate:

https://i.ytimg.com/vi/PgSvN70lJ6w/hqdefault.jpg

The swoop of his tail could be incorporated into the flourish of the
capital 'Q'.

On Sat, Jun 4, 2016 at 7:25 PM, Jignesh Patel  wrote:
> Great to hear from our resident marketing guru. Awesome suggestion Greg!
>
> Here is another design. It has the logo and the word art with the full system 
> name in it. Comments Greg? I may have misunderstood what you were suggesting.
>
> Powerpoint is also attached if someone is feeling adventurous. Note to see 
> the whole image, you will have to zoom out in Powerpoint.
>
> Cheers,
> Jignesh
>
>> On Jun 4, 2016, at 8:07 PM, Greg Chase  wrote:
>>
>> Cool logos Jignesh!
>>
>> Personally I'm a fan of word art that says what the brand is, so that 
>> everyone will know without requiring much education.
>>
>> So I would consider "Quickstep" in the logo.  You can also choose an icon to 
>> be part, or not.
>>
>> Having branded 3 Apache projects now, I will tell you that you don't need to 
>>  put "Apache" in the name.
>>
>> 0Greg

Re: Podling Report Reminder - May 2016

[Julian Hyde]

s/making a release before/making a release, before/

On Thu, Jun 2, 2016 at 1:50 PM, Julian Hyde  wrote:
> I'd like to see some concrete progress in (a) building a community,
> (b) making a release before the next report. Right now, I can tell
> that you're all about code. Quite frankly, we don't give a hoot about
> code. Build a community, and the code will happen. Quickstep needs to
> start building a community.
>
> Julian
>
>
> On Thu, Jun 2, 2016 at 1:41 PM, Jignesh Patel  wrote:
>> Thanks Julian! Adding this to the list to work on.
>>
>> Neat tips!
>>
>> Cheers,
>> Jignesh
>>
>>> On Jun 2, 2016, at 3:40 PM, Julian Hyde  wrote:
>>>
>>> You, as a PMC, should decide what are the criteria & process for
>>> making someone a committer. There are some guidelines[1], but they are
>>> only guidelines.
>>>
>>> In my opinion, you should err on setting the bar too low rather than
>>> too high. Making someone a committer early will tend to draw them into
>>> the community. And, remember that code is not the only kind of
>>> contribution.
>>>
>>> The Quickstep community should also have a broader discussion: how do
>>> you intend to meet your goal of "Acquire early adopters". Electing
>>> committers is a consequence of a successful strategy for growing
>>> community, and helps further that growth.
>>>
>>> Julian
>>>
>>> [1] http://community.apache.org/newcommitter.html
>>>
>>> On Thu, Jun 2, 2016 at 1:29 PM, Jignesh Patel  wrote:
>>>> Thanks Julian!
>>>>
>>>> What are the guidelines for election? We would love to welcome new
>>>> committers who are starting to make serious contributions.
>>>>
>>>> Cheers,
>>>> Jignesh
>>>>
>>>> On Jun 2, 2016, at 3:28 PM, Julian Hyde  wrote:
>>>>
>>>> The key word here is "elected", as opposed to "showed up in his
>>>> congressional office for the first time". :)
>>>>
>>>>
>>

Re: Podling Report Reminder - May 2016

[Julian Hyde]

I'd like to see some concrete progress in (a) building a community,
(b) making a release before the next report. Right now, I can tell
that you're all about code. Quite frankly, we don't give a hoot about
code. Build a community, and the code will happen. Quickstep needs to
start building a community.

Julian


On Thu, Jun 2, 2016 at 1:41 PM, Jignesh Patel  wrote:
> Thanks Julian! Adding this to the list to work on.
>
> Neat tips!
>
> Cheers,
> Jignesh
>
>> On Jun 2, 2016, at 3:40 PM, Julian Hyde  wrote:
>>
>> You, as a PMC, should decide what are the criteria & process for
>> making someone a committer. There are some guidelines[1], but they are
>> only guidelines.
>>
>> In my opinion, you should err on setting the bar too low rather than
>> too high. Making someone a committer early will tend to draw them into
>> the community. And, remember that code is not the only kind of
>> contribution.
>>
>> The Quickstep community should also have a broader discussion: how do
>> you intend to meet your goal of "Acquire early adopters". Electing
>> committers is a consequence of a successful strategy for growing
>> community, and helps further that growth.
>>
>> Julian
>>
>> [1] http://community.apache.org/newcommitter.html
>>
>> On Thu, Jun 2, 2016 at 1:29 PM, Jignesh Patel  wrote:
>>> Thanks Julian!
>>>
>>> What are the guidelines for election? We would love to welcome new
>>> committers who are starting to make serious contributions.
>>>
>>> Cheers,
>>> Jignesh
>>>
>>> On Jun 2, 2016, at 3:28 PM, Julian Hyde  wrote:
>>>
>>> The key word here is "elected", as opposed to "showed up in his
>>> congressional office for the first time". :)
>>>
>>>
>

Re: Podling Report Reminder - May 2016

[Julian Hyde]

You, as a PMC, should decide what are the criteria & process for
making someone a committer. There are some guidelines[1], but they are
only guidelines.

In my opinion, you should err on setting the bar too low rather than
too high. Making someone a committer early will tend to draw them into
the community. And, remember that code is not the only kind of
contribution.

The Quickstep community should also have a broader discussion: how do
you intend to meet your goal of "Acquire early adopters". Electing
committers is a consequence of a successful strategy for growing
community, and helps further that growth.

Julian

[1] http://community.apache.org/newcommitter.html

On Thu, Jun 2, 2016 at 1:29 PM, Jignesh Patel  wrote:
> Thanks Julian!
>
> What are the guidelines for election? We would love to welcome new
> committers who are starting to make serious contributions.
>
> Cheers,
> Jignesh
>
> On Jun 2, 2016, at 3:28 PM, Julian Hyde  wrote:
>
> The key word here is "elected", as opposed to "showed up in his
> congressional office for the first time". :)
>
>

Re: Podling Report Reminder - May 2016

[Julian Hyde]

The key word here is "elected", as opposed to "showed up in his
congressional office for the first time". :)

This section is important because the IPMC is looking for indications
that the project is able to grow beyond its base of initial
committers.

I signed off.

Julian


On Thu, Jun 2, 2016 at 1:07 PM, Jignesh Patel  wrote:
> Answers inlined.
>
>> On Jun 2, 2016, at 2:55 PM, Julian Hyde  wrote:
>
>> The report makes the incorrect statement "Last committer joined on May
>> 30, 2016." No committers have been elected since incubation, as far as
>> I know. Please correct that statement.
>
> I mentioned this last committer date since Navneet joined the committer list 
> on this date. But perhaps, I misunderstood the question. So, I have dropped 
> that line altogether and made this N/A. Please feel free to let me know if 
> there is a better answer there.
>
>> Also, please fix the formatting. There is a partial line "aware of?",
>> and "Quickstep has been incubating since 2016-03-29." should be a
>> separate paragraph.
>
> Done.
>
>>
>> I suggest that you email the mentors directly when the report is ready
>> for sign-off, this month and subsequent months. We're busy people, and
>> we sometimes need prodding.
>
> Will do. The new report is now ready with the changes above.
>
> Jignesh

Re: Podling Report Reminder - May 2016

[Julian Hyde]

I saw that the report is filed (thanks for that!) but I'm not ready to sign off.

The report makes the incorrect statement "Last committer joined on May
30, 2016." No committers have been elected since incubation, as far as
I know. Please correct that statement.

Also, please fix the formatting. There is a partial line "aware of?",
and "Quickstep has been incubating since 2016-03-29." should be a
separate paragraph.

I suggest that you email the mentors directly when the report is ready
for sign-off, this month and subsequent months. We're busy people, and
we sometimes need prodding.

Julian

On Wed, May 25, 2016 at 8:09 PM, Julian Hyde  wrote:
> Hi Quickstep committers/PPMC members,
>
> I think this is the first time you’ve filed a report. It’s not absolutely 
> required, but it’s useful if at this point someone volunteers to write the 
> report, and sends a draft to the dev list well in advance of the deadline for 
> comments.
>
> Does that sound like a good idea? If so, any volunteers?
>
> Your affectionate mentor,
>
> Julian
>
>> On May 25, 2016, at 7:33 PM, johndam...@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, 15 June 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, June 1st).
>>
>> 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/May2016
>>
>> 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: SUBSCRIBE

[Julian Hyde]

You’ll need to subscribe yourself. See 
http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/ 
 and similar.

> On May 31, 2016, at 12:30 PM, Rogers Jeffrey  
> wrote:
> 
> Please subscribe me to the lists
> 
> Thanks and Regards,
> Rogers Jeffrey L

Re: Update on the Quickstep project

[Julian Hyde]

There is already a definitive answer: 
https://issues.apache.org/jira/browse/LEGAL-156 
<https://issues.apache.org/jira/browse/LEGAL-156> 

But I agree with you, Spark’s process is a good one for Quickstep to adopt.

Julian


> On May 31, 2016, at 11:17 AM, Roman Shaposhnik  wrote:
> 
> On Tue, May 31, 2016 at 11:06 AM, Julian Hyde  wrote:
>> Roman,
>> 
>> Requiring the contributor to log a JIRA makes a lot of sense, and a lot of 
>> projects do that.
>> But from an IP hygiene standpoint, my understanding is that it is sufficient 
>> that the contributor
>> has created a github pull request to a project under 
>> https://github.com/apache. Just like
>> attaching a patch to an Apache JIRA, that demonstrates intent to contribute. 
>> Is my understanding correct?
> 
> Let me put it this way: I don't think a pure GH workflow will be OK by ASF:
>https://issues.apache.org/jira/browse/LEGAL-249
> 
> But! Once we consider GH notifications being pushed to our mailing
> lists it becomes
> a gray area in my view. One way to resolve it is to push the issue via
> ASF's VP of Legal
> for an authoritative answer (see one of my last comments on the above JIRA).
> 
> What I'm suggesting here is, in a way, a cop out, but a productive one ;-)
> 
> IOW, if what Spark folks have come up with jives well with Quickstep community
> lets just adopt that approach and move on without being a poster child 
> community
> to go resolve it with ASF's VP of Legal.
> 
> Thanks,
> Roman.
> 
> P.S. Sorry I couldn't give you a 100% iron clad answer.

Re: Update on the Quickstep project

[Julian Hyde]

Roman,

Requiring the contributor to log a JIRA makes a lot of sense, and a lot of 
projects do that. But from an IP hygiene standpoint, my understanding is that 
it is sufficient that the contributor has created a github pull request to a 
project under https://github.com/apache. Just like attaching a patch to an 
Apache JIRA, that demonstrates intent to contribute. Is my understanding 
correct?

Julian


> On May 31, 2016, at 10:29 AM, Roman Shaposhnik  wrote:
> 
> On Tue, May 31, 2016 at 10:26 AM, Jignesh Patel  wrote:
>> Hi Roman,
>> 
>> I’m guessing that someone closing a PR should check if the committer has an 
>> ICLA.
>> Or, is submitting a PR and implicit assignment by the code contributor that 
>> they are
>> willing to donate the code to Apache?
> 
> The safest bet here is an ASF JIRA workflow where the intent is
> tracked. Spark guys
> have mastered it pretty well:
>
> https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#ContributingtoSpark-ContributingCodeChanges
> 
> Thanks,
> Roman.

Re: Podling Report Reminder - May 2016

[Julian Hyde]

+1 to everything Roman said. 

And I’ll add that we are here to help and to advise, not just to govern. Apache 
infrastructure is complex, we acknowledge that. There are some things that only 
we have permission to do, and we’ll do those things. But the committers should 
do as much of the work as possible. Learning how to navigate Apache 
infrastructure is painful, but it is part of the process of incubation.

Julian


> On May 26, 2016, at 5:57 PM, Roman Shaposhnik  wrote:
> 
> On Thu, May 26, 2016 at 5:37 PM, Jignesh Patel  wrote:
>> Ah … catching on. So, not meritocracy based on that front?
> 
> This is a good question. Here's an analogy. Project mentors are to a podling
> what ASF board of directors' officers are to a TLP. They are
> individuals selected
> upfront. Based, hopefully, on foundation-wide merit, but not necessarily a 
> merit
> within each individual project (or a podling). The right that you have is to 
> say
> I don't want that dude as a mentor (or I don't want to vote for that
> guy to be on
> the board) but once they are elected you are kind of stuck with them.
> 
> So at the end of the day -- there's a meritocratic principle upfront.
> 
> Hope this helps to understand ASF better.
> 
> Thanks,
> Roman.

Re: Podling Report Reminder - May 2016

[Julian Hyde]

This looks good to me.

The “brief description” isn’t brief, but the detail is warranted since this is 
the first report.

I agree with your goals #1, #2 and #3. Or in more common Apache parlance, 
“Build community”. After the report is submitted, let’s have a discussion about 
how we can achieve this. In future reports, we can include more specific goals.

Can you also make sure that http://incubator.apache.org/projects/quickstep.html 
 is up to date, and 
mention in your report where you are in terms of adopting infrastructure 
(lists, JIRA, git, CI, etc.)

Julian


> On May 25, 2016, at 8:32 PM, Jignesh Patel  wrote:
> 
> Great point Julian and thanks for the prod. 
> 
> Here is the first cut. Comments welcome! Will populate the wiki after 
> collecting feedback from this group. 
> 
> ———
> 
> Your project name: Quickstep 
> 
> A brief description of your project: Modern servers pack enough storage and 
> computing power that just a decade ago was spread across a modest-sized 
> cluster. Given that we are on a technological path to continue to increase 
> the storage and compute densities of individual server nodes, we must 
> complement methods that focus on ``scaling-out'' by also developing methods 
> to ``scale-in'' to fully exploit the hardware capabilities that is packed in 
> each server node. The initial phase of the Quickstep project focuses on this 
> scaling-in aspect. Quickstep uses novel methods for organizing data 
> (including columnar and hybrid storage organization), template 
> metaprogramming for vectorized query execution, and a query execution 
> paradigm that separate control-flow from data-flow. Collectively, these 
> methods achieve high performance on contemporary servers with multi-socket, 
> multi-core processors and large main memory configurations. To keep the 
> project focused, the project’s initial target is interactive in-memory data 
> warehousing workloads in single-node settings. In the near future we plan to 
> expand from this initial single-node focus to a distributed setting. Early 
> results indicate that Quickstep is over an order-of-magnitude faster than 
> existing platforms including Spark 2.0 and PostgreSQL 9.6 Beta1 (that now has 
> parallel query processing).
> 
> A list of the three most important issues to address in the move  towards 
> graduation:
> #1: Acquire early adopters
> #2: Acquire early adopters
> #3: Acquire early adopters
> (We know it is that important!)
> 
> Any issues that the Incubator PMC or ASF Board might wish/need to be  aware 
> of: None
> 
> How has the community developed since the last report: We were incubated into 
> Apache recently, and the developers are actively learning about the Apache 
> way from two amazing mentors!
> 
> How has the project developed since the last report: This is the first report.

Re: Podling Report Reminder - May 2016

[Julian Hyde]

Hi Quickstep committers/PPMC members,

I think this is the first time you’ve filed a report. It’s not absolutely 
required, but it’s useful if at this point someone volunteers to write the 
report, and sends a draft to the dev list well in advance of the deadline for 
comments.

Does that sound like a good idea? If so, any volunteers?

Your affectionate mentor,

Julian

> On May 25, 2016, at 7:33 PM, johndam...@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, 15 June 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, June 1st).
> 
> 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/May2016
> 
> 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: Subscriber

[Julian Hyde]

Please follow the instructions on 
http://mail-archives.apache.org/mod_mbox/incubator-quickstep-dev/ 
.

> On May 15, 2016, at 6:30 AM, Soumasish  wrote:
> 
> Please include me in the QuickStep mailiing list. I wish to be a
> contributor to the project.
> 
> Best Regards
> Soumasish Goswami
> 
>   - www.linkedin.com/in/soumasish/

Re: When do you think you can fully transition to ASF infrastructure?

[Julian Hyde]

I did a quick search and found Geode’s request: 
https://issues.apache.org/jira/browse/INFRA-11322 
.

I think you need to log a similar INFRA issue. Link it to QUICKSTEP-2 and 
mention me & Roman so we can follow it.

Julian

> On May 10, 2016, at 4:37 PM, Zuyu Zhang  wrote:
> 
> We have a JIRA ticket QUICKSTEP-2 to track the progress of the Travis CI
> setup. What should we do regarding the INFRA request?

Re: When do you think you can fully transition to ASF infrastructure?

[Julian Hyde]

OK, you should log an INFRA request to get Travis set up. It shouldn’t take 
more than a day or two but definitely nothing will happen until you log an 
INFRA request. Ask the Geode folks what they had to do to set up Travis.

Julian


> On May 10, 2016, at 3:25 PM, Jignesh Patel  wrote:
> 
> Hi Julian: The current workflow is to have the PRs go through Travis to make 
> the job of the reviewer far easier. This is what is missing and slows closing 
> PRs. 
> 
> Cheers,
> Jignesh 
> 
>> On May 10, 2016, at 5:23 PM, Julian Hyde  wrote:
>> 
>> It’s a question of priority. Let’s not let the low priority stuff block the 
>> important stuff. Moving source control is urgent. I haven’t yet heard a 
>> reason why CI should delay moving source control.
>> 
>>> On May 10, 2016, at 3:15 PM, Jignesh Patel  wrote:
>>> 
>>> Dear Julian,
>>> 
>>> You do make a good point, but we have a very heavy reliance on the CI and 
>>> it will certainly help the transition. 
>>> 
>>> Since other Apache projects do have a Travis CI, Zuyu has reached out to 
>>> Roman to see if we can set this up. 
>>> 
>>> Agreed about the points that both you and Roman are making — we do need to 
>>> move fully to ASF soon. Thanks for your patience. 
>>> 
>>> Cheers,
>>> Jignesh 
>>> 
>>>> On May 9, 2016, at 1:27 AM, Julian Hyde  wrote:
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> On May 8, 2016, at 8:39 PM, Zuyu Zhang  wrote:
>>>>> 
>>>>> Yes, we need fix QUICKSTEP-2 before transiting to ASF.
>>>> 
>>>> I disagree. It is much more important that you use ASF infrastructure for 
>>>> source control than for CI, and the one does not block the other.
>>>> 
>>>> At Calcite it took a long time before we had CI running on ASF 
>>>> infrastructure. We continued to use Travis-CI, which we’d used before ASF.
>>>> 
>>>> As Roman says, it is important for IP hygiene that commits are made 
>>>> directly to ASF git, and the sooner you switch over the better. I think 
>>>> you can do that before you transition CI.
>>>> 
>>>> Julian
>>> 
>> 
> 

Re: When do you think you can fully transition to ASF infrastructure?

[Julian Hyde]

It’s a question of priority. Let’s not let the low priority stuff block the 
important stuff. Moving source control is urgent. I haven’t yet heard a reason 
why CI should delay moving source control.

> On May 10, 2016, at 3:15 PM, Jignesh Patel  wrote:
> 
> Dear Julian,
> 
> You do make a good point, but we have a very heavy reliance on the CI and it 
> will certainly help the transition. 
> 
> Since other Apache projects do have a Travis CI, Zuyu has reached out to 
> Roman to see if we can set this up. 
> 
> Agreed about the points that both you and Roman are making — we do need to 
> move fully to ASF soon. Thanks for your patience. 
> 
> Cheers,
> Jignesh 
> 
>> On May 9, 2016, at 1:27 AM, Julian Hyde  wrote:
>> 
>> 
>> 
>> 
>>> On May 8, 2016, at 8:39 PM, Zuyu Zhang  wrote:
>>> 
>>> Yes, we need fix QUICKSTEP-2 before transiting to ASF.
>> 
>> I disagree. It is much more important that you use ASF infrastructure for 
>> source control than for CI, and the one does not block the other.
>> 
>> At Calcite it took a long time before we had CI running on ASF 
>> infrastructure. We continued to use Travis-CI, which we’d used before ASF.
>> 
>> As Roman says, it is important for IP hygiene that commits are made directly 
>> to ASF git, and the sooner you switch over the better. I think you can do 
>> that before you transition CI.
>> 
>> Julian
> 

Re: When do you think you can fully transition to ASF infrastructure?

[Julian Hyde]

Regarding getting communication onto the ASF list. Rather than waiting until 
the perfect moment when everyone is on the Apache list, just tell developers to 
stop other channels, right now. Within hours the communication will have moved 
to the public list.

Regarding figuring out who has submitted what agreement, there are some useful 
links here:

https://people.apache.org/ <https://people.apache.org/>

But remember you don’t need to sign a CLA to join the dev list. Anyone can join.

I’m not sure why Quickstep is not showing up at 
https://people.apache.org/phonebook.html?podling=quickstep 
<https://people.apache.org/phonebook.html?podling=quickstep>. Other mentors, 
any ideas?

Julian


> On May 9, 2016, at 9:38 AM, Jignesh Patel  wrote:
> 
> Hi Julian,
> 
> I agree with the emails that moving faster is better. Working on it. 
> 
> Is there an easy way to see who has already signed the ICLA for Quickstep? 
> 
> Thanks! 
> Jignesh 
> 
>> On May 9, 2016, at 1:36 AM, Julian Hyde  wrote:
>> 
>> Also, how is the transition to Apache email lists going? I see a couple of 
>> commits per day going into git, and some discussion against pull requests, 
>> but no discussion on the dev list. Where is this discussion happening?
>> 
>>> On May 8, 2016, at 11:27 PM, Julian Hyde  wrote:
>>> 
>>> 
>>> 
>>> 
>>>> On May 8, 2016, at 8:39 PM, Zuyu Zhang  wrote:
>>>> 
>>>> Yes, we need fix QUICKSTEP-2 before transiting to ASF.
>>> 
>>> I disagree. It is much more important that you use ASF infrastructure for 
>>> source control than for CI, and the one does not block the other.
>>> 
>>> At Calcite it took a long time before we had CI running on ASF 
>>> infrastructure. We continued to use Travis-CI, which we’d used before ASF.
>>> 
>>> As Roman says, it is important for IP hygiene that commits are made 
>>> directly to ASF git, and the sooner you switch over the better. I think you 
>>> can do that before you transition CI.
>>> 
>>> Julian
>> 
> 

Re: When do you think you can fully transition to ASF infrastructure?

[Julian Hyde]

Also, how is the transition to Apache email lists going? I see a couple of 
commits per day going into git, and some discussion against pull requests, but 
no discussion on the dev list. Where is this discussion happening?

> On May 8, 2016, at 11:27 PM, Julian Hyde  wrote:
> 
> 
> 
> 
>> On May 8, 2016, at 8:39 PM, Zuyu Zhang  wrote:
>> 
>> Yes, we need fix QUICKSTEP-2 before transiting to ASF.
> 
> I disagree. It is much more important that you use ASF infrastructure for 
> source control than for CI, and the one does not block the other.
> 
> At Calcite it took a long time before we had CI running on ASF 
> infrastructure. We continued to use Travis-CI, which we’d used before ASF.
> 
> As Roman says, it is important for IP hygiene that commits are made directly 
> to ASF git, and the sooner you switch over the better. I think you can do 
> that before you transition CI.
> 
> Julian

Re: When do you think you can fully transition to ASF infrastructure?

[Julian Hyde]

> On May 8, 2016, at 8:39 PM, Zuyu Zhang  wrote:
> 
> Yes, we need fix QUICKSTEP-2 before transiting to ASF.

I disagree. It is much more important that you use ASF infrastructure for 
source control than for CI, and the one does not block the other.

At Calcite it took a long time before we had CI running on ASF infrastructure. 
We continued to use Travis-CI, which we’d used before ASF.

As Roman says, it is important for IP hygiene that commits are made directly to 
ASF git, and the sooner you switch over the better. I think you can do that 
before you transition CI.

Julian