[Openstack-doc-core] Stepping down from openstack-manuals core

2016-10-18 Thread Steve Gordon
Hi folks,

I think the time has come for me to step down from the core team. I still 
intend to review changes related to my subject areas of interest going forward 
but in addition to my review velocity slowing I am increasingly finding I do 
not have the full context required to wield a +2/-2 with the right level of 
consideration.

Thanks all,

Steve

-- 
Mailing list: https://launchpad.net/~openstack-doc-core
Post to : openstack-doc-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-doc-core
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack-doc-core] ha-guide extra cores?

2016-04-29 Thread Steve Gordon
- Original Message -
> From: "Anne Gentle" <annegen...@justwriteclick.com>
> To: "Andreas Jaeger" <a...@suse.com>
> 
> Adam came to the docs contributor session and I talked to him about the
> potential ideas. He sounds fine either way (in or out of openstack-manuals,
> and he's okay with in or out of an arch guide or something). He did bring
> up something that I hadn't thought of, which is HA guests -- where the VMs
> are highly available. Still sounds like it's admin/operator work, though,
> and the users aren't affected. So it's still in either a separate guide or
> the arch guide.

Sort of, in the recent versions of the implementations I am most familiar with 
there is a minor user facing component where you mark the image/flavor as 
requiring instance HA ("evacuable") to opt in. The check for this is in the 
compute fence agent [1] at ClusterLabs that the Red Hat and SUSE folks among 
others collaborate on so I *believe* it applies to both solutions. Probably not 
enough to justify putting the whole thing in user-orientated guides but just 
noting it.

-Steve

[1] 
https://github.com/ClusterLabs/fence-agents/blob/master/fence/agents/compute/fence_compute.py

> Would be nice to reboot the efforts around it.
> Anne
> 
> 
> 
> On Fri, Apr 29, 2016 at 3:45 PM, Andreas Jaeger <a...@suse.com> wrote:
> 
> > Hi,
> >
> > if we do not merge the ha-guide to openstack-manuals and keep a separate
> > team - which I think would be a good idea if there's interest -, I propose
> > to add Adam Spiers as core. He hasn't reviewed much so far but I talked
> > with him and this might be just the push he needs.
> >
> > I know this is unusual, so send this to the smaller list here for you to
> > discuss openly.
> >
> > Note, that he's a colleague of mine - one of SUSE's HA experts. He's also
> > currently forming the openstack-ha community that has regular IRC meetings,
> >
> > Andreas
> > --
> >  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
> >   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> >GF: Felix Imendörffer, Jane Smithard, Graham Norton,
> >HRB 21284 (AG Nürnberg)
> > GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
> >
> >
> > --
> > Mailing list: https://launchpad.net/~openstack-doc-core
> > Post to : openstack-doc-core@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack-doc-core
> > More help   : https://help.launchpad.net/ListHelp
> >
> 
> 
> 
> --
> Anne Gentle
> www.justwriteclick.com
> 
> --
> Mailing list: https://launchpad.net/~openstack-doc-core
> Post to : openstack-doc-core@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack-doc-core
> More help   : https://help.launchpad.net/ListHelp
> 

-- 
Steve Gordon,
Principal Product Manager,
Red Hat OpenStack Platform

-- 
Mailing list: https://launchpad.net/~openstack-doc-core
Post to : openstack-doc-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-doc-core
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack-doc-core] Core Team Review - March 2016

2016-03-03 Thread Steve Gordon
- Original Message -
> From: "Anne Gentle" <annegen...@justwriteclick.com>
> To: "Andreas Jaeger" <a...@suse.com>
> 
> On Thu, Mar 3, 2016 at 6:56 AM, Andreas Jaeger <a...@suse.com> wrote:
> 
> > On 2016-03-03 01:19, Lana Brindley wrote:
> > > Hi core team,
> > >
> > > Here's the core reviewer stats for this month[1]:
> > >
> > > Current cores not appearing in any stats:
> > > Matthew Kassawara
> > >
> > > Matt has been working hard on Install Guide testing (which doesn’t run
> > > through Gerrit), so this is expected. It’s also expected to impact the
> > > stats of other core reviewers involved in that task.
> > >
> >
> > What does "not appearing in any stats" mean exactly?
> >
> >
> I couldn't find him on Stackalytics, take a look at this (which makes me
> wonder if the affiliation change is broken?)
> 
> http://stackalytics.com/?module=openstack-manuals=liberty=commits_id=ionosphere80

