Thanks Harshad! Great idea to work backwards on the list of things that we need 
to do for a release. I think the current guidelines for a release are at: 
https://incubator.apache.org/guides/release.html . I can take a shot at working 
backwards from it. 

We need all the help we can to build the community, so if you feel like you 
want to help in that way, please announce it on this list. Just want to make 
sure the discussion on this thread doesn’t end with this email ☺ 

Cheers,
Jignesh 

On 10/25/16, 11:07 AM, "Harshad Deshmukh" <hars...@cs.wisc.edu> wrote:

    Hi Jignesh,
    
    I can certainly help with #1 and #3.
    
    For #1, we can set up a release deadline and set up milestones in 
    reverse chronological order so that we can meet the deadline. Apache has 
    an elaborate documentation on the release procedure and hopefully that's 
    a good starting point.
    
    For #3, we can begin from participating in BigData Wisconsin meetups. 
     From what I know, there is a healthy interest in data management 
    systems in the meetup, I can volunteer to attend and present the system 
    over there.
    
    For #4, I agree with you. Some of our JIRA reports are really extensive 
    and describe the issues in detail. We probably need to bring some of the 
    content from JIRA issues to the dev list. From here on, I can try to 
    summarize in an email to the dev list, the features that I am currently 
    working on (or about to begin work on) and its impact on the system.
    
    
    On 10/25/2016 10:02 AM, Jignesh Patel wrote:
    > I’m hoping to get some feedback from the general developers list on 
potential outreach activities for the project. To set the background for this 
discussion, Quickstep became an Apache project earlier this year. Nearly all 
the people on the project are relatively new to the Apache way of doing things 
(I certainly am, and I’m still learning various aspect of the Apache way).
    >
    >   
    >
    > Our mentors have been very helpful and rightly point out that we need to 
do more by way of outreach. This would include (but not limited to) doing 
things like:
    >
    >   
    >
    > #1: Making a release
    >
    > #2: Writing blogs about the project
    >
    > #3: Going to meetups and conferences like Apache Con to make a 
presentation about the project (we can find ways to fund these meetings).
    >
    > #4: Using the dev list more actively, even if it is to discuss 
interesting observations that we make – e.g. tried the new Xcode, and ran into 
the following issues.
    >
    >   
    >
    > Note on #4, I personally feel that we have a lot of active discussions. 
But, our primary mechanism is via Jiras and the discussion on the PRs. They are 
quite lively at times, and it is fantastic that people express their views in a 
respectful way but are not shy to point out any critical comments that they may 
have. We need to keep doing this. All those comments do go to the dev lists, 
but we should also talk about other things like what we think would be great to 
work on next, and/or just announce what topics you may be working on.
    >
    >   
    >
    > So, the main question in this email is: Are there folks on this list who 
want to help with building the Quickstep community in the ways described above? 
If you are interested, can you let this group know what you might want to help 
with. Also free free to pitch any ideas that you may have to help build the 
community. The main point is to get more people excited about the project in 
any role (including developers, users, …) and to share responsibilities for the 
core direction of the project.
    >
    >   
    >
    > One concrete proposal is to go make a release in about a month. I’m happy 
to help with that. Anyone else wants to help out? Now you may ask – what does 
it take to do a release? I honestly don’t know. But, we have to go read up on 
that, bug the mentors, and figure it out. All that is part of helping build an 
Apache community.
    >
    >   
    >
    > Cheers,
    >
    > Jignesh
    >
    >   
    >
    >   
    >
    >   
    >
    >   
    >
    >
    
    -- 
    Thanks,
    Harshad
    
    


Reply via email to