Hi Roman, We have confirmed with each HAWQ committer whether they want to remain with HAWQ project. As a summary, 37 PPMC members(including two mentors) and 7 committers confirmed they want to remain with HAWQ. [1] The total committers number 44 seems pretty close with PPMC member number 37, is it good enough to make PMC == committers as our graduation resolution? Should we update the whimsy and project webpage now or do update after graduation?
BTW, please kindly advice the next steps towards graduation? Thanks. [1] https://lists.apache.org/thread.html/4f31f2766ed6963f845ac4034163db542c7895cf7f4b7dfcaeedfb8c@%3Cdev.hawq.apache.org%3E Regards, Radar On Fri, May 4, 2018 at 2:26 PM, Radar Lei <r...@pivotal.io> wrote: > Thanks Alan, this is very helpful. It would be great we still can have > mentors to stay as HAWQ PMC members. > > I'd volunteer to proceed and collect all the current committers's > responds. I plan to send the email to dev list after this weekend, and then > send individual emails to other committers and our mentors one week after. > > Regards, > Radar > > On Fri, May 4, 2018 at 2:18 AM, Alan Gates <alanfga...@gmail.com> wrote: > >> On Thu, May 3, 2018 at 1:14 AM, Radar Lei <r...@pivotal.io> wrote: >> >> > Hi Roman, >> > >> > Thanks for your recognition and suggestion. >> > >> > Would you please give some guidance on: >> > >> > 1. Currently we have more than 50 committers on the list, should we send >> > email to each committer individually to get their confirmation? Or we >> can >> > just send one public email to ask in private/dev list? >> > >> Start with an email to the dev list. 80% of the people who are going to >> respond will respond there. After a few days send individual emails to >> those who don't respond on the dev list. >> >> >> >> > 2. What if someone want to keep to be a committer but not be a PMC >> member? >> > >> That's fine, if it's what they want. But you'll need to note that >> clearly >> when we write up the graduation resolution as there may be questions on >> why >> different people are being granted different status. >> >> >> > >> > 3. What if we can not get respond from some committers in time? E.g. one >> > week. >> > >> I would include in the email a time limit, probably closer to two weeks >> than one so that anyone who is on vacation has a better chance of seeing >> it. That two weeks can be from the time you send the original email on >> the >> dev list. Anyone who does not respond in the given time frame will be >> assumed to not want to continue with HAWQ. >> >> As another note, it is traditional to ask the mentors if they wish to stay >> on as PMC members. For new projects I think it is very valuable to have >> at >> least one experienced Apache person on the PMC, even if he or she is not >> contributing code. >> >> Alan. >> >> >> > >> > >> > >> > Regards, >> > Radar >> > >> > On Wed, May 2, 2018 at 5:40 AM, Roman Shaposhnik <ro...@shaposhnik.org> >> > wrote: >> > >> > > I think in general it makes sense to me. Looking at: >> > > http://incubator.apache.org/projects/hawq.html >> > > I'd like to suggest that perhaps you may want to >> > > explicitly ask folks on the committers list whether >> > > they wish to remain with the project or not (I suspect >> > > some of them will decline the invitation -- but perhaps >> > > I'm wrong). >> > > >> > > If the list of committers will match the list of PPMC >> > > closes -- then I'd also suggest considering making >> > > PMC == committers as part of your graduation >> > > resolution. >> > > >> > > Other than that -- I think you will make a great community. >> > > >> > > Thanks, >> > > Roman. >> > > >> > > On Sat, Apr 28, 2018 at 4:02 AM, 刘奎恩(局外) <kuien....@alibaba-inc.com> >> > > wrote: >> > > > Great news, I have no reason to reject this wonderful idea. One >> > > consideration is may we have time window to do a bit more efforts on >> > > execuation engine? because these derivative startup projects (hawq+, >> > > deepgreen) all claims their superiority on execuation engine. Maybe, >> Hawq >> > > may co-plan it with Greenplum, it is one common issue in both data >> > > warehouse. >> > > > -------------—— >> > > > Kuien Liu/奎恩 >> > > > ------------------------------------------------------------ >> > ------发件人：Radar >> > > Lei <r...@pivotal.io>发送时间：2018年4月26日(星期四) 10:16收件人：dev < >> > > dev@hawq.incubator.apache.org>主 题：[DISCUSS] Apache HAWQ Graduation >> from >> > > Incubator >> > > > Hi All, >> > > > >> > > > With the Apache HAWQ community keep healthy and growing, I think now >> > > would >> > > > be a good time to discuss where we stand regarding to graduation >> from >> > the >> > > > Incubator, and what requirements remains. >> > > > >> > > > Apache HAWQ entered incubation in September of 2015, since then, the >> > HAWQ >> > > > community learned a lot about how to do things in Apache ways. Now >> we >> > > are a >> > > > very helpful and engaged community, ready to help on all questions >> > > > from the HAWQ >> > > > community. We delivered four releases including two binary releases, >> > now >> > > we >> > > > can do self-driving releases in good cadence. The community is >> growing, >> > > > new committers and PPMC members keep joining. We addressed the >> > maturity >> > > > issues one by one followed by Apache Project Maturity Model [1], >> > > currently all >> > > > the License and IP issues we can see got resolved. >> > > > >> > > > Base on those, I believes it's time for us to graduate to TLP. [2] >> > > > >> > > > Any thoughts? And welcome advice from HAWQ Mentors? >> > > > >> > > > Thanks, >> > > > >> > > > [1] https://cwiki.apache.org/confluence/display/HAWQ/ASF+ >> > > Maturity+Evaluation >> > > > [2] https://incubator.apache.org/guides/graduation.html#grad >> > > > uating_to_a_top_level_project >> > > > >> > > > Regards, >> > > > Radar >> > > >> > >> > >
