Hi Jukka,
Sorry missed this email.
> Sounds like you're doing pretty good, and congratulations for the
> release! I'm also happy to see many sign-offs on your report.
>
Thanks
>> + Issues that must be addressed before graduation are:
>> +
>> + - Making a release
>> + - Attracting users and
Yeah, am happy to be a mentor on Ambari.
Devaraj
On May 10, 2012, at 8:19 AM, Owen O'Malley wrote:
> On Thu, May 10, 2012 at 4:55 AM, Franklin, Matthew B.
> wrote:
>
> Also, I noticed that ddas signed off on it as a mentor. I don't see him
> listed
>>> as an Apache member or IPMC m
On Thu, May 10, 2012 at 4:55 AM, Franklin, Matthew B.
wrote:
Also, I noticed that ddas signed off on it as a mentor. I don't see him
listed
>>as an Apache member or IPMC member.
>>>
>>> He was added to the IPMC. The message from Noel was dated 6 Oct 2011.
>>
>>Note: he is currently li
>-Original Message-
>From: sebb [mailto:seb...@gmail.com]
>Sent: Thursday, May 10, 2012 6:47 AM
>To: general@incubator.apache.org
>Subject: Re: Ambari Status
>
>On 10 May 2012 06:05, Owen O'Malley wrote:
>> On Wed, May 9, 2012 at 5:56 PM, Franklin, Matthe
On 10 May 2012 06:05, Owen O'Malley wrote:
> On Wed, May 9, 2012 at 5:56 PM, Franklin, Matthew B.
> wrote:
>> In reviewing the Amabari report, I have a couple of notes/concerns:
>>
>> * The community IMHO is in serious risk of failure to launch. A recent
>> code change has sparked project inte
HI,
On Thu, May 10, 2012 at 7:16 AM, Owen O'Malley wrote:
> There is a new code base that was developed in private, which has
> momentum. It was checked in on to a development branch and the
> discussion started. I was hoping for some response to Suhas' message
> from someone outside of Hortonwor
Hey Guys,
OK, so it was developed in private, that'll need to be fixed, but it sounds like
you are pushing to have it brought out into the open, so good job here,
Owen.
If you need mentor help to nudge the project along, let me know and I will
be happy to scope and help out. I'll start out by jo
On Wed, May 9, 2012 at 6:40 PM, Jukka Zitting wrote:
> Sounds like the project community still needs to learn how to develop
> code out in the open. The massive revision 1335750 [1] seems to have
> been based on no open discussion on the mailing list or the issue
> tracker.
There is a new code b
On Wed, May 9, 2012 at 5:56 PM, Franklin, Matthew B.
wrote:
> In reviewing the Amabari report, I have a couple of notes/concerns:
>
> * The community IMHO is in serious risk of failure to launch. A recent code
> change has sparked project interest, but list activity was non existent after
> Ja
Hi,
Thanks for the review Matt!
On Thu, May 10, 2012 at 2:56 AM, Franklin, Matthew B.
wrote:
> * The community IMHO is in serious risk of failure to launch. A recent code
>change has
> sparked project interest, but list activity was non existent after January.
Sounds like the project communit
On 10 May 2012 01:56, Franklin, Matthew B. wrote:
> *As Ambari went nearly 2 months without a single e-mail to the list, I
> think an issue for graduation should be added that the community must
> demonstrate viability for X more reporting periods (where x IMO is > 2).
I just had a look at th
In reviewing the Amabari report, I have a couple of notes/concerns:
* The community IMHO is in serious risk of failure to launch. A recent code
change has sparked project interest, but list activity was non existent after
January.
*As Ambari went nearly 2 months without a single e-mail
12 matches
Mail list logo
