[openstack-dev] [tc][swg] The future of the Stewardship Working Group

[Colette Alexander]

Hello Stackers,

As many of you know, I recently took a job with Spotify in New York City. I
spoke with many folks about the transition plans when I was at the Boston
Forum, and we all decided that it would make sense for me to get settled
into the new position before deciding what amounts of time I had to tend to
SWG work, and therefore what my future in the community would look like.

My new job has become a lot busier a lot sooner than expected. I think I'll
have a little bit more time in my schedule in the next month or so to do
OpenStack related work, but after summer holidays, I expect things to pick
back up again.

Because of all of the unknowns around my availability for working on SWG
things, I think now is a good time to start discussing a potential
replacement for me as the chair of the group. I have loved working with
OpenStack and I plan on sticking around in the IRC channel and monitoring
mailing list work, but I don't think it's fair to the SWG, TC or the entire
community for me to stay on as chair when I can't devote as much time as
I'd like to spearheading efforts in the community.

So - that means I'd love to hear from folks about who might be a good
replacement. I have spoken to a few people behind the scenes to gauge
interest, but I'd like to open it up the community as a whole at this point
to start a discussion.

For those of you who don't know what the Stewardship Working Group is:
https://wiki.openstack.org/wiki/Stewardship_Working_Group is a good place
to start

Some of the workstreams going on:
a) Follow up on project ideas from leadership training
https://etherpad.openstack.org/p/pathtocontribution
https://etherpad.openstack.org/p/communication-vision

b) Any more poking/helping along of the TC with their current vision

c) An actual vision for the SWG and their next batch of work (this would be
based on feedback from the training sessions above, and from the community,
collected at the Atlanta PTG - https://etherpad.openstack.org/p/AtlantaPTG-
SWG

d) The future of leadership training (more to schedule? break it up into
smaller groups? who knows?)

I'd be happy to onboard anyone who's interested in terms of getting them up
to speed on these items.

If anyone wants to discuss any of this with me directly I'm gothicmindfood
on IRC.

Thanks so much for being such an amazing community to be in - you all
continue to be some of my favorite humans and I'm so lucky to have gotten a
chance to work with you.

Sincerely,

-colette/gothicmindfood
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc][swg] Updates on the TC Vision for 2019

[Colette Alexander]

Hi everyone!

Just wanted to send the community some updates on the vision front and also
get a discussion with the members of the technical committee going here for
next steps on what we're up to with the TC Vision for 2019 [0].

A couple things:

1. We finished our feedback phase by closing the survey we had open, and
posting all collected feedback in a document for TC (and community) review
[1] and having a session at the Boston Forum where we presented the vision,
and also took feedback from those present [2]. There is also some feedback
in Gerrit for the review up of the first draft [0], so that's a few places
we've covered for feedback.

2. We're now entering the phase of work where we incorporate feedback into
the next draft of the vision and finalize it for posterity/the governance
repository/ourselves and ourselves.

So! What should feedback incorporation look like? I think we need to have
mbmers of the TC pipe up a bit here to discuss timelines for this round and
also who all will be involved. Some rough estimates we came up with were
something over the course of the 2-3 weeks after the Forum that could then
be +2d into governance by mid-June or so. I'm not sure if that's possible
based on everyone's travel/work/vacation schedules for the summer, but it
would be great. Thoughts on that?

Also - I promised to attempt to come up with some general themes in
feedback we've uncovered for suggestions for edits:

 - There is (understandably) a lot of feedback around what the nature of
the vision is itself. This might best be cleared up with a quick prologue
explaining why the vision reads the way it does, and what the intention was
behind writing it this way.
 - The writing about constellations, generally, got quite a bit of feedback
(some folks wanted more explanation, others wanted it to be more succinct,
so I think wading through the data to read everyone's input on this is
valuable here)
 - Ease of installation & upgrades are language that comes up multiple times
 - Many people asked for a bullet-points version, and/or that it be edited
& shortened a bit
 - A few people said 2 years was not enough time and this read more like a
5 year vision
 - A few people mentioned issues of OpenStack at scale and wondering
whether that might be addressed in the vision
 - There was some question of whether it was appropriate to vision for "x
number of users with yz types of deployments" as a target number to hit in
this vision, or whether it should be left for an OpenStack-wide community
vision.

Some favorites:
 - Lots of people loved the idea of constellations
 - A lot of likes for better mentoring & the ladders program
 - Some likes for diversity across the TC of the future

Okay - I think that's a pretty good summary. If anyone else has any
feedback they'd like to make sure gets into the conversation, please feel
free to reply in this thread.

Thanks!

-colette/gothicmindfood



[0] https://review.openstack.org/#/c/453262/
[1]
https://docs.google.com/spreadsheets/d/1YzHPP2EQh2DZWGTj_VbhwhtsDQebAgqldyi1MHm6QpE/edit?usp=sharing
[2]
https://www.openstack.org/videos/boston-2017/the-openstack-technical-committee-vision-for-2019-updates-stories-and-q-and-a
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc] Initial TC Vision for 2019 Draft survey responses

[Colette Alexander]

Hi everyone,

Good news! As of this morning, we've had 146 responses to our survey asking
for community feedback on the initial draft of the TC Vision for 2019.

The results are collected here:
https://docs.google.com/spreadsheets/d/1YzHPP2EQh2DZWGTj_VbhwhtsDQebAgqldyi1MHm6QpE/edit?usp=sharing


Please keep in mind that there isn't a great way to view long-form survey
comments (it's one of the downsides of wanting to allow people to express
themselves, alas) besides just... reading through them.

The top spreadsheet in the file is all responses collected in order of
completion, and the rest of the tabs are for respondents by-type. You'll
see multiple responses repeated over those type-sheets, as type was a
multi-select option (with the exception of "rather not say").

One person (responding under the 'other' category) left some personally
identifying information in their responses, and I have that available for
the TC in case they'd like to contact them, but felt it wasn't necessarily
prudent to give out their PII to the rest of the community without their
direct permission so it's edited out. If anyone does want to contact that
person who's *not* on the TC to talk more about their responses with them,
let me know and we can do an introduction on a case by case basis. I've
done no other editing of responses besides that.

I'll plan on updating this response sheet weekly with new data as my
schedule permits, until we decide to close the survey.

TC Members - what do you think is the best way to go about discussing this
feedback and incorporating it into a finalized vision (besides our planned
session at the Forum in Boston)? Taking some time out of a couple of TC
meetings might be nice but if agendas are full for the next few weeks I am
happy to attempt to schedule another time with everyone.

Thanks so much - and if you haven't taken the survey yet, please do so,
here: http://www.surveygizmo.com/s3/3490299/TC-2019-Vision

-colette/gothicmindfood
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc][swg]The 2019 TC Vision Draft - anonymous feedback now open

[Colette Alexander]

Hello Stackers,

By now, you all should have received an invitation to comment
anonymously[0] on the current draft of a TC Vision for 2019 that is up for
review in the governance repository[1].

We're going to leave the survey open for comment until the Boston Forum,
but I'd like to start incorporating feedback earlier by sending data and
information directly to the TC and setting aside some discussion time for
themes in the feedback in the next few TC meetings.

That means a couple of things:
1) Getting your feedback in sooner rather than later means it has a higher
likelihood of being integrated into the vision.
2) Discussion around vision feedback will occur in TC meetings, and then at
our Forum discussion on the vision[2]

We'd love to hear from you in both the survey/review forms as well as
during these discussions. Please stay tuned to the next few TC meetings,
and join us in Boston if you can. If you'd like to discuss the vision work
with TC members, you can also join #openstack-swg and ping people there.

Thanks so much!

-colette/gothicmindfood


[0] If you didn't, here's the link: http://www.surveygizmo.com/s3/
3490299/TC-2019-Vision
[1] Here's the Gerrit review: https://review.openstack.org/#/c/453262/
[2] https://www.openstack.org/summit/boston-2017/summit-
schedule/events/17585/the-openstack-technical-committee-
vision-for-2019-updates-stories-q-and-a
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all] Last call for Leadership Training April 11-13

