You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by "John D. Ament" <jo...@apache.org> on 2017/09/25 20:33:21 UTC
Planning to remove rosters from active podlings
All,
This coming weekend (9/29) I plan to remove the roster sections from all
podling status pages.
Podling rosters are meant to be managed in Whimsy. The roster in the
status page is redundant and end up out of sync. In place of the roster, I
will be adding a link automatically to all podling rosters.
John
Re: Planning to remove rosters from active podlings
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
On Tue, Sep 26, 2017 at 1:53 PM, John D. Ament <jo...@apache.org> wrote:
> ...I'm not sure we care any longer if 20
> people sign up as committers, but only 5 show up...
I agree, I don't think we've ever really cared about initial
committers not showing up.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Planning to remove rosters from active podlings
Posted by "John D. Ament" <jo...@apache.org>.
There are some cross checks in the clutch report that indicate whether all
committers have accounts. It parses the HTML table to figure which rows in
the table don't have usernames.
At this point, the way I'm seeing it flow is we create the proposal with
the initial committers in the list. When they get accounts, it's up to the
new PPMC to add them appropriately. I'm not sure we care any longer if 20
people sign up as committers, but only 5 show up, unless there was no other
growth beyond those 5.
John
On Mon, Sep 25, 2017 at 11:02 PM Henri Yandell <ba...@apache.org> wrote:
> Cool - I was asked why the info was in the podling pages the other day and
> all I had was "history/legacy" as an answer.
>
>
> On Mon, Sep 25, 2017 at 13:33 John D. Ament <jo...@apache.org> wrote:
>
> > All,
> >
> > This coming weekend (9/29) I plan to remove the roster sections from all
> > podling status pages.
> >
> > Podling rosters are meant to be managed in Whimsy. The roster in the
> > status page is redundant and end up out of sync. In place of the
> roster, I
> > will be adding a link automatically to all podling rosters.
> >
> > John
> >
>
Re: Planning to remove rosters from active podlings
Posted by Henri Yandell <ba...@apache.org>.
Cool - I was asked why the info was in the podling pages the other day and
all I had was "history/legacy" as an answer.
On Mon, Sep 25, 2017 at 13:33 John D. Ament <jo...@apache.org> wrote:
> All,
>
> This coming weekend (9/29) I plan to remove the roster sections from all
> podling status pages.
>
> Podling rosters are meant to be managed in Whimsy. The roster in the
> status page is redundant and end up out of sync. In place of the roster, I
> will be adding a link automatically to all podling rosters.
>
> John
>
Re: Planning to remove rosters from active podlings
Posted by Dave Fisher <da...@comcast.net>.
+1.
Sent from my iPhone
> On Sep 25, 2017, at 1:33 PM, John D. Ament <jo...@apache.org> wrote:
>
> All,
>
> This coming weekend (9/29) I plan to remove the roster sections from all
> podling status pages.
>
> Podling rosters are meant to be managed in Whimsy. The roster in the
> status page is redundant and end up out of sync. In place of the roster, I
> will be adding a link automatically to all podling rosters.
>
> John
Re: Planning to remove rosters from active podlings
Posted by Dave Fisher <da...@comcast.net>.
+1.
Sent from my iPhone
> On Sep 25, 2017, at 1:33 PM, John D. Ament <jo...@apache.org> wrote:
>
> All,
>
> This coming weekend (9/29) I plan to remove the roster sections from all
> podling status pages.
>
> Podling rosters are meant to be managed in Whimsy. The roster in the
> status page is redundant and end up out of sync. In place of the roster, I
> will be adding a link automatically to all podling rosters.
>
> John
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Fwd: Planning to remove rosters from active podlings
Posted by Andy Seaborne <an...@apache.org>.
-------- Forwarded Message --------
Subject: Planning to remove rosters from active podlings
Date: Mon, 25 Sep 2017 20:33:21 +0000
From: John D. Ament <jo...@apache.org>
Reply-To: general@incubator.apache.org
To: general@incubator.apache.org <ge...@incubator.apache.org>
All,
This coming weekend (9/29) I plan to remove the roster sections from all
podling status pages.
Podling rosters are meant to be managed in Whimsy. The roster in the
status page is redundant and end up out of sync. In place of the roster, I
will be adding a link automatically to all podling rosters.
John
Re: Planning to remove rosters from active podlings
Posted by sebb <se...@gmail.com>.
Note that Whimsy detects changes to the JSON files it generates and
sends them to
notifications@whimsical.a.o
Since these are just diffs of the JSON files, it's not always
immediately obvious what group name is involved.
On 26 September 2017 at 01:46, Greg Stein <gs...@gmail.com> wrote:
> PPMC roster changes are captured in LDAP logs (not available to public),
> and in private@ email archives (not available to public).
>
> So we have the record. Maybe not in the form you/others may like, however.
>
> Cheers,
> -g
>
> ps. committee-info.txt records PMC changes in svn history
>
> On Mon, Sep 25, 2017 at 7:35 PM, Niclas Hedhman <ni...@hedhman.org> wrote:
>
>> Does that maintain history? Or will that then become a snapshot in "now"
>> time, and by time of graduation completely dropping mentors? IMHO, there
>> should be a record of community history over time, not only for podlings.
>>
>> Niclas
>>
>> On Tue, Sep 26, 2017 at 4:33 AM, John D. Ament <jo...@apache.org>
>> wrote:
>>
>> > All,
>> >
>> > This coming weekend (9/29) I plan to remove the roster sections from all
>> > podling status pages.
>> >
>> > Podling rosters are meant to be managed in Whimsy. The roster in the
>> > status page is redundant and end up out of sync. In place of the
>> roster, I
>> > will be adding a link automatically to all podling rosters.
>> >
>> > John
>> >
>>
>>
>>
>> --
>> Niclas Hedhman, Software Developer
>> http://polygene.apache.org - New Energy for Java
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Planning to remove rosters from active podlings
Posted by Greg Stein <gs...@gmail.com>.
PPMC roster changes are captured in LDAP logs (not available to public),
and in private@ email archives (not available to public).
So we have the record. Maybe not in the form you/others may like, however.
Cheers,
-g
ps. committee-info.txt records PMC changes in svn history
On Mon, Sep 25, 2017 at 7:35 PM, Niclas Hedhman <ni...@hedhman.org> wrote:
> Does that maintain history? Or will that then become a snapshot in "now"
> time, and by time of graduation completely dropping mentors? IMHO, there
> should be a record of community history over time, not only for podlings.
>
> Niclas
>
> On Tue, Sep 26, 2017 at 4:33 AM, John D. Ament <jo...@apache.org>
> wrote:
>
> > All,
> >
> > This coming weekend (9/29) I plan to remove the roster sections from all
> > podling status pages.
> >
> > Podling rosters are meant to be managed in Whimsy. The roster in the
> > status page is redundant and end up out of sync. In place of the
> roster, I
> > will be adding a link automatically to all podling rosters.
> >
> > John
> >
>
>
>
> --
> Niclas Hedhman, Software Developer
> http://polygene.apache.org - New Energy for Java
>
Re: Planning to remove rosters from active podlings
Posted by Niclas Hedhman <ni...@hedhman.org>.
Does that maintain history? Or will that then become a snapshot in "now"
time, and by time of graduation completely dropping mentors? IMHO, there
should be a record of community history over time, not only for podlings.
Niclas
On Tue, Sep 26, 2017 at 4:33 AM, John D. Ament <jo...@apache.org>
wrote:
> All,
>
> This coming weekend (9/29) I plan to remove the roster sections from all
> podling status pages.
>
> Podling rosters are meant to be managed in Whimsy. The roster in the
> status page is redundant and end up out of sync. In place of the roster, I
> will be adding a link automatically to all podling rosters.
>
> John
>
--
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java