Re: [openstack-dev] Diversity and Inclusion at OpenStack Summit

[Amy Marrich]

Forgot one important one on Wednesday, 12:30 - 1:40!!!

We are very pleased to have the very first *Diversity Networking Lunch*
which os being sponsored by Intel[0]. In the past there was feedback that
allies and others didn't wish to intrude on the WoO lunch and Intel was all
for this change to a more open Diversity lunch! So please come and join us
on Wednesday for lunch!!

See you all soon,

Amy Marrich (spotz)
Diversity and Inclusion WG Chair


[0] -
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22850/diversity-networking-lunch-sponsored-by-intel



On Wed, Nov 7, 2018 at 9:18 AM, Amy Marrich  wrote:

> I just wanted to pass on a few things we have going on during Summit that
> might be of interest!
>
> *Diversity and Inclusion GroupMe* - Is it your first summit and you don't
> know anyone else? Maybe you just don't want to travel to and from the venue
> alone? In the tradition of WoO, I have created a GroupMe so people can
> communicate with each other. If you would like to be added to the group
> please let me know and I'll get you added!
>
> *Night Watch Tour *- On Wednesday night at 10PM, members of the community
> will be meeting up to go on a private Night Watch Tour[0]! This is a
> non-alcoholic activity for those wanting to get with other Stackers, but
> don't want to partake in the Pub Crawl! We've been doing these since Boston
> and they're a lot of fun. The cost is 15 euros cash and I do need you to
> RSVP to me as we will need to get a second guide if we grow too large!
>
> Summit sessions you may wish to attend:
> Tuesday -
> *Speed Mentoring Lunch* [1] 12:30 -1:40 - We are still looking for both
> Mentors and Mentees for the session so please RSVP! This is another great
> way to meet people in the community, learn more and give back!!!
> *Cohort Mentoring BoF* [2] 4:20 - 5:00 - Come talk to the people in
> charge of the Cohort Mentoring program and see how you can get involved as
> a Mentor or Mentee!
> *D WG Update* [3] 5:10- 5:50 - Learn what we've been up to, how you can
> get involved, and what's next.
>
> Wednesday -
> *Git and Gerrit Hands-On Workshop* [4] 3:20 - 4:20 - So you've seen some
> exciting stuff this week but don't know how to get setup to start
> contributing? This session is for you in that we'll walk you through
> getting your logins, your system configured and if time allows even how to
> submit a bug and patch!
>
> Thursday -
> *Mentoring Program Reboot* [5] 3:20 - 4:00 - Learn about the importance
> of mentoring, the changes in the OPenStack mentoring programs and how you
> can get involved.
>
> Hope to see everyone in Berlin next week! Please feel free to contact me
> or grab me in the hall next week with any questions or to join in the fun!
>
> Amy Marrich (spotz)
> Diversity and Inclusion WG Chair
>
> [0] - http://baerentouren.de/nachtwache_en.html
> [1] - https://www.openstack.org/summit/berlin-2018/summit-
> schedule/events/22873/speed-mentoring-lunch
> [2] - https://www.openstack.org/summit/berlin-2018/summit-
> schedule/events/22892/long-term-mentoring-keeping-the-party-going
> [3] - https://www.openstack.org/summit/berlin-2018/summit-
> schedule/events/22893/diversity-and-inclusion-wg-update
> [4] - https://www.openstack.org/summit/berlin-2018/summit-
> schedule/events/21943/git-and-gerrit-hands-on-workshop
> [5] - https://www.openstack.org/summit/berlin-2018/summit-
> schedule/events/22443/mentoring-program-reboot
>
__
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] Diversity and Inclusion at OpenStack Summit

[Amy Marrich]

I just wanted to pass on a few things we have going on during Summit that
might be of interest!

*Diversity and Inclusion GroupMe* - Is it your first summit and you don't
know anyone else? Maybe you just don't want to travel to and from the venue
alone? In the tradition of WoO, I have created a GroupMe so people can
communicate with each other. If you would like to be added to the group
please let me know and I'll get you added!

*Night Watch Tour *- On Wednesday night at 10PM, members of the community
will be meeting up to go on a private Night Watch Tour[0]! This is a
non-alcoholic activity for those wanting to get with other Stackers, but
don't want to partake in the Pub Crawl! We've been doing these since Boston
and they're a lot of fun. The cost is 15 euros cash and I do need you to
RSVP to me as we will need to get a second guide if we grow too large!

Summit sessions you may wish to attend:
Tuesday -
*Speed Mentoring Lunch* [1] 12:30 -1:40 - We are still looking for both
Mentors and Mentees for the session so please RSVP! This is another great
way to meet people in the community, learn more and give back!!!
*Cohort Mentoring BoF* [2] 4:20 - 5:00 - Come talk to the people in charge
of the Cohort Mentoring program and see how you can get involved as a
Mentor or Mentee!
*D WG Update* [3] 5:10- 5:50 - Learn what we've been up to, how you can
get involved, and what's next.

Wednesday -
*Git and Gerrit Hands-On Workshop* [4] 3:20 - 4:20 - So you've seen some
exciting stuff this week but don't know how to get setup to start
contributing? This session is for you in that we'll walk you through
getting your logins, your system configured and if time allows even how to
submit a bug and patch!

Thursday -
*Mentoring Program Reboot* [5] 3:20 - 4:00 - Learn about the importance of
mentoring, the changes in the OPenStack mentoring programs and how you can
get involved.

Hope to see everyone in Berlin next week! Please feel free to contact me or
grab me in the hall next week with any questions or to join in the fun!

Amy Marrich (spotz)
Diversity and Inclusion WG Chair

[0] - http://baerentouren.de/nachtwache_en.html
[1] -
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22873/speed-mentoring-lunch
[2] -
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22892/long-term-mentoring-keeping-the-party-going
[3] -
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22893/diversity-and-inclusion-wg-update
[4] -
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/21943/git-and-gerrit-hands-on-workshop
[5] -
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22443/mentoring-program-reboot
__
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 Diversity and Inclusion Survey

[Amy Marrich]

The Diversity and Inclusion WG is still looking for your assistance in
reaching and including data from as many members of our community as
possible.

We revised the Diversity Survey that was originally distributed to the
Community in the Fall of 2015 and reached out in August with our new
survey.  We are looking to update our view of the OpenStack community and
it's diversity. We are pleased to be working with members of the CHAOSS
project who have signed confidentiality agreements in order to assist us in
the following ways:

1) Assistance in analyzing the results
2) And feeding the results into the CHAOSS software and metrics development
work so that we can help other Open Source projects

Please take the time to fill out the survey and share it with others in the
community. The survey can be found at:

https://www.surveymonkey.com/r/OpenStackDiversity

Thank you for assisting us in this important task! Please feel free to
reach out to me via email, in Berlin, or to myself or any WG member in
#openstack-diversity!

Amy Marrich (spotz)
Diversity and Inclusion Working Group Chair
__
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-community] Sharing upstream contribution mentoring result with Korea user group

[Amy Marrich]

Ian,

Great job by yourself, your mentees and last but not least your mentors!

Way to go!!!

Amy (spotz)

On Tue, Oct 30, 2018 at 9:10 AM, Ian Y. Choi  wrote:

> Hello,
>
> I got involved organizing & mentoring Korean people for OpenStack upstream
> contribution for about last two months,
> and would like to share with community members.
>
> Total nine mentees had started to learn OpenStack, contributed, and
> finally survived as volunteers for
>  1) developing OpenStack mobile app for better mobile user interfaces and
> experiences
> (inspired from https://github.com/stackerz/app which worked on Juno
> release), and
>  2) translating OpenStack official project artifacts including documents,
>  and Container Whitepaper ( https://www.openstack.org/cont
> ainers/leveraging-containers-and-openstack/ ).
>
> Korea user group organizers (Seongsoo Cho, Taehee Jang, Hocheol Shin,
> Sungjin Kang, and Andrew Yongjoon Kong)
> all helped to organize total 8 offline meetups + one mini-hackathon and
> mentored to attendees.
>
> The followings are brief summary:
>  - "OpenStack Controller" Android app is available on Play Store
>   : https://play.google.com/store/apps/details?id=openstack.cont
> ributhon.com.openstackcontroller
>(GitHub: https://github.com/kosslab-kr/openstack-controller )
>
>  - Most high-priority projects (although it is not during string freeze
> period) and documents are
>100% translated into Korean: Horizon, OpenStack-Helm, I18n Guide, and
> Container Whitepaper.
>
>  - Total 18,695 words were translated into Korean by four contributors
>   (confirmed through Zanata API: https://translate.openstack.or
> g/rest/stats/user/[Zanata ID]/2018-08-16..2018-10-25 ):
>
> ++---+-+
> | Zanata ID  | Name  | Number of words |
> ++---+-+
> | ardentpark | Soonyeul Park | 12517   |
> ++---+-+
> | bnitech| Dongbim Im| 693 |
> ++---+-+
> | csucom | Sungwook Choi | 4397|
> ++---+-+
> | jaeho93| Jaeho Cho | 1088|
> ++---+-+
>
>  - The list of projects translated into Korean are described as:
>
> +-+-+
> | Project | Number of words |
> +-+-+
> | api-site| 20  |
> +-+-+
> | cinder  | 405 |
> +-+-+
> | designate-dashboard | 4   |
> +-+-+
> | horizon | 3226|
> +-+-+
> | i18n| 434 |
> +-+-+
> | ironic  | 4   |
> +-+-+
> | Leveraging Containers and OpenStack | 5480|
> +-+-+
> | neutron-lbaas-dashboard | 5   |
> +-+-+
> | openstack-helm  | 8835|
> +-+-+
> | trove-dashboard | 89  |
> +-+-+
> | zun-ui  | 193 |
> +-+-+
>
> I would like to really appreciate all co-mentors and participants on such
> a big event for promoting OpenStack contribution.
> The venue and food were supported by Korea Open Source Software
> Development Center ( https://kosslab.kr/ ).
>
>
> With many thanks,
>
> /Ian
>
> ___
> Community mailing list
> commun...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
>
__
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] [os-upstream-institute] Team lunch at the PTG next week - ACTION NEEDED

[Amy Marrich]

I'm game!

Amy (spotz)

On Fri, Sep 7, 2018 at 5:30 PM, Ildiko Vancsa 
wrote:

> Hi Training Team,
>
> As a couple of us will be at the PTG next week it would be great to get
> together one of the days maybe for lunch.
>
> Wednesday would work the best for Kendall and me, but we can look into
> other days as well if it would not work for the majority of people around.
>
> So my questions would be:
>
> * Are you interested in getting together one of the lunch slots during
> next week?
>
> * Would Wednesday work for you or do you have another preference?
>
> Please drop a response to this thread and we will figure it out by Monday
> or early next week based on the responses.
>
> Thanks,
> Ildikó
> (IRC: ildikov)
>
>
>
> __
> 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

Re: [openstack-dev] [election] [tc] thank you

[Amy Marrich]

Emilien,

Thank you so much for all you've done as part of the TC and continue todo
within the community!

Amy (spotz)

On Wed, Sep 5, 2018 at 8:03 AM, Anita Kuno  wrote:

> On 2018-09-05 04:01 AM, Thierry Carrez wrote:
>
>> Emilien Macchi wrote:
>>
>
> I personally feel like some rotation needs to happen
>>>
>>
> A very honourable sentiment, Emilien. I'm so grateful to have spent time
> working with your very generous spirit.
>
> To more such work in the future, Anita
>
>
>
> __
> 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

Re: [openstack-dev] non-candidacy for TC

[Amy Marrich]

Thanks for all your contributions while on the TC Paul!

Amy (spotz)

On Tue, Sep 4, 2018 at 4:46 PM, Paul Belanger  wrote:

> Greetings,
>
> After a year on the TC, I've decided not to run for another term. I'd
> like to thank the other TC members for helping bring me up to speed over
> the last year and community for originally voting.  There is always work
> to do, and I'd like to use this email to encourage everybody to strongly
> consider running for the TC if you are interested in the future of
> OpenStack.
>
> It is a great learning opportunity, great humans to work with and great
> project! Please do consider running if you are at all interested.
>
> Thanks again,
> Paul
>
> __
> 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

Re: [openstack-dev] [Openstack-sigs] UC Elections will not be held

[Amy Marrich]

Congrats to VW and Joseph. Thank you to Saverio for his hard work. And
lastly thank you to Ed, Chandan, and Mohamed for serving as our election
officials!

Amy (spotz)
User Committee

On Tue, Aug 21, 2018 at 2:44 PM, Ed Leafe  wrote:

> As there were only 2 nominations for the 2 open seats, elections will not
> be needed. Congratulations to Matt Van Winkle and Joseph Sandoval!
>
> -- Ed Leafe
>
>
>
>
>
>
> ___
> openstack-sigs mailing list
> openstack-s...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>
__
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 Diversity and Inclusion Survey

[Amy Marrich]

The Diversity and Inclusion WG is asking for your assistance. We have
revised the Diversity Survey that was originally distributed to the
Community in the Fall of 2015 and are looking to update our view of the
OpenStack community and it's diversity. We are pleased to be working with
members of the CHAOSS project who have signed confidentiality agreements in
order to assist us in the following ways:

1) Assistance in analyzing the results
2) And feeding the results into the CHAOSS software and metrics development
work so that we can help other Open Source projects

Please take the time to fill out the survey and share it with others in the
community. The survey can be found at:

https://www.surveymonkey.com/r/OpenStackDiversity

Thank you for assisting us in this important task!

Amy Marrich (spotz)
Diversity and Inclusion Working Group Chair
__
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] [cinder] Reminder about the weekly Cinder meeting ...

[Amy Marrich]

That bot is indeed missing from the channel

Amy (spotz)

On Mon, Aug 13, 2018 at 5:44 PM, Jeremy Stanley  wrote:

> On 2018-08-13 16:29:27 -0500 (-0500), Amy Marrich wrote:
> > I know we did a ping last week in #openstack-ansible for our meeting no
> > issue. I wonder if it's a length of names thing or a channel setting.
> [...]
>
> Freenode's Sigyn bot may not have been invited to
> #openstack-ansible. We might want to consider kicking it from
> channels while they have nick registration enforced.
> --
> Jeremy Stanley
>
> __
> 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] (no subject)

