Thanks Julian! Good to know. 

Cheers,
Jignesh 

> On Jun 7, 2016, at 11:17 AM, Julian Hyde <[email protected]> wrote:
> 
> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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!
>>> 
>>> 
>> 
> 

Reply via email to