That query is explicitly pinned to liberty only and also measuring commits not 
reviews. I would think these are the more relevant stackalytics views (and Matt 
is on them):

http://stackalytics.com/report/contribution/openstack-manuals/30
http://stackalytics.com/report/contribution/openstack-manuals/90

I still tend to use Russell's stats at:

http://russellbryant.net/openstack-stats/docs-reviewers-30.txt
http://russellbryant.net/openstack-stats/docs-reviewers-60.txt
http://russellbryant.net/openstack-stats/docs-reviewers-90.txt

-Steve

> > I see Matt reviewing a bit - but other cores reviewing even less ;(
> >
> 
> Ok, good. Stackalytics is incorrect then.
> 
> 
> >
> > Matt is ionosphere80 in the list - I see 60 reviews in the last 90 list
> > for him, and Christian Berendt with 40, Atsushi SAKAI with 32, and
> > Darren Chan with 26.
> >
> > I still think we should keep the current state - but let's discuss with
> > Darren, Atsushi and Christian what's up,
> >
> > Andreas
> > --
> >  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
> >   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> >GF: Felix Imendörffer, Jane Smithard, Graham Norton,
> >HRB 21284 (AG Nürnberg)
> > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
> >
> >
> > --
> > Mailing list: https://launchpad.net/~openstack-doc-core
> > Post to : openstack-doc-core@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack-doc-core
> > More help   : https://help.launchpad.net/ListHelp
> >
> 
> 
> 
> --
> Anne Gentle
> Rackspace
> Principal Engineer
> www.justwriteclick.com
> 
> --
> Mailing list: https://launchpad.net/~openstack-doc-core
> Post to : openstack-doc-core@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack-doc-core
> More help   : https://help.launchpad.net/ListHelp
> 

-- 
Steve Gordon,
Principal Product Manager,
Red Hat OpenStack Platform

-- 
Mailing list: https://launchpad.net/~openstack-doc-core
Post to : openstack-doc-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-doc-core
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack-doc-core] Core List - July 2015

2015-07-03 Thread Steve Gordon
- Original Message -
 From: Lana Brindley openst...@lanabrindley.com
 To: openstack-doc-core@lists.launchpad.net
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi Docs Cores,
 
 Here's the core reviewer stats for July[1]:
 
 Current cores not appearing in any stats:
 Alexander Adamov
 Stephen Gordon
 
 Current non-cores appearing in stats:
 to222 (30 day reviews only)[2]
 Alex Settle  (30  90 day reviews, and commits)
 Olena Logvinova (30  90 day reviews)
 Helimaniac (30 day reviews only)[2]
 Brian Moss (30 day reviews, and commits)
 KATO Tomoyuki (commits only)
 
 
 Regarding Alexander, he is currently #16 in 30 day, #19 in 90 day, and
 #86 in commits. Given that this is the second month in a row that his
 stats have been quite poor, I propose we drop him for now. Of course,
 this doesn't preclude him becoming core again later on if his commits
 pick up.