[Colette Alexander]

Hi everyone,

Just wanted to poke a bit, since there are still two slots available for
leadership training in Ann Arbor for April 11/12/13. You can sign up here:
https://etherpad.openstack.org/p/Leadershiptraining

I promise delicious food and a busy daily schedule with lots of learning
with some great members of the community. Training costs are covered by the
Foundation, but attendees are responsible for their own travel and
incidentals.

Please include your IRC nick and/or email address when you sign up.

I've begun the process of sending out logistics emails for everyone signed
up. If you *haven't* received an email from me, that means I probably
haven't been able to find one for you via the usual channels - please write
me at colettealexan...@gmail.com and we'll get that sorted. (If anyone else
on the -dev list has them, I'm particularly looking to contact Armstrong
Foundjem and Vinith Kumar.

Feel free to respond here, or ping me on IRC (I'm gothicmindfood) if you
have any questions at all.

Thank you!

-colette
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all]One last slot open for Leadership Training - April 11/12/13

[Colette Alexander]

Hi everyone,

Just a quick note that one slot has opened up for leadership training. If
you'd like to attend, and can confirm that you will be there, please sign
up on the etherpad:

https://etherpad.openstack.org/p/Leadershiptraining


Thanks!

-colette
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [swg] Today's meeting (March 16, 1400 UTC) cancelled

[Colette Alexander]

Hi everyone,

The Stewardship Working Group is in the midst of discussing alternatives to
regularly scheduled meetings to keep our workflow going. Partly because of
time zone issues and partly because of overscheduled people who are in the
SWG.

To allow for some breathing room for these discussions, and to give folks a
break this week in their schedules, I think we should cancel. We're always
in #openstack-swg if you need us, and the email thread on the status of
what we'll do in place of meetings is a good one to watch[0].


Thanks!

-colette/gothicmindfood

[0]
http://lists.openstack.org/pipermail/openstack-dev/2017-March/113994.html
is Thierry's response re: meeting timing & beginning of discussion of not
having one
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [swg][tc] Moving Stewardship Working Group meeting

[Colette Alexander]

On Thu, Mar 16, 2017 at 8:19 AM, Jim Rollenhagen 
wrote:

> On Thu, Mar 16, 2017 at 5:17 AM, Thierry Carrez 
> wrote:
>
>> Jim Rollenhagen wrote:
>> > On Wed, Mar 15, 2017 at 8:15 AM, John Garbutt > > > wrote:
>> >> In the absence of tooling, could we replace the meeting with weekly
>> >> email reporting current working streams, and whats planned next?
>> That
>> >> would include fixing any problems we face trying to work well
>> >> together.
>> >
>> > This is a good idea, I've quite liked cdent's weekly placement update,
>> > maybe something similar, and others can chime in with their own
>> updates/etc.
>>
>> I was thinking we could use a status board to track the various
>> activities / objectives / threads. As part of the status board the
>> leader of each thread would provide a $time_interval update by a given
>> deadline, and the workgroup chair would collect them all and post them
>> (to a single email) on the ML.
>>
>
> ++
>
>

I'm fine with this - I actually think it would be helpful for me, since
it's more likely I'll make an hour of time here and there throughout a week
to get work and updates done. I'm especially fine with it if it means more
participation in the SWG from the community because we move towards other
ways of collaborating that allow for time zone/scheduling differences.



>
>> The update could have predetermined sections: current status / progress,
>> assigned actions, open questions... If the open questions can't get
>> solved in the ML thread resulting from the $time_interval update, *then*
>> schedule an ad-hoc discussion on #openstack-swg between interested
>> parties.
>>
>> In terms of tooling, we can start by using a wiki page for tracking and
>> updates snippets. We can use framadate.org for ad-hoc discussion
>> scheduling.
>>
>
> Any reason not to just use storyboard for tracking? AIUI, it gives us a
> status
> board for free.
>
> // jim
>

I'm fine with trying whatever the group prefers for a couple of weeks,
assessing, and then continuing with something else or trying a different
tool.


I think we should probably just cancel today's meeting, though, since it
seems like most people are pretty booked anyhow.


-colette



>
>
>>
>> Combined with extra activity on the channel, I think that would preserve
>> all 3 attributes of the meeting (especially the $time_interval regular
>> kick in the butt to make continuous progress).
>>
>> --
>> Thierry Carrez (ttx)
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [swg][tc] Moving Stewardship Working Group meeting

[Colette Alexander]

Hi there!

Currently the Stewardship Working Group meetings every other Thursday at
1400 UTC.

We've had a couple of pings from folks who are interested in joining us for
meetings that live in US Pacific Time, and that Thursday time isn't
terribly conducive to them being able to make meetings. So - the question
is when to move it to, if we can.

A quick glance at the rest of the Thursday schedule shows the 1500 and 1600
time slots available (in #openstack-meeting I believe). I'm hesitant to go
beyond that in the daytime because we also need to accommodate attendees in
Western Europe.

Thoughts on whether either of those works from SWG members and anyone who
might like to drop in? We can also look into having meetings once a week,
and potentially alternating times between the two to help accommodate the
spread of people.

Let me know what everyone thinks - and for this week I'll see anyone who
can make it at 1400 UTC on Thursday.

Thank you!

-colette
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc][swg][all] Leadership training sign-up is open!

[Colette Alexander]

Hello Stackers!

We're opening up the sign-up sheet for leadership training beyond the TC,
Board and Foundation staff to the whole community.

What: Leadership Training, customized for members of the OpenStack Community
When: April 11/12/13
Where: ZingTrain, in Ann Arbor, Michigan.

If you can confirm your ability to attend, please sign up here:
https://etherpad.openstack.org/p/Leadershiptraining

There are a lot of details on that etherpad about timing, place,
recommended locations to stay, etc. You can also scroll down to read a
sample itinerary of subjects covered in the training. If you have any
questions at all, feel free to ask questions in this thread, or in
#openstack-swg as many folks who lurk in that channel have attended.

Some quick notes:

   - This is the exact same training that was done last year
   - We're planning on having 1-2 people attend who also attended training
   last year to give some context and continuity to the discussions.
   - The training costs are fully funded by the Foundation, and attendees
   only need to cover the cost of travel, lodging, and some meals (breakfast
   and lunch during training is provided).
   - We're capping attendance at 20 people.
   - I'd like to finalize our list by March 24th, so please start the work
   of getting travel approvals, etc., now.

If there are any past attendees who'd like to chime in in response to this
to discuss your experiences with training, please do! Please feel free to
ping me on IRC (I'm gothicmindfood) if you have any other questions.

Thanks so much,

-colette/gothicmindfood
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc][swg] Summary - Atlanta PTG Stewardship Working Group Session

[Colette Alexander]

Hi everyone!

I thought I'd send a summary of the Stewardship Working Group activities
from our time at the PTG this past week to the list to add voices to our
discussions, and start the work of organizing our work for the next cycle.

The SWG had a room to ourselves for all of Monday, which was the same day
that many other cross-project sessions had to get their work done. Because
we knew the vibe would be more of a drop-in and check-things-out in between
other sessions, we prepared for collecting feedback with a bunch of
question prompts, and post-its and sharpies available for anyone who
dropped in to reply to questions quickly, and stick around and discuss if
they wanted.

The questions:
1. What do you love?
2. What should we fix?
3. What bothers you?
4. Questions?

For most of the morning we had quite a few people sticking around to talk
about subjects in the community and problems they wanted to see addressed.
That conversation also generated a lot of post-its on the "wall of
questions" as it progressed. The end result we ended up affinity mapping
towards the end of the afternoon, and then I ended up transcribing that
fully at the bottom of our session's etherpad as best as I could.[0] I
cross-mapped some things if they seemed to align with things in other
areas, and I'll continue to do that between now and the next SWG meeting.

Based on previous discussions with the group, it's highly likely that most
or all of these items will end up forming the SWG's work backlog in the
next 3-6 months.

I'd like to extend a special thanks to everyone who dropped in and gave
feedback, and especially to those who came by late in the afternoon to help
with affinity mapping everything.