[Amy Marrich]

Hi everyone,

If you’re running OpenStack, please participate in the User Survey
<http://www.openstack.org/user-survey> to share more about the technology
you are using and provide feedback for the community by *August 21 - hurry,
it’s next week!!* By completing a deployment, you will qualify as an AUC
and receive a $300 USD ticket to the two upcoming Summits.

Please help us spread the word. a we're trying to gather as much real-world
deployment data as possible to share back with both the operator and
developer communities.

We are only conducting one survey this year, and the report will be
published at the Berlin Summit
<https://www.openstack.org/summit/berlin-2018/>.  II you would like
OpenStack user data in the meantime, check out the analytics dashboard
<https://www.openstack.org/analytics> updates in real time, throughout the
year.

The information provided is confidential and will only be presented in
aggregate unless you consent to make it public.

The deadline to complete the survey and be part of the next report is
next *Tuesday,
August 21** at 23:59 UTC.*

   - You can login and complete the OpenStack User Survey here:
   http://www.openstack.org/user-survey
   <http://www.openstack.org/user-survey>
   - If you’re interested in joining the OpenStack User Survey Working
   Group to help with the survey analysis, please complete this form:
   https://openstackfoundation.formstack.com/forms/user_survey_working_group
   <https://openstackfoundation.formstack.com/forms/user_survey_working_group>

   - Help us promote the User Survey: https://twitter.com/Op
   enStack/status/993589356312088577
   <https://twitter.com/OpenStack/status/993589356312088577>


Please let me know if you have any questions.

Thanks,
Amy

Amy Marrich (spotz)
OpenStack User Committee
__
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] [cinder] Reminder about the weekly Cinder meeting ...

[Amy Marrich]

I know we did a ping last week in #openstack-ansible for our meeting no
issue. I wonder if it's a length of names thing or a channel setting.

Amy (spotz)

On Mon, Aug 13, 2018 at 4:25 PM, Eric Fried  wrote:

> Are you talking about the nastygram from "Sigyn" saying:
>
> "Your actions in # tripped automated anti-spam measures
> (nicks/hilight spam), but were ignored based on your time in channel;
> stop now, or automated action will still be taken. If you have any
> questions, please don't hesitate to contact a member of staff"
>
> I'm getting this too, and (despite the implication to the contrary) it
> sometimes cuts off my messages in an unpredictable spot.
>
> I'm contacting "a member of staff" to see if there's any way to get
> "whitelisted" for big messages. In the meantime, the only solution I'm
> aware of is to chop your pasteypaste up into smaller chunks, and wait a
> couple seconds between pastes.
>
> -efried
>
> On 08/13/2018 04:06 PM, Ben Nemec wrote:
> >
> >
> > On 08/08/2018 12:04 PM, Jay S Bryant wrote:
> >> Team,
> >>
> >> A reminder that we have our weekly Cinder meeting on Wednesdays at
> >> 16:00 UTC.  I bring this up as I can no longer send the courtesy pings
> >> without being kicked from IRC.  So, if you wish to join the meeting
> >> please add a reminder to your calendar of choice.
> >
> > Do you have any idea why you're being kicked?  I'm wondering how to
> > avoid getting into this situation with the Oslo pings.
> >
> > 
> __
> > 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 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] User Committee Election Nominations Reminder

[Amy Marrich]

Just wanted to remind everyone that the nomination period for the User
Committee elections are open until August 17, 05:59 UTC. If you are an AUC
and thinking about running what's stopping you? If you know of someone who
would make a great committee member nominate them! Help make a difference
for Operators, Users and the Community!

Thanks,

Amy Marrich (spotz)
User Committee
__
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] Stepping down as coordinator for the Outreachy internships

[Amy Marrich]

Victoria,

Thank you for everything you've down with the Outreachy program!

Amy (spotz)

On Tue, Aug 7, 2018 at 6:47 PM, Victoria Martínez de la Cruz <
victo...@vmartinezdelacruz.com> wrote:

> Hi all,
>
> I'm reaching you out to let you know that I'll be stepping down as
> coordinator for OpenStack next round. I had been contributing to this
> effort for several rounds now and I believe is a good moment for somebody
> else to take the lead. You all know how important is Outreachy to me and
> I'm grateful for all the amazing things I've done as part of the Outreachy
> program and all the great people I've met in the way. I plan to keep
> involved with the internships but leave the coordination tasks to somebody
> else.
>
> If you are interested in becoming an Outreachy coordinator, let me know
> and I can share my experience and provide some guidance.
>
> Thanks,
>
> Victoria
>
> __
> 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] New AUC Criteria

[Amy Marrich]

*Are you an Active User Contributor (AUC)? Well you may be and not even
know it! Historically, AUCs met the following criteria: - Organizers of
Official OpenStack User Groups: from the Groups Portal- Active members and
contributors to functional teams and/or working groups (currently also
manually calculated for WGs not using IRC): from IRC logs- Moderators of
any of the operators official meet-up sessions: Currently manually
calculated.- Contributors to any repository under the UC governance: from
Gerrit- Track chairs for OpenStack summits: from the Track Chair tool-
Contributors to Superuser (articles, interviews, user stories, etc.): from
the Superuser backend- Active moderators on ask.openstack.org
<http://ask.openstack.org>: from Ask OpenStackIn July, the User Committee
(UC) voted to add the following criteria to becoming an AUC in order to
meet the needs of the evolving OpenStack Community. So in addition to the
above ways, you can now earn AUC status by meeting the following: - User
survey participants who completed a deployment survey- Ops midcycle session
moderators- OpenStack Days organizers- SIG Members nominated by SIG
leaders- Active Women of OpenStack participants- Active Diversity WG
participantsWell that’s great you have met the requirements to become an
AUC but what does that mean? AUCs can run for open UC positions and can
vote in the elections. AUCs also receive a discounted $300 ticket for
OpenStack Summit as well as having the coveted AUC insignia on your badge!*
And remember nominations for the User Committee open on Monday, August 6
and end on August, 17 with voting August 20 to August 24.

Amy Marrich (spotz)
User Committee
__
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-ansible] Proposing Jonathan Rosser as core reviewer

[Amy Marrich]

+2 from me!

Amy (spotz)

On Mon, Jul 30, 2018 at 3:16 AM, jean-phili...@evrard.me <
jean-phili...@evrard.me> wrote:

> Hello everyone,
>
> I'd like to propose Jonathan Rosser (jrosser) as core reviewer for
> OpenStack-Ansible.
> The BBC team [1] has been very active recently across the board, but
> worked heavily in our ops repo, making sure the experience is complete for
> operators.
>
> I value Jonathan's opinion (I remember the storage backend conversations
> for lxc/systemd-nspawn!), and I'd like this positive trend to continue. On
> top of it Jonathan has been recently reviewing quite a series of patches,
> and is involved into some of our important work: bringing the Bionic
> support.
>
> Best regards,
> Jean-Philippe Evrard (evrardjp)
>
> [1]: http://stackalytics.com/?project_type=openstack;
> release=rocky=commits=BBC
>
>
> __
> 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

Re: [openstack-dev] [Zun] Zun UI questions

[Amy Marrich]

Hongbin,

I just wanted to follow-up and let a fresh install of the most recent
release is working with no errors.

Thanks so much for your assistance!

Amy (spotz)

On Sun, Jul 15, 2018 at 10:49 AM, Hongbin Lu  wrote:

> Hi Amy,
>
> The wrong Keystone URI might be due to the an issue of the devstack
> plugins. I have proposed fixes [1] [2] for that. Thanks for the suggestion
> about adding a note for uninstalling pip packages. I have created a ticket
> [3] for that.
>
> [1] https://review.openstack.org/#/c/582799/
> [2] https://review.openstack.org/#/c/582800/
> [3] https://bugs.launchpad.net/zun/+bug/1781807
>
> Best regards,
> Hongbin
>
> On Sun, Jul 15, 2018 at 10:16 AM Amy Marrich  wrote:
>
>> Hongbin,
>>
>> Doing the pip uninstall did the trick with the Flask version, when
>> running another debug I did notice an incorrect IP for the Keystone URI and
>> have restarted the machines networking and cleaned up the /etc/hosts.
>>
>> When doing a second stack, I did need to uninstall the pip packages again
>> for the second stack.sh to complete, might be worth adding this to the docs
>> as a note if people have issues. Second install still had the wrong IP
>> showing as the Keystone URI, I'll try s fresh machine install next.
>>
>> Thanks for all your help!
>>
>> Amy (spotz)
>>
>> On Sat, Jul 14, 2018 at 9:42 PM, Hongbin Lu  wrote:
>>
>>> Hi Amy,
>>>
>>> Today, I created a fresh VM with Ubuntu16.04 and run ./stack.sh with
>>> your local.conf, but I couldn't reproduce the two issues you mentioned (the
>>> Flask version conflict issue and 401 issue). By analyzing the logs you
>>> provided, it seems some python packages in your machine are pretty old.
>>> First, could you paste me the output of "pip freeze". Second, if possible,
>>> I would suggest to remove all the python packages and re-stack again as
>>> following:
>>>
>>> * Run ./unstack
>>> * Run ./clean.sh
>>> * Run  pip freeze | grep -v '^\-e' | xargs sudo pip uninstall -y
>>> * Run ./stack
>>>
>>> Please let us know if above steps still don't work.
>>>
>>> Best regards,
>>> Hongbin
>>>
>>> On Sat, Jul 14, 2018 at 5:15 PM Amy Marrich  wrote:
>>>
>>>> Hongbin,
>>>>
>>>> This was a fresh install from master this week
>>>>
>>>> commit 6312db47e9141acd33142ae857bdeeb92c59994e
>>>>
>>>> Merge: ef35713 2742875
>>>>
>>>> Author: Zuul 
>>>>
>>>> Date:   Wed Jul 11 20:36:12 2018 +
>>>>
>>>>
>>>> Merge "Cleanup keystone's removed config options"
>>>>
>>>> Except for builds with my patching kuryr-libnetwork locally builds have
>>>> been done with reclone and fresh /opt/stack directories. Patch has been
>>>> submitted for the Flask issue
>>>>
>>>> https://review.openstack.org/582634 but hasn't passed the gates yet.
>>>>
>>>>
>>>> Following the instructions above on a new pull of devstack:
>>>>
>>>> commit 3b5477d6356a62d7d64a519a4b1ac99309d251c0
>>>>
>>>> Author: OpenStack Proposal Bot 
>>>>
>>>> Date:   Thu Jul 12 06:17:32 2018 +
>>>>
>>>> Updated from generate-devstack-plugins-list
>>>>
>>>> Change-Id: I8f702373c76953a0a29285f410d368c975ba4024
>>>>
>>>>
>>>> I'm still able to use the openstack CLI for non-Zun commands but 401 on
>>>> Zun
>>>>
>>>> root@zunui:~# openstack service list
>>>>
>>>> +--+--+-
>>>> -+
>>>>
>>>> | ID   | Name | Type
>>>>   |
>>>>
>>>> +--+--+-
>>>> -+
>>>>
>>>> | 06be414af2fd4d59af8de0ccff78149e | placement| placement
>>>>   |
>>>>
>>>> | 0df1832d6f8c4a5aa7b5e8bacf7339f8 | nova | compute
>>>>   |
>>>>
>>>> | 3f1b2692a184443c85b631fa7acf714d | heat-cfn | cloudformation
>>>> |
>>>>
>>>> | 3f6bcbb75f684041bf6eeaaf5ab4c14b | cinder   | block-storage
>>>>   |
>>>>
>>>> | 6e06ac1394ee4872aa134081d190f18e | neutron  | 

Re: [openstack-dev] [Zun] Zun UI questions

[Amy Marrich]

Hongbin,

Doing the pip uninstall did the trick with the Flask version, when running
another debug I did notice an incorrect IP for the Keystone URI and have
restarted the machines networking and cleaned up the /etc/hosts.

When doing a second stack, I did need to uninstall the pip packages again
for the second stack.sh to complete, might be worth adding this to the docs
as a note if people have issues. Second install still had the wrong IP
showing as the Keystone URI, I'll try s fresh machine install next.

Thanks for all your help!

Amy (spotz)

On Sat, Jul 14, 2018 at 9:42 PM, Hongbin Lu  wrote:

