openstack-doc-core team mailing list archive

[Alexandra Settle <a.settle@xxxxxxxxxxx>]

On 4/4/17, 9:47 AM, "Andreas Jaeger" <aj@xxxxxxxx> wrote:

    On 2017-04-04 10:28, Alexandra Settle wrote:
    > 
    > 
    > On 4/3/17, 6:48 PM, "Andreas Jaeger" <aj@xxxxxxxx> wrote:
    > 
    >     On 2017-04-03 17:47, Anne Gentle wrote:
    >     > Ah, okay, I wasn't sure if I remembered correctly and didn't take time
    >     > to look it up, eep.
    >     > 
    >     > So, we should probably have that discussion of scope of docs core
    >     > reviewers. For example, docs tools are super important and becoming
    >     > moreso as we enable more teams and become consultants. As another
    >     > example, someone like me, who focuses on all API docs but the source
    >     > changes are reviewed in other repos, I simply won't have the numbers to
    >     > remain core on openstack-manuals. 
    >     > 
    >     > What do others think? Is my view basically unique due to my specialty area? 
    >     
    >     We have very few repos and should either look at them together - or have
    >     different policies for them.
    >     
    >     As long as we do not have separate core teams for the different
    >     components, we should find a good balance and include tools, api-site -
    >     and consider also how to handle security-guide.
    >     
    >     Btw. let's not split core-teams, I think that opens a completely
    >     different set of problems
    > 
    > I completely agree with you Anne, and definitely echo Andreas regarding the core teams.
    > We should manage this appropriately, and ensure everyone is receiving the kudos they deserve regardless of the ‘project’ they are contributing to.
    > 
    > Is there a way we can have ‘one’ stackalytics measurement that looks at security-guide, api-ref, openstack-manuals, doc-tools, doc-theme? Can we get that merged?
    
    http://stackalytics.com/?module=documentation-group has some more in it,
    see the list of repos it covers (all in governance repo).
    
    Perhaps it's a starting point, you can look at people and filter out the
    training folks?
    
Well, that’s easy enough :) I can do as Anne originally thought (inadvertently suggested?) and use Module: Documentation official instead of the Module: openstack-manuals that we have been using. I can give it a go from next month, if this suits?