If you attended part of the session, I'd love to hear your feedback here,
and see you in the #openstack-swg channel and at the next SWG meeting, on
March 2nd at 1400 UTC. I know we have some folks interested who live on the
west coast of the US, so one of our agenda items this week will be to
discuss moving the meeting a little to accommodate that time zone.

If you couldn't attend the PTG, but are interested in contributing feedback
here (or in-channel, or at the meeting) we definitely need you! Let us know
what you think the SWG and TC can do to help improve OpenStack!

Sincerely,

colette/gothicmindfood

[0] https://etherpad.openstack.org/p/AtlantaPTG-SWG
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc][swg] Sessions for Atlanta PTG - writing a TC Vision/Other options

[Colette Alexander]

On Tue, Jan 24, 2017 at 11:53 AM, Alexis Monville <
alexis.monvi...@redhat.com> wrote:

>
> >
> > I spent quite a bit of our cross project session at the Ocata Summit
> doing a
> > quick recap of the concept of Servant Leadership and it seemed like
> plenty
> > of attendees appreciated that. Would a series of quick recaps of basic
> > leadership concepts (Servant Leadership, Visioning, Principles & Culture,
> > and Change Management) - if anyone is interested in having a small
> > discussion covering some of those topics, I'd love to hear from you!
>
> Thank you Colette!
> Do you think those discussions need to happen during the PTG in
> Atlanta, or could we also asked for online conversations on those
> topics?
>

We could certainly cover some of these topics online, whether in a
scheduled discussion in #openstack-swg or elsewhere. The advantages to
talking them through in a room are far less than organizing future work and
getting feedback from anyone who has ideas on what to do moving forward who
are at the PTG, so I'd place them last in my list of items to schedule,
unless there's remarkable interest in them.

Thanks Alexis!

-colette/gothicmindfood
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc][swg] Sessions for Atlanta PTG - writing a TC Vision/Other options

[Colette Alexander]

Hello Stackers,

As we move into the last four weeks of work before the PTG in Atlanta, I
wanted to check in to talk about what the Stewardship Working Group has
planned and what we're looking to accomplish during our one day (Monday) at
the gathering.

Currently, discussing among SWG members has focused around a few things:

1) Assisting the TC with writing a vision
2) Assessing our previous work list [0] and prioritizing future work for
the SWG based on the community's interest in that list
3) Creating space for drop-in/community feedback on what we should work on
next, and how it should be prioritized.

1) the TC Vision is on hold, and won't happen at the PTG. Since so many
contributors would've been in other cross project sessions throughout
Monday we thought it would be wiser to hold off, and do a facilitated
vision during another time when the TC might be able to fully focus on it
for a day. We're still working on timing for that, but I will keep everyone
posted once I know what we've settled on.

2 and 3 are listed on our etherpad/vision for the PTG [1], with 2 currently
scheduled in the morning, and 3 planned for a general availability for
drop-in feedback in the afternoon (as we assume more people will have more
sessions and less flexible schedules at that point, so drop-ins will be the
easiest way to allow anyone who is interested in what we do to stop by and
participate).

I'd love feedback on that, scheduling wise, from any folks interested in
participating. I'd also love to hear any other ideas about what we could
cover during our day that might be useful.

I spent quite a bit of our cross project session at the Ocata Summit doing
a quick recap of the concept of Servant Leadership and it seemed like
plenty of attendees appreciated that. Would a series of quick recaps of
basic leadership concepts (Servant Leadership, Visioning, Principles &
Culture, and Change Management) - if anyone is interested in having a small
discussion covering some of those topics, I'd love to hear from you!

Thanks so much, everyone - can't wait to see you all in Atlanta!

-colette/gothicmindfood


[0] https://etherpad.openstack.org/p/swg-short-list-deliverables
[1] https://etherpad.openstack.org/p/AtlantaPTG-SWG
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [swg][tc] meeting today (12/22) cancelled

[Colette Alexander]

Hi there everyone!

On account of it being a vacation week for many of us who have holidays
coming up, I'm going to cancel today's meeting.

We'll be continuing discussion of work items towards our next meeting (Jan
5) in the #openstack-swg channel. Please join us there!

Thanks!

-colette/gothicmindfood
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [swg] SWG meeting Thursday, 11/24 cancelled

[Colette Alexander]

Hi SWGers,

Due to the fact that most of the group will be away for the US
Thanksgiving holiday, I'm cancelling our SWG meeting in
#openstack-meeting-3. See you all on December 8th, at 1400 UTC, and
have a great holiday!

-colette/gothicmindfood

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [swg][tc] An attempt to clarify/discuss: what exactly is the Stewardship Working Group, anyhow?

[Colette Alexander]

Hi OpenStackers!

At the last Stewardship Working Group (SWG) meeting[0], we discussed a lot
of the feedback that we received in our cross project session and our panel
discussion in Barcelona from people who were wondering what, exactly, the
Stewardship Working Group is and what they do.

I thought it might be appropriate to bring that discussion to the mailing
list, so... here we are.

So, what do we do exactly?

A lot of that is, like other OpenStack projects, kind of up to whoever
shows up.

But, the current history/summary of what has happened with people who've
showed up so far:

The SWG was founded[1] after some members of the TC and some members of the
community attended a leadership training in Ann Arbor, in June of 2016. The
two day workshop covered a variety of topics, including a few key concepts
that I felt mirrored our own values in the community: servant leadership,
visioning, and how to implement change successfully. Out of those two days,
a third day devoted to talking about what we learned and how it might apply
to OpenStack led us to think about forming the SWG. Anne Gentle wrote a
great summary for the OpenStack blog, covering some of these.[2]

When I first thought about the SWG during that day of discussion, I saw it
as having two potential areas of work: 1) researching and discussing ideas
around stewardship and leadership and assessing issues that might arise in
the community in order to make recommendations to the TC around governance,
leadership, and anything related to culture (including, especially,
documenting that culture). And 2) providing/organizing resources for
*anyone* in the entire OpenStack community who is interested in adding to
their leadership skills, or who needs help understanding a less-technical
problem, more-people-problem that comes up. (And I mean "understand"
through any mechanism: resources/training provided, discussions had on the
#openstack-swg IRC channel, in meetings, or in personal discussion) In my
wildest dreams, we would also provide support and learning pathways about
OpenStack's culture and leadership values to anyone in the community.

The major value of the training that was echoed by all participants was
that it wasn't run-of-the-mill "corporate" leadership training - it focused
in on concepts and skills that were far more applicable in our open
governance/open participation environment. Anything that is provided to the
community by the SWG should pass the same smell test.

I feel rather strongly (and have even said so even while being filmed[3])
that OpenStack can often suffer from an avoidance in its culture - people
will tend to look away/walk away/close tabs in another direction when faced
with something that potentially involves having a difficult conversation
with someone or multiple people (especially if those people are in
unfamiliar groups/work at unfamiliar companies). How might we all feel more
comfortable asking each other difficult questions and having constructive
debate that ultimately will lead to a healthier more sustainable and
diverse community? I hope that the SWG can provide a kind of "safe space"
(even just for your brain to think about a thing) to spark some of that
change.

What are the sorts of things you'd like to see tackled? Some thoughts were
thrown up in the etherpad during our cross project session in Barcelona[4]
that might start good discussion here.

Any thoughts/debate/ideas on where we should go and what we should do are
most welcome here or on the other standard channels. I'm currently in the
process of writing a draft vision for where we'd like the group to be and
what we'd like to accomplish before and during the PTG in Atlanta. I'd love
to get more people involved. On account of the US/Thanksgiving holiday, our
next meeting will be Dec. 8, 1400 UTC in #openstack-meeting-3 so please
join us in #openstack-swg in the meantime and say hello.

Thanks!

-colette/gothicmindfood


[0]
http://eavesdrop.openstack.org/meetings/openstack_swg/2016/openstack_swg.2016-11-08-15.04.log.txt
[1] https://governance.openstack.org/resolutions/20160705-stewardship.html
[2]
http://www.openstack.org/blog/2016/07/technical-committee-highlights-july-17-2016/
[3] https://www.youtube.com/watch?v=juGktZ3xabA=1430s
[4] https://etherpad.openstack.org/p/Barcelona-SWG-cp
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [swg] Meeting next week cancelled & Barcelona Summit info

[Colette Alexander]

Hi there SWG-ers & OpenStackers,

This is official notice that our Tues, Oct 25th, 15:00 UTC meeting is
canceled due to the Ocata Summit in Barcelona.

The Stewardship Working Group has two sessions worth attending live if
you'll be in Barcelona.

1) A cross project session Wednesday at 12:15 PM [0][1]
2) A summit panel discussion Wednesday at 3:55 PM  [2]