> Hi Amy,
>
> Today, I created a fresh VM with Ubuntu16.04 and run ./stack.sh with your
> local.conf, but I couldn't reproduce the two issues you mentioned (the
> Flask version conflict issue and 401 issue). By analyzing the logs you
> provided, it seems some python packages in your machine are pretty old.
> First, could you paste me the output of "pip freeze". Second, if possible,
> I would suggest to remove all the python packages and re-stack again as
> following:
>
> * Run ./unstack
> * Run ./clean.sh
> * Run  pip freeze | grep -v '^\-e' | xargs sudo pip uninstall -y
> * Run ./stack
>
> Please let us know if above steps still don't work.
>
> Best regards,
> Hongbin
>
> On Sat, Jul 14, 2018 at 5:15 PM Amy Marrich  wrote:
>
>> Hongbin,
>>
>> This was a fresh install from master this week
>>
>> commit 6312db47e9141acd33142ae857bdeeb92c59994e
>>
>> Merge: ef35713 2742875
>>
>> Author: Zuul 
>>
>> Date:   Wed Jul 11 20:36:12 2018 +
>>
>>
>> Merge "Cleanup keystone's removed config options"
>>
>> Except for builds with my patching kuryr-libnetwork locally builds have
>> been done with reclone and fresh /opt/stack directories. Patch has been
>> submitted for the Flask issue
>>
>> https://review.openstack.org/582634 but hasn't passed the gates yet.
>>
>>
>> Following the instructions above on a new pull of devstack:
>>
>> commit 3b5477d6356a62d7d64a519a4b1ac99309d251c0
>>
>> Author: OpenStack Proposal Bot 
>>
>> Date:   Thu Jul 12 06:17:32 2018 +
>>
>> Updated from generate-devstack-plugins-list
>>
>> Change-Id: I8f702373c76953a0a29285f410d368c975ba4024
>>
>>
>> I'm still able to use the openstack CLI for non-Zun commands but 401 on
>> Zun
>>
>> root@zunui:~# openstack service list
>>
>> +--+--+-
>> -+
>>
>> | ID   | Name | Type
>> |
>>
>> +--+--+-
>> -+
>>
>> | 06be414af2fd4d59af8de0ccff78149e | placement| placement
>> |
>>
>> | 0df1832d6f8c4a5aa7b5e8bacf7339f8 | nova | compute
>> |
>>
>> | 3f1b2692a184443c85b631fa7acf714d | heat-cfn | cloudformation
>> |
>>
>> | 3f6bcbb75f684041bf6eeaaf5ab4c14b | cinder   | block-storage
>> |
>>
>> | 6e06ac1394ee4872aa134081d190f18e | neutron  | network
>> |
>>
>> | 76afda8ecd18474ba382dbb4dc22b4bb | kuryr-libnetwork | kuryr-libnetwork
>> |
>>
>> | 7b336b8b9b9c4f6bbcc5fa6b9400ccaf | cinderv3 | volumev3
>> |
>>
>> | a0f83f30276d45e2bd5fd14ff8410380 | nova_legacy  | compute_legacy
>> |
>>
>> | a12600a2467141ff89a406ec3b50bacb | cinderv2 | volumev2
>> |
>>
>> | d5bfb92a244b4e7888cae28ca6b2bbac | keystone | identity
>> |
>>
>> | d9ea196e9cae4b0691f6c4b619eb47c9 | zun  | container
>> |
>>
>> | e528282e291f4ddbaaac6d6c82a0036e | cinder   | volume
>> |
>>
>> | e6078b2c01184f88a784b390f0b28263 | glance   | image
>> |
>>
>> | e650be6c67ac4e5c812f2a4e4cca2544 | heat | orchestration
>> |
>>
>> +--+--+-
>> -+
>>
>> root@zunui:~# openstack appcontainer list
>>
>> Unauthorized (HTTP 401) (Request-ID: req-e44f5caf-642c-4435-ab1d-
>> 98feae1fada9)
>>
>> root@zunui:~# zun list
>>
>> ERROR: Unauthorized (HTTP 401) (Request-ID: req-587e39d6-463f-4921-b45b-
>> 29576a00c242)
>>
>>
>> Thanks,
>>
>>
>> Amy (spotz)
>>
>>
>>
>> On Fri, Jul 13, 2018 at 10:34 PM, Hongbin Lu 
>> wrote:
>>
>>> Hi Amy,
>>>
>>> First, I want to confirm which version of devstack

Re: [openstack-dev] [Zun] Zun UI questions

[Amy Marrich]

Hongbin,

This was a fresh install from master this week

commit 6312db47e9141acd33142ae857bdeeb92c59994e

Merge: ef35713 2742875

Author: Zuul 

Date:   Wed Jul 11 20:36:12 2018 +


Merge "Cleanup keystone's removed config options"

Except for builds with my patching kuryr-libnetwork locally builds have
been done with reclone and fresh /opt/stack directories. Patch has been
submitted for the Flask issue

https://review.openstack.org/582634 but hasn't passed the gates yet.


Following the instructions above on a new pull of devstack:

commit 3b5477d6356a62d7d64a519a4b1ac99309d251c0

Author: OpenStack Proposal Bot 

Date:   Thu Jul 12 06:17:32 2018 +

Updated from generate-devstack-plugins-list

Change-Id: I8f702373c76953a0a29285f410d368c975ba4024


I'm still able to use the openstack CLI for non-Zun commands but 401 on Zun

root@zunui:~# openstack service list

+--+--+--+

| ID   | Name | Type |

+--+--+--+

| 06be414af2fd4d59af8de0ccff78149e | placement| placement|

| 0df1832d6f8c4a5aa7b5e8bacf7339f8 | nova | compute  |

| 3f1b2692a184443c85b631fa7acf714d | heat-cfn | cloudformation   |

| 3f6bcbb75f684041bf6eeaaf5ab4c14b | cinder   | block-storage|

| 6e06ac1394ee4872aa134081d190f18e | neutron  | network  |

| 76afda8ecd18474ba382dbb4dc22b4bb | kuryr-libnetwork | kuryr-libnetwork |

| 7b336b8b9b9c4f6bbcc5fa6b9400ccaf | cinderv3 | volumev3 |

| a0f83f30276d45e2bd5fd14ff8410380 | nova_legacy  | compute_legacy   |

| a12600a2467141ff89a406ec3b50bacb | cinderv2 | volumev2 |

| d5bfb92a244b4e7888cae28ca6b2bbac | keystone | identity |

| d9ea196e9cae4b0691f6c4b619eb47c9 | zun  | container|

| e528282e291f4ddbaaac6d6c82a0036e | cinder   | volume   |

| e6078b2c01184f88a784b390f0b28263 | glance   | image|

| e650be6c67ac4e5c812f2a4e4cca2544 | heat | orchestration|

+--+--+--+

root@zunui:~# openstack appcontainer list

Unauthorized (HTTP 401) (Request-ID: req-e44f5caf-642c-4435-ab1d-
98feae1fada9)

root@zunui:~# zun list

ERROR: Unauthorized (HTTP 401) (Request-ID: req-587e39d6-463f-4921-b45b-
29576a00c242)


Thanks,


Amy (spotz)



On Fri, Jul 13, 2018 at 10:34 PM, Hongbin Lu  wrote:

> Hi Amy,
>
> First, I want to confirm which version of devstack you were using? (go to
> the devstack folder and type "git log -1").
>
> If possible, I would suggest to do the following steps:
>
> * Run ./unstack
> * Run ./clean
> * Pull down the latest version of devstack (if it is too old)
> * Pull down the latest version of all the projects under /opt/stack/
> * Run ./stack
>
> If above steps couldn't resolve the problem, please let me know.
>
> Best regards,
> Hongbin
>
>
> On Fri, Jul 13, 2018 at 10:33 AM Amy Marrich  wrote:
>
>> Hongbin,
>>
>> Let me know if you still want me to mail the dev list, but here are the
>> gists for the installations and the broken CLI I mentioned
>>
>> local.conf - which is basically the developer quickstart instructions for
>> Zun
>>
>> https://gist.github.com/spotz/69c5cfa958b233b4c3d232bbfcc451ea
>>
>>
>> This is the failure with a fresh devstack installation
>>
>> https://gist.github.com/spotz/14e19b8a3e0b68b7db2f96bff7fdf4a8
>>
>>
>> Requirements repo change a few weeks ago
>>
>> http://git.openstack.org/cgit/openstack/requirements/commit/?id=
>> cb6c00c01f82537a38bd0c5a560183735cefe2f9
>>
>>
>> Changed local Flask version for curry-libnetwork and set local.conf to
>> reclone=no and then installed and tried to use the CLI.
>>
>> https://gist.github.com/spotz/b53d729fc72d24b4454ee55519e72c07
>>
>>
>> It makes sense that Flask would cause an issue on the UI installation
>> even though it's enabled even for a non-enabled build according to the
>> quickstart doc. I don't mind doing a patch to fix kuryr-libnetwork to bring
>> it up to the current requirements. I don't however know where to start
>> troubleshooting the 401 issue. On a different machine I have decstack with
>> Zun but no zun-ui and the CLI responds correctly.
>>
>>
>> Thanks,
>>
>> Amy (spotz)
>>
>>
>> On Thu, Jul 12, 2018 at 11:21 PM, Hongbin Lu 
>> wrote:
>>
>>> Hi Amy,
>>>
>>> I am also in doubts about the Flask version issue. Perhaps you can
>>> provide more details about this issue? Do you see an

Re: [openstack-dev] [openstack-community] Give cinder-backup more CPU resources

[Amy Marrich]

Hey,

Forwarding to the Dev list as you may get a better response from there.

Thanks,

Amy (spotz)

On Thu, Jul 5, 2018 at 11:30 PM, Keynes Lee/WHQ/Wistron <
keynes_...@wistron.com> wrote:

> Hi
>
>
>
> When making “cinder backup-create”
>
> We found the process “cinder-backup” use 100% util of 1 CPU core on an
> OpenStack Controller node.
>
> It not just causes a bad backup performance, also make the
> openstack-cinder-backup unstable.
>
> Especially when we make several backup at the same time.
>
>
>
> The Controller Node has 40 CPU cores.
>
> Can we assign more CPU resources to cinder-backup ?
>
>
>
>
>
>
>
>
>
>
>
>
>
> [image: cid:image007.jpg@01D1747D.DB260110]
>
> *Keynes  Lee**李* *俊* *賢*
>
> Direct:
>
> +886-2-6612-1025
>
> Mobile:
>
> +886-9-1882-3787
>
> Fax:
>
> +886-2-6612-1991
>
>
>
> E-Mail:
>
> keynes_...@wistron.com
>
>
>
>
>
>
> *---*
>
> *This email contains confidential or legally privileged information and is
> for the sole use of its intended recipient. *
>
> *Any unauthorized review, use, copying or distribution of this email or
> the content of this email is strictly prohibited.*
>
> *If you are not the intended recipient, you may reply to the sender and
> should delete this e-mail immediately.*
>
>
> *---*
>
> ___
> Community mailing list
> commun...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
>
>
__
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-community] DevStack Installation issue

[Amy Marrich]

Abhijit,

I'm forwarding your issue to the OpenStack-dev list so that the right
people might see your issue and respond.

Thanks,

Amy (spotz)

-- Forwarded message --
From: Abhijit Dutta 
Date: Wed, Jun 27, 2018 at 5:23 AM
Subject: [openstack-community] DevStack Installation issue
To: "commun...@lists.openstack.org" 


Hi,


I am trying to install DevStack for the first time in a baremetal with
Fedora 28 installed.  While executing the stack.sh I am getting the
following error:


No match for argument: Django
Error: Unable to find a match

Can anybody in the community help me out with this problem.


PS:

[stack@localhost devstack]$ uname -a
Linux localhost.localdomain 4.16.3-301.fc28.x86_64 #1 SMP Mon Apr 23
21:59:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


~Thanks

Abhijit

___
Community mailing list
commun...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/community
__
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] Non-OpenStack projects under the Foundation umbrella

[Amy Marrich]

Nice write up, thanks Zane!

Amy (spotz)

On Wed, Jun 20, 2018 at 10:33 AM, Zane Bitter  wrote:

> You may or may not be aware that the Foundation is in the process of
> expanding its mission to support projects other than OpenStack. It's a
> confusing topic and it's hard to find information about it all in one
> place, so I collected everything I was able to piece together during the
> Summit into a blog post that I hope will help to clarify the current status:
>
> https://www.zerobanana.com/archive/2018/06/14#osf-expansion
>
> cheers,
> Zane.
>
> __
> 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

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

[Amy Marrich]

Zane,

Not sure it is to be honest.:)

Amy (spotz)

On Mon, Jun 4, 2018 at 7:29 AM, Zane Bitter  wrote:

> On 04/06/18 10:19, Amy Marrich wrote:
>
>> Zane,
>>
>> I'll read in more detail, but do we want to add rollcall-vote?
>>
>
> Is it used anywhere other than in the governance repo? We certainly could
> add it, but it didn't seem like a top priority.
>
> - ZB
>
> Amy (spotz)
>>
>>
>> On Mon, Jun 4, 2018 at 7:13 AM, Zane Bitter > zbit...@redhat.com>> wrote:
>>
>> On 31/05/18 14:35, Julia Kreger wrote:
>>
>> Back to the topic of nitpicking!
>>
>> I virtually sat down with Doug today and we hammered out the
>> positive
>> aspects that we feel like are the things that we as a community
>> want
>> to see as part of reviews coming out of this effort. The
>> principles
>> change[1] in governance has been updated as a result.
>>
>> I think we are at a point where we have to state high level
>> principles, and then also update guidelines or other context
>> providing
>> documentation to re-enforce some of items covered in this
>> discussion... not just to educate new contributors, but to serve
>> as a
>> checkpoint for existing reviewers when making the decision as to
>> how
>> to vote change set. The question then becomes where would such
>> guidelines or documentation best fit?
>>
>>
>> I think the contributor guide is the logical place for it. Kendall
>> pointed out this existing section:
>>
>> https://docs.openstack.org/contributors/code-and-documentati
>> on/using-gerrit.html#reviewing-changes
>> <https://docs.openstack.org/contributors/code-and-documentat
>> ion/using-gerrit.html#reviewing-changes>
>>
>> It could go in there, or perhaps we separate out the parts about
>> when to use which review scores into a separate page from the
>> mechanics of how to use Gerrit.
>>
>> Should we explicitly detail the
>> cause/effect that occurs? Should we convey contributor
>> perceptions, or
>> maybe even just link to this thread as there has been a massive
>> amount
>> of feedback raising valid cases, points, and frustrations.
>>
>> Personally, I'd lean towards a blended approach, but the question
>> of
>> where is one I'm unsure of. Thoughts?
>>
>>
>> Let's crowdsource a set of heuristics that reviewers and
>> contributors should keep in mind when they're reviewing or having
>> their changes reviewed. I made a start on collecting ideas from this
>> and past threads, as well as my own reviewing experience, into a
>> document that I've presumptuously titled "How to Review Changes the
>> OpenStack Way" (but might be more accurately called "The Frank
>> Sinatra Guide to Code Review" at the moment):
>>
>> https://etherpad.openstack.org/p/review-the-openstack-way
>> <https://etherpad.openstack.org/p/review-the-openstack-way>
>>
>> It's in an etherpad to make it easier for everyone to add their
>> suggestions and comments (folks in #openstack-tc have made some
>> tweaks already). After a suitable interval has passed to collect
>> feedback, I'll turn this into a contributor guide change.
>>
>> Have at it!
>>
>> cheers,
>> Zane.
>>
>>
>> -Julia
>>
>> [1]: https://review.openstack.org/#/c/570940/
>> <https://review.openstack.org/#/c/570940/>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> <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: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

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

[Amy Marrich]

Zane,

I'll read in more detail, but do we want to add rollcall-vote?

Amy (spotz)

