Re: More and better report nagging
I really don't object, but when the podling has graduated, they don't have such a reminder. What I am trying to say: the podling gets an reminder. It should be possible to just write this report without nagging. If they don't do it, it's a signal that "something went wrong". Now if you nag, somebody would do it finally. But it would no longer reflect if people actually care on the project or just want to make these e-mails stop. Of course, some Mentors nag when a report is not done. Finally it does also reflect on the Mentors. That said, i am no opposed if somebody would enable that feature, but on the other hand i think it is good as it is now. Cheers Christian On Mon, Dec 17, 2012 at 3:36 AM, Benson Margulies wrote: > I see how I could arrange for Marvin or someone like him to bug > podlings until they actually deliver a report if they are due in the > cycle. > > To enable this, I'll add a > > [ ] Add an X between the brackets when the report is complete. > > to the template. > > This could be taken to gentle reminders to individual mentors. > > Would anyone find this sort of thing objectionable? > > Now that I've figured out the MoinMoin XMLRPC api, I am positively dangerous. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: More and better report nagging
On Mon, Dec 17, 2012 at 5:54 AM, Christian Grobmeier wrote: > I really don't object, but when the podling has graduated, they don't > have such a reminder. > > What I am trying to say: the podling gets an reminder. It should be > possible to just write this report without nagging. If they don't do > it, it's a signal that "something went wrong". Now if you nag, > somebody would do it finally. But it would no longer reflect if people > actually care on the project or just want to make these e-mails stop. Please have mercy upon me. I'm the chair. I'm responsible for a complete report. I found it labor intensive to check for all the reports, and to manually nag the laggards. If it makes you feel better, you could view this as my personal tool to automate a task that I have to do anyway. > > Of course, some Mentors nag when a report is not done. Finally it does > also reflect on the Mentors. > > That said, i am no opposed if somebody would enable that feature, but > on the other hand i think it is good as it is now. > > Cheers > Christian > > > On Mon, Dec 17, 2012 at 3:36 AM, Benson Margulies > wrote: >> I see how I could arrange for Marvin or someone like him to bug >> podlings until they actually deliver a report if they are due in the >> cycle. >> >> To enable this, I'll add a >> >> [ ] Add an X between the brackets when the report is complete. >> >> to the template. >> >> This could be taken to gentle reminders to individual mentors. >> >> Would anyone find this sort of thing objectionable? >> >> Now that I've figured out the MoinMoin XMLRPC api, I am positively dangerous. >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: More and better report nagging
On Mon, Dec 17, 2012 at 1:24 PM, Benson Margulies wrote: > On Mon, Dec 17, 2012 at 5:54 AM, Christian Grobmeier > wrote: >> I really don't object, but when the podling has graduated, they don't >> have such a reminder. >> >> What I am trying to say: the podling gets an reminder. It should be >> possible to just write this report without nagging. If they don't do >> it, it's a signal that "something went wrong". Now if you nag, >> somebody would do it finally. But it would no longer reflect if people >> actually care on the project or just want to make these e-mails stop. > > Please have mercy upon me. I'm the chair. I'm responsible for a > complete report. I found it labor intensive to check for all the > reports, and to manually nag the laggards. If it makes you feel > better, you could view this as my personal tool to automate a task > that I have to do anyway. I have mercy. Do whatever you think fits best to you. In my opinion constant nagging is not necessary - "did not report" does the job as well as this line is a report as well; if a project constantly fails report to report its more a matter to retirement than to play kindergardener. Again, I do not object. Just wanted to give a you my thoughts. Cheers >> >> Of course, some Mentors nag when a report is not done. Finally it does >> also reflect on the Mentors. >> >> That said, i am no opposed if somebody would enable that feature, but >> on the other hand i think it is good as it is now. >> >> Cheers >> Christian >> >> >> On Mon, Dec 17, 2012 at 3:36 AM, Benson Margulies >> wrote: >>> I see how I could arrange for Marvin or someone like him to bug >>> podlings until they actually deliver a report if they are due in the >>> cycle. >>> >>> To enable this, I'll add a >>> >>> [ ] Add an X between the brackets when the report is complete. >>> >>> to the template. >>> >>> This could be taken to gentle reminders to individual mentors. >>> >>> Would anyone find this sort of thing objectionable? >>> >>> Now that I've figured out the MoinMoin XMLRPC api, I am positively >>> dangerous. >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> >> >> -- >> http://www.grobmeier.de >> https://www.timeandbill.de >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: More and better report nagging
On Mon, Dec 17, 2012 at 7:56 AM, Christian Grobmeier wrote: > On Mon, Dec 17, 2012 at 1:24 PM, Benson Margulies > wrote: >> On Mon, Dec 17, 2012 at 5:54 AM, Christian Grobmeier >> wrote: >>> I really don't object, but when the podling has graduated, they don't >>> have such a reminder. >>> >>> What I am trying to say: the podling gets an reminder. It should be >>> possible to just write this report without nagging. If they don't do >>> it, it's a signal that "something went wrong". Now if you nag, >>> somebody would do it finally. But it would no longer reflect if people >>> actually care on the project or just want to make these e-mails stop. >> >> Please have mercy upon me. I'm the chair. I'm responsible for a >> complete report. I found it labor intensive to check for all the >> reports, and to manually nag the laggards. If it makes you feel >> better, you could view this as my personal tool to automate a task >> that I have to do anyway. > > I have mercy. Do whatever you think fits best to you. > > In my opinion constant nagging is not necessary - "did not report" > does the job as well as this line is a report as well; if a project > constantly fails report to report its more a matter to retirement than > to play kindergardener. FWIW, I feel the same. I'd rather see 'did not report' and let the IPMC look for that pattern. Maybe just have your template generator default to DNR in the text? --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: More and better report nagging
On Mon, Dec 17, 2012 at 4:04 PM, Tim Williams wrote: > FWIW, I feel the same. I'd rather see 'did not report' and let the > IPMC look for that pattern. Maybe just have your template generator > default to DNR in the text? +1 on defaulting to DNR. How about sending out the whole Incubator report to all podling dev lists, every month? That way the DNR shows up without an IPMC member having to notice and take action. But in addition, it increases podling exposure to other projects and to the ASF at large. An alternative is to send it out to only the podlings that are reporting for a cycle, but that's more work and doesn't serve the purpose of connecting the podling to being in the Incubator quite so cleanly. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: More and better report nagging
On Mon, Dec 17, 2012 at 7:35 PM, Marvin Humphrey wrote: > On Mon, Dec 17, 2012 at 4:04 PM, Tim Williams wrote: >> FWIW, I feel the same. I'd rather see 'did not report' and let the >> IPMC look for that pattern. Maybe just have your template generator >> default to DNR in the text? > > +1 on defaulting to DNR. > > How about sending out the whole Incubator report to all podling dev lists, > every month? That way the DNR shows up without an IPMC member having to > notice and take action. But in addition, it increases podling exposure to > other projects and to the ASF at large. > > An alternative is to send it out to only the podlings that are reporting for a > cycle, but that's more work and doesn't serve the purpose of connecting the > podling to being in the Incubator quite so cleanly. I feel all that we are all volunteers, that podlings are volunteers who don't necessarily have their organizational act together, and that calling them out for DNR is not a very effective technique to providing the supervision that we, as a PMC, are on the hook for. So I'm inclined for now to nag, and to spend a few minutes making that job less labor-intensive. > > Marvin Humphrey > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: More and better report nagging
On Mon, Dec 17, 2012 at 7:48 PM, Benson Margulies wrote: > On Mon, Dec 17, 2012 at 7:35 PM, Marvin Humphrey > wrote: >> On Mon, Dec 17, 2012 at 4:04 PM, Tim Williams wrote: >>> FWIW, I feel the same. I'd rather see 'did not report' and let the >>> IPMC look for that pattern. Maybe just have your template generator >>> default to DNR in the text? >> >> +1 on defaulting to DNR. >> >> How about sending out the whole Incubator report to all podling dev lists, >> every month? That way the DNR shows up without an IPMC member having to >> notice and take action. But in addition, it increases podling exposure to >> other projects and to the ASF at large. >> >> An alternative is to send it out to only the podlings that are reporting for >> a >> cycle, but that's more work and doesn't serve the purpose of connecting the >> podling to being in the Incubator quite so cleanly. > > > I feel all that we are all volunteers, that podlings are volunteers > who don't necessarily have their organizational act together, and that > calling them out for DNR is not a very effective technique to > providing the supervision that we, as a PMC, are on the hook for. So > I'm inclined for now to nag, and to spend a few minutes making that > job less labor-intensive. I'm beginning to think your mind's made up and the original question was a pleasantry, but in case not... I hold a different view of things. While I think that we, ok you, are on the hook for a board report, we've (PMC) delegated[1] the reporting of each podling to the mentors that we approved for that podling. We aren't "calling out the podling" as DNR - we're calling out their mentor as DNR. If there's additional nags to go out, I'd do my "default to DNR" and send the nag to the mentors directly. Ultimately, making that job less labor-intensive involves getting mentors and would-be-mentors to realize they can't simply go around spewing their seeds as absentee fathers - it's a real commitment; to the podling and to the foundation. Shucks, keeping a record of deadbeat mentors would prolly help... In the end though, you've a thankless and tough job, so consider these as constructive thoughts to be readily ignored in favor of whatever it takes to get your job done:) Thanks, --tim [1] - http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: More and better report nagging
On Mon, Dec 17, 2012 at 8:23 PM, Tim Williams wrote: > On Mon, Dec 17, 2012 at 7:48 PM, Benson Margulies > wrote: >> On Mon, Dec 17, 2012 at 7:35 PM, Marvin Humphrey >> wrote: >>> On Mon, Dec 17, 2012 at 4:04 PM, Tim Williams wrote: FWIW, I feel the same. I'd rather see 'did not report' and let the IPMC look for that pattern. Maybe just have your template generator default to DNR in the text? >>> >>> +1 on defaulting to DNR. >>> >>> How about sending out the whole Incubator report to all podling dev lists, >>> every month? That way the DNR shows up without an IPMC member having to >>> notice and take action. But in addition, it increases podling exposure to >>> other projects and to the ASF at large. >>> >>> An alternative is to send it out to only the podlings that are reporting >>> for a >>> cycle, but that's more work and doesn't serve the purpose of connecting the >>> podling to being in the Incubator quite so cleanly. >> >> >> I feel all that we are all volunteers, that podlings are volunteers >> who don't necessarily have their organizational act together, and that >> calling them out for DNR is not a very effective technique to >> providing the supervision that we, as a PMC, are on the hook for. So >> I'm inclined for now to nag, and to spend a few minutes making that >> job less labor-intensive. > > I'm beginning to think your mind's made up and the original question > was a pleasantry, but in case not... At this point I'm cogitating. > > I hold a different view of things. While I think that we, ok you, are > on the hook for a board report, we've (PMC) delegated[1] the reporting > of each podling to the mentors that we approved for that podling. We > aren't "calling out the podling" as DNR - we're calling out their > mentor as DNR. If there's additional nags to go out, I'd do my > "default to DNR" and send the nag to the mentors directly. > > Ultimately, making that job less labor-intensive involves getting > mentors and would-be-mentors to realize they can't simply go around > spewing their seeds as absentee fathers - it's a real commitment; to > the podling and to the foundation. Shucks, keeping a record of > deadbeat mentors would prolly help... > > In the end though, you've a thankless and tough job, so consider these > as constructive thoughts to be readily ignored in favor of whatever it > takes to get your job done:) > > Thanks, > --tim > > [1] - > http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Mesos 0.10.0-incubating (RC2)
+1 Tested it on Mac OS X. Matei On Dec 11, 2012, at 12:56 PM, Benjamin Hindman wrote: > Please vote on releasing the following candidate as Apache Mesos > (incubating) version 0.10.0. This will be the second incubator release for > Mesos in Apache. > > The candidate for Mesos 0.10.0-incubating release is available at: > > http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz > > The tag to be voted on: > > https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.10.0-incubating-RC2 > > The MD5 checksum of the tarball can be found at: > > http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz.md5 > > The signature of the tarball can be found at: > > http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz.asc > > Mesos' KEYS file, containing the PGP keys used to sign the release: > http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS > > Please vote on releasing this package as Apache Mesos 0.10.0-incubating! > > The vote is open until Friday, December 14th at 5:00 pm (PST) and passes if > a majority of at least 3 +1 IPMC votes are cast. > > [ ] +1 Release this package as Apache Mesos 0.10.0-incubating > [ ] -1 Do not release this package because ... > > To learn more about Apache Mesos, please see http://www.mesosproject.org. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