If you can't attend the sessions, please do check out the etherpad for
the session [1] and feel free to join us at our next IRC meeting in
#openstack-meeting-3 on Nov 6, at 15:00 UTC.

Thanks, and looking forward to seeing you all in Barcelona!

-colette/gothicmindfood



[0] 
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16923/cross-project-workshops-re-inventing-the-tc-the-stewardship-working-group-discussion
[1] Etherpad is here: https://etherpad.openstack.org/p/Barcelona-SWG-cp
[2] 
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15243/stewardship-bringing-more-leadership-and-vision-to-openstack

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [band] OpenStack Summit - Barcelona - musicians please raise your hands

[Colette Alexander]

On Sat, Sep 17, 2016 at 1:35 PM, Amrith Kumar  wrote:
> So, would y'all musicians who plan to bring your gear to Barcelona please 
> start a little thread here on the ML and let's get a band going?

I would totally bring my gear if my cello didn't need its own plane seat!

If someone in Spain has a cello though, I will totally play.

-colette/gothicmindfood

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc][swg] Summary of today's SWG meeting/work items

[Colette Alexander]

Hi everyone,

I thought it might be a good idea to send a summary of the Stewardship
Working Group (SWG) meeting[0] to the -dev list today - both to
increase engagement around what we're up to, and to reach the (quite a
few) folks who couldn't make today's meeting because of conflicts:

1. We're in the process of refining our vision for what the SWG would
like accomplished in Barcelona[1]. Visioning is a concept we learned
about in training and is best summed up here:
https://www.zingtrain.com/content/why-and-how-visioning-works for
anyone who is curious.

The SWG already has a panel discussion scheduled in Barcelona[2], but
we discussed whether it might be good to add 2 more sessions:
a. A cross project themed session covering some of the recent
governance patches suggested by the TC[3]
b.  A general work session on Friday afternoon.

We're going to attempt to get both of those scheduled in the next week
or two, and we'd love to see anyone from the community who's
interested in stewardship/leadership there.

Also, we'd love feedback from the community (via ML or in
#openstack-swg ) on what they'd like to hear about/experience at any
of these sessions, so please chime in if you have anything you'd like
to see addressed by our group.

2. Our short list of work was reviewed[4]

We discussed the current governance changes in flight:
Goals for Ocata cycle & Principles

And some future goals listed:
A long term/overall vision for the Stewardship Working Group,
recommending that the TC write a vision

I floated the idea that having a vision for the SWG that we can all
align on would be the greatest selling point in proposing to the TC
that they have their own. It appears, based on our Barcelona vision,
that that is what we're targeting to start there.

Comments, questions, feedback most welcome!

Cheers,

-gothicmindfood


[0] Meeting Agenda: https://wiki.openstack.org/wiki/Meetings/SWGMeeting
[1] https://etherpad.openstack.org/p/BarcelonaSWGMagic
[2] 
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15243/stewardship-bringing-more-leadership-and-vision-to-openstack
[3] https://review.openstack.org/#/c/357260/ and
https://review.openstack.org/#/c/349068/
[4] https://etherpad.openstack.org/p/swg-short-list-deliverables

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][tc] establishing project-wide goals

[Colette Alexander]

On Tue, Aug 2, 2016 at 11:29 AM, Thierry Carrez  wrote:
>
> Doug Hellmann wrote:
> > [...]
> >> Likewise, what if the Manila project team decides they aren't interested
> >> in supporting Python 3.5 or a particular greenlet library du jour that
> >> has been mandated upon them? Is the only filesystem-as-a-service project
> >> going to be booted from the tent?
> >
> > I hardly think "move off of the EOL-ed version of our language" and
> > "use a library du jour" are in the same class.  All of the topics
> > discussed so far are either focused on eliminating technical debt
> > that project teams have not prioritized consistently or adding
> > features that, again for consistency, are deemed important by the
> > overall community (API microversioning falls in that category,
> > though that's an example and not in any way an approved goal right
> > now).
>
> Right, the proposal is pretty clearly about setting a number of
> reasonable, small goals for a release cycle that would be awesome to
> collectively reach. Not really invasive top-down design mandates that we
> would expect teams to want to resist.
>
> IMHO if a team has a good reason for not wanting or not being able to
> fulfill a common goal that's fine -- it just needs to get documented and
> should not result in itself in getting kicked out from anything. If a
> team regularly skips on common goals (and/or misses releases, and/or
> doesn't fix security issues) that's a general sign that it's not really
> behaving like an OpenStack project and then a case could be opened for
> removal, but there is nothing new here.
>

+1 to all of this.

As someone who was in leadership training with both Thierry and Doug,
I just want to point out that 'reasonable, small goals' and 'support a
particular library du jour or get kicked out of OpenStack' are
immensely different reads on the potential of this situation.

OpenStack suffers from a perception that it is not a usable, cohesive
set of projects that work together. Like many perceptions out in the
wild about OSS projects, that is part PR/spin/haters-gonna-hate, and
part reality. Apart from PR-land, the idea of having some basic
standards and cross-project goals to meet not just before a project is
accepted, but also as it matures, hopefully serves the ultimate
purpose of presenting an OpenStack with enough consistency and
usability that it doesn't make a user/operator want to throw a server
out the window.

Where does the technical independence of a project begin encroaching
on the ability of other projects to effectively work for their users
or their developer participation? Where do the desires of a single
project begin to negatively impact the entirety of OpenStack, and how
does the community respond when faced with tough situations like that?

The TC, as a body that oversees the overarching technical direction of
the entire group of projects, has identified areas where OpenStack
could be *highly* improved in its functionality and usability - those
certainly, on their surface, seem like noble goals for any person
creating any project with an end user that is not themselves. That the
TC is the mechanism to do that unifying, helpful, future-preserving
thing for OpenStack and also the same mechanism that, in the wrong
hands, could be used to ask impossible things of projects (and use
their failure to kick them out of the community, eventually) is
totally true, but it's also always been true of the TC. That's why
preserving our culture of leadership by election is so important -
leaders are elected to serve their constituents - *not* the other way
around.

-colette/gothicmindfood

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc] Leadership training recap & steps forward

[Colette Alexander]

Hello Stackers!

I wanted to send an update about what happened last week at the
leadership training session in Ann Arbor, Michigan and some of the
things moving out of the training that we're hoping help improve the
community as a whole.

17 people from the community (including 8 from the TC) and 2 trainers
from ZingTrain spent 2 days covering a range of materials and
subjects: servant leadership! Visioning! Stages of learning! Good
practices for leading organizational change! Also there were delicious
sandwiches and BBQ.

Reviews and reflections from the training have been overwhelmingly
positive, and some blog posts about it are starting to pop up.[0]

On the day after training, a slightly smaller group than the full 17
met to discuss how some of the ideas presented might help the
OpenStack community, and identified some areas of work that are now
being initiated by the TC. Some of the work identified involves the TC
examining and where necessary, altering the ways it works, and some of
it involves a general support for and development of leadership in all
areas of the OpenStack community. To more clearly define and
accomplish that work, a Stewardship Working Group has been
proposed.[1]

Because of the success of the training, and the fact that 5 TC members
weren't able to attend this past instance, I'm working to arrange a
repeated offering. It's still very much in the planning stages, but
I'm hoping it will be in September, and follow the same 2-day
training/1 day reflection/planning structure as before. The training
will be enrolled similarly to the last one - with TC and Board members
having first crack at the sign up list, and then opening remaining
seats to the rest of the community. I will post to the -dev list as
dates and details are finalized for that.

