Hi,
 No I wasn’t advocating off-list communication - that would be very 
counterproductive. The purpose was tied to the rest of my email where I 
proposed having organized public training sessions and such a list would help 
in identifying who to specifically recruit. In addition, this code base is 
actually quite old and some of the people that have worked on parts of NetBeans 
have moved on (some a long time ago). In this case, the list could identify 
where we could re-engage someone or a segment of code that is in need of 
volunteers.

-Ryan

 It is just handy to know who’s attention

> On Oct 6, 2017, at 4:36 AM, Bertrand Delacretaz <[email protected]> 
> wrote:
> 
> Hi,
> 
> On Fri, Oct 6, 2017 at 8:46 AM, Ryan Cuprak <[email protected]> wrote:
>> ... 1. Construct a list of individuals that have special knowledge for the 
>> different modules (basically a goto list for deep questions)....
> 
> In an Apache project, asking questions to specific people (I assume
> you mean off-list) is frowned upon, as the goal is to build a
> community with a low bus factor, as well as cross-pollinate knowledge.
> Experts should emerge naturally based on focused discussions.
> 
> The recommended way to handle this is to define a set of [tags] that
> can be used in the subject lines of messages sent to this list. People
> can then, visually or using their mail clients, filter on such tags to
> pay special attention to a set of topics.
> 
> The set of [tags] can also emerge naturally as people start using
> those, in general there's no need for a big upfront effort in defining
> them. Maybe just maintain a website page which lists the recommended
> one, based on which ones emerge.
> 
> The OpenStack dev list [1] is a great example of that - a single list
> for many topics, with multiple [tags] as needed, and I suppose not
> using those [tags] there means nobody reads your message, which
> creates a virtuous cycle.
> 
> -Bertrand (with my incubation mentor hat on)
> 
> [1] http://lists.openstack.org/pipermail/openstack-dev/2017-June/thread.html

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to