Re: Cultivating Outstanding IP Stewards
I don't think this is prudent, having only one binding vote is too low a check. We at the ASF have a responsibility to the public. I want to be certain that no one steam rolls the process. Just the fact that there are edge cases means we need to be careful. Regards, Dave Sent from my iPhone On Nov 10, 2013, at 4:04 AM, ant elder ant.el...@gmail.com wrote: How about simply changing the rules for Incubator releases so that they don't require at least three binding votes, but instead make it at least three votes only one of which must be binding. That would mean there would still be the element of oversight that a mentor vote gives but avoids all the problems with not having three mentors. I'm sure the board would grant the Incubator authority to implement that change. ...ant On Sun, Nov 10, 2013 at 8:00 AM, Alex Harui aha...@adobe.com wrote: IMO, there are two problems: 1) We're trying to train folks to manage IP for their community but they have to seek approval from folks are aren't as vested in their community. My analogy is telling a new city council member: Welcome to the city council. For the next year all of your decisions will require ratification by 3 state senators. 2) Release voting takes a long time. It would seem like tools should be able to reduce the time on several of the steps, except for this one from [1] compile it as provided, and test the resulting executable on their own platform. Sometimes I think about trying to get on the IPMC and helping some podling get a release out but: A) Really, I just want to help check the legal aspects of a podling's release and don't have bandwidth to want to take on the other roles implied by being on the IPMC. B) I don't want to take the time to figure out how to build and test a release that I have no vested interest in. Now, incubating releases are not official releases, right? So why have such time- consuming requirements to get approval from the IPMC? Let's assume that the podling folks tested the building and operation of the source package. Could we build an ant script that any IPMC member or any PMC member from any TLP (to expand the pool of potential helpers to folks who supposedly know how) can run just to check: 1) source package has the name incubating - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Majority vs Lazy Majority
Hi, Every American that has voted for a public office knows that winning the majority has nothing to do with the total population of potential voters. Where I'm from voting is compulsory so it has a different meaning. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Majority vs Lazy Majority
Well I can assure you it’s NOT compulsory at Apache ;-). On Nov 10, 2013, at 3:54 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Every American that has voted for a public office knows that winning the majority has nothing to do with the total population of potential voters. Where I'm from voting is compulsory so it has a different meaning. Thanks, Justin - 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
[RESULT] [VOTE] Release of Apache Allura (incubating) v1.0.1
Hello, Thanks for your support! The 72 hours have passed and we have 10 positive votes, of which 3 are binding and 7 are non-binding. We now have the required number of positive binding votes and will therefore proceed with the release. Thanks, Cory Johns Binding votes (3): +1 Rich Bowen +1 Daniel Gruno +1 Jim Jagielski Non-binding votes (7): +1 Dave Brondsema +1 Cory Johns +1 Daniel Hinojosa +1 Tim Van Steenburgh +1 Wayne Witzel III +1 Roberto Galoppini +1 Christopher Tsai Votes from the Incubator mailing list: http://mail-archives.apache.org/mod_mbox/incubator-general/201311.mbox/%3CCAGN0FaSkTrKpfVMwvC5LMcsPojU8DQ4K8%3DGhg7kJVHJRPxHFkA%40mail.gmail.com%3E Votes from the Allura mailing list: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201310.mbox/%3CCAGN0FaRemYQmMLcd%3DEr91%2BL0zhwU1kyPQVeG4wMCeJ22_nALUg%40mail.gmail.com%3E On Sat, Nov 9, 2013 at 9:50 AM, Jim Jagielski j...@jagunet.com wrote: Agreed. Not a blocker: Still +1 On Nov 8, 2013, at 1:52 PM, Dave Brondsema d...@brondsema.net wrote: On 11/8/13 6:17 AM, Daniel Gruno wrote: On 11/04/2013 07:09 PM, Cory Johns wrote: Hello, This is a call for a vote on Apache Allura 1.0.1 incubating. This is our second attempt at an initial release, which specifically addresses the concerns raised in the previous, cancelled vote. A vote was held on developer mailing list and it passed with 8 +1's, and 0 -1's or +0's (with one of the +1's being from a project mentor) and now requires a vote on general@incubator.apache.org. The [VOTE] and [DISCUSS] threads can be found at: [VOTE]: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201310.mbox/%3CCAGN0FaRemYQmMLcd%3DEr91%2BL0zhwU1kyPQVeG4wMCeJ22_nALUg%40mail.gmail.com%3E [DISCUSS]: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201310.mbox/%3CCAGN0FaR0FeNuMB2%3D_%2Bea8Z15a94T-OR9oamk4v7LhxF-ijxf3Q%40mail.gmail.com%3E Source tarball and signature are available at: https://dist.apache.org/repos/dist/dev/incubator/allura/allura-incubating-1.0.1.tar.gz https://dist.apache.org/repos/dist/dev/incubator/allura/allura-incubating-1.0.1.tar.gz.asc Checksums: MD5:06bd5311ab4fc5103e4fb96e737da2ff allura-incubating-1.0.1.tar.gz SHA1: 76a6bfdaee1a3c38e920f3f173fd920e1f8aefd0 allura-incubating-1.0.1.tar.gz SHA512: 813a15b1c32a90e6404bd432874b7ed3ede3b62162d39fde35f6bbfd540f0f75cfc9ca348eeaac3992b2455366339133d0d69524fe118059edb20a440ed7f09c allura-incubating-1.0.1.tar.gz Note: The checksum values are correct, but the format of the checksum files is off slightly (single instead of double space after checksum, absolute path for file name) preventing automatic verification with the -c option without minor editing of the files. (This was discussed on the [DISCUSS] thread [1] and the current files are what were voted on.) The KEYS file can be found at: http://www.apache.org/dist/incubator/allura/KEYS The release has been signed with key (449C78B1): http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0xDB6E071B449C78B1 Source corresponding to this release can be found at: Commit: 924e0204706aeb5367e60df19ba38b26ac4474a3 Tag:asf_release_1.0.1 Browse: https://git-wip-us.apache.org/repos/asf?p=incubator-allura.git;a=shortlog;h=refs/tags/asf_release_1.0.1 The RAT report is available at: https://sourceforge.net/p/allura/pastebin/525eea8f485acd3ba7c37a22 Vote will be open for at least 72 hours (2013-11-07 12PM IST). [1]: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201310.mbox/%3CCAGN0FaRy5GNSEv7_km_h8LmO3ZPWSsyOzXUqRh5tuVhFhNpSzQ%40mail.gmail.com%3E +0.9 (I might be inclined to add another 0.1 if you can sway me) There is still a reference to sourceforge inside the allura base - when I create a new project and click on the Git tab, I get this: Did you get asked for your SourceForge password during this process? You can securely use your Git repository and avoid having to re-enter your password by setting up an ssh-key. I don't think this is a critical or legal blocker, so given the social/procedural overhead of getting an Allura release out, I think we'd be better off to ship this release as-is. We can fix this for our next release. There are some other less-prominent references to SourceForge in the codebase as well. -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - 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: NPanday needs our attention
On Thu, Nov 7, 2013 at 7:32 PM, Raphael Bircher r.birc...@gmx.ch wrote: Hi all This month I review NPanday as Shepherd. And this project realy needs our attention! There is nearly no Mailing list activity since months. The only one who writes frequenty is the Jenkins server who told that the build is broken. The only human who talks some times on the ML is Brett Porter. They have only one mentor, Dennis Lundberg, who say nothing since a year. Report is not field (wich is no surprice) I wrote a message to the Npanday-dev and asked if there is still energy in the project or not. If there is still life in this project, than they need minimum one, better two new mentors. I can't help there, because I'm not a IPMC. If not, we should think about retiring. Just my option. Hi Raphael, If you think any of this should go into our November Board report, can you please post it to the wiki? I'm not sure how much of this text you'd want to be there. Also to my fellow IPMC members: I'm lacking the bandwidth right now to take point on addressing another low-activity podling. In addition to everything else, I still have to follow through on the retirement steps for Tashi. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: NPanday needs our attention
Am 11.11.13 22:55, schrieb Marvin Humphrey: On Thu, Nov 7, 2013 at 7:32 PM, Raphael Bircher r.birc...@gmx.ch wrote: Hi all This month I review NPanday as Shepherd. And this project realy needs our attention! There is nearly no Mailing list activity since months. The only one who writes frequenty is the Jenkins server who told that the build is broken. The only human who talks some times on the ML is Brett Porter. They have only one mentor, Dennis Lundberg, who say nothing since a year. Report is not field (wich is no surprice) I wrote a message to the Npanday-dev and asked if there is still energy in the project or not. If there is still life in this project, than they need minimum one, better two new mentors. I can't help there, because I'm not a IPMC. If not, we should think about retiring. Just my option. Hi Raphael, If you think any of this should go into our November Board report, can you please post it to the wiki? I'm not sure how much of this text you'd want to be there. I propose to move the report to december because of delay. Since my mail there is a bit activity there, Unfortunaly all newbies. So the problem is actualy, that they can't do work because no one review it. I advise them to be patient, and give the others time to wake up. So there is a chance that the project can be restarted. It would be good to have somone experianced there. Greetings Raphael - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: NPanday needs our attention
On Mon, Nov 11, 2013 at 2:12 PM, Raphael Bircher r.birc...@gmx.ch wrote: I propose to move the report to december because of delay. +1, good plan. I'll remove their section from the report, leaving them only in the Did not report, expected next month summary. Also so everybody knows: when podlings miss a month, in order to make sure we don't forget about them, someone needs to add back their monthly attribute in podlings.xml (as I've now done for NPanday). That will cause them to get the automated report reminder, get added to the report template, get assigned a shepherd, etc. -reporting group=2/ +reporting group=2 monthly=trueDecember/reporting Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Shepherding November 2013
Shepherd reviews extracted from https://wiki.apache.org/incubator/November2013: Ambari Roman Shaposhnik (rvs): Project should be pretty close to a well deserved graduation. Kudos to the community building effort! BatchEE Suresh Marru (smarru): The podling is waiting on website setup. The dev mailing list is not yet setup (or atleast not visible in archives), surprisingly the user and commit lists have archives, is something amiss? Blur Suresh Marru (smarru): * The podling seems to be very healthy and kudos to PPMC for pulling of their first release and getting ready for second. * A big kudos to couple of mentors for pro-actively engaging. * Blur website does not conform to the branding guidelines and should add the incubator logo and disclaimer prominently. Also, should include the ASF, security and thanks to sponsor links. Sirona Roman Shaposhnik (rvs): Given that it has been less then a month since project entered incubation I see that the most immediate needs of having a source code repo, JIRA and MLs have been met. Still it would be nice if the bootstrapping were to wrap up as quickly as possible. At this point, for example, there's no website and no wiki, etc. Those are the tools for helping the community growth and it would be very nice to see those coming online in a few weeks. Tez Andrei Savu (asavu): The project is moving very quickly, but needs to make a release soon. Podlings which did not receive shepherd reviews this cycle: Aurora DeviceMap Droids Hadoop Development Tools Knox Open Climate Workbench Ripple Sentry Storm - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding November 2013
Hi Marvin, Can anyone volunteer? Or only IPMC? I'd like to volunteer to help you guys out next month. John On Mon, Nov 11, 2013 at 7:13 PM, Marvin Humphrey mar...@rectangular.comwrote: On Mon, Nov 11, 2013 at 3:19 PM, Raphael Bircher r.birc...@gmx.ch wrote: Am 12.11.13 00:04, schrieb Marvin Humphrey: Podlings which did not receive shepherd reviews this cycle: Aurora DeviceMap Droids Hadoop Development Tools Knox Open Climate Workbench Ripple Sentry Storm So many not reviewed? Ok, I'm willing to take two text month if needed. Shepherd participation waxes and wanes. We ostensibly had all podlings covered in that every one was assigned a shepherd, but four of our shepherd volunteers didn't come through this cycle, including three stalwarts who we have been able to rely on most of the time. I'm not sure how to solve this problem even if we get more volunteers and spread the load out, because by the time we discover that a shepherd didn't submit a review, it's too late for someone else to fill in. The shepherd window with the current schedule is 4 days long (Thursday through Sunday), because we need to leave time for people to respond to the shepherd comments before the report is filed. Doubling up shepherds would probably make matters worse, because each would likely let the the other assignee take care of things. Maybe if we were to recruit enough volunteers that each shepherd had only one assignment per month, there would be less fatigue and we'd get higher participation rates? Next month's cycle will have more podlings and we probably won't be able to cover all of them with the available roster of volunteers. Your taking on a second assignment is much appreciated. But please don't burn out! You've done a great job both last month with Olingo and this month with NPanday. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding November 2013
John D. Ament wrote: Hi Marvin, Can anyone volunteer? Or only IPMC? I'd like to volunteer to help you guys out next month. Anyone can. Please. I gather that you just need to add/maintain this file: https://svn.apache.org/repos/asf/incubator/public/trunk/content/shepherds.json -David John - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: projects graduated need to tidy up
I've decided that I must have been doing *something* wrong as I was just able to commit to this file. On Thu, Nov 7, 2013 at 9:46 PM, David Crossley cross...@apache.org wrote: John D. Ament wrote: Well, must be missing something. I'm 'johndament' yet I don't have write access to the trunk. I used to understand svn auth, but not so sure now. Following this: http://incubator.apache.org/guides/mentor.html#who-auth-karma It seems to me that all in committers as well as all in the incubator group have rw access to incubator/public/trunk/ Do your fellow project committers also have this trouble? If so, i wonder if this identifies a problem which indicates why few people have edited podlings.xml or fix the website docs. If so, then i would be horrifed that they have not told us. -David On Thu, Nov 7, 2013 at 6:26 PM, David Crossley cross...@apache.org wrote: John D. Ament wrote: Well, I can appreciate the frustration. I'm willing to help clean up some of this stuff. Any special rights required to edit podlings.xml? IIUC then everyone who comes through the Incubator is able: http://people.apache.org/committers-by-project.html#incubator -David On Thu, Nov 7, 2013 at 5:45 PM, David Crossley cross...@apache.org wrote: John D. Ament wrote: David, On that note, how come DeltaSpike is still listed as incubating at [1] Note the table on the 3rd bullet. [1]: http://incubator.apache.org/ Because these graduated projects do not tidy up after themselves. They seem to leave everything for other Incubator volunteers to clean up in their wake. Such a mess causes the Incubator tools, that try so hard to help us all, to become overloaded and then not as useful because there is too much fluff. DeltaSpike is not the only one. See the list that poor Clutch tries so desperately to highlight: http://incubator.apache.org/clutch.html#other which also attempts to directly link them to the relevant docs. The projects listing http://incubator.apache.org/projects/ also tries to encourage projects to maintain their own records. I presume that these projects will continue such behaviour as TLPs. (Sorry if i come across as frustrated in these threads. I certainly am, but trying to curb it.) -David On Thu, Nov 7, 2013 at 5:23 PM, David Crossley cross...@apache.org wrote: David Crossley wrote: Romain Manni-Bucau wrote: Hi David not sure what you mean but list are working AFAIK. We got batchee mail this morning again and I got some sirona mails yesterday The archives. Clutch gathers the mail list addresses by ensuring that the archives are available [1]. See the URL provided below in my initial email. e.g. http://mail-archives.apache.org/mod_mbox/#batchee.incubator There is only the commits archives. Someone from these two projects needs to follow up with Infra until your resources are properly established. And this is why you are not receiving the report reminders. [1] We should enhance this page to explain more detail about how the set of reporting mailing list addresses are handled. I have explained it many times in email, so we should find that and add it to this doc. http://incubator.apache.org/facilities.html#reminders The Voting Status monitor (the poor neglected thing!) has also been trying to warn about this issue. See the top-left of http://incubator.apache.org/ and then the bottom table. -David Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/7 David Crossley cross...@apache.org: Those two reminders are intended for BatchEE and Sirona. Their email dev list archive is not yet available, so this goes to general@ list. Clutch does detect their commits lists, but not their dev lists. http://mail-archives.apache.org/mod_mbox/#batchee.incubator http://mail-archives.apache.org/mod_mbox/#sirona.incubator Does anyone know why? Are they missing moderators or something? -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding November 2013
Something is fishy. I haven't received any Shepherd assignments ... email for November and I've done no reviews. It's not clear to me how my name got added as a reviewer for Tez. On Mon, Nov 11, 2013 at 3:04 PM, Marvin Humphrey mar...@rectangular.comwrote: Shepherd reviews extracted from https://wiki.apache.org/incubator/November2013: Ambari Roman Shaposhnik (rvs): Project should be pretty close to a well deserved graduation. Kudos to the community building effort! BatchEE Suresh Marru (smarru): The podling is waiting on website setup. The dev mailing list is not yet setup (or atleast not visible in archives), surprisingly the user and commit lists have archives, is something amiss? Blur Suresh Marru (smarru): * The podling seems to be very healthy and kudos to PPMC for pulling of their first release and getting ready for second. * A big kudos to couple of mentors for pro-actively engaging. * Blur website does not conform to the branding guidelines and should add the incubator logo and disclaimer prominently. Also, should include the ASF, security and thanks to sponsor links. Sirona Roman Shaposhnik (rvs): Given that it has been less then a month since project entered incubation I see that the most immediate needs of having a source code repo, JIRA and MLs have been met. Still it would be nice if the bootstrapping were to wrap up as quickly as possible. At this point, for example, there's no website and no wiki, etc. Those are the tools for helping the community growth and it would be very nice to see those coming online in a few weeks. Tez Andrei Savu (asavu): The project is moving very quickly, but needs to make a release soon. Podlings which did not receive shepherd reviews this cycle: Aurora DeviceMap Droids Hadoop Development Tools Knox Open Climate Workbench Ripple Sentry Storm - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding November 2013
On Mon, Nov 11, 2013 at 4:17 PM, John D. Ament john.d.am...@gmail.com wrote: Hi Marvin, Can anyone volunteer? Or only IPMC? Anyone can volunteer. Honestly, I would be thrilled if our shepherd roster was composed entirely of fresh recruits rather than grizzled IPMC veterans. Shepherding is a great way to gain knowledge about Apache. The first task of a shepherd is to scan the mailing list archives for the last three-month cycle looking for Mentor participation. What the IPMC needs most is a dead man's switch[1] which warns us when activity is dangerously low. So long as you can tell us Podling is active, N mentors participating, our basic needs have been met. The benefit for novice shepherds is that that you're looking through Mentor emails -- and what Mentors have to say to other podlings is often very interesting. You get to see what kinds of problems those podlings are working through and what guidance their Mentors are giving -- possibly providing a new perspective on challenges faced by projects you participate in. A secondary function of shepherding is to provide an outsider's perspective for the benefit of the podling being reviewed. That's a task that only someone fairly experienced should take on, because it's politically sensitive. However, while detailed commentary can be quite helpful, in my view there is such great value to the Incubator and the ASF at large in increasing cross-pollination that we should prioritize giving new volunteers a chance. I'd like to volunteer to help you guys out next month. Excellent. I see that you've added yourself to shepherds.json while I was writing this -- thanks for signing up! Marvin Humphrey http://en.wikipedia.org/wiki/Dead_man%27s_switch - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding November 2013
Andrei Savu wrote: Something is fishy. I haven't received any Shepherd assignments ... email for November and I've done no reviews. It's not clear to me how my name got added as a reviewer for Tez. Dunno about email. I added a section to explain the process a bit: http://incubator.apache.org/facilities.html#shepherds So you were assigned to Tez by the script. Regarding the edits, my local 'mairix' search found this: https://wiki.apache.org/incubator/November2013?action=diffrev1=26rev2=27 -David On Mon, Nov 11, 2013 at 3:04 PM, Marvin Humphrey mar...@rectangular.comwrote: Shepherd reviews extracted from https://wiki.apache.org/incubator/November2013: Ambari Roman Shaposhnik (rvs): Project should be pretty close to a well deserved graduation. Kudos to the community building effort! BatchEE Suresh Marru (smarru): The podling is waiting on website setup. The dev mailing list is not yet setup (or atleast not visible in archives), surprisingly the user and commit lists have archives, is something amiss? Blur Suresh Marru (smarru): * The podling seems to be very healthy and kudos to PPMC for pulling of their first release and getting ready for second. * A big kudos to couple of mentors for pro-actively engaging. * Blur website does not conform to the branding guidelines and should add the incubator logo and disclaimer prominently. Also, should include the ASF, security and thanks to sponsor links. Sirona Roman Shaposhnik (rvs): Given that it has been less then a month since project entered incubation I see that the most immediate needs of having a source code repo, JIRA and MLs have been met. Still it would be nice if the bootstrapping were to wrap up as quickly as possible. At this point, for example, there's no website and no wiki, etc. Those are the tools for helping the community growth and it would be very nice to see those coming online in a few weeks. Tez Andrei Savu (asavu): The project is moving very quickly, but needs to make a release soon. Podlings which did not receive shepherd reviews this cycle: Aurora DeviceMap Droids Hadoop Development Tools Knox Open Climate Workbench Ripple Sentry Storm - 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: Shepherding November 2013
On Mon, Nov 11, 2013 at 6:31 PM, Andrei Savu as...@apache.org wrote: Something is fishy. I haven't received any Shepherd assignments ... email for November and I've done no reviews. It's not clear to me how my name got added as a reviewer for Tez. The comment was added by Owen O'Malley. I've corrected the report. With regards to Shepherd assignments email, I didn't send one out this month, instead noting in the November 2013 report timeline that the assignments are on the report wiki page. Maybe that explains the low participation. :( In future months, I think there should be only one email, so please watch for it. The shepherd assignments are now done automatically by a script[1]; I plan to add another `report_timeline.py` script which generates the report timeline email, and finally a `report_runbook.py` which generates all the commands and instructions that a Report Manager would need to execute -- analogous to a release runbook. I'd meant to have all this stuff done two months ago, but other Incubator Chair responsibilities kept eating my time. I think it's important for future Chairs that we lighten the load of preparing the monthly report. Marvin Humphrey [1] It was actually pretty tricky (and time-consuming) to make the shepherd assignments manually, taking into account all the necessary criteria: never repeat a podling-shepherd pairing, Mentors can't be shepherds for their own podlings, only so many per month per person, some shepherds prefer specific types of podlings, etc. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding November 2013
Hi, Just added myself. I've seen a project though incubation, I'm a PMC member and been a release manager. Thanks, Justin On Tue, Nov 12, 2013 at 2:50 PM, Marvin Humphrey mar...@rectangular.comwrote: On Mon, Nov 11, 2013 at 6:31 PM, Andrei Savu as...@apache.org wrote: Something is fishy. I haven't received any Shepherd assignments ... email for November and I've done no reviews. It's not clear to me how my name got added as a reviewer for Tez. The comment was added by Owen O'Malley. I've corrected the report. With regards to Shepherd assignments email, I didn't send one out this month, instead noting in the November 2013 report timeline that the assignments are on the report wiki page. Maybe that explains the low participation. :( In future months, I think there should be only one email, so please watch for it. The shepherd assignments are now done automatically by a script[1]; I plan to add another `report_timeline.py` script which generates the report timeline email, and finally a `report_runbook.py` which generates all the commands and instructions that a Report Manager would need to execute -- analogous to a release runbook. I'd meant to have all this stuff done two months ago, but other Incubator Chair responsibilities kept eating my time. I think it's important for future Chairs that we lighten the load of preparing the monthly report. Marvin Humphrey [1] It was actually pretty tricky (and time-consuming) to make the shepherd assignments manually, taking into account all the necessary criteria: never repeat a podling-shepherd pairing, Mentors can't be shepherds for their own podlings, only so many per month per person, some shepherds prefer specific types of podlings, etc. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding November 2013
On Mon, Nov 11, 2013 at 8:05 PM, Justin Mclean justinmcl...@gmail.com wrote: Just added myself. I've seen a project though incubation, I'm a PMC member and been a release manager. Sweet, Justin's on board. Great to have you! Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding November 2013
On Mon, Nov 11, 2013 at 7:50 PM, Marvin Humphrey mar...@rectangular.comwrote: The comment was added by Owen O'Malley. I've corrected the report. I'm glad we sorted that out. With regards to Shepherd assignments email, I didn't send one out this month, instead noting in the November 2013 report timeline that the assignments are on the report wiki page. Maybe that explains the low participation. :( Sorry for not helping this month - I've missed the note on the report timeline.