Ideally there will be some discussion and work on this (including a
potential panel discussion) at the Ocata Summit in Barcelona as well -
stay tuned for information on that as it becomes available!

A huge thanks to all who attended, and to the Foundation who sponsored
the training for everyone - I'm incredibly excited to work on all of
this in such a great environment, with such great people.

Sincerely,

-colette/gothicmindfood

[0] http://www.tesora.com/openstack-tc-will-not-opening-deli/
[1] https://review.openstack.org/#/c/337895/

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] Leadership training - ideas to include those not in the room?

[Colette Alexander]

On Thu, May 26, 2016 at 2:29 PM, Anita Kuno <ante...@anteaya.info> wrote:
> On 05/26/2016 05:01 PM, Colette Alexander wrote:
>> On Thu, May 26, 2016 at 12:10 PM, Anita Kuno <ante...@anteaya.info> wrote:
>
> Well I think you have just set the intent for the event that I should be
> careful what I say or do since anyone is encouraged to blog my
> statements or actions in their blog post. I will comply with
> expectations, but I must say I had expected an intent that valued my
> personal privacy higher for what was billed in my mind anyway as a
> leadership training event.
>

I actually think this is a very important point to bring up early re:
training, so thanks for mentioning it, Anita! While it's certainly
fair to share one's own experience and observations around training
with the larger community if you choose, it is absolutely important to
respect the boundaries of others' experiences of training and allow
them space to talk about it, or not. It's also crucial that anything
that is expressed by others be treated with a bias towards privacy and
confidentiality (i.e., if you want to write about something someone
said during training on social media, it's appropriate to ask them for
permission to share, first).

I should add - I didn't intend to set any expectations that the
etherpads even be used - I just wanted to provide them as an option to
facilitate, if anyone desires to use them. If no one does, I'm also
fine with that, and I'm happy to take responsibility to answer
questions asked by community members who aren't present on them as I'm
able to.

Thanks!

-colette

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] Leadership training - ideas to include those not in the room?

[Colette Alexander]

On Thu, May 26, 2016 at 12:10 PM, Anita Kuno  wrote:

> I personally think that for any environment to be able to foster
> personal growth the environment has to first and foremost protect the
> privacy of the individual and the sanctity of the space. Personally I
> feel that we as a group have lost the ability we used to have to listen
> to each other in large part because we are expected to be fodder for the
> public at all times. There is a time and a place for privacy. I had
> hoped this event would cultivate this very necessary environment.
>
> As for what others read or what others write, that is up to them. But I
> do hope they are encouraged to internalize, examine and process the
> event rather than just consider themselves a voice for the non present
> as that diminishes significantly from any possible benefit that could be
> gained by those attending. I hope this isn't just another lost opportunity.
>
> I don't know if we have considered the cost of having to be constantly
> on display but there is a cost and I think we are all paying the price.


I should add, I guess, that I doubt there will be any room for laptops
being open or online reaction to activities as-they-happen. there
might be time to reflect on sections of the training at lunch times,
or breaks, or after our day is done, and I wanted to give that option
to folks who felt like sharing their thoughts in a more informal
setting than a blog post. I apologize if it made anyone feel pressured
to share who doesn't want to - that wasn't my intent at all.

-colette

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc] Leadership training - ideas to include those not in the room?

[Colette Alexander]

Hello Stackers!

I just wanted to check in as we approach the leadership training
session that some of the TC and community will be attending in Ann
Arbor, Michigan together [0].


First thing: fostering as much inclusion as possible.

Because of the limited amount of space, I was wondering if anyone had
any ideas of how we might be able to share the experience with anyone
not-in-the-room who is interested.

As a first step, I've set up an etherpad for each of the two days of
training [1] where attendees can jot notes if they'd like to share,
and where anyone not in the room can ask questions, potentially, about
what's happening.

I also expect a few attendees, at least, might find the training
interesting enough to blog about after the fact.

We're barred from recording the training to share with the larger
community (for now) because of contracts, etc., but I can share a
bunch of work from the ZingTrain camp related to the training we'll
have:

1. Free essays (esp. the Leadership and Visioning sections):

http://zingtrain.com/free-samples-and-enews

2. Free webinars (which contain a lot of the elements of blocks of the
training):

http://info.zingtrain.com/webinars

3. Books related to the ZingTrain leadership philosophy:

http://zingtrain.com/being-a-better-leader
and
http://zingtrain.com/managing-ourselves

If anyone has any other suggestions or questions, please respond with
input (and feel free to write me privately if you'd prefer).

Second thing: logistics for attendees

I'm going to have to do some housekeeping/organizational things with
the 19 people attending, and that will just be via private email (and
using the existing etherpad [0]). Keep an eye out for that soon!

Thanks - and I'm really looking forward to sharing this experience
with the whole community!

Sincerely,

-colette/gothicmindfood



[0] https://etherpad.openstack.org/p/Leadershiptraining
[1] https://etherpad.openstack.org/p/ZingTrain1 and
https://etherpad.openstack.org/p/ZingTrain2

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc]Leadership training sign-up available for entire community

[Colette Alexander]

On Wed, May 11, 2016 at 5:02 AM, Colette Alexander
<colettealexan...@gmail.com> wrote:


> [0] 
> http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-05-10-20.02.log.html
> [1] https://etherpad.openstack.org/p/Leadershiptraining

Hey all,

Just a quick update and housekeeping on leadership training:

Steve Martinelli had to drop out, so his spot can be taken by anyone
in the community interested at this point in time. Please see the sign
up sheet, and add your name if you can make it!

Also -
1. If you are listed as tentative (which at this point is Carol
Barrett I think, only) please be kind and update your information as
your travel plans solidify - I'd love to have anyone marked
'tentative' as a final sign up by this Friday, May 20th.
2. If you signed up and haven't done so already, please mark next to
your name how many days you're staying so we know who will be around
on Thursday for the optional 'debrief' day.

Thanks again!

-colette/gothicmindfood

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc]Leadership training sign-up available for entire community

[Colette Alexander]

Good morning, OpenStackers -

At yesterday's TC meeting, we discussed opening up a planned
leadership training at ZingTrain to the entire group, and I'd like to
make that official on the -dev list this morning.[0]

Specifics for the training along with a sign-up are on an etherpad [1]
but the tl;dr is that it will be June 28/29, with an optional day of
discussion/team reflection on the 30th (if you're flying in you should
plan on arriving on June 27th). The Foundation will be covering
training costs (which include meals during training time) but the rest
of meals and lodging and other travel expenses should be covered by
the attendee.

There are only a limited number of spaces available (as of this
morning, 6, though some tentative attendees signed up currently may
open slots later) - please only write your name on the sign-up list on
the etherpad if you know you can go. If for some reason you are signed
up but are unable to attend, please remove yourself from the list and
also ping me on IRC to let me know.

I'm so excited we can open up the training to the greater community -
do let me know if you have any questions or concerns. I'd like to
extend sign-up until May 20th. At that point, I'll consider the list
on the etherpad the final list of attendees, and I'll begin to reach
out to attendees to make sure travel specifics have been worked out.

Thanks!

-colette/gothicmindfood


[0] http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-05-10-20.02.log.html
[1] https://etherpad.openstack.org/p/Leadershiptraining

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] Leadership training dates - please confirm attendance

[Colette Alexander]

On Fri, Apr 22, 2016 at 7:57 AM, Colette Alexander
<colettealexan...@gmail.com> wrote:
> On Thu, Apr 21, 2016 at 10:42 AM, Doug Hellmann <d...@doughellmann.com> wrote:
>>
>> Excerpts from Colette Alexander's message of 2016-04-21 08:07:52 -0700:
>>
>> >
>> > Hi everyone,
>> >
>> > Just checking in on this - if you're a current or past member of the TC and
>> > haven't yet signed up on the etherpad [0] and would like to attend
>> > training, please do so by tomorrow if you can! If you're waiting on travel
>> > approval or something else before you confirm, but want me to hold you a
>> > spot, just ping me on IRC and let me know.
>> >
>> > If you'd like to go to leadership training and you're *not* a past or
>> > current TC member, stay tuned - I'll know about free spots and will send
>> > out information during the summit next week.
>> >
>> > Thank you!
>> >
>> > -colette/gothicmindfood
>> >
>> > [0] https://etherpad.openstack.org/p/Leadershiptraining
>>
>> I've been waiting to have a chance to confer with folks in Austin. Are
>> we under a deadline to get a head-count?

