incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Franklin, Matthew B." <>
Subject RE: Shepherds for podling reports
Date Wed, 02 May 2012 11:50:07 GMT
>-----Original Message-----
>From: Ross Gardler []
>Sent: Wednesday, May 02, 2012 7:24 AM
>Subject: Re: Shepherds for podling reports
>On 2 May 2012 10:19, Jukka Zitting <> wrote:
>> Hi,
>> On Wed, May 2, 2012 at 10:59 AM, Ross Gardler
>> <> wrote:
>>> This is a good idea. I have signed up.
>> Excellent, thanks!
>>> I only ask you bear one thing in mind. Some months active people here
>>> have lots of their own podlings reporting, which takes quite a bit of time
>>> if done diligently. When assigning shepherd each month please bear in
>>> mind how many reports they are already signing off on.
>> Good point.
>> How about we start with an approximation that being a mentor of one of
>> the reporting podlings is equivalent to reviewing the reports of three
>> other podlings? We can tweak that down the line based on experience.
>Looking a little further forward i.e. not suggesting this initial
>small step should be transformed into a larger step but rather looking
>at what the next small step might be...
>I'd like to revisit the idea of grouping projects, e.g. big data,
>content, semantic, social etc. I imagine that people willing to be
>Shepherds will also have specific areas of interest. I imagine that
>shepherds would get more value from their time, and projects would get
>more cross-community feedback, if try to match shepherds to projects.
>For example, as a mentor on Wookie I'm interested in the progress of,
>and potential for collaboration with, Wave. My interest isn't
>sufficiently strong for me to dive into the dev list, but I'd
>certainly be willing to help the IPMC and myself by Shepherding that
>projects reports periodically.

The only (small) issue with bucketing podlings is what do we do when one fits in more than
one category?  I think the idea would be useful in general, so long as we clearly define the
rules for cross-cutting projects (ie they exist in both, they choose one, etc)

>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message