On Mon, Jun 4, 2018 at 7:13 AM, Zane Bitter  wrote:

> On 31/05/18 14:35, Julia Kreger wrote:
>
>> Back to the topic of nitpicking!
>>
>> I virtually sat down with Doug today and we hammered out the positive
>> aspects that we feel like are the things that we as a community want
>> to see as part of reviews coming out of this effort. The principles
>> change[1] in governance has been updated as a result.
>>
>> I think we are at a point where we have to state high level
>> principles, and then also update guidelines or other context providing
>> documentation to re-enforce some of items covered in this
>> discussion... not just to educate new contributors, but to serve as a
>> checkpoint for existing reviewers when making the decision as to how
>> to vote change set. The question then becomes where would such
>> guidelines or documentation best fit?
>>
>
> I think the contributor guide is the logical place for it. Kendall pointed
> out this existing section:
>
> https://docs.openstack.org/contributors/code-and-documentati
> on/using-gerrit.html#reviewing-changes
>
> It could go in there, or perhaps we separate out the parts about when to
> use which review scores into a separate page from the mechanics of how to
> use Gerrit.
>
> Should we explicitly detail the
>> cause/effect that occurs? Should we convey contributor perceptions, or
>> maybe even just link to this thread as there has been a massive amount
>> of feedback raising valid cases, points, and frustrations.
>>
>> Personally, I'd lean towards a blended approach, but the question of
>> where is one I'm unsure of. Thoughts?
>>
>
> Let's crowdsource a set of heuristics that reviewers and contributors
> should keep in mind when they're reviewing or having their changes
> reviewed. I made a start on collecting ideas from this and past threads, as
> well as my own reviewing experience, into a document that I've
> presumptuously titled "How to Review Changes the OpenStack Way" (but might
> be more accurately called "The Frank Sinatra Guide to Code Review" at the
> moment):
>
> https://etherpad.openstack.org/p/review-the-openstack-way
>
> It's in an etherpad to make it easier for everyone to add their
> suggestions and comments (folks in #openstack-tc have made some tweaks
> already). After a suitable interval has passed to collect feedback, I'll
> turn this into a contributor guide change.
>
> Have at it!
>
> cheers,
> Zane.
>
>
> -Julia
>>
>> [1]: https://review.openstack.org/#/c/570940/
>>
>
> __
> 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

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

[Amy Marrich]

Coming from Ops, yes things should always be deployable, backward
compatible and shouldn't break, but at the same time we're talking about a
master branch which is always in flux and not an actual release. I think
that statement you provided Dims should apply to releases or tags and not
the master branch as a whole. And to be honest unless someone desperately
needed something just committed into master, I doubt most folks are using
master in dev let alone production, at least that's my hope.

We can't move forward as a community if we don't welcome new members to it,
which is the heart of this proposal.

Amy (spotz)

On Wed, May 30, 2018 at 2:50 PM, Davanum Srinivas  wrote:

> Please see below:
>
> On Wed, May 30, 2018 at 2:37 PM, Chris Dent 
> wrote:
> > On Wed, 30 May 2018, Julia Kreger wrote:
> >
> >> I don't feel like anyone is proposing to end the use of -1's, but that
> >> we should generally be encouraging, accepting, and trusting.
> >
> >
> > Being encouraging, accepting, and trusting is the outcome I'd like
> > to see from this process. Being less nitpicking is a behavior or
> > process change. Adjusting attitudes (in some environments lightly,
> > in others more) so that we (where "we" is regulars in the projects,
> > experienced reviewers, and cores) perceive patches as something to
> > be grateful for and shepherded instead of an intrusion or obligation
> > would be a significant and beneficial culture change.
> >
> > A perhaps more straightforward way to put it is: When someone (even
> > one of "us") submits a patch they are doing us (the same "we" as
> > above) a favor and we owe them not just a cordial and supportive
> > response, but one with some continuity.
> >
> > Like many, I'm guilty of letting a false or inflated sense of urgency
> > get the better of me and being an ass in some reviews. Sorry about
> > that.
> >
> > A cultural shift in this area will improve things for all of us.
> > Nitpicking is symptomatic of an attitude, one we can change, not the
> > disease itself.
> >
> >> We also need to be mindful
> >> of context as well, and in the grand scheme not try for something
> >> perfect as many often do. This *does* mean we land something that
> >> needs to be fixed later or reverted later, but neither are things we
> >> should fear. We can't let that fear control us.
>
> Let me poke at this a bit. Some of the projects do say (not in so many
> words):
>
> "master should be always deployable and fully backward compatible and
> so we cant let anything in anytime that could possibly regress anyone"
>
> Should we change that attitude too? Anyone agree? disagree?
>
> Thanks,
> Dims
>
> >
> > Yes, very much yes.
> >
> > --
> > Chris Dent   ٩◔̯◔۶   https://anticdent.org/
> > freenode: cdent tw: @anticdent
> > 
> __
> > 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
> >
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> 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

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

[Amy Marrich]

If I have a nit that doesn't affect things, I'll make a note of it and say
if you do another patch I'd really like it fixed but also give the patch a
vote. What I'll also do sometimes if I know the user or they are online
I'll offer to fix things for them, that way they can see what I've done,
I've sped things along and I haven't caused a simple change to take a long
amount of time and reviews.

I think this is a great addition!

Thanks,

Amy (spotz)

On Tue, May 29, 2018 at 6:55 AM, Julia Kreger 
wrote:

> During the Forum, the topic of review culture came up in session after
> session. During these discussions, the subject of our use of nitpicks
> were often raised as a point of contention and frustration, especially
> by community members that have left the community and that were
> attempting to re-engage the community. Contributors raised the point
> of review feedback requiring for extremely precise English, or
> compliance to a particular core reviewer's style preferences, which
> may not be the same as another core reviewer.
>
> These things are not just frustrating, but also very inhibiting for
> part time contributors such as students who may also be time limited.
> Or an operator who noticed something that was clearly a bug and that
> put forth a very minor fix and doesn't have the time to revise it over
> and over.
>
> While nitpicks do help guide and teach, the consensus seemed to be
> that we do need to shift the culture a little bit. As such, I've
> proposed a change to our principles[1] in governance that attempts to
> capture the essence and spirit of the nitpicking topic as a first
> step.
>
> -Julia
> -
> [1]: https://review.openstack.org/570940
>
> __
> 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

Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling

[Amy Marrich]

+1, leading meetings is a great way to get folks involved in the Community
and gives them some 'ownership' within the project.

Amy (spotz)

On Wed, May 2, 2018 at 10:14 AM, Jean-Philippe Evrard <
jean-phili...@evrard.me> wrote:

> Hello everyone,
>
> Now that we are all part-time, I'd like to toy with a new idea,
> proposed in the past by Jesse, to rotate the duties with people who
> are involved in OSA, or want to get involved more (it's not restricted
> to core developers!).
>
> One of the first duties to be handled this way could be the weekly meeting.
>
> Handling the meeting is not that hard, it just takes time to prepare,
> and to facilitate.
>
> I think everyone should step into this, not only core developers, but
> core developers are now expected to run the meetings when their turn
> comes.
>
>
> What are the actions to take:
> - Prepare the triage. Generate the list of the bugs for the week.
> - Ping people with the triage links around 1h before the weekly
> meeting. It would give them time to get prepared for meeting,
> eventually updating the agenda, and read the current bugs
> - Ping people at the beginning of the meeting
> - Chair the meeting: The structure of the meeting is now always
> the same, a recap of the week, and handling the bug triage.
> - After the meeting we would ask who is volunteer to run next
> meeting, and if none, a meeting char will be selected amongst core
> contributors at random.
>
> Thank you for your understanding.
>
> Jean-Philippe Evrard (evrardjp)
>
> __
> 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

Re: [openstack-dev] The Forum Schedule is now live

[Amy Marrich]

Emilien,

I believe that the Project Updates are separate from the Forum? I know I
saw some in the schedule before the Forum submittals were even closed.
Maybe contact speaker support or Jimmy will answer here.

Thanks,

Amy (spotz)

On Mon, Apr 30, 2018 at 10:33 AM, Emilien Macchi  wrote:

>
>
> On Fri, Apr 27, 2018 at 9:04 AM, Jimmy McArthur 
> wrote:
>
>> Hello all -
>>
>> Please take a look here for the posted Forum schedule:
>> https://www.openstack.org/summit/vancouver-2018/summit-schedule#track=224
>> You should also see it update on your Summit App.
>>
>
> Why TripleO doesn't have project update?
> Maybe we could combine it with TripleO - Project Onboarding if needed but
> it would be great to have it advertised as a project update!
>
> Thanks,
> --
> Emilien Macchi
>
> __
> 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

Re: [openstack-dev] [openstack-ansible] Proposing Mohammed Naser as core reviewer

[Amy Marrich]

+2 from me!

Amy (spotz)

On Tue, Apr 24, 2018 at 10:05 AM, Jean-Philippe Evrard <
jean-phili...@evrard.me> wrote:

> Hi everyone,
>
> I’d like to propose Mohammed Naser [1] as a core reviewer for
> OpenStack-Ansible.
>
> He has been working actively on fixing the telemetry stack, and is now
> willing to step up to improve the CentOS platform which is now in a
> very degraded state.
>
> I feel that it’s important that he’s able to safeguard the existing
> and future work about CentOS
> and help grow the maintenance community for it.
>
> [1] http://stackalytics.com/?module=openstackansible-group;
> user_id=mnaser=rocky=person-day
>
> Best regards,
>
> Jean-Philippe Evrard
> IRC: evrardjp
>
> __
> 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] OpenStack Summit Vancouver Speed Mentoring Workshop—Call for Mentors

[Amy Marrich]

*Calling All OpenStack Mentors!We’re quickly nearing the Vancouver Summit,
and gearing up for another successful Speed Mentoring workshop! This
workshop, now a mainstay at OpenStack Summits, is designed to provide
guidance to newcomers so that they can dive in and actively engage,
participate and contribute to our community. And we couldn’t do this
without you—our fearless mentors!Speed Mentoring Workshop & LunchMonday,
May 21, 12:15 – 1:30 pmVancouver Convention Centre West, Level 2, Room
215-216https://bit.ly/2HCGjMo Who should sign
up?Are you excited about OpenStack and interested in sharing your career,
community or technical advice and expertise with others? Contributed (code
and non-code contributions welcome) to the OpenStack community for at least
one year? Any mentor of any gender with a technical or non-technical
background is encouraged to join us. Share your insights, inspire those new
to our community, grab lunch, and pick up special mentor gifts!How does it
work?Simply sign up here
,
and fill in a short survey about your areas of interests and expertise.
Your answers will be used to produce fun, customized baseball cards that
you can use to introduce yourself to the mentees. You will be provided with
mentees’ areas of interest and questions in advance to help you prepare,
and we’ll meet as a team ahead of time to go over logistics and answer any
questions you may have. On the day of the event, plan to arrive ~ 15
minutes before the session. During the session, you will meet with small
groups of mentees in 15-minute intervals and answer their questions about
how to grow in the community.It’s a fast-paced event and a great way to
meet new people, introduce them to the Summit and welcome them to the
OpenStack community.Be sure to sign up today
!*

*Thanks,*

*Amy (spotz)*
__
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] [k8s] OpenStack and Containers White Paper

[Amy Marrich]

Chris,

Can't help with content but can volunteer as an editor.

Amy (spotz)

On Mon, Apr 2, 2018 at 3:59 PM, Chris Hoge  wrote:

> Hi everyone,
>
> In advance of the Vancouver Summit, I'm leading an effort to publish a
> community produced white-paper on OpenStack and container integrations.
> This has come out of a need to develop materials, both short and long
> form, to help explain how OpenStack interacts with container
> technologies across the entire stack, from infrastructure to
> application. The rough outline of the white-paper proposes an entire
> technology stack and discuss deployment and usage strategies at every
> level. The white-paper will focus on existing technologies, and how they
> are being used in production today across our community. Beginning at
> the hardware layer, we have the following outline (which may be inverted
> for clarity):
>
> * OpenStack Ironic for managing bare metal deployments.
> * Container-based deployment tools for installing and managing OpenStack
>* Kolla containers and Kolla-Ansible
>* Loci containers and OpenStack Helm
> * OpenStack-hosted APIs for managing container application
>   infrastructure.
>* Magnum
>* Zun
> * Community-driven integration of Kubernetes and OpenStack with K8s
>   Cloud Provider OpenStack
> * Projects that can stand alone in integrations with Kubernetes and
>   other cloud technology
>* Cinder
>* Neutron with Kuryr and Calico integrations
>* Keystone authentication and authorization
>
> I'm looking for volunteers to help produce the content for these sections
> (and any others we may uncover to be useful) for presenting a complete
> picture of OpenStack and container integrations. If you're involved with
> one of these projects, or are using any of these tools in
> production, it would be fantastic to get your input in producing the
> appropriate section. We especially want real-world deployments to use as
> small case studies to inform the work.
>
> During the process of creating the white-paper, we will be working with a
> technical writer and the Foundation design team to produce a document that
> is consistent in voice, has accurate and informative graphics that
> can be used to illustrate the major points and themes of the white-paper,
> and that can be used as stand-alone media for conferences and
> presentations.
>
> Over the next week, I'll be reaching out to individuals and inviting them
> to collaborate. This is also a general invitation to collaborate, and if
> you'd like to help out with a section please reach out to me here, on the
> K8s #sig-openstack Slack channel, or at my work e-mail,
> ch...@openstack.org.
> Starting next week, we'll work out a schedule for producing and delivering
> the white-paper by the Vancouver Summit. We are very short on time, so
> we will have to be focused to quickly produce high-quality content.
>
> Thanks in advance to everyone who participates in writing this
> document. I'm looking forward to working with you in the coming weeks to
> publish this important resource for clearly describing the multitude of
> interactions between these complementary technologies.
>
> -Chris Hoge
> K8s-SIG-OpenStack/OpenStack-SIG-K8s Co-Lead
>
>
> __
> 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

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

[Amy Marrich]

And just an aside, the All-in-ones are great tools for new operators to be
able to get in and learn how to use OpenStack, even if the underlying
configuration isn't a multi-node installation.