Hey All -

Just checking in on the sign up sheet. I know a few folks mentioned
they were hoping to get travel approval from their managers last week
at the Summit.

Please sign up here as soon as you can (preferably by Friday, May 6th)
and let me know if you're interested but can't confirm travel before
then:  https://etherpad.openstack.org/p/Leadershiptraining

A few folks who are not TC members or TC emeriti have already
contacted me to express interest in attending. If you fall into that
category and think you might want to go to this first, experimental
round of training, and can get travel expenses covered, please feel
free to ping me now to let me know you're interested and/or talk about
logistics. Once I have a final count of TC-related attendance, I'll
make an official announcement on the dev list of extra space
available, and ask folks who are interested to sign up.

It was great to speak with so many of you about this in Austin last week!

Thanks,

-colette/gothicmindfood

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] Leadership training dates - please confirm attendance

[Colette Alexander]

On Thu, Apr 21, 2016 at 10:42 AM, Doug Hellmann  wrote:
>
> Excerpts from Colette Alexander's message of 2016-04-21 08:07:52 -0700:
>
> >
> > Hi everyone,
> >
> > Just checking in on this - if you're a current or past member of the TC and
> > haven't yet signed up on the etherpad [0] and would like to attend
> > training, please do so by tomorrow if you can! If you're waiting on travel
> > approval or something else before you confirm, but want me to hold you a
> > spot, just ping me on IRC and let me know.
> >
> > If you'd like to go to leadership training and you're *not* a past or
> > current TC member, stay tuned - I'll know about free spots and will send
> > out information during the summit next week.
> >
> > Thank you!
> >
> > -colette/gothicmindfood
> >
> > [0] https://etherpad.openstack.org/p/Leadershiptraining
>
> I've been waiting to have a chance to confer with folks in Austin. Are
> we under a deadline to get a head-count?

Only in the sense that I wanted to give non-TC folks some decent lead
time with travel arrangements if there are free spots and they want to
attend. Let's push it back a week if you all need the time to confer.


-colette

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] Leadership training dates - please confirm attendance

[Colette Alexander]

>
>
> >> Colette Alexander wrote:
> >>> Hi everyone!
> >>>
> >>> Quick summary of where we're at with leadership training: dates are
> >>> confirmed as available with ZingTrain, and we're finalizing trainers
> >>> with them right now. *June 28/29th in Ann Arbor, Michigan.*
> >>>
> >>> https://etherpad.openstack.org/p/Leadershiptraining


Hi everyone,

Just checking in on this - if you're a current or past member of the TC and
haven't yet signed up on the etherpad [0] and would like to attend
training, please do so by tomorrow if you can! If you're waiting on travel
approval or something else before you confirm, but want me to hold you a
spot, just ping me on IRC and let me know.

If you'd like to go to leadership training and you're *not* a past or
current TC member, stay tuned - I'll know about free spots and will send
out information during the summit next week.

Thank you!

-colette/gothicmindfood

[0] https://etherpad.openstack.org/p/Leadershiptraining
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc] Leadership training dates - please confirm attendance

[Colette Alexander]

Hi everyone!

Quick summary of where we're at with leadership training: dates are
confirmed as available with ZingTrain, and we're finalizing trainers with
them right now. *June 28/29th in Ann Arbor, Michigan.*

https://etherpad.openstack.org/p/Leadershiptraining

Has updated info, a sample itinerary that's currently being worked on, and
a request for current/recent past TC to please sign up/reserve your spot if
you know you can attend. I'm also probably bugging you on IRC this week a
lot, for good measure. I'm currently waiting on an address for the training
site so I can give decent hotel recs. Keep an eye on the etherpad for that
in the next two days.

I would *really* love to get as many current and past TC members to this as
possible, but totally understand that is dependent on personal schedules
and travel budgets. *If you are uninterested or unable to attend, please
let me know ASAP,* as I'd like to get a count of how many spots are
potentially open for non-TC members of the community who'd like to attend.
I would like to confirm open space on this list by next Friday, April 22nd,
to allow community members who are interested to sign up throughout the end
of April and into early May.

Do let me know if you have any other questions, too.

-colette

(gothicmindfood)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

[Colette Alexander]

On Tue, Mar 8, 2016 at 1:37 PM, Doug Hellmann  wrote:

>
>
> The etherpad [1] doesn't discuss any other alternatives that were
> evaluated and rejected. Were any other options considered? In
> particular, how does this course compare to an event such as the
> Community Leadership Summit[2], for which all of the participants
> are other open source contributors, rather than small business
> owners/managers?
>
> [1] https://etherpad.openstack.org/p/Leadershiptraining
>
>
I just wanted to chime in here, too, that the etherpad does list (at the
bottom) a few other options/companies/groups I researched/vetted, some of
which are larger and more corporate offerings, and/or self-guided online
learning opportunities that I think might cover good leadership training
for the OpenStack community. None of them seemed particularly geared
towards getting the conversation going around defining goals around
leadership in a larger community (rather than corporation) while offering a
subset of varied training opportunities tailored to the group in the way
that ZingTrain does (which they do, btw, because they're geared less
towards corporations, more towards small businesses). I've started filling
in even more options that have come my way since starting to talk with
folks who are giving feedback about what they'd like to see available - so
consider this an invitation to the entire community to add more
options/detail/reviews if you've taken anything you like or hate, or are
curious about an option you may have heard of through colleagues or friends!

I've also posted the sample mash-up itinerary I mentioned previously under
the option for that training in the etherpad, and I'll continue to work
with ZingTrain to finalize a couple of other options. In the meantime if
anyone has feedback or questions or would like to see something look a
little different, do let me know.

Thierry - I didn't quite respond directly to you question about the
consequence of having this expand to include much of the TC in attendance
being that the dev community as a whole feels like there's too much of a
divide between the TC and the larger Community. As I see it, given that we
max out around 20 participants, we could certainly work to actively reserve
space for non-TC community members who express interest. All 13 current
members of the TC have expressed interest in going, and we have potentially
7 entirely new members that can be elected, which puts us around the
maximum preferred in a training if every spot is newly elected and everyone
interested now decides to come (though ZingTrain has said that 22-25 is
sometimes an acceptable overflow). The event-planner in me is assuming that
won't actually happen and we'll have space, but we won't know til after the
election. I think it'd be a huge asset to have more than the TC represented
there, so consider me signed up for helping to organize/engage there.

thanks everyone!

-colette
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

[Colette Alexander]

On Wed, Mar 9, 2016 at 9:32 AM, Doug Hellmann  wrote:

> Excerpts from Sean Dague's message of 2016-03-09 12:22:08 -0500:
> > On 03/09/2016 11:36 AM, Doug Hellmann wrote:
> > > Excerpts from Colette Alexander's message of 2016-03-08 14:34:19 -0800:
> > >> On Tue, Mar 8, 2016 at 1:37 PM, Doug Hellmann 
> wrote:
> > > My interest in attending is based solely on the number of other TC
> > > members going. If a majority go, I feel I need to attend to have a good
> > > common frame of reference for future discussions. If only one or two
> > > folks go and prepare some sort of evaluation, I can skip the trip and
> > > only attend a future course if the evaluators recommend it.
>

