incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré>
Subject Re: [DRAFT] Incubator PMC Board Report - August 2016
Date Mon, 08 Aug 2016 19:04:45 GMT
Hi John,

I've probably missed your ping. That's right that last month I didn't 
sign for two reasons:
1. the report was empty
2. I don't see lot of activity on the BatchEE project:
2.1. There are some commits 
( but not 
super active
2.2. Same for the mailing lists:

I'm not sure that BatchEE can be a project by its own as I'm not sure we 
have a community around (especially an user community).
I agree with Romain that BatchEE could be part of a kind of umbrella 
If we have good sign that we have an user community around, then it 
makes sense to discuss about graduation.


On 08/08/2016 05:57 PM, John D. Ament wrote:
> Romain,
> I've actually been pushing to get BatchEE to graduate for some time.  IMHO
> there's no more benefit in the incubator for you guys.
> I'm pointing out the issue, as last month a mentor refused sign off due to
> lack of content in your report.  The current report doesn't seem to be much
> better.  I pinged JB off list, so far no answer there either.
> - John
> On Mon, Aug 8, 2016 at 11:49 AM Romain Manni-Bucau <>
> wrote:
>> Hi John,
>> Think we can be blamed to not have answered you but we took actions in
>> general. That said Mark was more pointing out that if there are issues with
>> the content it should probably be sent to batchee too explaining why and
>> what is expected/how we can enhance it. Typically this time you pointed out
>> it was "too empty" for you but I'm not sure there is a list I'm not aware
>> of but it would have been completely silently ignored cause batchee@
>> wouldn't have been notified of that.
>> More generally it is quite hard to fill this report for stable projects
>> (which doesn't mean they are not alive but just they are stable enough to
>> not get as much activity as BigData projects ;)). I'm not sure we should
>> group them either in a new umbrella project or an existing one - typically
>> we could create an inconsistent bucket in term of user communities but
>> consistent in term of maintainers/asf guys - or just keep it like that but
>> this "issue" will come back regularly I think and it would be great to
>> "skip" these round trips if possible and have a clear statement about
>> projects having by design an irregular activity - thinking to EE projects
>> which have a big activity after spec releases then mainly just maintenance
>> until next round.
>> You probably guessed that I would love to avoid to let small projects be
>> swallowed by bigger projects to skip this kind of lifecycle/activity issue
>> and avoid to create inconsistent (user) communities but I have to admit I
>> don't have a good view of the incubator freedom we can have on that area.
>> Romain Manni-Bucau
>> @rmannibucau <> |  Blog
>> <> | Old Wordpress Blog
>> <> | Github <
>>> |
>> LinkedIn <> | Tomitriber
>> <> | JavaEE Factory
>> <>
>> 2016-08-08 17:22 GMT+02:00 John D. Ament <>:
>>> On Mon, Aug 8, 2016 at 3:47 AM Mark Struberg <>
>>> wrote:
>>>> John, others. Would you please also add in the BatchEE amendments I did
>>>> today.
>>> Next time a draft is sent, it will be picked up (its just copy and
>> paste).
>>>> The feedback mechanism is great but we could improve this by also
>> sending
>>>> a mail to the respective podling if you have feedback.
>>> I know that I've personally sent feedback/questions to BatchEE before,
>>> without any response from the podling.
>>> - John
>>>> That way we could fix left-overs and missed paragraphs much easier.
>>>> txs and LieGrue,
>>>> strub
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail:
>>>> For additional commands, e-mail:

Jean-Baptiste Onofré
Talend -

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message