Amy (spotz)

On Fri, Mar 30, 2018 at 10:53 AM, Wesley Hayutin 
wrote:

>
>
> On Fri, 30 Mar 2018 at 08:45 Paul Grist  wrote:
>
>> On Thu, Mar 29, 2018 at 5:32 PM, Emilien Macchi 
>> wrote:
>>
>>> Greeting folks,
>>>
>>> During the last PTG we spent time discussing some ideas around an
>>> All-In-One installer, using 100% of the TripleO bits to deploy a single
>>> node OpenStack very similar with what we have today with the containerized
>>> undercloud and what we also have with other tools like Packstack or
>>> Devstack.
>>>
>>> https://etherpad.openstack.org/p/tripleo-rocky-all-in-one
>>>
>>> One of the problems that we're trying to solve here is to give a simple
>>> tool for developers so they can both easily and quickly deploy an OpenStack
>>> for their needs.
>>>
>>> Big +1 on the concept,  thanks to all those putting effort into this.
>>
>>
>>> "As a developer, I need to deploy OpenStack in a VM on my laptop,
>>> quickly and without complexity, reproducing the same exact same tooling as
>>> TripleO is using."
>>> "As a Neutron developer, I need to develop a feature in Neutron and test
>>> it with TripleO in my local env."
>>> "As a TripleO dev, I need to implement a new service and test its
>>> deployment in my local env."
>>> "As a developer, I need to reproduce a bug in TripleO CI that blocks the
>>> production chain, quickly and simply."
>>>
>>>
>> Would this also be an opportunity for CI to enable lighter weight sanity
>> and preliminary tests?
>> "As a project, I want to implement a TripleO CI gate to detect
>> regressions early, but have resource and test execution time constraints"
>>
>>
> Paul,
> You are 100% correct sir.  That is the opportunity and intention we have
> here.  Moving forward I see a single node installer that is comprable to
> devstack/packstack as a requirement for the project as we continue to
> improve the deployment to enable other projects to test/ci with TripleO in
> their check jobs.
>
> Thanks for responding and your support!
>
>
>>
>>
>>> Probably more use cases, but to me that's what came into my mind now.
>>>
>>> Dan kicked-off a doc patch a month ago: https://review.openstack.org/#
>>> /c/547038/
>>> And I just went ahead and proposed a blueprint:
>>> https://blueprints.launchpad.net/tripleo/+spec/all-in-one
>>> So hopefully we can start prototyping something during Rocky.
>>>
>>> Before talking about the actual implementation, I would like to gather
>>> feedback from people interested by the use-cases. If you recognize yourself
>>> in these use-cases and you're not using TripleO today to test your things
>>> because it's too complex to deploy, we want to hear from you.
>>> I want to see feedback (positive or negative) about this idea. We need
>>> to gather ideas, use cases, needs, before we go design a prototype in Rocky.
>>>
>>> Thanks everyone who'll be involved,
>>> --
>>> Emilien Macchi
>>>
>>> 
>>> __
>>> 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 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

Re: [openstack-dev] Adding "not docs" banner to specs website?

[Amy Marrich]

I think it's a good idea especially as some times a spec is never completed
or not in the same release.

Thanks,

Amy(spotz)

On Mon, Mar 19, 2018 at 9:57 AM, Jim Rollenhagen 
wrote:

> Ironic (and surely other projects) have had to point out many times that
> specs are a point in time design discussion, and not completed
> documentation. It's obviously too much work to go back and update specs
> constantly.
>
> What do folks think about a banner at the top of the specs website (or
> each individual spec) that points this out? I'm happy to do the work if we
> agree it's a good thing to do. My suggested wording:
>
> "NOTE: specifications are a point-in-time design reference, not up-to-date
> feature documentation."
>
> // jim
>
> __
> 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

Re: [openstack-dev] [Openstack-sigs] [First Contact][SIG] [PTG] Summary of Discussions

[Amy Marrich]

Just one comment on this section before I forget again:
#IRC Channels#
We want to get rid of #openstack-101 and begin using #openstack-dev
instead. The 101 channel isn't watched closely enough anymore and it makes
more sense to move onboarding activities (like in OpenStack Upstream
Institute) to a channel where there are people that can answer questions
rather than asking those to move to a new channel. For those concerned
about noise, OUI is run the weekend before the summit when most people are
traveling to the Summit anyway.

I would recommend sending folks to #openstack vs #openstack-dev by default.

Amy (spotz)

On Mon, Mar 5, 2018 at 2:00 PM, Kendall Nelson 
wrote:

> Hello Everyone :)
>
> It was wonderful to see and talk with so many of you last week! For those
> that couldn't attend our whole day of chats or those that couldn't attend
> at all, I thought I would put forth a summary of our discussions which were
> mostly noted in the etherpad[1]
>
> #Contributor Guide#
>
> - Walkthrough: We walked through every section of what exists and came up
> with a variety of improvements on what is there. Most of these items have
> been added to our StoryBoard project[2]. This came up again Tuesday in docs
> sessions and I have added those items to StoryBoard as well.
>
> - Google Analytics: It was discussed we should do something about getting
> the contributor portal[3] to appear higher in Google searches about
> onboarding. Not sure what all this entails. NEEDS AN OWNER IF ANYONE WANTS
> TO VOLUNTEER.
>
> #Mission Statement#
>
> We updated our mission statement[4]! It now states:
>
> To provide a place for new contributors to come for information and
> advice. This group will also analyze and document successful contribution
> models while seeking out and providing information to new members of the
> community.
>
> #Weekly Meeting#
>
> We discussed beginning a weekly meeting- optimized for APAC/Europe and
> settled on 800 UTC in #openstack-meeting on Wednesdays. Proposed here[5].
> For now I added a section to our wiki for agenda organization[6]. The two
> main items we want to cover on a weekly basis are new contributor patches
> in gerrit and if anything has come up on ask.openstack.org about
> contributors so those will be standing agenda items.
>
> #Forum Session#
>
> We discussed proposing some forum sessions in order to get more
> involvement from operators. Currently, our activities focus on development
> activities and we would like to diversify. When this SIG was first proposed
> we wanted to have two chairs- one to represent developers and one to
> represent operators. We will propose a session or two when the call for
> forum proposals go out (should be today).
>
> #IRC Channels#
> We want to get rid of #openstack-101 and begin using #openstack-dev
> instead. The 101 channel isn't watched closely enough anymore and it makes
> more sense to move onboarding activities (like in OpenStack Upstream
> Institute) to a channel where there are people that can answer questions
> rather than asking those to move to a new channel. For those concerned
> about noise, OUI is run the weekend before the summit when most people are
> traveling to the Summit anyway.
>
> #Ongoing Onboarding Efforts#
>
> - GSOC: Unfortunately we didn't get accepted this year. We will try again
> next year.
>
> - Outreachy: Applications for the next round of interns are due March
> 22nd, 2018 [7]. Decisions will be made by April and then internships run
> May to August.
>
> - WoO Mentoring: The format of mentoring is changing from 1x1 to cohorts
> focused on a single goal. If you are interested in helping out, please
> contact me! I NEED HELP :)
>
> - Contributor guide: Please see the above section.
>
> - OpenStack Upstream Institute: It will be run, as usual, the weekend
> before the Summit in Vancouver. Depending on how much progress is made on
> the contributor guide, we will make use of it as opposed to slides like
> previous renditions. There have also been a number of OpenStack Days
> requesting we run it there as well. More details of those to come.
>
> #Project Liaisons#
>
> The list is filling out nicely, but we still need more coverage. If you
> know someone from a project not listed that might be willing to help,
> please reach out to them and get them added to our list [8].
>
> I thiink that is just about everything. Hopefully I at least covered
> everything important :)
>
> Thanks Everyone!
>
> - Kendall Nelson (diablo_rojo)
>
> [1] PTG Etherpad https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG
> [2] StoryBoard Tracker https://storyboard.openstack.org/#!/project/913
> [3] Contributor Portal https://www.openstack.org/community/
> [4] Mission Statement Update https://review.openstack.org/#/c/548054/
> [5] Meeting Slot Proposal https://review.openstack.org/#/c/549849/
> [6] Meeting Agenda https://wiki.openstack.org/wiki/First_Contact_SIG#
> Meeting_Agenda
> [7] Outreachy 

Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Amy Marrich]

I think if we're going to have that go to the development contributors
section (which makes sense) maybe we should also have ways of getting to
the deployment and admin docs as well?

Amy (spotz)

On Tue, Mar 13, 2018 at 2:55 PM, Jay S Bryant  wrote:

>
>
> On 3/13/2018 1:38 PM, Petr Kovar wrote:
>
>> On Thu, 8 Mar 2018 12:54:06 -0600
>> Jay S Bryant  wrote:
>>
>> Good overview.  Thank you!
>>>
>>> One additional goal I want to mention on the list, for awareness, is the
>>> fact that we would like to eventually get some consistency to the pages
>>> that the 'Contributor Guide' lands on for each of the projects.  Needs
>>> to be a page that is friendly to new contributors, makes it easy to
>>> learn about the project and is not overwhelming.
>>>
>>> What exactly that looks like isn't defined yet but I have talked to
>>> Manila about this.  They were interested in working together on this.
>>> Cinder and Manila will work together to get something consistent put
>>> together and then we can work on spreading that to other projects once
>>> we have agreement from the SIG that the approach is agreeable.
>>>
>> This is a good cross-project goal, I think. We discussed a similar
>> approach
>> in the docs room wrt providing templates to project teams that they can
>> use to design their landing pages for admin, user, configuration docs;
>> that
>> would also include the main index page for project docs.
>>
>> As for the project-specific contributor guides,
>> https://docs.openstack.org/doc-contrib-guide/project-guides.html
>> specifies
>> that any contributor content should go to doc/source/contributor/. This
>> will
>> allow us to use templates to generate lists of links, similarly to what
>> we do for other content areas.
>>
>> Cheers,
>> pk
>>
>>
>> 
>> __
>> 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
>>
> Petr,
>
> Good point.  I was trying to think of how to make a better landing page
> for new contributors and you may have hit on the answer.  RIght now when
> you click through from  here: https://www.openstack.org/community  You
> land at the top level Cinder documentation page which is incredibly
> overwhelming for a new person:  https://docs.openstack.org/cinder/latest/
>
> If the new contributor page instead lands here:
> https://docs.openstack.org/cinder/latest/contributor/index.html It would
> give me a page to craft for new users looking for information to get
> started.
>
> Thoughts on this approach?
>
> Kendall and Mike ... Does the above approach make sense?
>
> Jay
>
>
>
> __
> 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

Re: [openstack-dev] Going but not gone

[Amy Marrich]

I've already said this but don't be a stranger. You've been a great
influence and mentor to a lot of people, me included.

You'll do great in the new gig and you'll be a real asset to your new team!

Amy (spotz)

On Fri, Mar 9, 2018 at 7:54 AM, Major Hayden  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello there,
>
> I'm leaving my current role for a new opportunity and, unfortunately, this
> means I won't be as involved in OpenStack as much in the near future. I've
> spoken with our fearless OpenStack-Ansible PTL and I let JP know that I
> will resign from the core reviewers group immediately if I feel that I
> cannot meet the obligations of the role.
>
> With that said, the OpenStack community has been truly amazing. My first
> humble contribution[0] was a fix for broken glance tests back in 2011. I've
> done a little more since then and I'm proud to be a tiny part of what
> OpenStack has become today.
>
> I'd like to thank everyone who has reviewed one of my patches, fixed one
> of the bugs I created with my patches, and fixed the gate jobs that I broke
> with my patches. Thanks to everyone who has attended one of my talks at the
> Summits and thanks to everyone who has put up with my oddball suggestions
> at Design Summits, Forums, and PTGs. I have learned an *incredible* amount
> about OpenStack, Python, Linux, open source, communities, and how to be a
> better human.
>
> Thanks to the leaders of the OpenStack Foundation as well for their
> continued support. They have been excellent listeners and they took lots of
> time to consider my suggestions for improvements.
>
> I love you all and working in this community has been one of the best
> experiences in my professional career. :)
>
> [0] https://review.openstack.org/#/c/2652/
>
> - --
> Major Hayden
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEEG/mSZJWWADNpjCUrc3BR4MEBH7EFAlqikg0ACgkQc3BR4MEB
> H7HN9Q/+PKC0TpfosAcZwotuVoSncoJc5D3RDL6RgO09Vm1xbI84BWkv6b6tJz4/
> SvBmiqR7LtXUQDN1yiDg1g8Bq8gNKJO7E0hW7WqRE5rJmXAX2Gpx80pQ04mO0LBv
> 21OaeJSGElT5MdQYu/wz6oP8iNwjAqUaU7b/BZFXcGgpA+S9qDMaQCMK/EXnrodd
> hsDbBxtOridNk9j7SefgwIGZKOr4gdPCxvqnTfj0/X5Cjb+OfMU4rU6dRSIoVaiz
> JVrwZr7DVVyvJmF5JFtpsOJGS9SF7YkOJKia3BsmCnJWeNm9+r1n2XjSXHY240tQ
> gjNfqgvWbyaLddm+8ZMC77zsZu3Kaf4M2ta9F95K0/PlsShoZYBCDso23aDRsjps
> czR3RjT51bdGdEDNhpJkimHQLLFqrvO6NRfg6Azf+Wii3/POrtez60Nx49SQgBul
> PTB/i+mHl44Yn9R2VpWgqKM+WMixRxD75SRyOlDXrU0setUv/91Hz+x32cqeeiX0
> C8mWOPh9POOdQPLeIalR2E4F9//CFv4nWZNSjpwIEEeXLd/Mlkyf2ue7ye+1s/5U
> JYo2wygRLEiLimacaoEyTRguR5/QsKtMieqKKfIYQglQDQkulWhhxOeqJmkpP10p
> xQp11b/GIwrXA4wVi5KA3hQEB/ST/2ENvTO76e/oGW41RK9S0gw=
> =5+cM
> -END PGP SIGNATURE-
>
> __
> 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

Re: [openstack-dev] [openstack-ansible] Meetings change (PTG discussion follow-up)

