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 12:24:54 GMT
>-----Original Message-----
>From: Ross Gardler []
>Sent: Wednesday, May 02, 2012 8:09 AM
>Subject: Re: Shepherds for podling reports
>On 2 May 2012 12:50, Franklin, Matthew B. <> wrote:
>>>-----Original Message-----
>>>From: Ross Gardler []
>>>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)
>I don't imagine the "bucketing" to be enshrined in written process, or
>even be fixed. More of a convenience. We might do it by, for example,
>asking Shepherds to identify the projects they would *prefer* to
>shepherd and why. To continue my example above I might say "I have an
>interest in any social related podling so I would prefer to shepherd
>Wave which is one such project I'm not a mentor on". Someone else
>might say "I'm really interested in communications protocols and so I
>will shepherd Wave".

Fair enough.  I think that makes a lot of sense then.

>I'm not suggesting formality, just a semblance of structure. I think
>the best way to proceed is to get out list of shepherds, do a couple
>of months and then discuss whether this proposed next step will add
>anything to the process. My goal is to have more cross-community
>awareness in the incubator projects as I've observed that those
>projects that have someone actively seeking relationships tend to
>build critical mass sooner. My proposed approach is only one thing
>that might help in this regard.
>To unsubscribe, e-mail:
>For additional commands, e-mail:

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

View raw message