I understand that feeling of not wanting to be left out if a majority of
folks are attending - that, I guess, is a side-concern of having seen more
interest in it than I initially expected there would be. Certainly, no one
has done a solid commit yet on the dates - I was going to have to wait
until after the April TC election was over to ask for one, anyhow. By then,
I was hoping to have a few options for itineraries/schedules to send out to
folks to get feedback/preferences on, and figured looking at a sample
schedule(s) might lead some to either decide to skip the trip or be more
interested in attending. Currently, the potential schedules being sent back
and forth between the trainers there have the daytime (8 AM - 5 PM) pretty
booked up with training, with lunch and evenings open, so an accidental
TC-midcycle could definitely occur after-hours. I think
preventing-a-mid-cycle-feeling is also a stronger case for letting TC
members sign up first, but attempting to leave some space open for other
interested members of the community, which I think could only help broaden
the perspectives on all the conversations happening there. As Sean
mentioned, showing up out of obligation rather than genuine interest would
probably be a huge drag for everyone - even skeptics will have an
interest/reason to be there.

I know leading that sort of session is difficult. Is that what
> ZingTrain is offering to do? My understanding from the earlier,
> off-list, discussion was that this was their pre-canned training
> seminar based on one of the books they have available, and not a
> customized facilitation of a discussion about our needs.  Colette,
> can you clarify?


So currently, there are now 3 different 2-day itineraries I've seen, that
I'm ironing out with the trainers (who've spent a few hours on the phone
with me getting background on the community and doing research on the
community on their own) - those itineraries include the standard 2-day
Leading with Zing! training, a brand new Managing Ourselves training, and a
custom 1 day of Leading with Zing! + 1 day Managing Ourselves that I think
might give the most interesting set of shared experiences to start a
conversation about leadership with. FWIW - my understanding of the
activities in the itinerary is that they're inherently structured to be
action/information intake and then group reflection - so there's
conversation built into the training itself. Additionally, I discussed with
them the idea that this would be about facilitating a larger conversation
about the community, to be led by attendees, and they offered to switch up
training on the fly to accommodate where the conversation led and/or add an
extra day post-training with the trainer as facilitator purely to have
reflection/discussion about what comes next. When I thought this might be
6-8 people just before the Summit, that day seemed to not be as necessary
as creating flexibility in the training schedule itself. But if we're
looking at ~14-17 people, and we're not running into the Summit directly
after, it might be more worthwhile. Thoughts on that?


-colette
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

[Colette Alexander]

On Tue, Mar 8, 2016 at 2:34 PM, Colette Alexander <
colettealexan...@gmail.com> wrote:

> So I laid out some of the questions I think the community could benefit
> from alignment on in the etherpad I started already[0], but one of the
> things that really struck me when talking to various members of the TC and
> the community at large about leadership was how vastly different everyone's
> experience, opinions, and approaches were to the questions I asked (which
> were variations of: "As an elected leader in OpenStack, what do you wish
> you would've had as resources to help you adjust to a leadership position?"
> and "What do you think leaders in OpenStack could benefit from, in terms of
> skillsets that could be strengthened or added via any kind of training?")
> At some points, I had people suggesting to me completely opposite
> definitions for the 'problem' of leadership in OpenStack, suggesting that
> certain skillsets that others wanted training for didn't matter at all, and
> generally realized that maybe we all don't have a great shared definition
> of what leadership skills matter here in the community. Having been
> interacting with the community for a few years  now, I wasn't surprised by
> the diversity of opinions, but I think it does mean that some alignment on
> defining the problem would be worthwhile.
>
> Hence, the idea that perhaps a small group of existing leadership should
> get together in a room and talk about how to define/agree on the problem
> appropriately, first, before even beginning to think about having the
> conversation to come up with solutions for it. So in many ways, the goals
> or outcomes of this training would be to get more than a few people in
> leadership positions within the community to gather around a shared
> language and understanding of leadership in order to define problems
> collectively and move forward with discussing solutions more broadly. That
> could take so many possible forms, and be so many things, it's almost
> impossible to sort through.
>
> If you ask me what the 'big goal' of talking about leadership in this
> community is about, I'd say it's about infusing a culture of leadership and
> support for leadership skills and practices in the community that serve its
> members and ultimately provide a more sustainable and humane experience for
> any of the community members who wish to take on leadership positions here.
> To just blatantly copy/paste my case from the etherpad:
> *"As the OpenStack community matures, so too must its support and
> development of its leaders. Many open source movements are not as
> thoroughly democratized as OpenStack, and rely on a Benevolent Dictator for
> Life (BDFL) who is largely responsible for shaping the vision and strategy
> and making ‘product’ decisions for the whole of the project. Without a
> BDFL, many have argued OpenStack will be unable to navigate to product
> maturity. But when one looks back at the last 5 years of growth, it’s very
> apparent that the strength of OpenStack lies in its democracy and community
> diversity - that a reliance on many strong and capable leaders in the
> community is a crucial part of its character and intrinsic to its success.
> Bolstering leadership skills even more through available training and
> resources, and infusing OpenStack’s culture with an emphasis on leadership
> as a core value will only work towards strengthening its democracy."*[0]
>
>
ETA the elusive etherpad link:
[0] https://etherpad.openstack.org/p/Leadershiptraining
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

[Colette Alexander]

On Tue, Mar 8, 2016 at 1:37 PM, Doug Hellmann  wrote:

>
>
> As I understood it when this course was originally proposed, the
> idea was to have a few folks already in leadership positions go
> take the training and evaluate it. Then, assuming the evaluation
> was good, we would offer it to (or at least suggest it to) other
> members of the community like PTLs or folks interested in running
> for leadership positions of some sort (not that folks who aren't
> elected can't be leaders, but one step at a time).
>
> How did that evolve into most of the TC (and Board?) going? Did
> someone do that evaluation already?
>

it only evolved into much of the TC going because more people than I
initially expected to based on previous conversations expressed interest in
being able to attend. The general cost of a single custom-session for a
group makes it possible to accommodate that larger group (so, having 10-20
people in an exclusive, not-public session, is within the bounds of
expected attendance).  No one from the board so far has said they'd be able
to attend, fwiw, and I've checked with a few of them privately to gauge
interest, which seems minimal there. I don't think the expectation that
this is an 'official' or 'required' training is suddenly there, though -
this will still be intended to be an evaluative session, just one that was
more conducive, timing-wise, to the schedules of people who expressed
interest in attending it.



> I've already expressed my skepticism of the idea of a business
> leadership class, and this specific class, being useful to us. I
> did so privately because I am willing to listen to the feedback
> from folks that do attend and I haven't really been involved in the
> planning aside from being asked to be part of the small group doing
> an initial evaluation.  But now if we're gearing up to send a large
> group to I feel it's necessary to say something publicly.
>
> Do we have a set of goals for the outcome of having folks take a
> "leadership" course? Do we have specific issues we would like to
> address through changes in leadership style? Does this course cover
> them?
>

So I laid out some of the questions I think the community could benefit
from alignment on in the etherpad I started already[0], but one of the
things that really struck me when talking to various members of the TC and
the community at large about leadership was how vastly different everyone's
experience, opinions, and approaches were to the questions I asked (which
were variations of: "As an elected leader in OpenStack, what do you wish
you would've had as resources to help you adjust to a leadership position?"
and "What do you think leaders in OpenStack could benefit from, in terms of
skillsets that could be strengthened or added via any kind of training?")
At some points, I had people suggesting to me completely opposite
definitions for the 'problem' of leadership in OpenStack, suggesting that
certain skillsets that others wanted training for didn't matter at all, and
generally realized that maybe we all don't have a great shared definition
of what leadership skills matter here in the community. Having been
interacting with the community for a few years  now, I wasn't surprised by
the diversity of opinions, but I think it does mean that some alignment on
defining the problem would be worthwhile.

Hence, the idea that perhaps a small group of existing leadership should
get together in a room and talk about how to define/agree on the problem
appropriately, first, before even beginning to think about having the
conversation to come up with solutions for it. So in many ways, the goals
or outcomes of this training would be to get more than a few people in
leadership positions within the community to gather around a shared
language and understanding of leadership in order to define problems
collectively and move forward with discussing solutions more broadly. That
could take so many possible forms, and be so many things, it's almost
impossible to sort through.

If you ask me what the 'big goal' of talking about leadership in this
community is about, I'd say it's about infusing a culture of leadership and
support for leadership skills and practices in the community that serve its
members and ultimately provide a more sustainable and humane experience for
any of the community members who wish to take on leadership positions here.
To just blatantly copy/paste my case from the etherpad:
*"As the OpenStack community matures, so too must its support and
development of its leaders. Many open source movements are not as
thoroughly democratized as OpenStack, and rely on a Benevolent Dictator for
Life (BDFL) who is largely responsible for shaping the vision and strategy
and making ‘product’ decisions for the whole of the project. Without a
BDFL, many have argued OpenStack will be unable to navigate to product
maturity. But when one looks back at the last 5 years of growth, it’s very
apparent that the 

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

[Colette Alexander]

On Tue, Mar 8, 2016 at 12:27 PM, Matt Riedemann 
wrote:

>
>>
> So is this for only current TC members? What about people that aren't on
> the TC?
>
> I asked in this in today's TC meeting but figured I'd ask here where it's
> more global.


Because of limited space in the class, and because of the very early stages
of figuring out what, exactly, leadership training or support might look
like in OpenStack, we're focusing on current and future-elected (in April)
TC members as attendees. If there is any extra space in the class
available, I'll be sure to announce that here on the ML as soon as we know,
and would *love* to open space up to the rest of the community, even in
these early stages. Anyone who's interested in learning more or giving
feedback should also feel free to ping me on IRC (I'm gothicmindfood) or
email - I'm happy to answer any and all questions about this.

Thanks!

-colette
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] Leadership training proposal/info

[Colette Alexander]

On Fri, Mar 4, 2016 at 12:54 PM, Colette Alexander <
colettealexan...@gmail.com> wrote:
>
> Current status, btw is 5 TC members as a 'yes' for going on April 21/22  -
> the Thurs/Fri before the summit. 4 additional people have mentioned they're
> interested, but unable to make the scheduling work for this particular
> time.
>
> I also have heard from some core reviewers and PTLs who are eager to
> participate, and who've asked to attend if it's possible.
>
>
Hi everyone,

Just following up with this - I've been in touch with every member of the
TC and there's been a pretty significant interest in the training itself,
and a desire from folks who can't make it in April for pushing dates back
to accommodate as many members as possible.

So - I'm going to suggest we hold off on training until June, with the
understanding that current TC members will be invited as well as those
elected to the TC In April. I'll be checking in on preferred dates with
everyone in the next few days.

Thanks everyone, for all of the feedback and interest!

-colette
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

[Colette Alexander]

On Fri, Mar 4, 2016 at 11:22 AM, Sean Dague <s...@dague.net> wrote:

> On 03/04/2016 02:00 PM, Anne Gentle wrote:
> >
> >
> > On Tue, Mar 1, 2016 at 4:41 PM, Colette Alexander
> > <colettealexan...@gmail.com <mailto:colettealexan...@gmail.com>> wrote:
>
> > tl;dr - If you're a member of the TC or the Board and would like to
> > attend Leadership Training at ZingTrain in Ann Arbor, please get
> > back to me ASAP with your contact info and preferred timing/dates
> > for this two-day training - also, please let me know whether April
> > 20/21 (or April 21/22) would specifically work for you or not.
> >
> >
> >
> > I'd like to, but curious about the possibility of deferring until after
> > the new TC is elected? I know the seats tend to stay static, but with
> > possibly half the TC changing it would offer a nice opportunity to get
> > to know any new members.
>
> The whole thing sounds great, however the timing of that week in April
> is problematic, for the same reason that back to back summit /
> conference weeks would be. 2 weeks away from family is really tough.
>
> Hopefully there will be some later opportunity.
>

I hope so, too!

Current status, btw is 5 TC members as a 'yes' for going on April 21/22  -
the Thurs/Fri before the summit. 4 additional people have mentioned they're
interested, but unable to make the scheduling work for this particular
time.

I also have heard from some core reviewers and PTLs who are eager to
participate, and who've asked to attend if it's possible.

My initial thoughts were that this might ideally be located as far away
from mid-cycles or summits as possible, to give those attending a lot of
time and space to soak it in. I backed away from that stance with
suggesting the week before the summit only because I realized that a) This
is meant to be more of a pilot/test balloon than a final version of some
kind of training, and b) getting everyone to be in one place physically is
going to be difficult, no matter how we approach scheduling. (For example,
Thierry is basically unable to attend May/June/July for anything at this
point, as his schedule is booked up)

I'm absolutely okay with pushing this off to another time, if the TC feels
very strongly about waiting until more TC members can attend (I expect,
even with the newer elected TC, we'll get no more than 8 TC members
attending for the April dates). However, if you all are comfortable, adding
in a few PTLs/core reviewers who are interested and able to attend might be
a good addition to the group in terms of evaluating the potential of the
training. The expectation would be that those who attend would be able to
report back to the rest of the TC, the Board, and the community at large,
and talk about what they thought worked/what didn't, and make
recommendations for future leadership work in the community based on that.

Let me know what you're thinking - I'd love to have the April date nailed
down by early next week (Mon/Tues) *before* the TC meeting so I can allow
people to book their travel.

Thanks everyone!

-colette
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] {openstack-dev][tc] Leadership training proposal/info