[Amy Marrich]

JP,

When the Community meeting was moved to once a month there was a lot of
resulting miscommunication as a result. If a weekly review is going to be
sent to the mailing list with channel discussions is going to be sent out,
I think that's a good alternative but the conversations still need to take
place and as many people involved as possible. What about having office
hours?

Amy (spotz)

On Tue, Mar 6, 2018 at 9:51 AM, Jean-Philippe Evrard <
jean-phili...@evrard.me> wrote:

> Hello,
>
> During the PTG, we've discussed about changing our meetings.
> I'd like to have a written evidence in our mailing lists, showing what
> we discussed, and what we proposed to change. I propose we validate
> those changes if they get no opposition in the next 7 days (deadline:
> 13 March).
>
> What we discussed was:
> - Should the meetings be rescheduled, and at what time;
> - Should the meetings be happening in alternance for US/Europe
> friendly timezones;
> - What is the purpose/expected outcome of those meetings;
> - What is the reason the attendance is low.
>
> The summary is the following:
> - The expected outcome of bug triage is currently (drumroll)
> actively triaging bugs which produces better deliverables (what a
> surprise!).
> - The expected outcome of the community meeting is to discuss about
> what we actively need to work on together, but we are doing these kind
> of conversations, ad-hoc, in the channel. So if we summarize things on
> a regular basis to make sure everyone is aware of the conversations,
> we should be good.
> - The timezone friendly things won't impact the attendance positively.
> - Right now, the Europe meetings can be postponed of one hour, but
> decision should be re-discussed with daylight saving.
> - A lot of ppl have meetings at 4PM UTC right now.
>
> As such, here is the PTG proposed change:
> - Moving the bug triage meeting to 5PM UTC until next daylight saving
> change.
> - Keep the "Focus of the week" section of the bug triage, to list what
> we discussed in the week (if more conversations have to happen, they
> can happen just after the bug triage)
> - Removing the community meeting.
>
> Any opposition there? If we are all okay, I will update our procedures
> next week.
>
> Best regards,
> JP
>
> __
> 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

Re: [openstack-dev] [Women-of-openstack] Introduction

[Amy Marrich]

And if we don't answer right away we will when we can!

Amy (spotz)

On Wed, Dec 13, 2017 at 11:37 AM, Kendall Nelson 
wrote:

> Hello Again :)
>
> I know I had responded the other day, but I just wanted to check in and
> make sure the setup was going well. We would love to chat with you on IRC
> in #openstack-dev or in #openstack-women. Feel free to ping me once you get
> connected and we can chat more about getting you connected with a project.
>
> Here are those directions again if you need them[1].
>
> -Kendall (IRC: diablo_rojo)
>
> On Sat, Dec 9, 2017 at 5:15 AM courage angeh 
> wrote:
>
>> Hi guys,
>>
>> My name is Angeh Courage, computer engineering student at the University
>> of Buea currently in my forth year of studies. Was a GSoC intern at Mifos
>> Initiavie for 2016/2017 and I am good with Python, Java - Spring, web(HTML,
>> CSS, JS - React, Angular...)
>> I am very interested in cloud computing and containerization and also
>> interested contributing to openstack and I will like some help on where I
>> should get started.
>>
>> Thanks,
>> Angeh
>> ___
>> Women-of-openstack mailing list
>> women-of-openst...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack
>>
>
> ___
> Women-of-openstack mailing list
> women-of-openst...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-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] [all] Switching to longer development cycles

[Amy Marrich]

I think Sean has made some really good points with the PTG setting things
off in the start of the year and conversations carrying over to the Forums
and their importance. And having a gap at the end of the year as Jay
mentioned will give time for those still about to do finishing work if
needed and if it's planned for in the individual projects they can have an
earlier 'end' to allow for members not being around.

The one year release would help to get 'new' users to adopt a more recent
release, even if it's the one from the year previously as there is the
'confidence' that it's been around for a bit and been used by others in
production. And if projects want to do incrementals they can, if I've read
the thread correctly. Also those that want the latest will just use master
anyways as some do currently.

With the move to a yearly cycle I agree with the 1 year cycle for PTLs,
though if needed perhaps a way to have a co-PTL or a LT could be
implemented to help with the longer duties?

My 2 cents from the peanut gallery:)

Amy (spotz)

On Wed, Dec 13, 2017 at 11:29 AM, Sean McGinnis 
wrote:

> On Wed, Dec 13, 2017 at 05:16:35PM +, Chris Jones wrote:
> > Hey
> >
> > On 13 December 2017 at 17:12, Jimmy McArthur 
> wrote:
> >
> > > Thierry Carrez wrote:
> > >
> > >> - It doesn't mean that teams can only meet in-person once a year.
> > >> Summits would still provide a venue for team members to have an
> > >> in-person meeting. I also expect a revival of the team-organized
> > >> midcycles to replace the second PTG for teams that need or want to
> meet
> > >> more often.
> > >>
> > > The PTG seems to allow greater coordination between groups. I worry
> that
> > > going back to an optional mid-cycle would reduce this
> cross-collaboration,
> > > while also reducing project face-to-face time.
> >
> >
> > I can't speak for the Foundation, but I would think it would be good to
> > have an official PTG in the middle of the cycle (perhaps neatly aligned
> > with some kind of milestone/event) that lets people discuss plans for
> > finishing off the release, and early work they want to get started on for
> > the subsequent release). The problem with team-organised midcycles (as
> I'm
> > sure everyone remembers), is that there's little/no opportunity for
> > cross-project work.
> >
> > --
> > Cheers,
> >
> > Chris
>
> This was one of my concerns initially too. We may have to see how things
> go and
> course correct once we have a little more data to go on. But the thought
> (or at
> least the hope) was that we could get by with using the one PTG early in
> the
> cycle to get alignment, then though IRC, the mailing list, and the Forums
> (keep
> in mind there will be two Forums within the cycle) we would be able to keep
> things going and discuss any cross project concerns.
>
> This may actually get more emphasis on developers attending the Forum. I
> think
> that is one part of our PTG/Design Summit split that has not fully settled
> the
> way we had hoped. The Forum is still encouraged for developers to attend.
> But I
> think the reality has been many companies now just see the Summit as a
> marketing event and see no reason to send any developers.
>
> I can say from the last couple Forum experiences, a lot of really good
> discussions have happened there. It's really been unfortunate that there
> were a
> lot of key people missing from some of those discussions though.
> Personally, my
> hope with making this change would mean that the likelihood of devs being
> able
> to justify going to the Forum increases.
>
> Sean
>
> __
> 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

Re: [openstack-dev] [First Contact] [OUI] Call for Project Liaisons

[Amy Marrich]

Pretty sure he said both!:)

Amy (spotz)

On Mon, Dec 11, 2017 at 4:33 PM, Kendall Nelson 
wrote:

> Thank you Matt!
>
> To clarify, you want to be Project Liaison for sSwift? Or a member of the
> SIG? Or both? :)
>
> -Kendall (diablo_rojo)
>
>
> On Mon, Dec 11, 2017 at 2:18 PM Matthew Oliver  wrote:
>
>> I'll put my hand up for my timezone. Especially as interest in my side of
>> the world grows I'd love to make sure there is someone available.
>>
>> Project: Swift
>> Name: Matthew Oliver
>> IRC: mattolverau
>> email: m...@oliver.net.au
>> timezone: UTC +11 (AEDT)
>>
>> Matt
>>
>> On Tue, Dec 12, 2017 at 8:25 AM, Kendall Nelson 
>> wrote:
>>
>>> Hello,
>>>
>>> As some of you may know there is a newly formed SIG focused on the
>>> initial interactions of someone new to the community called the First
>>> Contact SIG. While the team we have looking out for these first
>>> introductions is growing they can only get us so far. After we get them up
>>> to speed with the tools and community it is important that they are
>>> connected with someone who can get them up to speed on a project. While
>>> these SIG members cover a variety of projects, there are several projects
>>> that don’t have someone to help these newcomers.
>>>
>>> If you are interested in being a project liaison please reply to this
>>> thread with your name, irc nic, email, and timezone (UTC +/- x).
>>>
>>> Previously, Upstream Institute had started to collect a list of people
>>> interested in helping get new community members up to speed in the past and
>>> I think it would be good to unite these efforts. That list covers only 6
>>> projects: Cinder, Keystone, Nova, Neutron, QA, and Trove[1]. If you signed
>>> up before and are interested in this renewed effort please let me know!
>>>
>>> Even if everyone from the initial effort participates, there are still
>>> many projects missing from the list. How best to ensure the growth and
>>> success of your project than to invest in the people interested in
>>> contributing to your project?
>>>
>>> Thanks!
>>>
>>> Kendall Nelson (diablo_rojo)
>>>
>>> 
>>> __
>>> 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 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] Diversity WG

[Amy Marrich]

At the Sydney Summit, there seemed to be interest in re-activating the
Diversity WG. I am sending this email to give some background on the group
as well as to gauge interest.

A charter was proposed to the board May 2015 by Egle Sigler, Kavit Munshi,
and Imad Sousou to form the group [1]. The group was formed a short time
later with Egle Sigler and Carol Barrett as co-chairs and falling under the
oversight of the Board.

The main work of the diversity group was the diversity survey and its
results which were released prior to the Tokyo Summit in October, 2015 and
we had about 20 people show up for the Working Group session held there to
go over the results. A working group session was also held at the Austin
Summit with about 10 people in attendance. It was not long after the Austin
summit that the group membership dwindled down and activity ended.

Things that came out of the work of the Diversity WG are the Git and Gerrit
Lunch and Learn held at the last 5 summits, the Communication Tools Lunch
and Learn held in Barcelona, and the Greeters in Barcelona that were
provided by the Women of OpenStack.

I feel there is still work to do in this area even if only revisiting the
survey and gathering more data that can be evaluated and used to help grow
the community.

If you are interested in helping to revive the Diversity WG please let me
know. The group used the Foundation mailing list (
foundat...@lists.openstack.org) with the [Diversity] tag and still has the
#openstack-diversity channel on Freenode though it is not currently being
logged as Egle and myself until recently were the only 2 members.

Thanks,

Amy Marrich (spotz)

[1] https://wiki.openstack.org/wiki/Diversity/ProposedCharter
__
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] [elections] Technical Committee Election Results

[Amy Marrich]

Congrats everyone!

On Fri, Oct 20, 2017 at 6:59 PM, Kendall Nelson 
wrote:

> Hello Everyone :)
>
> Please join me in congratulating the 6 newly elected members of the
> Technical Committee (TC)!
>
> Colleen Murphy (cmurphy)
> Doug Hellmann (dhellmann)
> Emilien Macchi (emilienm)
> Jeremy Stanley (fungi)
> Julia Kreger (TheJulia)
> Paul Belanger (pabelanger)
>
> Full results: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_
> ce86063991ef8aae
>
> Election process details and results are also available here:
> https://governance.openstack.org/election/
>
> Thank you to all of the candidates, having a good group of candidates
> helps engage the community in our democratic process.
>
> Thank you to all who voted and who encouraged others to vote. We need to
> ensure your voice is heard.
>
> Thank you for another great round.
>
> -Kendall Nelson (diablo_rojo)
>
> [1] https://review.openstack.org/#/c/513881/
>
> __
> 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

Re: [openstack-dev] Thanks for all the fish

[Amy Marrich]

We'll miss you Lana but so glad you found something finally!!!

Amy (spotz)

On Tue, Oct 10, 2017 at 7:34 PM, Lana Brindley 
wrote:

> Hi everyone,
>
> As most of you know, I was caught up in the Rackspace layoffs that
> happened earlier this year, and have been looking for work (in between knee
> surgery) since then. Well, in good news for my bank account, I have now
> secured a new job with a startup based here in Brisbane. The bad news is
> that, while it's working on cool stuff and is likely to be at least
> partially open sourced at some point, there's currently no scope for me to
> continue working on OpenStack. Sadly, an OpenStack related position just
> did not come my way, despite my best efforts.
>
> So, this is goodbye for now. I'm going to unsubscribe from the OpenStack
> mailing lists, and resign my core positions, but you can still email me at
> this address if you want to. Feel free to hit me up on LinkedIn or Twitter,
> if that's your thing.
>
> I'm going to miss being part of the community we built here, and all the
> fabulous people I've met over my OpenStack years. Keep being awesome, I'll
> be cheering from the sidelines.
>
> Keep on Doc'ing :)
>
> Lana
>
> --
> Lana Brindley
> Technical Writer
> http://lanabrindley.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
>
>
__
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][election] TC non-candidacy

[Amy Marrich]

Monty,

Thank you for everything you've done on the TC and in and for the community
as well!

Glad you're not going anywhere!!!

Amy (spotz)

On Tue, Oct 10, 2017 at 6:40 PM, Monty Taylor  wrote:

> Hey everybody!
>
> I have decided not to seek reelection for the TC.
>
> I have had the honor and privilege of serving you on the TC and it's
> predecessor the PPB since the fall of 2011 (with one six month absence that
> I blame on Jay Pipes)
>
> There are a wealth of amazing people running for the TC this cycle, many
> of whom have a different genetic, cultural or geographic background than I
> do. I look forward to seeing how they shepherd our amazing community.
>
> I am not going anywhere. We're just getting Zuul v3 rolled out, there's a
> pile of work to do to merge and rationalize shade and openstacksdk and I
> managed to sign myself up to implement application credentials in Keystone.
> I still haven't even managed to convince all of you that Floating IPs are a
> bad idea...
>
> Thank you, from the bottom of my heart, for the trust you have placed in
> me. I look forward to seeing as many of you as I can in Sydney, Vancouver,
> Berlin and who knows where else.
>
> Monty
>
> __
> 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

Re: [openstack-dev] [tc][election] non-candidacy for TC

[Amy Marrich]

Steve,

Just wanted to say thanks for everything and glad you'll still be about!

Amy (spotz)

On Tue, Oct 3, 2017 at 10:05 PM, Steve Martinelli 
wrote:

