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" <jmp.quicks...@gmail.com> wrote:

    Good tips Julian! 
    
    Cheers,
    Jignesh  
    
    On 2/9/18, 6:00 PM, "Julian Hyde" <jh...@apache.org> 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 <jmp.quicks...@gmail.com> 
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
        > 
        > 
        > 
        
        
    
    


Reply via email to