Thanks for setting this up Leonidas. As for the important issues, it seems to me that you all have added more requirements to graduation than are "necessary".
1. It seems to me that if everyone in the original committers list is reasonably active then you've already achieved diversity. 2. A release would be good only because it vets the contribution and project organization. 3. I don't think that performance is required at all to graduate. With that said, have you guys looked into what are the bare minimum requirements? I think that you would be surprised at how little there is. Let's make a concrete check list. Can someone pick that up? Regards, Alan On Jun 4, 2013, at 5:11 PM, Leonidas Fegaras <[email protected]> wrote: > OK. The June report is now in the wiki. > If you are an MRQL mentor and you approve it, please go to the MRQL section in > http://wiki.apache.org/incubator/June2013 > and put an [X] next to your name. > Leonidas > > > On 06/04/2013 12:56 PM, Leonidas Fegaras wrote: >> I have written the first draft. Please review and make corrections. I will >> upload it to the site tonight. >> Leonidas >> >> >> >> MRQL >> >> MRQL is a query processing and optimization system for large-scale, >> distributed data analysis, built on top of Apache Hadoop and Hama. >> >> MRQL has been incubating since 2013-03-13. >> >> Three most important issues to address in the move towards graduation: >> >> 1. Expand the development community to include more diverse committers >> 2. Complete the first release >> 3. Improve query performance on large clusters >> >> 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? >> >> We have posted a project description on the HadoopSphere blog, which >> initiated some discussion and interest. Since the last report, there >> was little activity in recruiting new users and developers, but we are >> very close to completing the first release. We believe that, as soon >> as we make the first release available, many users will start using >> the system, will request bug fixes, improvements, and additional >> functionality, and will become new contributors. >> >> How has the project developed since the last report? >> >> We are in the process of completing the MRQL codebase to make it ready >> for the first release, which we expect to take place in the next few >> weeks. The only major component missing that delays this release is >> switching to maven as our project management tool. We believe that >> using maven is important because it will facilitate contributions by >> (and recruitment of) committers and will ease version management. The >> reasons for the delay are: 1) no one of the current developers has >> prior experience with maven 2) the codebase is non-standard because it >> uses non-standard tools to generate Java code. >> >> Date of last release: >> >> none yet >> >> Please check this [ ] when you have filled in the report for MRQL. >> >> Signed-off-by: >> Alan Cabrera: [ ](mrql) >> Anthony Elder: [ ](mrql) >> Alex Karasulu: [ ](mrql) >> Mohammad Nour El-Din: [ ](mrql) >> >> . >> >