> Folks, due to changes in my day job I will not be running in the next TC
> election. I still intend to contribute to OpenStack whenever possible. I
> look forward to seeing how the community continues to grow, change, and
> approach new challenges.
>
> I'd like to encourage others to step up to the challenge and run. It's an
> excellent experience to learn more about yourself, OpenStack, and
> governance of a large open source project.
>
> Thanks for your time,
> Steve
>
> __
> 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

Re: [openstack-dev] It's time...

[Amy Marrich]

Tom,

You will be missed! It's been a pleasure working with you even on opposing
tracks this last track chair round!

Thanks for everything you've done for the community!

Amy (spotz)

On Wed, Oct 4, 2017 at 9:21 AM, Tom Fifield  wrote:

> Hi all,
>
> Tom here, on a personal note.
>
> It's quite fitting that this November our summit is in Australia :)
>
> I'm hoping to see you there because after being part of 15 releases, and
> travelling the equivalent of a couple of round trips to the moon to witness
> OpenStack grow around the world, the timing is right for me to step down as
> your Community Manager.
>
> We've had an incredible journey together, culminating in the healthy
> community we have today. Across more than 160 countries, users and
> developers collaborate to make clouds better for the work that matters. The
> diversity of use is staggering, and the scale of resources being run is
> quite significant. We did that :)
>
>
> Behind the scenes, I've spent the past couple of months preparing to
> transition various tasks to other members of the Foundation staff. If you
> see a new name behind an openstack.org email address, please give them
> due attention and care - they're all great people. I'll be around through
> to year end to shepherd the process, so please ping me if you are worried
> about anything.
>
> Always remember, you are what makes OpenStack. OpenStack changes and
> thrives based on how you feel and what work you do. It's been a privilege
> to share the journey with you.
>
>
>
> So, my plan? After a decade of diligent effort in organisations
> euphemistically described as "minimally-staffed", I'm looking forward to
> taking a decent holiday. Though, if you have a challenge interesting enough
> to wrest someone from a tropical beach or a misty mountain top ... ;)
>
>
> There are a lot of you out there to whom I remain indebted. Stay in touch
> to make sure your owed drinks make it to you!
>
> +886 988 33 1200
> t...@tomfifield.net
> https://www.linkedin.com/in/tomfifield
> https://twitter.com/TomFifield
>
>
> Regards,
>
>
>
> Tom
>
> __
> 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

Re: [openstack-dev] [tc] [election] NON nomination for TC

[Amy Marrich]

Sean,

Thank you for all your hard work over the last 4 years!

Amy (spotz)

On Mon, Oct 2, 2017 at 11:03 AM, Sean Dague  wrote:

> I'd like to announce that after 4 years serving on the OpenStack
> Technical Committee, I will not be running in this fall's
> election. Over the last 4 years we've navigated some rough seas
> together, including the transition to more inclusion of projects, the
> dive off the hype curve, the emergence of real interoperability
> between clouds, and the beginnings of a new vision of OpenStack
> pairing with more technologies beyond our community.
>
> There remains a ton of good work to be done. But it's also important
> that we have a wide range of leaders to do that. Those opportunities
> only exist if we make space for new leaders to emerge. Rotational
> leadership is part of what makes OpenStack great, and is part of what
> will ensure that this community lasts far beyond any individuals
> within it.
>
> I plan to still be around in the community, and contribute where
> needed. So this is not farewell. However it will be good to see new
> faces among the folks leading the next steps in the community.
>
> I would encourage all members of the community that are interested in
> contributing to the future of OpenStack to step forward and run. It's
> important to realize what the TC is and can be. This remains a
> community driven by consensus, and the TC reflects that. Being a
> member of the TC does raise your community visibility, but it does not
> replace the need to listen, understand, communicate clearly, and
> realize that hard work comes through compromise.
>
> Good luck to all our candidates this fall, and thanks for letting me
> represent you the past 4 years.
>
> -Sean
>
> --
> Sean Dague
> http://dague.net
>
> __
> 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

Re: [openstack-dev] OpenStack-Ansible and Trove support

[Amy Marrich]

Michael,

There are release notes for each release that will go over what's new,
what's on it's way out or even gone as well as bug fixes and other
information. Here's a link to the Ocata release notes for OpenStack-Ansible
which includes the announcement of the Trove role.

https://docs.openstack.org/releasenotes/openstack-ansible/ocata.html

Thanks,

Amy (spotz)

On Tue, Sep 26, 2017 at 6:04 PM, Michael Gale 
wrote:

> Hello,
>
>Based on github and https://docs.openstack.org/openstack-ansible-os_
> trove/latest/ it looks like OpenStack-Ansible will support Trove under
> the Ocata release.
>
> Is that assumption correct? is there a better method to determine when a
> software component will likely be included in a release?
>
> Michael
>
> __
> 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] [openstack-ansible] Meeting Cancelled 9/21

[Amy Marrich]

Just wanted to let everyone know we will be cancelling the IRC meeting on
9/21

Thanks,

Amy (spotz)
__
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] Help us grow The Women of OpenStack

[Amy Marrich]

Did you know the Women of OpenStack isn't just for people who identify as
female, but allies as well? Well now you do and we're looking for new
members!

Our mission statement is:

The Women of OpenStack (WOO) strive to increase the diversity of the
OpenStack community by overcoming OpenStack's barrier to entry through
educational sessions, professional networking, mentorship, social
inclusion, and enhanced resource access. WOO recognizes that individuals in
minority groups are more likely to have challenges accessing the resources
it takes to learn and participate in complex technologies, which is why WOO
welcomes all women and their allies who share an interest in OpenStack,
open source, and adjacent technologies. These goals are achieved through
leading and sponsorship of educational sessions and social events that
promote inclusion in the OpenStack Community.

We follow this mission by sponsoring ongoing Mentoring throughout the year
and through the Speed Mentoring and Lunch and Learns which are held during
summit as well as other activities through the year.

Our Wiki page can be found here:
https://wiki.openstack.org/wiki/Women_of_OpenStack

And you can join our mailing list here:
http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack

And of course you can join us in Freenode IRC on the #openstack-women
channel.

Come sit in on a meeting and check us out! Meetings are held every other
Monday with our next meeting scheduled for 08/21/17. You can join us with
the following information:
2000 UTC, 4 PM EDT, 3 PM CDT, 2 PM MDT, 1 PM PDT
Dial In: 1-203-277-8157 <(203)%20277-8157> or *866-619-0383
<(866)%20619-0383>  Participant: 7217256**#* Leader 4018#
webex - https://verizon2.webex.com/verizon2-en/e.php?MTID=
m0e7ba518a2d4487bc0a78d00055f62e2

And if you forget you'll get a reminder on the mailing list before hand!

Hope you join us!

Amy Marrich (spotz)
__
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-Ansible] Not running for Queens PTL

[Amy Marrich]

Andy,

You'll be missed you did a great job(as did Kevin and Jesse before you)!
Glad you'll be around still as you'd definitely be missed.

Amy (spotz)

On Mon, Jul 31, 2017 at 4:48 AM, Andy McCrae  wrote:

> Following on from last week's meeting - I've had 2 cycles as PTL for OSA,
> which has been a really great experience - we've achieved a lot and built
> on the strong base we had, which I'm really proud of. I strongly believe
> that inviting a fresh perspective and new ideas as PTL is a winning
> strategy - it's served us well so far, and in line with previous PTLs I
> won't be standing for a 3rd cycle.
>
> Looking forward to assisting the next PTL, and helping to continue to
> mature and improve the project!
>
> Thanks!
> Andy
>
> __
> 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

Re: [openstack-dev] [all] Cleaning up inactive meetbot channels

[Amy Marrich]

Yeah I'd say stop logging it and we'll request being added back in should
we get going.

Amy(spotz)

On Wed, Jul 19, 2017 at 3:22 PM, Jeremy Stanley <fu...@yuggoth.org> wrote:

> On 2017-07-19 15:15:51 -0500 (-0500), Amy Marrich wrote:
> > Sorry to see the Diversity channel go as we really need to get the
> > Working Group back up and running but it never was really high
> > volume.
> [...]
>
> If you anticipate activity picking up soon in that channel we can
> certainly keep logging it for now. Alternatively, even if we stop
> logging it today, you can always submit a change to add logging back
> later if people decide to start using that channel for discussions
> again.
> --
> Jeremy Stanley
>
> __
> 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

Re: [openstack-dev] [all] Cleaning up inactive meetbot channels

[Amy Marrich]

Sorry to see the Diversity channel go as we really need to get the Working
Group back up and running but it never was really high volume.

Amy(spotz)

On Wed, Jul 19, 2017 at 2:24 PM, Jeremy Stanley  wrote:

> For those who are unaware, Freenode doesn't allow any one user to
> /join more than 120 channels concurrently. This has become a
> challenge for some of the community's IRC bots in the past year,
> most recently the "openstack" meetbot (which not only handles
> meetings but also takes care of channel logging to
> eavesdrop.openstack.org and does the nifty bug number resolution
> some people seem to like).
>
> I have run some rudimentary analysis and come up with the following
> list of channels which have had fewer than 10 lines said by anyone
> besides a bot over the past three months:
>
> #craton
> #openstack-api
> #openstack-app-catalog
> #openstack-bareon
> #openstack-cloudpulse
> #openstack-community
> #openstack-cue
> #openstack-diversity
> #openstack-gluon
> #openstack-gslb
> #openstack-ko
> #openstack-kubernetes
> #openstack-networking-cisco
> #openstack-neutron-release
> #openstack-opw
> #openstack-pkg
> #openstack-product
> #openstack-python3
> #openstack-quota
> #openstack-rating
> #openstack-solar
> #openstack-swauth
> #openstack-ux
> #openstack-vmware-nsx
> #openstack-zephyr
>
> I have a feeling many of these are either no longer needed, or what
> little and infrequent conversation they get used for could just as
> easily happen in a general channel like #openstack-dev or #openstack
> or maybe in the more active channel of their parent team for some
> subteams. Who would miss these if we ceased logging/using them? Does
> anyone want to help by asking around to people who might not see
> this thread, maybe by popping into those channels and seeing if any
> of the sleeping denizens awaken and say they still want to keep it
> around?
>
> Ultimately we should improve our meetbot deployment to support
> sharding channels across multiple bots, but that will take some time
> to implement and needs volunteers willing to work on it. In the
> meantime we're running with the meetbot present in 120 channels and
> have at least one new channel that desires logging and can't get it
> until we whittle that number down.
> --
> Jeremy Stanley
>
> __
> 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

Re: [openstack-dev] [OpenStack-Ansible] Proposing Markos Chandras for osa-core

[Amy Marrich]

+1 from the meeting and prosperity!

Amy (spotz)

On Tue, Jul 18, 2017 at 4:23 AM, Andy McCrae  wrote:

> Following on from last week's meeting I'd like to propose Markos
> (hwoarang) for OSA core.
>
> Markos has done a lot of good reviews and commits over an extended period
> of time, and has shown interest in the project as a whole. (Not to mention
> the addition of SUSE support)
>
> We already have quite a few +1's from the meeting itself, but opening up
> to everybody who wasn't available at the meeting!
>
> Thanks,
> Andy
>
>
>
>
>
> __
> 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

Re: [openstack-dev] [User-committee] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

[Amy Marrich]

On Thu, Jun 29, 2017 at 3:12 PM, Mike Perez <thin...@gmail.com> wrote:

> On June 29, 2017 at 13:01:09, Amy Marrich (a...@demarco.com) wrote:
> > First off it looks really sleek and I love the look! A few thoughts
> though
> > and I do realize it's just a mock up:
> >
> > 1) We have Sponsor just to pick one but don't have
> Operators/Administrators
> > and their feedback is a major contribution so please don't leave them
> out.
>
> Ah yes, I should’ve mentioned earlier that this is totally a POC.
> There are lots missing, don’t worry! :)
>
> > 2) I would list the contributor types in alphabetical order that way no
> > group feels slighted, you can't help it if Use Cases are last it's just
> > that they start with a U vs Code which is a C.
>
> Sure!
>
> > 3) What if you would like to contribute in multiple ways?
>
> You would come back to the main contributor portal and click on a
> different contribution. How about at the end of each lesson it gives
> them the option to go back to main contributor portal to pick another
> way to contribute?
>
> What if on the bottom it could list out the other ways and they could just
proceed from there?


> >
> > Resources are definitely still underdevelopment there but are they meant
> to
> > be broad applicable to all resources with more specialized one's visible
> > when you click on how you'd like to contribute?
>
> That’s a good question. I think it should probably on top contain the
> more general stuff, then in alphabetical order we can list resources
> for all contribution types? It can be like the “I want to contribute
> to OpenStack by…” top piece, but instead lists resource links to pick
> through based on your contribution type(s). Maybe we keep them as
> separate pages as originally given in the mock up so it’s not overly
> crowded?
>
> Thanks for the help Amy!
>
> —
> Mike Perez
>

Amy (spotz)
__
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] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

[Amy Marrich]

Mike,

We've gone through some of this with the Git and Gerrit Lunch and Learns
and the Upstream Institute, but those are both live teaching type
situations. I'd be more then happy to help incorporate some of the stuff we
already have into an on-line effort for those who can't attend in person so
that we can help get them the same experience if not close to it.

Amy (aka spotz)

On Fri, Jun 23, 2017 at 3:17 PM, Mike Perez  wrote:

