You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Marvin Humphrey <ma...@rectangular.com> on 2015/05/27 01:35:11 UTC
June report prep
Greets,
For June, Ted and I have arranged to split the duties of Report Manager. Ted
will execute most technical aspects, with support from general@incubator.
I'll take point on creating the freeform narrative content at the top of the
report, subject to the Chair's editorial oversight.
The responsibilities of the Report Manager are documented using a script,
report_runbook.py, which generates all the necessary commands. Ted, please
try running this from a checkout of the Incubator Subversion repo:
python3 report_runbook.py --month=6 --apache-id=tdunning
The first action of the June report cycle is to send the "timeline" email to
general@incubator. This should be done by the last Wednesday of the month,
so that people see it a full week before podling reports are due. Here's
a sample:
http://markmail.org/thread/xelqzblvvc5s4vy3
Please feel free to ask any questions you may have on this thread.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Luke Han <lu...@gmail.com>.
Thanks Ted, this is more clear now.
You are right, to have monthly summary is also very important to share such
information in project community,
and it's good start point for people learn more about that project when
they joined a new community
Thanks.
Best Regards!
---------------------
Luke Han
2015-05-29 16:23 GMT+08:00 Ted Dunning <te...@gmail.com>:
> Incubator projects start with monthly reporting and then switch to
> quarterly after the first few reports.
>
> I think that it is very helpful to do a bit of the report each month even
> after switching to quarterly reporting because it is hard to remember
> everything that has happened after 3 months. Even just making a few notes
> each week is a good thing.
>
> This is also a good opportunity to build community if you spread around the
> writing of those few lines. Starting with super easy contributions like
> that often leads to much more significant contributions later.
>
>
>
>
> On Fri, May 29, 2015 at 12:40 AM, Luke Han <lu...@gmail.com> wrote:
>
> > What's the rotation rule of all incubator projects? I found our project
> in
> > May's report but not on June
> > Would like to know that and get ready for coming report.
> >
> > Thank you very much.
> > Luke
> >
> >
> > Best Regards!
> > ---------------------
> >
> > Luke Han
> >
> > 2015-05-28 6:04 GMT+08:00 Marvin Humphrey <ma...@rectangular.com>:
> >
> > > On Tue, May 26, 2015 at 8:38 PM, Ted Dunning <te...@gmail.com>
> > > wrote:
> > > > On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey
> > > > <ma...@rectangular.com> wrote:
> > >
> > > >> The first action of the June report cycle is to send the "timeline"
> > > >> email to general@incubator. This should be done by the last
> > > >> Wednesday of the month, so that people see it a full week before
> > > >> podling reports are due. Here's a sample:
> > > >
> > > > Yay!
> > > >
> > > > With the correct version of python, this now works for me. We won't
> > > > know what problems I had before, but I don't plan to care too much.
> > >
> > > Thanks, Ted -- looks good!
> > >
> > > And I'm glad that you sent it out, because it seems that "the other
> > > Marvin" flaked again and the per-podling reminder emails have not fired
> > > yet. That's not something that the Report Manager is responsible for,
> > > though -- it's something the Incubator relies on individual volunteers
> > > to monitor.
> > >
> > > If the automatic reminders haven't fired by tomorrow, I'll send out
> > > manual reminders again.
> > >
> > > Marvin Humphrey
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
>
Re: June report prep
Posted by Ted Dunning <te...@gmail.com>.
Incubator projects start with monthly reporting and then switch to
quarterly after the first few reports.
I think that it is very helpful to do a bit of the report each month even
after switching to quarterly reporting because it is hard to remember
everything that has happened after 3 months. Even just making a few notes
each week is a good thing.
This is also a good opportunity to build community if you spread around the
writing of those few lines. Starting with super easy contributions like
that often leads to much more significant contributions later.
On Fri, May 29, 2015 at 12:40 AM, Luke Han <lu...@gmail.com> wrote:
> What's the rotation rule of all incubator projects? I found our project in
> May's report but not on June
> Would like to know that and get ready for coming report.
>
> Thank you very much.
> Luke
>
>
> Best Regards!
> ---------------------
>
> Luke Han
>
> 2015-05-28 6:04 GMT+08:00 Marvin Humphrey <ma...@rectangular.com>:
>
> > On Tue, May 26, 2015 at 8:38 PM, Ted Dunning <te...@gmail.com>
> > wrote:
> > > On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey
> > > <ma...@rectangular.com> wrote:
> >
> > >> The first action of the June report cycle is to send the "timeline"
> > >> email to general@incubator. This should be done by the last
> > >> Wednesday of the month, so that people see it a full week before
> > >> podling reports are due. Here's a sample:
> > >
> > > Yay!
> > >
> > > With the correct version of python, this now works for me. We won't
> > > know what problems I had before, but I don't plan to care too much.
> >
> > Thanks, Ted -- looks good!
> >
> > And I'm glad that you sent it out, because it seems that "the other
> > Marvin" flaked again and the per-podling reminder emails have not fired
> > yet. That's not something that the Report Manager is responsible for,
> > though -- it's something the Incubator relies on individual volunteers
> > to monitor.
> >
> > If the automatic reminders haven't fired by tomorrow, I'll send out
> > manual reminders again.
> >
> > Marvin Humphrey
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
Re: June report prep
Posted by Luke Han <lu...@gmail.com>.
What's the rotation rule of all incubator projects? I found our project in
May's report but not on June
Would like to know that and get ready for coming report.
Thank you very much.
Luke
Best Regards!
---------------------
Luke Han
2015-05-28 6:04 GMT+08:00 Marvin Humphrey <ma...@rectangular.com>:
> On Tue, May 26, 2015 at 8:38 PM, Ted Dunning <te...@gmail.com>
> wrote:
> > On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey
> > <ma...@rectangular.com> wrote:
>
> >> The first action of the June report cycle is to send the "timeline"
> >> email to general@incubator. This should be done by the last
> >> Wednesday of the month, so that people see it a full week before
> >> podling reports are due. Here's a sample:
> >
> > Yay!
> >
> > With the correct version of python, this now works for me. We won't
> > know what problems I had before, but I don't plan to care too much.
>
> Thanks, Ted -- looks good!
>
> And I'm glad that you sent it out, because it seems that "the other
> Marvin" flaked again and the per-podling reminder emails have not fired
> yet. That's not something that the Report Manager is responsible for,
> though -- it's something the Incubator relies on individual volunteers
> to monitor.
>
> If the automatic reminders haven't fired by tomorrow, I'll send out
> manual reminders again.
>
> Marvin Humphrey
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: June report prep
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Tue, May 26, 2015 at 8:38 PM, Ted Dunning <te...@gmail.com>
wrote:
> On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey
> <ma...@rectangular.com> wrote:
>> The first action of the June report cycle is to send the "timeline"
>> email to general@incubator. This should be done by the last
>> Wednesday of the month, so that people see it a full week before
>> podling reports are due. Here's a sample:
>
> Yay!
>
> With the correct version of python, this now works for me. We won't
> know what problems I had before, but I don't plan to care too much.
Thanks, Ted -- looks good!
And I'm glad that you sent it out, because it seems that "the other
Marvin" flaked again and the per-podling reminder emails have not fired
yet. That's not something that the Report Manager is responsible for,
though -- it's something the Incubator relies on individual volunteers
to monitor.
If the automatic reminders haven't fired by tomorrow, I'll send out
manual reminders again.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Ted Dunning <te...@gmail.com>.
Well, I do have to say that my impressions are based on an accelerated reading of the dev list, but I really didn't see much attention paid to issues like the preparation of the report, posting a vote result email to the right place and so on. More importantly as far as my impression is concerned I really didn't see much reaction to correction. What I have seen in other communities in incubation has been any of several reactions from disputing requirements, shock that they had missed a step, or some other indication of attachment to what is happening. It is very hard to quantify or point to but I really got sort of a dissociated feeling from the mailing list, almost as if the action was happening somewhere else and the mailing list was peripheral. For that matter, I didn't see design discussions much at all and only saw one external question which was shut down with a "we don't plan to do this, maybe someday" instead of the more customary and inviting "we don't do this bit would love to hear your thoughts and possibly an implementation".
On the positive side, release reviews appear to be checking the right things, although not holding a vote on general@ negates such virtues.
Sent from my iPhone
On Jun 5, 2015, at 20:23, Patrick Hunt <ph...@apache.org> wrote:
>> They seem oblivious to process issues
>
> Are there specific process issues that are missing and should hold up a
> vote? I see alot of process related details on their wiki
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Ted Dunning <te...@gmail.com>.
We can omit (my tendency) or publish with notes. I think just including a
note saying that there was an issue on Sentry that is being dealt with
aggressively and which will be reported on monthly for a bit is
sufficient. The board needs to know that they know everything they need to
know. A half done report is effectively misleading. Besides, David will
be at the meeting to provide any necessary back story.
I owe the group a draft of the entire report (instantly) in any case.
On Tue, Jun 9, 2015 at 6:53 PM, John D. Ament <jo...@apache.org> wrote:
> So, I hate to bring this up, but I think we're at a stalemate for the
> sentry podling for this month. We tend to not include a podlings report if
> there are no mentor sign offs. It seems like the mentors aren't inclined
> to sign off based on some of the issues that have popped up.
>
> On Mon, Jun 8, 2015 at 12:35 PM Patrick Hunt <ph...@apache.org> wrote:
>
> > Hi David, you and Joe have been doing great, I'm afraid I've been
> > distracted with more issues at home/work than usual. I've been
> > concerned, and this is more serious than usual given the fact that
> > both the community and the oversight missed a serious issue, but given
> > the current feedback and the response (ongoing) from the community we
> > should be able to get things back on track.
> >
> > Thanks,
> >
> > Patrick
> >
> > On Sat, Jun 6, 2015 at 3:14 PM, David Nalley <da...@gnsa.us> wrote:
> > > On Fri, Jun 5, 2015 at 3:23 PM, Patrick Hunt <ph...@apache.org> wrote:
> > >> Ted can you give some concrete examples, because I see some good
> > feedback
> > >> along with folks attempting to address the feedback. Processes updated
> > or
> > >> re-iterated, etc... I haven't seen any comments like "stop the presses
> > >> till... is addressed" and that being ignored. More along the lines of
> an
> > >> issue being raised and the community immediately working to address
> it.
> > For
> > >> example most recently giving more time to construct the board report.
> > >>
> > >> Failing to cc general@ on the vote is a serious issue. That's part of
> > the
> > >> release process though, it's documented and been followed in previous
> > >> releases. Human error this time around afaict (along with the mentors,
> > >> myself included, who didn't notice it till later)
> > >> https://cwiki.apache.org/confluence/display/SENTRY/How+to+Release
> > >>
> > >>> They seem oblivious to process issues
> > >>
> > >> Are there specific process issues that are missing and should hold up
> a
> > >> vote? I see alot of process related details on their wiki
> > >> https://cwiki.apache.org/confluence/display/SENTRY/Home
> > >>
> > >> Patrick
> > >>
> > >
> > >
> > > Patrick,
> > >
> > > I agree with most of what you wrote. In many ways I'm worried that
> > > this is a failure on the part of mentors. Very early, this morning in
> > > Tokyo, it dawned on me that perhaps the mentors (esp. me) are part of
> > > the problem. This isn't the first time that issues have been called
> > > out with Sentry - and there does seem to be willingness to address
> > > issues on the part of the project. 'We keep saying $n is problematic'
> > > - and I worry (and am certainly guilty in my case) of assuming
> > > everyone largely 'gets it'. I've also not shown them specific concrete
> > > examples of some types of non-problematic behavior. By the time most
> > > folks become a member, or join the IPMC, the Apache way of doing
> > > things is second nature, and we don't always realize that it may be
> > > completely foreign to folks who haven't been doing it for as long.
> > >
> > > I've just sent a long email to dev@ to hopefully make this clearer,
> > > call out some examples, and hopefully generate a discussion on how we
> > > move forward.
> > >
> > > --David
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
Re: June report prep
Posted by Patrick Hunt <ph...@apache.org>.
I believe the podling community was interested to update the report,
however they were concerned about making changes after the cutoff
date. (didn't want to get into more process issues...)
I agree with Ted's reply about adding the additional detail he called
out in his response and moving forward.
Patrick
On Tue, Jun 9, 2015 at 6:53 PM, John D. Ament <jo...@apache.org> wrote:
> So, I hate to bring this up, but I think we're at a stalemate for the
> sentry podling for this month. We tend to not include a podlings report if
> there are no mentor sign offs. It seems like the mentors aren't inclined
> to sign off based on some of the issues that have popped up.
>
> On Mon, Jun 8, 2015 at 12:35 PM Patrick Hunt <ph...@apache.org> wrote:
>
>> Hi David, you and Joe have been doing great, I'm afraid I've been
>> distracted with more issues at home/work than usual. I've been
>> concerned, and this is more serious than usual given the fact that
>> both the community and the oversight missed a serious issue, but given
>> the current feedback and the response (ongoing) from the community we
>> should be able to get things back on track.
>>
>> Thanks,
>>
>> Patrick
>>
>> On Sat, Jun 6, 2015 at 3:14 PM, David Nalley <da...@gnsa.us> wrote:
>> > On Fri, Jun 5, 2015 at 3:23 PM, Patrick Hunt <ph...@apache.org> wrote:
>> >> Ted can you give some concrete examples, because I see some good
>> feedback
>> >> along with folks attempting to address the feedback. Processes updated
>> or
>> >> re-iterated, etc... I haven't seen any comments like "stop the presses
>> >> till... is addressed" and that being ignored. More along the lines of an
>> >> issue being raised and the community immediately working to address it.
>> For
>> >> example most recently giving more time to construct the board report.
>> >>
>> >> Failing to cc general@ on the vote is a serious issue. That's part of
>> the
>> >> release process though, it's documented and been followed in previous
>> >> releases. Human error this time around afaict (along with the mentors,
>> >> myself included, who didn't notice it till later)
>> >> https://cwiki.apache.org/confluence/display/SENTRY/How+to+Release
>> >>
>> >>> They seem oblivious to process issues
>> >>
>> >> Are there specific process issues that are missing and should hold up a
>> >> vote? I see alot of process related details on their wiki
>> >> https://cwiki.apache.org/confluence/display/SENTRY/Home
>> >>
>> >> Patrick
>> >>
>> >
>> >
>> > Patrick,
>> >
>> > I agree with most of what you wrote. In many ways I'm worried that
>> > this is a failure on the part of mentors. Very early, this morning in
>> > Tokyo, it dawned on me that perhaps the mentors (esp. me) are part of
>> > the problem. This isn't the first time that issues have been called
>> > out with Sentry - and there does seem to be willingness to address
>> > issues on the part of the project. 'We keep saying $n is problematic'
>> > - and I worry (and am certainly guilty in my case) of assuming
>> > everyone largely 'gets it'. I've also not shown them specific concrete
>> > examples of some types of non-problematic behavior. By the time most
>> > folks become a member, or join the IPMC, the Apache way of doing
>> > things is second nature, and we don't always realize that it may be
>> > completely foreign to folks who haven't been doing it for as long.
>> >
>> > I've just sent a long email to dev@ to hopefully make this clearer,
>> > call out some examples, and hopefully generate a discussion on how we
>> > move forward.
>> >
>> > --David
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by "John D. Ament" <jo...@apache.org>.
So, I hate to bring this up, but I think we're at a stalemate for the
sentry podling for this month. We tend to not include a podlings report if
there are no mentor sign offs. It seems like the mentors aren't inclined
to sign off based on some of the issues that have popped up.
On Mon, Jun 8, 2015 at 12:35 PM Patrick Hunt <ph...@apache.org> wrote:
> Hi David, you and Joe have been doing great, I'm afraid I've been
> distracted with more issues at home/work than usual. I've been
> concerned, and this is more serious than usual given the fact that
> both the community and the oversight missed a serious issue, but given
> the current feedback and the response (ongoing) from the community we
> should be able to get things back on track.
>
> Thanks,
>
> Patrick
>
> On Sat, Jun 6, 2015 at 3:14 PM, David Nalley <da...@gnsa.us> wrote:
> > On Fri, Jun 5, 2015 at 3:23 PM, Patrick Hunt <ph...@apache.org> wrote:
> >> Ted can you give some concrete examples, because I see some good
> feedback
> >> along with folks attempting to address the feedback. Processes updated
> or
> >> re-iterated, etc... I haven't seen any comments like "stop the presses
> >> till... is addressed" and that being ignored. More along the lines of an
> >> issue being raised and the community immediately working to address it.
> For
> >> example most recently giving more time to construct the board report.
> >>
> >> Failing to cc general@ on the vote is a serious issue. That's part of
> the
> >> release process though, it's documented and been followed in previous
> >> releases. Human error this time around afaict (along with the mentors,
> >> myself included, who didn't notice it till later)
> >> https://cwiki.apache.org/confluence/display/SENTRY/How+to+Release
> >>
> >>> They seem oblivious to process issues
> >>
> >> Are there specific process issues that are missing and should hold up a
> >> vote? I see alot of process related details on their wiki
> >> https://cwiki.apache.org/confluence/display/SENTRY/Home
> >>
> >> Patrick
> >>
> >
> >
> > Patrick,
> >
> > I agree with most of what you wrote. In many ways I'm worried that
> > this is a failure on the part of mentors. Very early, this morning in
> > Tokyo, it dawned on me that perhaps the mentors (esp. me) are part of
> > the problem. This isn't the first time that issues have been called
> > out with Sentry - and there does seem to be willingness to address
> > issues on the part of the project. 'We keep saying $n is problematic'
> > - and I worry (and am certainly guilty in my case) of assuming
> > everyone largely 'gets it'. I've also not shown them specific concrete
> > examples of some types of non-problematic behavior. By the time most
> > folks become a member, or join the IPMC, the Apache way of doing
> > things is second nature, and we don't always realize that it may be
> > completely foreign to folks who haven't been doing it for as long.
> >
> > I've just sent a long email to dev@ to hopefully make this clearer,
> > call out some examples, and hopefully generate a discussion on how we
> > move forward.
> >
> > --David
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: June report prep
Posted by Patrick Hunt <ph...@apache.org>.
Hi David, you and Joe have been doing great, I'm afraid I've been
distracted with more issues at home/work than usual. I've been
concerned, and this is more serious than usual given the fact that
both the community and the oversight missed a serious issue, but given
the current feedback and the response (ongoing) from the community we
should be able to get things back on track.
Thanks,
Patrick
On Sat, Jun 6, 2015 at 3:14 PM, David Nalley <da...@gnsa.us> wrote:
> On Fri, Jun 5, 2015 at 3:23 PM, Patrick Hunt <ph...@apache.org> wrote:
>> Ted can you give some concrete examples, because I see some good feedback
>> along with folks attempting to address the feedback. Processes updated or
>> re-iterated, etc... I haven't seen any comments like "stop the presses
>> till... is addressed" and that being ignored. More along the lines of an
>> issue being raised and the community immediately working to address it. For
>> example most recently giving more time to construct the board report.
>>
>> Failing to cc general@ on the vote is a serious issue. That's part of the
>> release process though, it's documented and been followed in previous
>> releases. Human error this time around afaict (along with the mentors,
>> myself included, who didn't notice it till later)
>> https://cwiki.apache.org/confluence/display/SENTRY/How+to+Release
>>
>>> They seem oblivious to process issues
>>
>> Are there specific process issues that are missing and should hold up a
>> vote? I see alot of process related details on their wiki
>> https://cwiki.apache.org/confluence/display/SENTRY/Home
>>
>> Patrick
>>
>
>
> Patrick,
>
> I agree with most of what you wrote. In many ways I'm worried that
> this is a failure on the part of mentors. Very early, this morning in
> Tokyo, it dawned on me that perhaps the mentors (esp. me) are part of
> the problem. This isn't the first time that issues have been called
> out with Sentry - and there does seem to be willingness to address
> issues on the part of the project. 'We keep saying $n is problematic'
> - and I worry (and am certainly guilty in my case) of assuming
> everyone largely 'gets it'. I've also not shown them specific concrete
> examples of some types of non-problematic behavior. By the time most
> folks become a member, or join the IPMC, the Apache way of doing
> things is second nature, and we don't always realize that it may be
> completely foreign to folks who haven't been doing it for as long.
>
> I've just sent a long email to dev@ to hopefully make this clearer,
> call out some examples, and hopefully generate a discussion on how we
> move forward.
>
> --David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by David Nalley <da...@gnsa.us>.
On Fri, Jun 5, 2015 at 3:23 PM, Patrick Hunt <ph...@apache.org> wrote:
> Ted can you give some concrete examples, because I see some good feedback
> along with folks attempting to address the feedback. Processes updated or
> re-iterated, etc... I haven't seen any comments like "stop the presses
> till... is addressed" and that being ignored. More along the lines of an
> issue being raised and the community immediately working to address it. For
> example most recently giving more time to construct the board report.
>
> Failing to cc general@ on the vote is a serious issue. That's part of the
> release process though, it's documented and been followed in previous
> releases. Human error this time around afaict (along with the mentors,
> myself included, who didn't notice it till later)
> https://cwiki.apache.org/confluence/display/SENTRY/How+to+Release
>
>> They seem oblivious to process issues
>
> Are there specific process issues that are missing and should hold up a
> vote? I see alot of process related details on their wiki
> https://cwiki.apache.org/confluence/display/SENTRY/Home
>
> Patrick
>
Patrick,
I agree with most of what you wrote. In many ways I'm worried that
this is a failure on the part of mentors. Very early, this morning in
Tokyo, it dawned on me that perhaps the mentors (esp. me) are part of
the problem. This isn't the first time that issues have been called
out with Sentry - and there does seem to be willingness to address
issues on the part of the project. 'We keep saying $n is problematic'
- and I worry (and am certainly guilty in my case) of assuming
everyone largely 'gets it'. I've also not shown them specific concrete
examples of some types of non-problematic behavior. By the time most
folks become a member, or join the IPMC, the Apache way of doing
things is second nature, and we don't always realize that it may be
completely foreign to folks who haven't been doing it for as long.
I've just sent a long email to dev@ to hopefully make this clearer,
call out some examples, and hopefully generate a discussion on how we
move forward.
--David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Patrick Hunt <ph...@apache.org>.
Ted can you give some concrete examples, because I see some good feedback
along with folks attempting to address the feedback. Processes updated or
re-iterated, etc... I haven't seen any comments like "stop the presses
till... is addressed" and that being ignored. More along the lines of an
issue being raised and the community immediately working to address it. For
example most recently giving more time to construct the board report.
Failing to cc general@ on the vote is a serious issue. That's part of the
release process though, it's documented and been followed in previous
releases. Human error this time around afaict (along with the mentors,
myself included, who didn't notice it till later)
https://cwiki.apache.org/confluence/display/SENTRY/How+to+Release
> They seem oblivious to process issues
Are there specific process issues that are missing and should hold up a
vote? I see alot of process related details on their wiki
https://cwiki.apache.org/confluence/display/SENTRY/Home
Patrick
On Fri, Jun 5, 2015 at 8:03 AM, Ted Dunning <te...@gmail.com> wrote:
> I don't think that the Sentry PPMC actually disagrees with the mentor's
> recommendation (and, in fact, at least one person agreed to reverting to
> monthly reports).
>
> But in reading the last 4 months of traffic on the dev list, I really don't
> think that the PPMC has internalized the critique at all either. They seem
> oblivious to process issues and have even voted to try to proceed with
> graduation without really noticing that there are problems.
>
> This indicates (to me) that the Incubator shepherds and project mentors are
> largely not being understood by the PPMC. Neither are the release
> procedures being internalized. The result is that the conversation tends
> to go a bit like
>
> MENTOR: I see a serious problem X
> PPMC: We will have to address that in the future
> ...
> PPMC: Let's release
> ...
> MENTOR: I see a serious problem Y with your release
> PPMC: We will have to address that in the future
> ...
> ...
> PPMC: Let's graduate
>
>
> There is never an argument or contradiction to the assertion of a problem,
> but there doesn't seem to be much attention paid either. My impression is
> that the community is not actually reading the dev list very carefully.
>
>
>
>
> On Fri, Jun 5, 2015 at 3:23 PM, John D. Ament <jo...@gmail.com>
> wrote:
>
> > Does the Sentry podling (PPMC) disagree with their mentors
> recommendation?
> > I agree with the mentors proposal for both and actually raised this last
> > month as an issue.
> >
> > John
> >
> > On Fri, Jun 5, 2015 at 8:56 AM Ted Dunning <te...@gmail.com>
> wrote:
> >
> > > Marvin,
> > >
> > > Thanks as ever for the coaching.
> > >
> > > One question that has come in from David Nalley is how to deal with the
> > > issue of Sentry. They have had some problems with process and seem not
> > to
> > > recognize that in the report. David suggests reverting to monthly
> > reports
> > > as we try to clear up the questions. I suggest adding a note to the
> > > report. The situation is a bit problematic because there are several
> > people
> > > in the project who should understand process better and raise this
> issue
> > > themselves.
> > >
> > >
> > > On Fri, Jun 5, 2015 at 8:37 AM, Marvin Humphrey <
> marvin@rectangular.com>
> > > wrote:
> > >
> > > > On Tue, May 26, 2015 at 8:38 PM, Ted Dunning <te...@gmail.com>
> > > > wrote:
> > > > > On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey <
> > > marvin@rectangular.com
> > > > >
> > > > > wrote:
> > > > >
> > > > >> The responsibilities of the Report Manager are documented using a
> > > > script,
> > > > >> report_runbook.py, which generates all the necessary commands.
> Ted,
> > > > please
> > > > >> try running this from a checkout of the Incubator Subversion repo:
> > > > >>
> > > > >> python3 report_runbook.py --month=6 --apache-id=tdunning
> > > > >>
> > > > >> The first action of the June report cycle is to send the
> "timeline"
> > > > email
> > > > >> to general@incubator. This should be done by the last Wednesday
> of
> > > the
> > > > >> month, so that people see it a full week before podling reports
> are
> > > due.
> > > > >> Here's a sample:
> > > > >
> > > > > Yay!
> > > > >
> > > > > With the correct version of python, this now works for me. We
> won't
> > > know
> > > > > what problems I had before, but I don't plan to care too much.
> > > >
> > > > Hi Ted,
> > > >
> > > > Now that the deadline has passed for filing podling reports, we can
> > > > perform a
> > > > few more actions.
> > > >
> > > > * Normalize podling report formatting.
> > > > * Generate list of releases.
> > > > * Categorize the podlings by stage of incubation and create the
> > podling
> > > > summary.
> > > > * Edit podlings.xml to assign podlings who did not report a
> "monthly"
> > > tag
> > > > so that they don't fall through the cracks. See
> > > > <http://s.apache.org/At0>.
> > > >
> > > > See the output of report_runbook.py for more detailed instructions
> and
> > > let
> > > > us
> > > > know if you have questions.
> > > >
> > > > I'll work on the narrative section either tomorrow or Saturday.
> > > >
> > > > The goal is to have everything done by Sunday night so that we can
> send
> > > > out a
> > > > mature draft on Monday.
> > > >
> > > > Marvin Humphrey
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > >
> > > >
> > >
> >
>
Re: June report prep
Posted by Ted Dunning <te...@gmail.com>.
I don't think that the Sentry PPMC actually disagrees with the mentor's
recommendation (and, in fact, at least one person agreed to reverting to
monthly reports).
But in reading the last 4 months of traffic on the dev list, I really don't
think that the PPMC has internalized the critique at all either. They seem
oblivious to process issues and have even voted to try to proceed with
graduation without really noticing that there are problems.
This indicates (to me) that the Incubator shepherds and project mentors are
largely not being understood by the PPMC. Neither are the release
procedures being internalized. The result is that the conversation tends
to go a bit like
MENTOR: I see a serious problem X
PPMC: We will have to address that in the future
...
PPMC: Let's release
...
MENTOR: I see a serious problem Y with your release
PPMC: We will have to address that in the future
...
...
PPMC: Let's graduate
There is never an argument or contradiction to the assertion of a problem,
but there doesn't seem to be much attention paid either. My impression is
that the community is not actually reading the dev list very carefully.
On Fri, Jun 5, 2015 at 3:23 PM, John D. Ament <jo...@gmail.com>
wrote:
> Does the Sentry podling (PPMC) disagree with their mentors recommendation?
> I agree with the mentors proposal for both and actually raised this last
> month as an issue.
>
> John
>
> On Fri, Jun 5, 2015 at 8:56 AM Ted Dunning <te...@gmail.com> wrote:
>
> > Marvin,
> >
> > Thanks as ever for the coaching.
> >
> > One question that has come in from David Nalley is how to deal with the
> > issue of Sentry. They have had some problems with process and seem not
> to
> > recognize that in the report. David suggests reverting to monthly
> reports
> > as we try to clear up the questions. I suggest adding a note to the
> > report. The situation is a bit problematic because there are several
> people
> > in the project who should understand process better and raise this issue
> > themselves.
> >
> >
> > On Fri, Jun 5, 2015 at 8:37 AM, Marvin Humphrey <ma...@rectangular.com>
> > wrote:
> >
> > > On Tue, May 26, 2015 at 8:38 PM, Ted Dunning <te...@gmail.com>
> > > wrote:
> > > > On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey <
> > marvin@rectangular.com
> > > >
> > > > wrote:
> > > >
> > > >> The responsibilities of the Report Manager are documented using a
> > > script,
> > > >> report_runbook.py, which generates all the necessary commands. Ted,
> > > please
> > > >> try running this from a checkout of the Incubator Subversion repo:
> > > >>
> > > >> python3 report_runbook.py --month=6 --apache-id=tdunning
> > > >>
> > > >> The first action of the June report cycle is to send the "timeline"
> > > email
> > > >> to general@incubator. This should be done by the last Wednesday of
> > the
> > > >> month, so that people see it a full week before podling reports are
> > due.
> > > >> Here's a sample:
> > > >
> > > > Yay!
> > > >
> > > > With the correct version of python, this now works for me. We won't
> > know
> > > > what problems I had before, but I don't plan to care too much.
> > >
> > > Hi Ted,
> > >
> > > Now that the deadline has passed for filing podling reports, we can
> > > perform a
> > > few more actions.
> > >
> > > * Normalize podling report formatting.
> > > * Generate list of releases.
> > > * Categorize the podlings by stage of incubation and create the
> podling
> > > summary.
> > > * Edit podlings.xml to assign podlings who did not report a "monthly"
> > tag
> > > so that they don't fall through the cracks. See
> > > <http://s.apache.org/At0>.
> > >
> > > See the output of report_runbook.py for more detailed instructions and
> > let
> > > us
> > > know if you have questions.
> > >
> > > I'll work on the narrative section either tomorrow or Saturday.
> > >
> > > The goal is to have everything done by Sunday night so that we can send
> > > out a
> > > mature draft on Monday.
> > >
> > > Marvin Humphrey
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
>
Re: June report prep
Posted by "John D. Ament" <jo...@gmail.com>.
Does the Sentry podling (PPMC) disagree with their mentors recommendation?
I agree with the mentors proposal for both and actually raised this last
month as an issue.
John
On Fri, Jun 5, 2015 at 8:56 AM Ted Dunning <te...@gmail.com> wrote:
> Marvin,
>
> Thanks as ever for the coaching.
>
> One question that has come in from David Nalley is how to deal with the
> issue of Sentry. They have had some problems with process and seem not to
> recognize that in the report. David suggests reverting to monthly reports
> as we try to clear up the questions. I suggest adding a note to the
> report. The situation is a bit problematic because there are several people
> in the project who should understand process better and raise this issue
> themselves.
>
>
> On Fri, Jun 5, 2015 at 8:37 AM, Marvin Humphrey <ma...@rectangular.com>
> wrote:
>
> > On Tue, May 26, 2015 at 8:38 PM, Ted Dunning <te...@gmail.com>
> > wrote:
> > > On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey <
> marvin@rectangular.com
> > >
> > > wrote:
> > >
> > >> The responsibilities of the Report Manager are documented using a
> > script,
> > >> report_runbook.py, which generates all the necessary commands. Ted,
> > please
> > >> try running this from a checkout of the Incubator Subversion repo:
> > >>
> > >> python3 report_runbook.py --month=6 --apache-id=tdunning
> > >>
> > >> The first action of the June report cycle is to send the "timeline"
> > email
> > >> to general@incubator. This should be done by the last Wednesday of
> the
> > >> month, so that people see it a full week before podling reports are
> due.
> > >> Here's a sample:
> > >
> > > Yay!
> > >
> > > With the correct version of python, this now works for me. We won't
> know
> > > what problems I had before, but I don't plan to care too much.
> >
> > Hi Ted,
> >
> > Now that the deadline has passed for filing podling reports, we can
> > perform a
> > few more actions.
> >
> > * Normalize podling report formatting.
> > * Generate list of releases.
> > * Categorize the podlings by stage of incubation and create the podling
> > summary.
> > * Edit podlings.xml to assign podlings who did not report a "monthly"
> tag
> > so that they don't fall through the cracks. See
> > <http://s.apache.org/At0>.
> >
> > See the output of report_runbook.py for more detailed instructions and
> let
> > us
> > know if you have questions.
> >
> > I'll work on the narrative section either tomorrow or Saturday.
> >
> > The goal is to have everything done by Sunday night so that we can send
> > out a
> > mature draft on Monday.
> >
> > Marvin Humphrey
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
Re: June report prep
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Fri, Jun 5, 2015 at 3:13 PM, Marvin Humphrey <ma...@rectangular.com> wrote:
> David, me, you, or any other interested party could also add a section in the
> general narrative at the top of the report mentioning that Sentry has been a
> topic of discussion on general@incubator. I'll probably do that.
I see that Joe Brockmeier has taken care of this:
http://s.apache.org/roE
Thanks Joe -- what you wrote looks great!
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Fri, Jun 5, 2015 at 5:55 AM, Ted Dunning <te...@gmail.com> wrote:
> One question that has come in from David Nalley is how to deal with the
> issue of Sentry. They have had some problems with process and seem not to
> recognize that in the report. David suggests reverting to monthly reports
> as we try to clear up the questions. I suggest adding a note to the
> report. The situation is a bit problematic because there are several people
> in the project who should understand process better and raise this issue
> themselves.
There are two issues here:
1. What should go in the report.
2. What actions to take regarding Sentry, if any.
David has already provided his perspective in an excellent Mentor comment on
Sentry. The formatting needs to be cleaned up, but I think that's the optimal
spot on the report for that information.
David, me, you, or any other interested party could also add a section in the
general narrative at the top of the report mentioning that Sentry has been a
topic of discussion on general@incubator. I'll probably do that.
The only other thing about commenting on Sentry is that it's important to get
any such material into Monday's DRAFT in order to give the Sentry community
(both contributors and Mentors) sufficient opportunity to review and respond
if necessary. Adding commentary *after* the DRAFT goes out is dangerous.
With regards to what actions to take, Sentry Mentors David Nalley, Patrick
Hunt, and Joe Brockmeier are all engaged and I'm content to defer to their
judgment. If they think that reporting monthly for the next three months is
appropriate, they can edit podlings.xml themselves, or they can ask for
someone else to do it and I'm sure John, me, you or another volunteer would
help out.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Ted Dunning <te...@gmail.com>.
Great idea on taking notes.
On Mon, Jun 22, 2015 at 5:17 PM, Sam Ruby <ru...@intertwingly.net> wrote:
> On Mon, Jun 22, 2015 at 11:43 AM, Marvin Humphrey
> <ma...@rectangular.com> wrote:
> > On Mon, Jun 15, 2015 at 6:58 PM, Ted Dunning <te...@gmail.com>
> wrote:
> >> On Mon, Jun 15, 2015 at 4:48 PM, Marvin Humphrey <
> marvin@rectangular.com>
> >> wrote:
> >>
> >>> There are a few more cleanup and followup tasks to take care of in
> order to
> >>> prepare for next month:
> >>>
> >>> * Assign podlings who did not report a "monthly" attribute in
> >>> podlings.xml.
> >>> * Remove any expired "monthly" attributes.
> >>> * Run clutch.py.
> >>> * Assign shepherds.
> >>> * Generate the July report template and publish on the wiki.
> >>>
> >>> No hurry, so take a couple days to catch your breath. Will your
> schedule
> >>> allow you to get to those by the end of this week?
> >>
> >> It should. After the presentation tomorrow at Spark Summit, I should be
> >> clear for a few days.
> >
> > Hi Ted -- can you take care of these items please?
> >
> >>> Once you close out this month's cycle, we might also have a
> conversation
> >>> about how you think the report process could be improved.
> >>
> >> Happy to do so.
> >>
> >> So far, the support of the team has been absolutely extraordinary. The
> >> only suggestion so far is to help a new VP know that the support exists.
> >> My assumption was that I was jumping into the deep end. The facts were
> >> quite different.
> >
> > Well, I think we can do better yet if we integrate the Incubator's
> monthly
> > reporting into whimsy. My perception is that the total burden is too
> high.
> > In the past it was borne solely by the Chair, which was not at all
> > sustainable. Now it is spread, but additional tooling can improve
> matters
> > more.
> >
> > However, I'm trying to hold off on that conversation until the current
> Chair
> > has actually performed all the tasks involved with the report and so
> groks the
> > full scope. Hint hint. ;)
>
> One thing that would be helpful is to take good notes during this
> process. Anything you can do via the command line can be done via a
> script - this includes SVN and LDAP. Anything that requires user
> input is generally easier when done via a HTML form (buttons,
> textareas, checkboxes and the like). And steps like "remove expired
> monthly attributes" can be automated away entirely.
>
> > Marvin Humphrey
>
> - Sam Ruby
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: June report prep
Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, Jun 22, 2015 at 11:43 AM, Marvin Humphrey
<ma...@rectangular.com> wrote:
> On Mon, Jun 15, 2015 at 6:58 PM, Ted Dunning <te...@gmail.com> wrote:
>> On Mon, Jun 15, 2015 at 4:48 PM, Marvin Humphrey <ma...@rectangular.com>
>> wrote:
>>
>>> There are a few more cleanup and followup tasks to take care of in order to
>>> prepare for next month:
>>>
>>> * Assign podlings who did not report a "monthly" attribute in
>>> podlings.xml.
>>> * Remove any expired "monthly" attributes.
>>> * Run clutch.py.
>>> * Assign shepherds.
>>> * Generate the July report template and publish on the wiki.
>>>
>>> No hurry, so take a couple days to catch your breath. Will your schedule
>>> allow you to get to those by the end of this week?
>>
>> It should. After the presentation tomorrow at Spark Summit, I should be
>> clear for a few days.
>
> Hi Ted -- can you take care of these items please?
>
>>> Once you close out this month's cycle, we might also have a conversation
>>> about how you think the report process could be improved.
>>
>> Happy to do so.
>>
>> So far, the support of the team has been absolutely extraordinary. The
>> only suggestion so far is to help a new VP know that the support exists.
>> My assumption was that I was jumping into the deep end. The facts were
>> quite different.
>
> Well, I think we can do better yet if we integrate the Incubator's monthly
> reporting into whimsy. My perception is that the total burden is too high.
> In the past it was borne solely by the Chair, which was not at all
> sustainable. Now it is spread, but additional tooling can improve matters
> more.
>
> However, I'm trying to hold off on that conversation until the current Chair
> has actually performed all the tasks involved with the report and so groks the
> full scope. Hint hint. ;)
One thing that would be helpful is to take good notes during this
process. Anything you can do via the command line can be done via a
script - this includes SVN and LDAP. Anything that requires user
input is generally easier when done via a HTML form (buttons,
textareas, checkboxes and the like). And steps like "remove expired
monthly attributes" can be automated away entirely.
> Marvin Humphrey
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Ted Dunning <te...@gmail.com>.
On Mon, Jun 22, 2015 at 8:43 AM, Marvin Humphrey <ma...@rectangular.com>
wrote:
> However, I'm trying to hold off on that conversation until the current
> Chair
> has actually performed all the tasks involved with the report and so groks
> the
> full scope. Hint hint. ;)
>
Hint accepted.
Re: June report prep
Posted by Sam Ruby <ru...@intertwingly.net>.
On Sat, Jun 27, 2015 at 12:47 PM, Marvin Humphrey
<ma...@rectangular.com> wrote:
> On Tue, Jun 23, 2015 at 6:32 AM, Ted Dunning <te...@gmail.com> wrote:
>> On Mon, Jun 22, 2015 at 8:43 AM, Marvin Humphrey <ma...@rectangular.com>
>> wrote:
>>
>>> >> * Assign podlings who did not report a "monthly" attribute in
>>> >> podlings.xml.
>>> >> * Remove any expired "monthly" attributes.
>>> >> * Run clutch.py.
>>> >> * Assign shepherds.
>>> >> * Generate the July report template and publish on the wiki.
>>> >>
>>> >> No hurry, so take a couple days to catch your breath. Will your
>>> >> schedule allow you to get to those by the end of this week?
>>> >
>>> > It should. After the presentation tomorrow at Spark Summit, I should be
>>> > clear for a few days.
>>>
>>> Hi Ted -- can you take care of these items please?
>>
>> Yes. Should have time tonight or a bit tomorrow while sitting in the
>> airport.
>
> Ay, caramba. This past Wednesday was the last one in June. Podling reports
> are due next Wednesday, July 1st. The robot "Marvin" who sends out podling
> reminders flaked yet again.
>
> We can't wait any longer for these tasks to be completed. I'll attend to
> them, and then I'll send out manual reminders.
Again, take good notes :-)
This too can be done by whimsy.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Tue, Jun 23, 2015 at 6:32 AM, Ted Dunning <te...@gmail.com> wrote:
> On Mon, Jun 22, 2015 at 8:43 AM, Marvin Humphrey <ma...@rectangular.com>
> wrote:
>
>> >> * Assign podlings who did not report a "monthly" attribute in
>> >> podlings.xml.
>> >> * Remove any expired "monthly" attributes.
>> >> * Run clutch.py.
>> >> * Assign shepherds.
>> >> * Generate the July report template and publish on the wiki.
>> >>
>> >> No hurry, so take a couple days to catch your breath. Will your
>> >> schedule allow you to get to those by the end of this week?
>> >
>> > It should. After the presentation tomorrow at Spark Summit, I should be
>> > clear for a few days.
>>
>> Hi Ted -- can you take care of these items please?
>
> Yes. Should have time tonight or a bit tomorrow while sitting in the
> airport.
Ay, caramba. This past Wednesday was the last one in June. Podling reports
are due next Wednesday, July 1st. The robot "Marvin" who sends out podling
reminders flaked yet again.
We can't wait any longer for these tasks to be completed. I'll attend to
them, and then I'll send out manual reminders.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Ted Dunning <te...@gmail.com>.
On Mon, Jun 22, 2015 at 8:43 AM, Marvin Humphrey <ma...@rectangular.com>
wrote:
> >> * Assign podlings who did not report a "monthly" attribute in
> >> podlings.xml.
> >> * Remove any expired "monthly" attributes.
> >> * Run clutch.py.
> >> * Assign shepherds.
> >> * Generate the July report template and publish on the wiki.
> >>
> >> No hurry, so take a couple days to catch your breath. Will your
> schedule
> >> allow you to get to those by the end of this week?
> >
> > It should. After the presentation tomorrow at Spark Summit, I should be
> > clear for a few days.
>
> Hi Ted -- can you take care of these items please?
Yes. Should have time tonight or a bit tomorrow while sitting in the
airport.
Re: June report prep
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Mon, Jun 15, 2015 at 6:58 PM, Ted Dunning <te...@gmail.com> wrote:
> On Mon, Jun 15, 2015 at 4:48 PM, Marvin Humphrey <ma...@rectangular.com>
> wrote:
>
>> There are a few more cleanup and followup tasks to take care of in order to
>> prepare for next month:
>>
>> * Assign podlings who did not report a "monthly" attribute in
>> podlings.xml.
>> * Remove any expired "monthly" attributes.
>> * Run clutch.py.
>> * Assign shepherds.
>> * Generate the July report template and publish on the wiki.
>>
>> No hurry, so take a couple days to catch your breath. Will your schedule
>> allow you to get to those by the end of this week?
>
> It should. After the presentation tomorrow at Spark Summit, I should be
> clear for a few days.
Hi Ted -- can you take care of these items please?
>> Once you close out this month's cycle, we might also have a conversation
>> about how you think the report process could be improved.
>
> Happy to do so.
>
> So far, the support of the team has been absolutely extraordinary. The
> only suggestion so far is to help a new VP know that the support exists.
> My assumption was that I was jumping into the deep end. The facts were
> quite different.
Well, I think we can do better yet if we integrate the Incubator's monthly
reporting into whimsy. My perception is that the total burden is too high.
In the past it was borne solely by the Chair, which was not at all
sustainable. Now it is spread, but additional tooling can improve matters
more.
However, I'm trying to hold off on that conversation until the current Chair
has actually performed all the tasks involved with the report and so groks the
full scope. Hint hint. ;)
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Ted Dunning <te...@gmail.com>.
On Mon, Jun 15, 2015 at 4:48 PM, Marvin Humphrey <ma...@rectangular.com>
wrote:
> There are a few more cleanup and followup tasks to take care of in order to
> prepare for next month:
>
> * Assign podlings who did not report a "monthly" attribute in
> podlings.xml.
> * Remove any expired "monthly" attributes.
> * Run clutch.py.
> * Assign shepherds.
> * Generate the July report template and publish on the wiki.
>
> No hurry, so take a couple days to catch your breath. Will your schedule
> allow you to get to those by the end of this week?
>
It should. After the presentation tomorrow at Spark Summit, I should be
clear for a few days.
>
> Once you close out this month's cycle, we might also have a conversation
> about
> how you think the report process could be improved.
>
Happy to do so.
So far, the support of the team has been absolutely extraordinary. The
only suggestion so far is to help a new VP know that the support exists.
My assumption was that I was jumping into the deep end. The facts were
quite different.
Re: June report prep
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Sun, Jun 14, 2015 at 9:48 PM, Ted Dunning <te...@gmail.com> wrote:
>
> I can get it tonight. This last week has been crazy.
Thanks for following through, Ted! Especially since we had you performing
unfamiliar tasks.
In the future, we should see if we can share responsibilities rather than
blocking on one person's contributions. There are several people who could
have finished out the tasks in question: myself, John Ament, Roman and Alan
Cabrera all know the drill. We gained the benefit of bringing you up to speed
this month, which is useful -- but it's important that the Incubator's report
be filed on time most months.
There are a few more cleanup and followup tasks to take care of in order to
prepare for next month:
* Assign podlings who did not report a "monthly" attribute in podlings.xml.
* Remove any expired "monthly" attributes.
* Run clutch.py.
* Assign shepherds.
* Generate the July report template and publish on the wiki.
No hurry, so take a couple days to catch your breath. Will your schedule
allow you to get to those by the end of this week?
Once you close out this month's cycle, we might also have a conversation about
how you think the report process could be improved.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Ted Dunning <te...@gmail.com>.
I can get it tonight. This last week has been crazy.
Sent from my iPhone
> On Jun 14, 2015, at 20:36, Marvin Humphrey <ma...@rectangular.com> wrote:
>
> Hi, Ted,
>
> Do you need someone else to finish and file the report?
>
> Marvin Humphrey
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Marvin Humphrey <ma...@rectangular.com>.
Hi, Ted,
Do you need someone else to finish and file the report?
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Ted Dunning <te...@gmail.com>.
Marvin,
Thanks as ever for the coaching.
One question that has come in from David Nalley is how to deal with the
issue of Sentry. They have had some problems with process and seem not to
recognize that in the report. David suggests reverting to monthly reports
as we try to clear up the questions. I suggest adding a note to the
report. The situation is a bit problematic because there are several people
in the project who should understand process better and raise this issue
themselves.
On Fri, Jun 5, 2015 at 8:37 AM, Marvin Humphrey <ma...@rectangular.com>
wrote:
> On Tue, May 26, 2015 at 8:38 PM, Ted Dunning <te...@gmail.com>
> wrote:
> > On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey <marvin@rectangular.com
> >
> > wrote:
> >
> >> The responsibilities of the Report Manager are documented using a
> script,
> >> report_runbook.py, which generates all the necessary commands. Ted,
> please
> >> try running this from a checkout of the Incubator Subversion repo:
> >>
> >> python3 report_runbook.py --month=6 --apache-id=tdunning
> >>
> >> The first action of the June report cycle is to send the "timeline"
> email
> >> to general@incubator. This should be done by the last Wednesday of the
> >> month, so that people see it a full week before podling reports are due.
> >> Here's a sample:
> >
> > Yay!
> >
> > With the correct version of python, this now works for me. We won't know
> > what problems I had before, but I don't plan to care too much.
>
> Hi Ted,
>
> Now that the deadline has passed for filing podling reports, we can
> perform a
> few more actions.
>
> * Normalize podling report formatting.
> * Generate list of releases.
> * Categorize the podlings by stage of incubation and create the podling
> summary.
> * Edit podlings.xml to assign podlings who did not report a "monthly" tag
> so that they don't fall through the cracks. See
> <http://s.apache.org/At0>.
>
> See the output of report_runbook.py for more detailed instructions and let
> us
> know if you have questions.
>
> I'll work on the narrative section either tomorrow or Saturday.
>
> The goal is to have everything done by Sunday night so that we can send
> out a
> mature draft on Monday.
>
> Marvin Humphrey
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: June report prep
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Thu, Jun 4, 2015 at 11:37 PM, Marvin Humphrey <ma...@rectangular.com> wrote:
> I'll work on the narrative section either tomorrow or Saturday.
Done.
Once the other tasks listed earlier are complete, the next thing is to
send the DRAFT out on Monday.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Tue, May 26, 2015 at 8:38 PM, Ted Dunning <te...@gmail.com> wrote:
> On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey <ma...@rectangular.com>
> wrote:
>
>> The responsibilities of the Report Manager are documented using a script,
>> report_runbook.py, which generates all the necessary commands. Ted, please
>> try running this from a checkout of the Incubator Subversion repo:
>>
>> python3 report_runbook.py --month=6 --apache-id=tdunning
>>
>> The first action of the June report cycle is to send the "timeline" email
>> to general@incubator. This should be done by the last Wednesday of the
>> month, so that people see it a full week before podling reports are due.
>> Here's a sample:
>
> Yay!
>
> With the correct version of python, this now works for me. We won't know
> what problems I had before, but I don't plan to care too much.
Hi Ted,
Now that the deadline has passed for filing podling reports, we can perform a
few more actions.
* Normalize podling report formatting.
* Generate list of releases.
* Categorize the podlings by stage of incubation and create the podling
summary.
* Edit podlings.xml to assign podlings who did not report a "monthly" tag
so that they don't fall through the cracks. See
<http://s.apache.org/At0>.
See the output of report_runbook.py for more detailed instructions and let us
know if you have questions.
I'll work on the narrative section either tomorrow or Saturday.
The goal is to have everything done by Sunday night so that we can send out a
mature draft on Monday.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: June report prep
Posted by Ted Dunning <te...@gmail.com>.
On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey <ma...@rectangular.com>
wrote:
> The responsibilities of the Report Manager are documented using a script,
> report_runbook.py, which generates all the necessary commands. Ted, please
> try running this from a checkout of the Incubator Subversion repo:
>
> python3 report_runbook.py --month=6 --apache-id=tdunning
>
> The first action of the June report cycle is to send the "timeline" email
> to
> general@incubator. This should be done by the last Wednesday of the
> month,
> so that people see it a full week before podling reports are due. Here's
> a sample:
>
Yay!
With the correct version of python, this now works for me. We won't know
what problems I had before, but I don't plan to care too much.
Re: June report prep
Posted by "John D. Ament" <jo...@apache.org>.
A special note for all community members...
Marvin noted a lack of shepherds available compared to our podling count.
There are currently 10 active shepherds and 27 active podlings for this
month's report, meaning on average 2.7 podlings per shepherd (thankfully I
didn't have to bust out my math degree to figure out that one). Some
shepherds can only handle one podling (due to capacity) and as a result we
do have gaps in our podling coverage.
This is a great month for any new community members who are interested in
the incubator to get their feet wet and start learning to be a shepherd.
Shepherds help monitor monthly progress of podlings, ensuring there's an
external reviewer.
If you're interested, there's two steps.
1. Sign up on the wiki -> https://wiki.apache.org/incubator/June2015
2. Add your name to content/shepherds.json (in the incubator site).
Thanks!
John
On Tue, May 26, 2015 at 7:35 PM Marvin Humphrey <ma...@rectangular.com>
wrote:
> Greets,
>
> For June, Ted and I have arranged to split the duties of Report Manager.
> Ted
> will execute most technical aspects, with support from general@incubator.
> I'll take point on creating the freeform narrative content at the top of
> the
> report, subject to the Chair's editorial oversight.
>
> The responsibilities of the Report Manager are documented using a script,
> report_runbook.py, which generates all the necessary commands. Ted, please
> try running this from a checkout of the Incubator Subversion repo:
>
> python3 report_runbook.py --month=6 --apache-id=tdunning
>
> The first action of the June report cycle is to send the "timeline" email
> to
> general@incubator. This should be done by the last Wednesday of the
> month,
> so that people see it a full week before podling reports are due. Here's
> a sample:
>
> http://markmail.org/thread/xelqzblvvc5s4vy3
>
> Please feel free to ask any questions you may have on this thread.
>
> Marvin Humphrey
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>