← Back to team overview

openstack-doc-core team mailing list archive

Re: Core team review - February 2017

 

You're looking at Feb 2016. Change to the Feb 2017 tab.

L

On 02/02/17 08:18, Anne Gentle wrote:
> Sure, here's a side-by-side screenshot. I placed strikethrough on names that did not appear in the top 12, like ventakamesh.Inline image 1 
> 
> On Wed, Feb 1, 2017 at 3:59 PM, Lana Brindley <openstack@xxxxxxxxxxxxxxxx <mailto:openstack@xxxxxxxxxxxxxxxx>> wrote:
> 
>     On 01/02/17 23:42, Anne Gentle wrote:
>     > I did some inline editing to strikethrough inaccuracies -- your columns don't seem to match with what the 30-day 90-day links show. Maybe the tab is mislabeled?
> 
>     Can you be more specific?
> 
>     >
>     > I'd like some discussion about how best to onboard new cores - Andreas is onto something with an introduction to the mailing list. Do they want to be cores? Do they know their stats are being watched for this?
> 
>     So generally, once this team has agreed on a new core, I email them directly to ask first. There's usually some discussion on email, where we can discuss responsibilities, etc, before they agree to take on the role. It is *always* an offer, not a command, and I make it clear that I'm around to answer questions.
> 
>     I like the idea of intros on the ML, but I think that should go for all new contributors, not just new cores. By the time someone is getting to core, we should already know who they are.
> 
>     Lana
> 
>     --
>     Lana Brindley
>     Technical Writer
>     Rackspace Cloud Builders Australia
>     http://lanabrindley.com
> 
> 
> 
> 
> -- 
> 
> Read my blog: justwrite.click <https://justwriteclick.com>
> Subscribe to Docs|Code: docslikecode.com <http://docslikecode.com> 

-- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com

Attachment: signature.asc
Description: OpenPGP digital signature


Follow ups

References