> Hello all,
>
> Every month we have people asking on IRC or the dev mailing list having
> interest in working on OpenStack, and sometimes they're given different
> answers from people, or worse, no answer at all.
>
> Suggestion: lets work our efforts together to create some common
> documentation so that all teams in OpenStack can benefit.
>
> First it’s important to note that we’re not just talking about code
> projects here. OpenStack contributions come in many forms such as running
> meet ups, identifying use cases (product working group), documentation,
> testing, etc. We want to make sure those potential contributors feel
> welcomed too!
>
> What is common documentation? Things like setting up Git, the many
> accounts you need to setup to contribute (gerrit, launchpad, OpenStack
> foundation account). Not all teams will use some common documentation, but
> the point is one or more projects will use them. Having the common
> documentation worked on by various projects will better help prevent
> duplicated efforts, inconsistent documentation, and hopefully just more
> accurate information.
>
> A team might use special tools to do their work. These can also be
> integrated in this idea as well.
>
> Once we have common documentation we can have something like:
> 1. Choose your own adventure: I want to contribute by code
> 2. What service type are you interested in? (Database, Block storage,
> compute)
> 3. Here’s step-by-step common documentation to setting up Git, IRC,
> Mailing Lists, Accounts, etc.
> 4. A service type project might choose to also include additional
> documentation in that flow for special tools, etc.
>
> Important things to note in this flow:
> * How do you want to contribute?
> * Here are **clear** names that identify the team. Not code names like
> Cloud Kitty, Cinder, etc.
> * The documentation should really aim to not be daunting:
> * Someone should be able to glance at it and feel like they can finish
> things in five minutes. Not be yet another tab left in their browser that
> they’ll eventually forget about
> * No wall of text!
> * Use screen shots
> * Avoid covering every issue you could hit along the way.
>
> ## Examples of More Simple Documentation
> I worked on some documentation for the Upstream University preparation
> that has received excellent feedback meet close to these suggestions:
> * IRC [1]
> * Git [2]
> * Account Setup [3]
>
> ## 500 Feet Birds Eye view
> There will be a Contributor landing page on the openstack.org website.
> Existing contributors will find reference links to quickly jump to things.
> New contributors will find a banner at the top of the page to direct them
> to the choose your own adventure to contributing to OpenStack, with ordered
> documentation flow that reuses existing documentation when necessary.
> Picture also a progress bar somewhere to show how close you are to being
> ready to contribute to whatever team. Of course there are a lot of other
> fancy things we can come up with, but I think getting something up as an
> initial pass would be better than what we have today.
>
> Here's an example of what the sections/chapters could look like:
>
> - Code
> * Volumes (Cinder)
>  * IRC
>  * Git
>  * Account Setup
>  * Generating Configs
> * Compute (Nova)
>  * IRC
>  * Git
>  * Account Setup
> * Something about hypervisors (matrix?)
> -  Use Cases
> * Products (Product working group)
> * IRC
> * Git
> * Use Case format
>
> There are some rough mock up ideas [4]. Probably Sphinx will be fine for
> this. Potentially we could use this content for conference lunch and
> learns, upstream university, and the on-boarding events at the Forum. What
> do you all think?
>
> [1] - http://docs.openstack.org/upstream-training/irc.html
> [2] - http://docs.openstack.org/upstream-training/git.html
> [3] - http://docs.openstack.org/upstream-training/accounts.html
> [4] - https://www.dropbox.com/s/o46xh1cp0sv0045/OpenStack%
> 20contributor%20portal.pdf?dl=0
>
> —
>
> Mike Perez
>
> __
> 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 

[openstack-dev] [OpenStack-Ansible][OSA] Next week's meeting is cancelled

[Amy Marrich]

Just wanted to give everyone a heads up that next week's meeting on 6/15
has been cancelled.

Thanks all!

Amy (spotz)
__
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-Ansible] Meeting Cancelled

[Amy Marrich]

Sorry for the short notice but today's meeting has been cancelled. We'll
resume with our bug-triage on Tuesday and our next Meeting on next Thursday
at their usual times and places.

Amy (spotz)
__
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] [os-upstream-institute] Order of Slides

[Amy Marrich]

I was going over the 2 sections I'm presenting this weekend and noticed
that in

https://docs.openstack.org/upstream-training/workflow-training-contribution-process.html

We talk about submitting and taking bugs, doing reviews and pushing up code
sets as it's the overview. But the next section

https://docs.openstack.org/upstream-training/workflow-reg-and-accounts.html

we sign up for the actual accounts.

I'm not sure if in the future we might want to change the order of these
sections so that folks can possibly work a little ahead or if we want to
keep the order to prevent it. Either way we can always reference the other
section, in this case with a 'In the next section you'll be making the
account to do this'  or if we switched the order 'Using the username from
the last section'.

Amy (spotz)
__
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-Ansible Onboarding -day/time change

[Amy Marrich]

Just wanted to let everyone know the time and day for the OpenStack-Ansible
Onboarding has changed. We will now have our onboarding on Wednesday, May
10 from 9:00 to 10:30.

https://www.openstack.org/summit/boston-2017/summit-schedule/events/18711/ansible-project-onboarding

Hope to see lots of new and familiar faces!

Amy (aka spotz)
__
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] Arrivederci

[Amy Marrich]

Ian,

You will be missed. Best wishes in your new endeavours,

Amy (aka spotz)

On Wed, Mar 22, 2017 at 7:06 AM, Ian Cordasco 
wrote:

> Hi everyone,
>
> Friday 24 March 2017 will be my last day working on OpenStack. I'll remove
> myself from teams (glance, craton, security, hacking) on Friday and
> unsubscribe
> from the OpenStack mailing lists.
>
> I want to thank all of you for the last ~3 years. I've learned quite a bit
> from all of you. It's been a unique privilege to call the people in this
> community my colleagues. Treat each other well. Don't let minor technical
> arguments cause rifts in the community. Lift each other up.
>
> As for me, I'm moving onto something completely different. You all are
> welcome
> to keep in touch via email, IRC, or some other method. At the very
> least, I'll see y'all
> around PyCon, the larger F/OSS world, etc.
>
> --
> Ian Cordasco
> IRC/Git{Hub,Lab}/Twitter: sigmavirus24
>
> __
> 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

Re: [openstack-dev] [OpenStack-docs] [all] Upstream Training Team meeting at PTG - Are you coming?

[Amy Marrich]

I tried to get into the google hangout
https://hangouts.google.com/call/4htgw2zmb5ar5mzihizsnppf4ye and it said I
wasn't allowed to join. I did send Ildiko my phone number if I'm the only
remote.

Amy

On Wed, Feb 22, 2017 at 11:04 AM, Csatari, Gergely (Nokia - HU/Budapest) <
gergely.csat...@nokia.com> wrote:

> Hi,
> We are waiting in Savannah 1 as there is a meeting still ongoing in
> Savannah 3.
> Br,
> Gerg0
>
> Sent from Nine 
> --
> *From:* Ildiko Vancsa 
> *Sent:* Feb 21, 2017 9:05 AM
> *To:* OpenStack Development Mailing List (not for usage questions);
> openstack-d...@lists.openstack.org; user-committee
> *Subject:* Re: [openstack-dev] [all] Upstream Training Team meeting at
> PTG - Are you coming?
>
> Hi All,
>
> A quick reminder that we will have our face to face gathering on
> __Wednesday (tomorrow) at lunch time (12pm ET)__.
>
> I booked Savannah 3 on the second floor (Lobby level). Please grab a lunch
> box after the morning sessions and join us for lunch if you would like to
> get involved with the Upstream Training and/or new contributor on boarding
> activities.
>
> Thanks and Best Regards,
> Ildikó
> IRC: ildikov
>
>
> > On 2017. Feb 15., at 13:16, Ildiko Vancsa 
> wrote:
> >
> > Hi,
> >
> > We are forming a virtual upstream collaboration training team including
> everyone who’s either helping us out with maintaining and improving the
> training material and/or who are attending the course as coaches or mentors.
> >
> > We are planning to meet at the PTG in person next week on Wednesday at
> lunch time. We picked this slot as our first face to face gathering as all
> of us have project related assignments to drive and sessions to attend that
> makes scheduling a meeting even more challenging.
> >
> > If you are interested in what we are doing and how we are trying to make
> the on boarding process for new contributors a pleasant experience and
> would like to join our activities meet us there!
> >
> > The meeting time is __Wednesday (February 22) lunch time__. I will share
> the meeting point next week before the meeting.
> >
> > If you would like to have a mail reminder prior to the meeting next week
> please reach out to me.
> >
> > Thanks and Best Regards,
> > Ildikó
> > IRC: ildikov
>
>
> __
> 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-docs mailing list
> openstack-d...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
__
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] The end of OpenStack packages in Debian?

[Amy Marrich]

+2

On Wed, Feb 15, 2017 at 9:41 AM, Tobias Urdin 
wrote:

> On 02/15/2017 01:46 PM, Thomas Goirand wrote:
> > Hi there,
> >
> > It's been a while since I planed on writing this message. I couldn't
> > write it because the situation makes me really sad. At this point, it
> > starts to be urgent to post it.
> >
> > As for many other folks, Mirantis decided to end its contract with me.
> > This happened when I was the most successful doing the job, with all of
> > the packaging CI moved to OpenStack infra at the end of the OpenStack
> > Newton cycle, after we were able to release Newton this way. I was
> > hoping to start packaging on every commit for Ocata. That's yet another
> > reason for me to be very frustrated about all of this. Such is life...
> >
> > Over the last few months, I hoped for having enough strengths to
> > continue my packaging work anyway, and get Ocata packages done. But
> > that's not what happened. The biggest reason for this is that I know
> > that this needs to be a full time job. And at this point, I still don't
> > know what my professional future will be. A company, in Barcelona, told
> > me I'd get hired to continue my past work of packaging OpenStack in
> > Debian, but so far, I'm still waiting for a definitive answer, so I'm
> > looking into some other opportunities.
> >
> > All this to say that, unless someone wants to hire me for it (which
> > would be the best outcome, but I fear this wont happen), or if someone
> > steps in (this seems unlikely at this point), both the packaging-deb and
> > the faith of OpenStack packages in Debian are currently compromised.
> >
> > I will continue to maintain OpenStack Newton during the lifetime of
> > Debian Stretch though, but I don't plan on doing anything more. This
> > means that maybe, Newton will be the last release of OpenStack in
> > Debian. If things continue this way, I probably will ask for the removal
> > of all OpenStack packages from Debian Sid after Stretch gets released
> > (unless I know that someone will do the work).
> >
> > As a consequence, the following projects wont get packages even in
> > Ubuntu (as they were "community maintained", which means done by me and
> > later sync into Ubuntu...):
> >
> > - congress
> > - gnocchi
> > - magnum
> > - mistral
> > - murano
> > - sahara
> > - senlin
> > - watcher
> > - zaqar
> >
> > Hopefully, Canonical will continue to maintain the other 15 (more
> > core...) projects in UCA.
> >
> > Thanks for the fish,
> >
> > Thomas Goirand (zigo)
> >
> > P,S: To the infra folks: please keep the packaging CI as it is, as it
> > will be useful for the lifetime of Stretch.
> >
> > 
> __
> > 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
> >
> Somebody please hire Thomas, he's amazing!
>
> Thank you for everything!
>
>
> __
> 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

Re: [openstack-dev] [openstack-ansible] Propose Marc Gariepy as core reviewer

[Amy Marrich]

+1 from me too!

Amy
IRC: spotz

On Fri, Feb 3, 2017 at 7:33 AM, Jesse Pretorius <
jesse.pretor...@rackspace.co.uk> wrote:

> Hi everyone,
>
>
>
> I’d like to propose Marc Gariepy [1] as a core reviewer for
> OpenStack-Ansible. His tireless effort to get CentOS as a supported
> platform in the last two cycles is getting very close to completion, and I
> feel that it’s important that he’s able to safeguard this work and help
> grow the maintenance community for it.
>
>
>
> [1] http://stackalytics.com/?module=openstackansible-group;
> user_id=mgariepy=ocata=person-day
>
>
>
> Best regards,
>
>
>
> Jesse
>
> IRC: odyssey4me
>
> --
> Rackspace Limited is a company registered in England & Wales (company
> registered number 03897010) whose registered office is at 5 Millington
> Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy
> can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail
> message may contain confidential or privileged information intended for the
> recipient. Any dissemination, distribution or copying of the enclosed
> material is prohibited. If you receive this transmission in error, please
> notify us immediately by e-mail at ab...@rackspace.com and delete the
> original message. Your cooperation is appreciated.
>
> __
> 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

Re: [openstack-dev] [openstack-ansible] Mid Cycle Sprint

[Amy Marrich]

I'd be game to join in if it's in San Antonio. While I'd love to go to London I 
don't think I'd make.

Like Major I'd like to see some doc work.

Amy Marrich

From: Jesse Pretorius <jesse.pretor...@gmail.com>
Sent: Wednesday, December 9, 2015 6:45:56 AM
To: openstack-dev@lists.openstack.org; openstack-operat...@lists.openstack.org
Subject: [openstack-dev] [openstack-ansible] Mid Cycle Sprint

Hi everyone,

At the Mitaka design summit in Tokyo we had some corridor discussions about 
doing a mid-cycle meetup for the purpose of continuing some design discussions 
and doing some specific sprint work.

***
I'd like indications of who would like to attend and what 
locations/dates/topics/sprints would be of interest to you.
***

For guidance/background I've put some notes together below:

Location

We have contributors, deployers and downstream consumers across the globe so 
picking a venue is difficult. Rackspace have facilities in the UK (Hayes, West 
London) and in the US (San Antonio) and are happy for us to make use of them.

Dates
-
Most of the mid-cycles for upstream OpenStack projects are being held in 
January. The Operators mid-cycle is on February 15-16.

As I feel that it's important that we're all as involved as possible in these 
events, I would suggest that we schedule ours after the Operators mid-cycle.

It strikes me that it may be useful to do our mid-cycle immediately after the 
Ops mid-cycle, and do it in the UK. This may help to optimise travel for many 
of us.

Format
--
The format of the summit is really for us to choose, but typically they're 
formatted along the lines of something like this:

Day 1: Big group discussions similar in format to sessions at the design summit.

Day 2: Collaborative code reviews, usually performed on a projector, where the 
goal is to merge things that day (if a review needs more than a single 
iteration, we skip it. If a review needs small revisions, we do them on the 
spot).

Day 3: Small group / pair programming.

Topics
--
Some topics/sprints that come to mind that we could explore/do are:
 - Install Guide Documentation Improvement [1]
 - Development Documentation Improvement (best practises, testing, how to 
develop a new role, etc)
 - Upgrade Framework [2]
 - Multi-OS Support [3]

[1] https://etherpad.openstack.org/p/oa-install-docs
[2] https://etherpad.openstack.org/p/openstack-ansible-upgrade-framework
[3] https://etherpad.openstack.org/p/openstack-ansible-multi-os-support

--
Jesse Pretorius
IRC: odyssey4me
__
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