[Colette Alexander]

Hello Stackers,

This is the continuation of an ongoing conversation within the TC about
encouraging the growth of leadership skills within the community that began
just after the Mitaka summit last year[1]. After being asked by lifeless to
do a bit of research and discussing needs/wants re: leadership directly
with TC members, I made some suggestions on an etherpad[2], and was then
asked to go find out about funding possibilities.

tl;dr - If you're a member of the TC or the Board and would like to attend
Leadership Training at ZingTrain in Ann Arbor, please get back to me ASAP
with your contact info and preferred timing/dates for this two-day training
- also, please let me know whether April 20/21 (or April 21/22) would
specifically work for you or not.


Longer version:
Mark Collier and the Foundation have graciously offered to cover the costs
of training for a two-day session at ZingTrain in Ann Arbor  - this
includes the cost of breakfast/lunch for two days as well as two full
working-days of seminars. Attendees would be responsible for their own
travel, lodging, and incidental expenses beyond that (hopefully picked up
by your employer who sees this as an amazing opportunity for your career
growth). Currently, I've heard the week before the Austin Summit suggested
by more than one person coming in from out of the country as preferred
dates, but we've not committed to anything yet, so here might be a great
time and place to hash that out among interested parties. ZingTrain has
suggested a cap of ~20 people on the course, but that's not totally firm,
so it's possible to add more if more are interested, or we could hold two
separate two-day sessions to accommodate overflow. My ideal mix of people
include those who are really excited by the idea of training, and those who
are are seriously skeptical of any leadership training at all. In fact, if
you've been to leadership training before and have found it to be terrible
and awful, I think your input would be most valuable on this one. My
summary of reasoning behind the 'why' of ZingTrain can be found on the
etherpad I already mentioned[2]. Also, did I mention, the food will be
amazing? It will be[3].

Some complications: the week before the Newton Summit there will be a set
of incoming TC members (elected in early April) and likely some TC members
who will be outgoing. Some possible solutions: we can certainly push back
training til post-Summit when we can have a set of the 'new' TC, or we can
sign up anyone interested currently, and allow a limited number of newly
elected folks who are interested sign on as the election is finished. I
certainly welcome any thoughts on that.

A note about starting out with the TC/Board for training: this initiative
began as a set of conversations about leadership as a whole in the entire
OpenStack community, so the intent with limiting to TC/Board here is not
exclusion, merely finding the right place to start. My proposal with the TC
begins with them, because the leadership conversation within OpenStack
began with them, and the goals of training are really to help them talk
about defining the issue/problem collectively, within a space designed to
help people do that.

If you have any questions at all, please feel free to ping me on IRC
(gothicmindfood) or ask them here.

Thanks everyone!

-colette


[1]
http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-11-03-20.07.log.html
[2] https://etherpad.openstack.org/p/Leadershiptraining
[3] http://www.zingermansdeli.com/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev