Re: Graduation concerns

Thanks Ted. Echoing some of the followup discussion we had over on the HAWQ mailing list Roman suggested doing something similar to what Groovy did, i.e. incorporate a maturity model document into our code and review it around how we can continue to make improvements and move the project towards

Re: Graduation concerns

Thanks Ted, Niall, Caleb and Roman for helping on this thread... Sharing a bit of Geode, we do have a Maturity Level wiki page [1] since June, which reflects the current status of the project as well as a Community Development [2] page also frequently updated with all developments and efforts,

Re: Graduation concerns

On Wed, Nov 4, 2015 at 7:13 PM, Roman Shaposhnik wrote: > To echo Caleb's post to the HAWQ ML: > > In case you haven't been watching the Apache general list there is an > interesting thread on the Apache Sentry project and their graduation from > incubator. > > >

Re: Graduation concerns

Also note that projects that evolve out of commercial projects often have a very hard time moving design decisions to a mailing. It is much more natural to continue using well known communication paths. The point, however, of moving to Apache is, well, moving to Apache. That involves more than

Re: Graduation concerns

On Wed, Nov 4, 2015 at 8:26 PM, Niall Pemberton wrote: > On Wed, Nov 4, 2015 at 7:13 PM, Roman Shaposhnik wrote: > >> To echo Caleb's post to the HAWQ ML: >> >> In case you haven't been watching the Apache general list there is an >> interesting thread

Graduation concerns

To echo Caleb's post to the HAWQ ML: In case you haven't been watching the Apache general list there is an interesting thread on the Apache Sentry project and their graduation from incubator. http://mail-archives.apache.org/mod_mbox/incubator-general/201511.mbox/browser Lots of discussion on