Re: June report prep

2015-06-27 Thread Sam Ruby
On Sat, Jun 27, 2015 at 12:47 PM, Marvin Humphrey wrote: > On Tue, Jun 23, 2015 at 6:32 AM, Ted Dunning wrote: >> On Mon, Jun 22, 2015 at 8:43 AM, Marvin Humphrey >> wrote: >> >>> >> * Assign podlings who did not report a "monthly" attribute in >>> >> podlings.xml. >>> >> * Remove any ex

Re: June report prep

2015-06-27 Thread Marvin Humphrey
On Tue, Jun 23, 2015 at 6:32 AM, Ted Dunning wrote: > On Mon, Jun 22, 2015 at 8:43 AM, Marvin Humphrey > wrote: > >> >> * Assign podlings who did not report a "monthly" attribute in >> >> podlings.xml. >> >> * Remove any expired "monthly" attributes. >> >> * Run clutch.py. >> >> * Ass

Re: June report prep

2015-06-23 Thread Ted Dunning
On Mon, Jun 22, 2015 at 8:43 AM, Marvin Humphrey 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

2015-06-23 Thread Ted Dunning
On Mon, Jun 22, 2015 at 8:43 AM, Marvin Humphrey 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 p

Re: June report prep

2015-06-23 Thread Ted Dunning
Great idea on taking notes. On Mon, Jun 22, 2015 at 5:17 PM, Sam Ruby wrote: > On Mon, Jun 22, 2015 at 11:43 AM, Marvin Humphrey > wrote: > > On Mon, Jun 15, 2015 at 6:58 PM, Ted Dunning > wrote: > >> On Mon, Jun 15, 2015 at 4:48 PM, Marvin Humphrey < > mar...@rectangular.com> > >> wrote: >

Re: June report prep

2015-06-22 Thread Sam Ruby
On Mon, Jun 22, 2015 at 11:43 AM, Marvin Humphrey wrote: > On Mon, Jun 15, 2015 at 6:58 PM, Ted Dunning wrote: >> On Mon, Jun 15, 2015 at 4:48 PM, Marvin Humphrey >> wrote: >> >>> There are a few more cleanup and followup tasks to take care of in order to >>> prepare for next month: >>> >>> *

Re: June report prep

2015-06-22 Thread Marvin Humphrey
On Mon, Jun 15, 2015 at 6:58 PM, Ted Dunning wrote: > On Mon, Jun 15, 2015 at 4:48 PM, Marvin Humphrey > 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 >>

Re: June report prep

2015-06-15 Thread Ted Dunning
On Mon, Jun 15, 2015 at 4:48 PM, Marvin Humphrey 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. > *

Re: June report prep

2015-06-15 Thread Marvin Humphrey
On Sun, Jun 14, 2015 at 9:48 PM, Ted Dunning 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 per

Re: June report prep

2015-06-14 Thread Ted Dunning
I can get it tonight. This last week has been crazy. Sent from my iPhone > On Jun 14, 2015, at 20:36, Marvin Humphrey wrote: > > Hi, Ted, > > Do you need someone else to finish and file the report? > > Marvin Humphrey > > --

Re: June report prep

2015-06-14 Thread Marvin Humphrey
Hi, Ted, Do you need someone else to finish and file the report? Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: June report prep

2015-06-10 Thread Patrick Hunt
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

Re: June report prep

2015-06-09 Thread Ted Dunning
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

Re: June report prep

2015-06-09 Thread John D. Ament
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, 20

Re: June report prep

2015-06-08 Thread Patrick Hunt
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 res

Re: June report prep

2015-06-06 Thread Marvin Humphrey
On Thu, Jun 4, 2015 at 11:37 PM, Marvin Humphrey 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

Re: June report prep

2015-06-06 Thread David Nalley
On Fri, Jun 5, 2015 at 3:23 PM, Patrick Hunt 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 addresse

Re: June report prep

2015-06-05 Thread Marvin Humphrey
On Fri, Jun 5, 2015 at 3:13 PM, Marvin Humphrey 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

Re: June report prep

2015-06-05 Thread Ted Dunning
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 concer

Re: June report prep

2015-06-05 Thread Marvin Humphrey
On Fri, Jun 5, 2015 at 5:55 AM, Ted Dunning 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 cle

Re: June report prep

2015-06-05 Thread Patrick Hunt
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 b

Re: June report prep

2015-06-05 Thread Ted Dunning
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 ei

Re: June report prep

2015-06-05 Thread John D. Ament
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 wrote: > Marvin, > > Thanks as ever for the coaching. > > One question that has

Re: June report prep

2015-06-05 Thread Ted Dunning
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 question

Re: June report prep

2015-06-04 Thread Marvin Humphrey
On Tue, May 26, 2015 at 8:38 PM, Ted Dunning wrote: > On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey > 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

Re: June report prep

2015-05-29 Thread Luke Han
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

Re: June report prep

2015-05-29 Thread Ted Dunning
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. Ev

Re: June report prep

2015-05-29 Thread Luke Han
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 : > On Tue, May 26,

Re: June report prep

2015-05-27 Thread Marvin Humphrey
On Tue, May 26, 2015 at 8:38 PM, Ted Dunning wrote: > On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey > 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

Re: June report prep

2015-05-26 Thread Ted Dunning
On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey 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 re

Re: June report prep

2015-05-26 Thread John D. Ament
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 d

June report prep

2015-05-26 Thread Marvin Humphrey
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 resp