My feeling is no, just because it isn't directly asked about. However, my feeling is not very strong.
Here are some of our plans, for the record: For community growth, various PMC members are busily tagging issues as "newbie" right now. Once that's done, I will post about that to dev@ and user@. I'm also going to propose we blog and tweet about "newbie" issues. For documentation, John Russell, one of our PMC members, and Laurel Hale, another community member who is going to assist, have already started working on this. The mechanics aren't all worked out, but the documentation is buildable. Questions remain about where in git the docs source will go, how it will be rendered, and so on. For migration of pre-commit CI, Taras Bobrovytsky, one of our PMC members, is working on duplicating Apache Kudu's Jenkins setup. On Wed, Oct 26, 2016 at 2:39 PM, Tim Armstrong <[email protected]> wrote: > Looks good, thanks for writing this up (and all the work that went into > those accomplishments). > > Is it worth mentioning what we plan to do about the top three issues? > > On Wed, Oct 26, 2016 at 2:34 PM, Jim Apple <[email protected]> wrote: > >> Dear dev@ and mentors: >> >> Here is my draft of our next status report. Your feedback is welcomed. >> I plan to post this in about 48 hours. >> >> Impala is a high-performance C++ and Java SQL query engine for data >> stored in Apache Hadoop-based clusters. >> >> > * A list of the three most important issues to address in the move >> > towards graduation. >> >> The three most important issues are: >> >> * Community growth >> >> * Transition of user documentation to Apache hosting >> >> * Migration of pre-commit continuous integration testing to >> publicly-available infrastructure >> >> > * Any issues that the Incubator PMC or ASF Board might wish/need to be >> > aware of >> >> No >> >> > * How has the community developed since the last report >> >> Our last report was in August. Since then, we have five new >> contributors who have authored patches, while two relatively recent >> contributors who were active before August have continued their >> involvement by authoring new patches. Traffic to our developer mailing >> list has grown by about 60%. >> >> > * How has the project developed since the last report. >> >> There have been 241 commits since the last report. >> >> Our status website now has 16 of the 17 listed work items complete. We >> had our first Apache release and have a wiki page describing how to >> perform the release in detail. We scrubbed our code using the RAT tool >> for copyright notices not compliant with the ASF rules. We wrote >> guidelines for contributors on how to become a committer and added a >> new committer. All developer documentation has now moved to the >> Apache-hosted wiki. >>
