I've updated the wiki with the contents posted above, for the new section
"Is the PPMC managing the podling's brand / trademarks?", I've put the
following:

> There has been recent discussion/activity regarding trademarks on the
podling's private mailing list.

On Tue, Dec 3, 2019 at 5:22 PM Jonathan Wei <jon...@apache.org> wrote:

> Hi all,
>
> I've written a draft for the upcoming podling report, please comment if
> you have any feedback.
>
> ========
>
> Druid is a high-performance, column-oriented, distributed data store.
>
> Druid has been incubating since 2018-02-28.
>
> Three most important issues to address in the move towards graduation:
>
>  1. No major issues
>
> 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?
>  - 2 new committers have been added
>  - A healthy, constant flow of bug fixes, quality improvements and new
> features are still ongoing at https://github.com/apache/incubator-druid.
>  - Several community meetups have been held.
>
> How has the project developed since the last report?
>  - Since the last report, we have had a total of 187 commits from 34
> contributors.
>  - We have released 1 version, 0.16.0.
>  - We currently have a vote open for 0.16.1, second release candidate
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>  [ ] Initial setup
>  [ ] Working towards first release
>  [ ] Community building
>  [X] Nearing graduation
>  [ ] Other:
>
> Date of last release:
>
>  - Druid 0.16.0-incubating was released on Sep 24, 2019.
>
> When were the last committers or PPMC members elected?
>
>  The Druid PPMC elected 2 new committers to the project on September 22,
>  2019.
>
>  The previous Sep 2019 report was incorrect here, as the two committers
> were not yet officially elected then.
>
> Have your mentors been helpful and responsive or are things falling
> through the cracks? In the latter case, please list any open issues
> that need to be addressed.
>
>  As always, Julian has been quite helpful.
>

Reply via email to