bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary <>
Subject Re: June reports in two weeks
Date Tue, 05 Jun 2012 23:27:04 GMT
Yes, sorry about this but I am a bit out of contact. I am effectively 
away until next week but I would like to make some time to try to at 
least contribute to the report.

A few small things that immediately spring to mind that could be worth 
pointing out are:

  * we have apparently had some limited growth in the community with 
people providing code to the project
  * the last report that I remember, I think we had talked about first 
commits and now we appear to have a reasonable body of code that will 
form the bulk of the initial release.

I think from that it is clear that I haven't had time to come up with 
much! I will try to make sure that I have some time to help review tomorrow.

Sorry about the bad timing and a big thank you to Greg for the extra help!


On 05/06/12 15:41, Greg Stein wrote:
> Offlist, I've heard both Gary and Hyrum are out of town. I'll write up
> something, but I will need the community to review it.
> Thx,
> -g
> On Jun 5, 2012 7:16 AM, "Hyrum K Wright"<>  wrote:
>> +1, though I understand that yesterday and today are UK holidays.
>> (I'm travelling at the moment, and can review, but not contribute to,
>> the report.)
>> -Hyrum
>> On Mon, Jun 4, 2012 at 10:24 PM, Greg Stein<>  wrote:
>>> Gary: you wanna volunteer for the podling report this month?
>>> ---------- Forwarded message ----------
>>> From: Jukka Zitting<>
>>> Date: Wed, May 23, 2012 at 7:28 PM
>>> Subject: June reports in two weeks
>>> To: general<>
>>> Hi all,
>>> There's plenty of time still before the June reports [1] start flowing
>>> in. As an early remainder to podlings starting to draft their reports,
>>> here's how the IPMC saw your status as of the previous quarterly
>>> report in March [2]:
>>>   IP clearance: Openmeetings
>>>   No release: Bloodhound, Cordova, OpenOffice
>>>   Low activity: Kalumet, Kato
>>>   Low diversity: Bigtop, Etch, Isis, HCatalog, S4, Wave
>>>   Ready to graduate: Flume
>>> Has the situation in your podling changed over the last three months?
>>> If not, what's your plan for improving the situation? Is there
>>> anything for which you'd appreciate more help?
>>> I'm especially worried about Kato as it seems like the project has
>>> more or less died even though the JSR 326 / Oracle trouble got finally
>>> sorted out. Is it time to retire the project or can we hope for a
>>> revival?
>>> I also wanted to start preparing for this reporting round in good time
>>> by assigning shepherds [3] already now. Using a fuzzy algorithm based
>>> on the available volunteers, their stated preferences, and the
>>> podlings they're already mentoring, I came up with the following
>>> initial assignments that I've also recorded on the wiki page:
>>>   Benson Margulies - CloudStack, HCatalog, Kato
>>>   Dave Fisher      - Bloodhound, Flume
>>>   Matt Franklin    - Bigtop, Flex, Openmeetings
>>>   Matt Hogstrom    - Cordova,
>>>   Jukka Zitting    - Etch, Isis, S4
>>>   Mohammad Nour    - Kalumet
>>>   Ross Gardler     - Wave
>>> Feel free to shuffle these around or ask for someone else to fill in
>>> if you're expecting to be too busy for the extra reviews in early
>>> June. Other IPMC members and interested observers, please jump in and
>>> volunteer as extra shepherds if you'd like to help this effort.
>>> As discussed earlier, shepherds are not there to replace existing
>>> mentors. If everything is going well with a project, the shepherd can
>>> simply acknowledge a report and move on. If there are any relevant
>>> questions that the report doesn't answer, the shepherd may ask the
>>> podling and its mentors for more details. And finally if something
>>> seems wrong, the shepherd should raise a flag for the mentors and the
>>> rest of the IPMC to focus on. Most importantly, we need to be talking
>>> *with* the podlings, not just *about* them, so especially any
>>> constructive and encouraging feedback to them will be highly useful.
>>> [1]
>>> [2]
>>> [3]
>>> BR,
>>> Jukka Zitting
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> For additional commands, e-mail:
>> --
>> uberSVN: Apache Subversion Made Easy

View raw message