I guess my concern here is we're proposing dropping a reviewer whose review 
numbers are actually trending in the right direction (that is, we previously 
kept Alexander on the list when his numbers were worse and now that they are 
showing improvement we're dropping him).

 Regarding Steve, he is currently #14 in 30 day, #16 in 90 day, and #76
 in commits. I propose that we keep Steve as core, as he's a long-time
 core, and it's entirely possible he's just had a bad month.

As I have fallen out of all of the criteria as currently set I would recommend 
just removing me for now. If I make the bar in the future or the bar changes I 
will no doubt be added back on merit, no need for a farewell tour.

 Regarding additions, I think Alex Settle, Olena Logvinova, and Brian
 Moss are all eligible. If we accept all of them, that brings our total
 core group to 15, which I feel is a little large. As Brian is a very new
 contributor and only just scraped in at number 12 on both the lists he
 appears in, I would like to encourage him to keep up the good work, and
 consider him for core next month.

Looking today Brian is 12th in commits, 15th in 30 day review stats, and 15th 
in 60 and 90 day review stats. This goes to the fact that having a cap of 12 or 
even 15 can leave a lot of people on the bubble so to speak depending on 
exactly where the next real gap in reviews/commits is, with quite a bit of 
variability involved depending on exactly when you look. I think we need to be 
a little bit flexible with how many cores we have as long as they are all 
actively engaged - with an emphasis on reviewing patches as being able to 
actually merge patches is the primary extra ability granted by being core. I 
actually think this is *more* important if we're endeavoring to cap the number 
of cores as a core who isn't reviewing as actively as those who aren't is 
effectively slowing down team velocity.

 My recommendation, therefore, is:
 Drop: Alexander

I've noted my concerns about Alexander's removal above so +0 on that for now 
(that is - could go either way but wanted to raise the concern).

 Add: Alex  Olena
 
 Yay or nay?

+1, no issues with these two - though based on Andreas's note that Helimaniac 
and Kato are one and the same I would suggest that they are a strong candidate 
to make core if not now then certainly in the near future (same goes for to222 
but it wasn't clear to me whether we worked out who that is?).

Thanks,

Steve

 1: For ease of reference, I've put this all into a spreadsheet, which
 you can see here (note that the months are in tabs at the bottom of the
 page):
 https://docs.google.com/spreadsheets/d/15rPHjQ3BKYsImLqKWlW1BD-NfMKzh9Hzl2_gfHp9bc0/edit?usp=sharing
 
 2: I couldn't locate real names for these users. Can anyone enlighten me?
 
 - --
 Lana Brindley
 Technical Writer
 Rackspace Cloud Builders Australia
 http://lanabrindley.com
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1
 
 iQEcBAEBAgAGBQJVlcXNAAoJELppzVb4+KUyqHEH/iMVfIqlJXGxilXyxFs2lzgA
 zAQEYzxPDkXw/6uWhZo2Y9PKszkWA0H1TtULEFLw/YCLP9hL2yvR9lCslNCu+L9N
 4pdJbjaid7TJFI0lGlGc/MozvGOnpC4q91PJqq4ES+3MKc4bRnfpL7nJojGPtud/
 j+fdFAj7XUpBHWAPU1yhV3fEqF+b7Wq31lFeCVVonzEwza4wzSfWMnndCh/SQvyo
 R1vfoD31Bq6Zv72WCTVUf28A2s80rPVUVkgNtTtxMa1o23tjXnJCY+xL81Sl459G
 7Kp/dezTLeHOSwJxggALJYo/tfBVdYL2acjrP8UqzQBGkVMkexxyAhzaoa7VmWk=
 =ghFn
 -END PGP SIGNATURE-
 
 --
 Mailing list: https://launchpad.net/~openstack-doc-core
 Post to : openstack-doc-core@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack-doc-core
 More help   : https://help.launchpad.net/ListHelp
 

-- 
Steve Gordon, RHCE
Sr. Technical Product Manager,
Red Hat Enterprise Linux OpenStack Platform

-- 
Mailing list: https://launchpad.net/~openstack-doc-core
Post to : openstack-doc-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-doc-core
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack-doc-core] Cacoon for diagram?

2015-05-27 Thread Steve Gordon
- Original Message -
 From: Andreas Jaeger a...@suse.com
 To: openstack-doc-core@lists.launchpad.net
 
 Change
 https://review.openstack.org/#/c/185321/5 brings in a graph with a short
 goo.gl URL that confused me - it points to the source at cacoon.
 
 I rather prefer to have the source in our repos than linking to an
 online tool - so, adding the SVG in addition would be fine for me.
 
 Also, I'm not sure that the URL should be in the graph.
 
 Please have a look and tell me whether I worry to much ;).
 
 thanks,
 Andreas

+1 from me, looks like the tool has an export feature for logged in users so 
the submitter should be able to get an SVG easy enough (unless that is a for 
pay feature but then that would just be another strike against the tool).

Thanks,

Steve

-- 
Mailing list: https://launchpad.net/~openstack-doc-core
Post to : openstack-doc-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-doc-core
More help   : https://help.launchpad.net/ListHelp