Dear Chris and Mentors:

The team had a meeting to retrospect our Apache Incubator experience. We 
realized that the team has put a lot of intention to building the project but 
put insufficient efforts on fulfilling Apache requirements. Our deep apology 
from the team.

Now that we have understood the importance of following Apache procedure and 
smoothing and documenting all communications, we would like to ask for another 
chance to work on the incubator project. Say, we would ask for a three month of 
testing time frame. If we fail to meet the requirement, we will retire the 
project.

Please let us know your thoughts.

Best regards,
Jia

> On Jul 5, 2016, at 8:59 AM, Chris Mattmann <[email protected]> wrote:
> 
> As a mentor, this is a difficult decision for me. Overall, I am +1
> in favor of retiring the podling.
> 
> The podling has been given ample time to discuss and make use of 
> the Apache mentorship and community and its actions have shown that
> the mentality for development is unfortunately different. I believe
> it is in the best interests of both the community for CMDA and the 
> Apache community to retire the podling at this point in time.
> 
> Sincerely,
> Chris Mattmann
> 
> 
> 
>> On 7/5/16, 8:57 AM, "Martin Desruisseaux" <[email protected]> 
>> wrote:
>> 
>> Hello John
>> 
>> Sorry for the delay. I saw the thread and the call for the vote, but I'm
>> not sure to understand what "podling" means?
>> 
>>   Martin
>> 
>> 
>>> Le 03/07/16 à 15:27, John D. Ament a écrit :
>>> All,
>>> 
>>> There was a discussion recently [1] started by Chris about the state of the
>>> podling.  I'm concerned about lack of public activity, and what seems to be
>>> external forces who control the state of the podling.  As a result, I'm
>>> calling a vote to retire the CMDA podling.
>>> 
>>> [ ] +1 to retire CMDA from the Incubator
>>> [ ] -1 to keep CMDA in the Incubator
>>> 
>>> John
>>> 
>>> [1]:
>>> https://lists.apache.org/thread.html/3c341a6f977e1e650980fb0c66f8669e428c98bc2e8c130d6f948d21@%3Cdev.cmda.apache.org%3E
> 

Reply via email to