No worries, no harm done! Cheers, Fokko
Op do 5 sep. 2019 om 22:17 schreef Julian Hyde <jh...@apache.org>: > Oops! We need to change our invite process so that we do not announce > committers before they have accepted. Sorry about that, Fokko. > > Julian > > > > On Sep 5, 2019, at 2:54 AM, Driesprong, Fokko <fo...@driesprong.frl> > wrote: > > > > Not to make things awkward, but I think it is already out in the open on > > the mailing list: > > > https://lists.apache.org/thread.html/b3a158e04b7ed2f4f958b6e86554e4a6794eca193736f1cf774eb8a9@%3Cgeneral.incubator.apache.org%3E > > > > Process wise, I haven't gotten any formal invite, so this makes it > > difficult to accept or decline. We might want to formalize this process a > > bit more. The process is described here > > <https://community.apache.org/newcommitter.html#new-committer-process>. > > Apart from that, I feel as well that Druid is nearing graduation. > > > > Cheers, Fokko Driesprong > > > > Op wo 4 sep. 2019 om 21:58 schreef Julian Hyde <jh...@apache.org>: > > > >> It’s probably better to wait until they have accepted. It would be > >> embarrassing if they declined. > >> > >> As every CFO knows, it’s good to defer the reporting of revenue… you > have > >> something positive in the bag to add to the next report. > >> > >> Julian > >> > >> > >>> On Sep 3, 2019, at 8:40 PM, David Lim <david...@apache.org> wrote: > >>> > >>> Thanks Jon, looks good. > >>> > >>> I think it's okay to mention that we have voted on and extended > >> invitations > >>> to two additional committers and are awaiting their acceptance (without > >>> mentioning them by name). > >>> > >>> On Tue, Sep 3, 2019 at 5:13 PM Jonathan Wei <jon...@apache.org> wrote: > >>> > >>>> Hi all, > >>>> > >>>> I've prepared the following podling report draft, and I am planning to > >>>> submit it before the deadline tomorrow. > >>>> > >>>> Please take a look and let me know 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. Resolve trademark issues > >>>> > >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > >>>> aware of? > >>>> > >>>> We will need to resolve the trademark issues before graduation, which > >> the > >>>> board has been made aware of privately. We are grateful for the > board's > >>>> support, and we will work with trademarks@ to resolve the issues. > >>>> > >>>> How has the community developed since the last report? > >>>> > >>>> - A healthy, constant flow of bug fixes, quality improvements and new > >>>> features are still ongoing at > https://github.com/apache/incubator-druid > >> . > >>>> - Two Druid community meetups have been scheduled on 9/17 and 9/19. > >>>> > >>>> How has the project developed since the last report? > >>>> > >>>> - Since the last report, we have had a total of 293 commits from 30 > >>>> contributors. > >>>> - The project website has been migrated to Apache infrastructure. > >>>> - We have released 2 versions, 0.15.0 and 0.15.1. > >>>> - We have code frozen the upcoming 0.16.0 release branch and are > >> preparing > >>>> the first 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.15.1-incubating was released on Aug 15, 2019. > >>>> > >>>> When were the last committers or PPMC members elected? > >>>> > >>>> The Druid PPMC elected 10 new committers to the project on November > 20, > >>>> 2018. > >>>> > >>>> 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. > >>>> > >>>> Julian has continued to be very helpful. > >>>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > >> For additional commands, e-mail: dev-h...@druid.apache.org > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > >
