Thanks for updating the report, Luke.

Will sign it off.

On Tue, Feb 3, 2015 at 7:50 AM, Luke Han <[email protected]> wrote:
> Dear mentors,
>       Kylin's report has been updated in Feb report:
> http://wiki.apache.org/incubator/February2015
>
>       Please help to review and let's know if there's any issue.
>
> Thanks.
> Luke
>
>
> ========Text Copy===========
>
> --------------------
> Kylin
>
> Kylin is a distributed and scalable OLAP engine built on Hadoop to support
> extremely large datasets.
>
> Kylin has been incubating since 2014-11-25.
>
> Three most important issues to address in the move towards graduation:
>
>   1.Make the first release from apache
>   2.Discuss and decide on a medium-term roadmap
>   3.Grow user and contributor base.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   * Nothing
>
> How has the community developed since the last report?
>
>   1. Kylin topic has been confirmed to present at Strata+Hadoop World 2015
> London,
> also proposed to HBaseCon, Hadoop Summit and Big Data Technology Conference
> 2015 Beijing
>   2. Offical twitter account created: @ApacheKylin
>     * Followers 173
>   3. Issue backlog status since last report:
>     * Created:   587 (including imported from github.com)
>     * Resolved:  283 (including imported from github.com)
>   4. Mailing list activity since last report:
>     * @dev      227 messages
>   5. Github activity:
>     * Star 405
>     * Fork 172
>     * Contributors 17
>
> How has the project developed since the last report?
>
>   1. Kylin website is available on http://kylin.incubator.apache.org
>   2. Making changes in build and packaging with respect to apache release
> process
>   3. Development are happening on v0.7.1 version which we are preparing for
> first release.
>
> Date of last release:
>
>     None yet.
>
> When were the last committers or PMC members elected?
>
>     NONE
>
> Signed-off-by:
>
>   [ ](kylin) Owen O'Malley
>   [ ](kylin) Ted Dunning
>   [ ](kylin) Henry Saputra
>
> Shepherd/Mentor notes:
>
>
>
> Best Regards!
> ---------------------
>
> Luke Han
>
> 2015-02-03 0:46 GMT+08:00 Marvin <[email protected]>:
>
>>
>>
>> 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 February 2015, 10:30 am PST.
>> 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, Feb 4th).
>>
>> 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/February2015
>>
>> 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
>>
>>

Reply via email to