You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Jukka Zitting <ju...@gmail.com> on 2012/07/10 20:36:13 UTC

DirectMemory status (Was: Shepherding: chukwa, mesos, directmemory)

Hi,

On Sun, Jul 1, 2012 at 11:59 PM, Niall Pemberton
<ni...@gmail.com> wrote:
> On Sun, Jul 1, 2012 at 8:46 PM, Benson Margulies <bi...@gmail.com> wrote:
>> DirectMemory lacks only a release to be green across the launch control board.
>
> Looks like a release is imminent:
>     markmail.org/message/a3yczwysqognrtg4

The release is now out, so given Benson's overview from above I
classified DirectMemory as ready to graduate.

The DirectMemory report says the following on this topic:

+ There is only one important issue to address in the move towards graduation
+
+    - Understanding process/decision making guidelines (new committer process
+      is undergoing testing, release process still yet to be worked out)

I suppose the release process is now covered. I notice DirectMemory
has already added a committer since incubation started, so there's
already some experience on that as well. And with many Apache members
as committers I think the project is in any case pretty well covered
on the process side.

So from my perspective it looks like DirectMemory is close to
graduation. The only bit I'm a bit uncertain about is the "burstiness"
of DirectMemory activity (with notable spikes in November, February
and June), though that shouldn't be too troublesome as there's a
steady level of base activity and it looks like the June burst is
continuing well into this month.

Does that (and my classification as ready to graduate) sound like an
accurate assessment of DirectMemory status?

BR,

Jukka Zitting

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: DirectMemory status (Was: Shepherding: chukwa, mesos, directmemory)

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Jul 11, 2012 at 12:28 PM, Jukka Zitting <ju...@gmail.com> wrote:
> ...the shepherding model indeed is sort of middle-management that
> ideally wouldn't be needed...

FWIW, as a board member I find the summary that's been recently added
to the Incubator reports very useful, it makes it much easier to
concentrate on the important parts of the large Incubator report.

There's also value IMO in podlings discussing their respective
statuses on this list, as it makes them aware of other podling's
issues and solutions, which rarely happened before.

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: DirectMemory status (Was: Shepherding: chukwa, mesos, directmemory)

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Wed, Jul 11, 2012 at 4:13 AM, Tim Williams <wi...@gmail.com> wrote:
> On Tue, Jul 10, 2012 at 2:36 PM, Jukka Zitting <ju...@gmail.com> wrote:
>> Does that (and my classification as ready to graduate) sound like an
>> accurate assessment of DirectMemory status?
>
> I suppose.  Though, it's not clear why we're answering that question
> on general@ instead of letting the mentors run through the graduation
> guide with the community?  This list is chatty though, so perhaps I
> missed something?

I'm just verifying that I understood the report correctly. We're
providing a summary of the overall status of the Incubator in our
report to the board, and for that I need a rough indication of where
each podling stands in terms of progress towards graduation.

The intention is certainly not interfere with the work mentors are
doing as long as everything's fine, just to verify that everything
indeed is fine.

> FWIW, this shepherd thing is starting to feel like [duplicative]
> middle-management.  I'd strongly encourage a more passive board-style
> role (e.g. stepping in only when a problem exists).

Yes, the shepherding model indeed is sort of middle-management that
ideally wouldn't be needed. Unfortunately with lots of absent mentors
and podlings that were stuck in a limbo, there was a clear need to do
something about the situation. That's why there's recently been a
concentrated effort to review podling reports and status in much more
detail and provide feedback where needed. Once we have such problems
covered, we may well be able to fall back to a more passive mode of
operation.

In this case I just wanted to confirm that my understanding of the
project status based on the report and other available information was
correct. It seems like the mentors and the project in general are
doing all the right things, so I see no need to interfere further.
Apologies if my message implied otherwise.

BR,

Jukka Zitting

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: DirectMemory status (Was: Shepherding: chukwa, mesos, directmemory)

Posted by Tim Williams <wi...@gmail.com>.
On Tue, Jul 10, 2012 at 2:36 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Sun, Jul 1, 2012 at 11:59 PM, Niall Pemberton
> <ni...@gmail.com> wrote:
>> On Sun, Jul 1, 2012 at 8:46 PM, Benson Margulies <bi...@gmail.com> wrote:
>>> DirectMemory lacks only a release to be green across the launch control board.
>>
>> Looks like a release is imminent:
>>     markmail.org/message/a3yczwysqognrtg4
>
> The release is now out, so given Benson's overview from above I
> classified DirectMemory as ready to graduate.
>
> The DirectMemory report says the following on this topic:
>
> + There is only one important issue to address in the move towards graduation
> +
> +    - Understanding process/decision making guidelines (new committer process
> +      is undergoing testing, release process still yet to be worked out)
>
> I suppose the release process is now covered. I notice DirectMemory
> has already added a committer since incubation started, so there's
> already some experience on that as well. And with many Apache members
> as committers I think the project is in any case pretty well covered
> on the process side.
>
> So from my perspective it looks like DirectMemory is close to
> graduation. The only bit I'm a bit uncertain about is the "burstiness"
> of DirectMemory activity (with notable spikes in November, February
> and June), though that shouldn't be too troublesome as there's a
> steady level of base activity and it looks like the June burst is
> continuing well into this month.
>
> Does that (and my classification as ready to graduate) sound like an
> accurate assessment of DirectMemory status?

I suppose.  Though, it's not clear why we're answering that question
on general@ instead of letting the mentors run through the graduation
guide with the community?  This list is chatty though, so perhaps I
missed something?

FWIW, this shepherd thing is starting to feel like [duplicative]
middle-management.  I'd strongly encourage a more passive board-style
role (e.g. stepping in only when a problem exists).

The "burstiness", btw, is likely a result of this being a true
volunteer effort - AFAIK, no one's being paid to hack on it.

Thanks,
--tim

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org