Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-03-10 Thread Ronald Bradford
I attended the first day of the bugsmash event in New York and I have some
general feedback for future organizers of these types of events.  Hopefully
others can also share their experiences.

These comments are for the benefit of making the event better the next
time. As I attended only one location and one of three days, the experience
may have been vastly different elsewhere.

Connectivity.  The University location blocked IRC, git and gerrit ports.
One should be prepared for this situation when talking about the use of IRC
(but not being able to demonstrate your local client for example).  Knowing
how to adjust devstack to use https was something we needed to do.  I was
told you could communicate with gerrit over https but never got to see
that.  Having a reference to this, say the wiki would be great.


Prerequisites:  It would likely be more ideal if your focus is on fixing
bugs rather then talking about the process of how to contribute to fixing
bugs in OpenStack then stating that installing devstack as a pre-requisite.
At NYC almost all attendees have never installed devstack, so a good
portion of the day was getting this setup.  As such it was requested by
some devstack cores to propose this in docs, and hence
http://docs-draft.openstack.org/54/290854/1/check/gate-devstack-publish-docs/d6e9b5b//doc/build/html/guides/first-time.html
via https://review.openstack.org/#/c/290854/.   Again, this was just our
experience but this guide is for the absolute first time devstack user, and
it's detailed for that purpose.

Approach: There are multiple ways to consider addressing bugs, do you even
need devstack, or do you just use the code and unit tests. I think it's
important to cultivate the varied approaches and provide demonstrations of
each.  Which way to do you start, again it depends.   I feel that given the
NYC audience (and this may also not reflect others), that a live demo of
devstack, looking at screen logs, restarting a service, even changing
something (say a logging format, or a line of code) will show the audience
the impact of using devstack and validating manually the impact of your
code change.  Demonstrating unit tests, and other tox environments such as
pep8 is also a solid grounding in fixing bugs well and consistently.

Audience: The NYC event lacked any prep information (e.g. a surveymonkey)
of the level of attendee, this could have facilitated splitting the first
day into different tracks based on skills level.  For a 3 day event,
perhaps advertising day 1 specifically as getting your environment ready,
informs people.

Baseline:  At our event one of the outcomes was for a few cloud images to
be spun up with devstack and code. This solves some of the connectivity
issues, and also solves this first day getting started.  It enables it to
be potential more a homework task.  I think is a great way, having a public
cloud image and devstack and sample code base.  It serves as the basis of
demo land, can be cloned for attendees at any location.

My 2 cents to making this type of event even better next time.







Ronald Bradford

Web Site: http://ronaldbradford.com
LinkedIn:  http://www.linkedin.com/in/ronaldbradford
Twitter:@RonaldBradford 
Skype: RonaldBradford
GTalk: Ronald.Bradford
IRC: rbradfor


On Thu, Jan 28, 2016 at 4:11 AM, Wang, Shane  wrote:

> *Save the Date:*
> *Global OpenStack Bug Smash*
> *Wednesday-Friday, March 2-4, 2016*
> *RSVP by Friday, February 19*
>
> How can you help make the OpenStack Mitaka release stable and bug-free
> while having fun with your peers? Join Intel, Rackspace, Mirantis, IBM, HP,
> Huawei, CESI and others in a global bug smash across four continents as we
> work together. Then, join us later in April in Austin, Texas, U.S.A. at the
> OpenStack Summit to get re-acquainted & celebrate our accomplishments!
>
> *OUR GOAL*
> Our key goal is to collaborate round-the-clock and around the world to fix
> as many bugs as possible across the wide range of OpenStack projects. In
> the process, we’ll also help onboard and grow the number of OpenStack
> developers, and increase our collective knowledge of OpenStack tools and
> processes. To ease collaboration among all of the participants and ensure
> that core reviews can be conducted promptly, we will use the IRC channel,
> the mailing list, and Gerrit and enlist core reviewers in the event.
>
> *GET INVOLVED*
> Simply choose a place near you—and register by Friday, February 19.
> Registration is free, and we encourage you to invite others who may be
> interested.
>
>
>- Australia
>- China
>- India
>
>
>- Russia
>- United Kingdom
>- United States
>
>
> Visit the link below for additional details:
> *https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka*
> 
>
> Come make the Mitaka release a grand success through your contributions,
> and ease the 

Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-03-07 Thread Markus Zoeller
"Wang, Shane" <shane.w...@intel.com> wrote on 03/05/2016 07:04:56 AM:

> From: "Wang, Shane" <shane.w...@intel.com>
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev@lists.openstack.org>
> Date: 03/05/2016 07:05 AM
> Subject: Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash 
Mitaka
> 
> Yes, sure, Markus, we are using https://etherpad.openstack.org/p/
> OpenStack-Bug-Smash-Mitaka-Bugs to track. They were edited by those 
> participants to share between different geos. Feel free to let the 
> community know on communication channels, IRC channel (e.g. nova) or 
mail list.
> Let's talk via them to concentrate fixing from next Monday to next 
Wednesday.
> 
> Thanks.
> --
> Shane

I screwed up the dates. I thought I had some more time. IOW, I don't 
have a list ready. Luckily dims bashed his way through the stale 
in progress bugs in Nova and had reset a lot of them. If you need some
kind of query for Launchpad you can use my scripts at [1]. They are
fairly short and simple. They are written with Nova in mind but you
will see in the code where you have to change that in case for Cinder,
Neutron and so on.
Thanks dims for your effort!

References:
[1] 
https://github.com/markuszoeller/openstack/tree/master/scripts/launchpad

Regards, Markus Zoeller (markus_z) 


> -Original Message-
> From: Markus Zoeller [mailto:mzoel...@de.ibm.com] 
> Sent: Thursday, March 03, 2016 2:09 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash 
Mitaka
> 
> "Wang, Shane" <shane.w...@intel.com> wrote on 02/05/2016 04:42:21 AM:
> 
> > From: "Wang, Shane" <shane.w...@intel.com>
> > To: "OpenStack Development Mailing List (not for usage questions)" 
> > <openstack-dev@lists.openstack.org>
> > Date: 02/05/2016 04:43 AM
> > Subject: Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash
> Mitaka
> > 
> > Hi all,
> > 
> > After discussing with TC members and other community guys, we thought 
> > March 2-4 might not be a good timing for bug smash. So we decided to 
> > change the dates to be March 7 ? 9 (Monday ? Wednesday) in R4.
> > Please join our efforts to fix bugs for OpenStack.
> > 
> > Thanks.
> 
> Hi Shane,
> 
> I'm the bug list maintainer of Nova, is it possible for me to propose 
> a list of bugs which need fixes? 
> Nova (and surely other projects too) would also benefit from:
> * a cleanup of inconsistencies in bug reports in Launchpad
> * triaging new bugs in Launchpad
> * reviews of pushed bug fixes in Gerrit
> Basically the steps from [1]. As we're heading to the rc phase in a 
> few weeks it would be benefitial to have a lot of eyes on that. 
> 
> References:
> [1] https://wiki.openstack.org/wiki/BugTriage
> 
> Regards, Markus Zoeller (markus_z)
> 
> 
> 
__
> 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] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-03-04 Thread Wang, Shane
Typo: view -> review:)

From: Wang, Shane
Sent: Saturday, March 05, 2016 2:09 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: RE: [bug-smash] Global OpenStack Bug Smash Mitaka

A reminder for the community, the bug smashes are going to start next Monday, 
if you can't join those 11 sites, you can do virtual bug smash remotely by 
fixing the bugs in your offices.
Also, please help do remote view. Thanks.

Best Regards.
--
Shane
From: Wang, Shane [mailto:shane.w...@intel.com]
Sent: Friday, February 05, 2016 11:42 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka
Importance: High

Hi all,

After discussing with TC members and other community guys, we thought March 2-4 
might not be a good timing for bug smash. So we decided to change the dates to 
be March 7 - 9 (Monday - Wednesday) in R4.
Please join our efforts to fix bugs for OpenStack.

Thanks.
--
Shane
From: Wang, Shane [mailto:shane.w...@intel.com]
Sent: Thursday, January 28, 2016 5:12 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

Save the Date:
Global OpenStack Bug Smash
Wednesday-Friday, March 7-9, 2016
RSVP by Friday, February 24

How can you help make the OpenStack Mitaka release stable and bug-free while 
having fun with your peers? Join Intel, Rackspace, Mirantis, IBM, HP, Huawei, 
CESI and others in a global bug smash across four continents as we work 
together. Then, join us later in April in Austin, Texas, U.S.A. at the 
OpenStack Summit to get re-acquainted & celebrate our accomplishments!

OUR GOAL
Our key goal is to collaborate round-the-clock and around the world to fix as 
many bugs as possible across the wide range of OpenStack projects. In the 
process, we'll also help onboard and grow the number of OpenStack developers, 
and increase our collective knowledge of OpenStack tools and processes. To ease 
collaboration among all of the participants and ensure that core reviews can be 
conducted promptly, we will use the IRC channel, the mailing list, and Gerrit 
and enlist core reviewers in the event.

GET INVOLVED
Simply choose a place near you-and register by Friday, February 24. 
Registration is free, and we encourage you to invite others who may be 
interested.

* Australia
* China
* India

* Russia
* United Kingdom
* United States


Visit the link below for additional details:
https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka

Come make the Mitaka release a grand success through your contributions, and 
ease the journey for newcomers!

Regards.
--
OpenStack Bug Smash team

__
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] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-03-04 Thread Wang, Shane
A reminder for the community, the bug smashes are going to start next Monday, 
if you can't join those 11 sites, you can do virtual bug smash remotely by 
fixing the bugs in your offices.
Also, please help do remote view. Thanks.

Best Regards.
--
Shane
From: Wang, Shane [mailto:shane.w...@intel.com]
Sent: Friday, February 05, 2016 11:42 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka
Importance: High

Hi all,

After discussing with TC members and other community guys, we thought March 2-4 
might not be a good timing for bug smash. So we decided to change the dates to 
be March 7 - 9 (Monday - Wednesday) in R4.
Please join our efforts to fix bugs for OpenStack.

Thanks.
--
Shane
From: Wang, Shane [mailto:shane.w...@intel.com]
Sent: Thursday, January 28, 2016 5:12 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

Save the Date:
Global OpenStack Bug Smash
Wednesday-Friday, March 7-9, 2016
RSVP by Friday, February 24

How can you help make the OpenStack Mitaka release stable and bug-free while 
having fun with your peers? Join Intel, Rackspace, Mirantis, IBM, HP, Huawei, 
CESI and others in a global bug smash across four continents as we work 
together. Then, join us later in April in Austin, Texas, U.S.A. at the 
OpenStack Summit to get re-acquainted & celebrate our accomplishments!

OUR GOAL
Our key goal is to collaborate round-the-clock and around the world to fix as 
many bugs as possible across the wide range of OpenStack projects. In the 
process, we'll also help onboard and grow the number of OpenStack developers, 
and increase our collective knowledge of OpenStack tools and processes. To ease 
collaboration among all of the participants and ensure that core reviews can be 
conducted promptly, we will use the IRC channel, the mailing list, and Gerrit 
and enlist core reviewers in the event.

GET INVOLVED
Simply choose a place near you-and register by Friday, February 24. 
Registration is free, and we encourage you to invite others who may be 
interested.

* Australia
* China
* India

* Russia
* United Kingdom
* United States


Visit the link below for additional details:
https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka

Come make the Mitaka release a grand success through your contributions, and 
ease the journey for newcomers!

Regards.
--
OpenStack Bug Smash team

__
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] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-03-04 Thread Wang, Shane
Yes, sure, Markus, we are using 
https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka-Bugs to track. They 
were edited by those participants to share between different geos. Feel free to 
let the community know on communication channels, IRC channel (e.g. nova) or 
mail list.
Let's talk via them to concentrate fixing from next Monday to next Wednesday.

Thanks.
--
Shane

-Original Message-
From: Markus Zoeller [mailto:mzoel...@de.ibm.com] 
Sent: Thursday, March 03, 2016 2:09 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

"Wang, Shane" <shane.w...@intel.com> wrote on 02/05/2016 04:42:21 AM:

> From: "Wang, Shane" <shane.w...@intel.com>
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev@lists.openstack.org>
> Date: 02/05/2016 04:43 AM
> Subject: Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash
Mitaka
> 
> Hi all,
> 
> After discussing with TC members and other community guys, we thought 
> March 2-4 might not be a good timing for bug smash. So we decided to 
> change the dates to be March 7 ? 9 (Monday ? Wednesday) in R4.
> Please join our efforts to fix bugs for OpenStack.
> 
> Thanks.

Hi Shane,

I'm the bug list maintainer of Nova, is it possible for me to propose a list of 
bugs which need fixes? 
Nova (and surely other projects too) would also benefit from:
* a cleanup of inconsistencies in bug reports in Launchpad
* triaging new bugs in Launchpad
* reviews of pushed bug fixes in Gerrit
Basically the steps from [1]. As we're heading to the rc phase in a few weeks 
it would be benefitial to have a lot of eyes on that. 

References:
[1] https://wiki.openstack.org/wiki/BugTriage

Regards, Markus Zoeller (markus_z)


__
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] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-03-02 Thread Markus Zoeller
"Wang, Shane" <shane.w...@intel.com> wrote on 02/05/2016 04:42:21 AM:

> From: "Wang, Shane" <shane.w...@intel.com>
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev@lists.openstack.org>
> Date: 02/05/2016 04:43 AM
> Subject: Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash 
Mitaka
> 
> Hi all,
> 
> After discussing with TC members and other community guys, we thought 
> March 2-4 might not be a good timing for bug smash. So we decided to 
> change the dates to be March 7 ? 9 (Monday ? Wednesday) in R4.
> Please join our efforts to fix bugs for OpenStack.
> 
> Thanks.

Hi Shane,

I'm the bug list maintainer of Nova, is it possible for me to propose
a list of bugs which need fixes? 
Nova (and surely other projects too) would also benefit from:
* a cleanup of inconsistencies in bug reports in Launchpad
* triaging new bugs in Launchpad
* reviews of pushed bug fixes in Gerrit
Basically the steps from [1]. As we're heading to the rc phase in a 
few weeks it would be benefitial to have a lot of eyes on that. 

References:
[1] https://wiki.openstack.org/wiki/BugTriage

Regards, Markus Zoeller (markus_z)


__
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] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-02-08 Thread Jeremy Stanley
On 2016-02-07 03:19:45 + (+), Wang, Shane wrote:
> You are over worried about the new contributors. We are going to
> limit the number of attendees, and from my experience and
> knowledge, most of developers who join bug smash are old and
> experienced OpenStack developers, and they already have ATC codes.
> On the other hand, if those events don't exist, you are not able
> to stop new contributors from submitting and merging individual
> patches or fixes. You might set a deadline of sending the ATC
> codes - say some Release Candidate.

As I said in my previous message, we do set a deadline: the main
feature freeze listed on the release schedule. I was merely pointing
out that the deadline for contributors to qualify for registration
discounts is prior to this Bug Smash event, and so any contributions
made during the event won't solely qualify anyone for a registration
code. Some of our conference coordinators had expressed concern that
new or latent contributors participating in the Bug Smash may be
expecting a discount code, so I volunteered to send a follow-up to
this thread on their behalf.
-- 
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


Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-02-06 Thread Wang, Shane
Hi Robert,

Thank you for your offering, it is great to have you in Germany.

Best Regards.
--
Shane
-Original Message-
From: Robert Simai [mailto:robert.si...@suse.com] 
Sent: Friday, February 05, 2016 5:28 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

All,

I like to announce that SUSE joins these efforts, we're going to provide rooms 
in Nuremberg/Germany and have developers from our side available to contribute 
to the Mitaka bug smash.

The etherpad page [1] is updated, the etherpad page for the location [2] is 
under construction. Hope to see some of you in Nuremberg!

[1] https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka
[2] https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka-Nuremberg

--
Thanks,
   Robert

On Friday 05 February 2016, 03:42:21 Wang, Shane <shane.w...@intel.com> wrote:
> Hi all,
> 
> After discussing with TC members and other community guys, we thought 
> March
> 2-4 might not be a good timing for bug smash. So we decided to change 
> the dates to be March 7 - 9 (Monday - Wednesday) in R4. Please join 
> our efforts to fix bugs for OpenStack.
> 
> Thanks.
> --
> Shane
> From: Wang, Shane [mailto:shane.w...@intel.com]
> Sent: Thursday, January 28, 2016 5:12 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka
> 
> Save the Date:
> Global OpenStack Bug Smash
> Wednesday-Friday, March 7-9, 2016
> RSVP by Friday, February 24
> 
> How can you help make the OpenStack Mitaka release stable and bug-free 
> while having fun with your peers? Join Intel, Rackspace, Mirantis, 
> IBM, HP, Huawei, CESI and others in a global bug smash across four 
> continents as we work together. Then, join us later in April in 
> Austin, Texas, U.S.A. at the OpenStack Summit to get re-acquainted & 
> celebrate our accomplishments!
> 
> OUR GOAL
> Our key goal is to collaborate round-the-clock and around the world to 
> fix as many bugs as possible across the wide range of OpenStack 
> projects. In the process, we'll also help onboard and grow the number 
> of OpenStack developers, and increase our collective knowledge of 
> OpenStack tools and processes. To ease collaboration among all of the 
> participants and ensure that core reviews can be conducted promptly, 
> we will use the IRC channel, the mailing list, and Gerrit and enlist core 
> reviewers in the event.
> 
> GET INVOLVED
> Simply choose a place near you-and register by Friday, February 24.
> Registration is free, and we encourage you to invite others who may be 
> interested.
> 
> * Australia
> * China
> * India
> 
> * Russia
> * United Kingdom
> * United States
> 
> 
> Visit the link below for additional details:
> https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka
> 
> Come make the Mitaka release a grand success through your 
> contributions, and ease the journey for newcomers!
> 
> Regards.
> --
> OpenStack Bug Smash team


__
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] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-02-06 Thread Wang, Shane
Hi Jeremy,

You are over worried about the new contributors. We are going to limit the 
number of attendees, and from my experience and knowledge, most of developers 
who join bug smash are old and experienced OpenStack developers, and they 
already have ATC codes. On the other hand, if those events don't exist, you are 
not able to stop new contributors from submitting and merging individual 
patches or fixes. You might set a deadline of sending the ATC codes - say some 
Release Candidate.

Regards.
--
Shane
-Original Message-
From: Jeremy Stanley [mailto:fu...@yuggoth.org] 
Sent: Saturday, February 06, 2016 5:25 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

On 2016-02-05 03:42:21 + (+), Wang, Shane wrote:
> After discussing with TC members and other community guys, we thought 
> March 2-4 might not be a good timing for bug smash. So we decided to 
> change the dates to be March 7 - 9 (Monday - Wednesday) in R4. Please 
> join our efforts to fix bugs for OpenStack.

It's worth pointing out that this puts the event well after Mitaka feature 
freeze, which is traditionally when we stop sending Summit registration 
discount codes to new contributors to the release.
Presumably that's not anyone's reason for participating in such an event, but 
just wanted to clarify it's my understanding that our conference organizers 
aren't prepared for the logistical challenges of generating extra codes for Bug 
Smash participants who haven't otherwise contributed to the release so close to 
the Summit dates.
--
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


Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-02-05 Thread Jeremy Stanley
On 2016-02-05 03:42:21 + (+), Wang, Shane wrote:
> After discussing with TC members and other community guys, we
> thought March 2-4 might not be a good timing for bug smash. So we
> decided to change the dates to be March 7 - 9 (Monday - Wednesday)
> in R4. Please join our efforts to fix bugs for OpenStack.

It's worth pointing out that this puts the event well after Mitaka
feature freeze, which is traditionally when we stop sending Summit
registration discount codes to new contributors to the release.
Presumably that's not anyone's reason for participating in such an
event, but just wanted to clarify it's my understanding that our
conference organizers aren't prepared for the logistical challenges
of generating extra codes for Bug Smash participants who haven't
otherwise contributed to the release so close to the Summit dates.
-- 
Jeremy Stanley


signature.asc
Description: Digital 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


Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-02-05 Thread Robert Simai
All,

I like to announce that SUSE joins these efforts, we're going to provide rooms 
in Nuremberg/Germany and have developers from our side available to contribute 
to the Mitaka bug smash.

The etherpad page [1] is updated, the etherpad page for the location [2] is 
under construction. Hope to see some of you in Nuremberg!

[1] https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka
[2] https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka-Nuremberg

-- 
Thanks,
   Robert

On Friday 05 February 2016, 03:42:21 Wang, Shane <shane.w...@intel.com> wrote:
> Hi all,
> 
> After discussing with TC members and other community guys, we thought March
> 2-4 might not be a good timing for bug smash. So we decided to change the
> dates to be March 7 - 9 (Monday - Wednesday) in R4. Please join our efforts
> to fix bugs for OpenStack.
> 
> Thanks.
> --
> Shane
> From: Wang, Shane [mailto:shane.w...@intel.com]
> Sent: Thursday, January 28, 2016 5:12 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka
> 
> Save the Date:
> Global OpenStack Bug Smash
> Wednesday-Friday, March 7-9, 2016
> RSVP by Friday, February 24
> 
> How can you help make the OpenStack Mitaka release stable and bug-free while
> having fun with your peers? Join Intel, Rackspace, Mirantis, IBM, HP,
> Huawei, CESI and others in a global bug smash across four continents as we
> work together. Then, join us later in April in Austin, Texas, U.S.A. at the
> OpenStack Summit to get re-acquainted & celebrate our accomplishments!
> 
> OUR GOAL
> Our key goal is to collaborate round-the-clock and around the world to fix
> as many bugs as possible across the wide range of OpenStack projects. In
> the process, we'll also help onboard and grow the number of OpenStack
> developers, and increase our collective knowledge of OpenStack tools and
> processes. To ease collaboration among all of the participants and ensure
> that core reviews can be conducted promptly, we will use the IRC channel,
> the mailing list, and Gerrit and enlist core reviewers in the event.
> 
> GET INVOLVED
> Simply choose a place near you-and register by Friday, February 24.
> Registration is free, and we encourage you to invite others who may be
> interested.
> 
> * Australia
> * China
> * India
> 
> * Russia
> * United Kingdom
> * United States
> 
> 
> Visit the link below for additional details:
> https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka
> 
> Come make the Mitaka release a grand success through your contributions, and
> ease the journey for newcomers!
> 
> Regards.
> --
> OpenStack Bug Smash team


__
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] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-02-04 Thread Wang, Shane
Hi all,

After discussing with TC members and other community guys, we thought March 2-4 
might not be a good timing for bug smash. So we decided to change the dates to 
be March 7 - 9 (Monday - Wednesday) in R4.
Please join our efforts to fix bugs for OpenStack.

Thanks.
--
Shane
From: Wang, Shane [mailto:shane.w...@intel.com]
Sent: Thursday, January 28, 2016 5:12 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

Save the Date:
Global OpenStack Bug Smash
Wednesday-Friday, March 7-9, 2016
RSVP by Friday, February 24

How can you help make the OpenStack Mitaka release stable and bug-free while 
having fun with your peers? Join Intel, Rackspace, Mirantis, IBM, HP, Huawei, 
CESI and others in a global bug smash across four continents as we work 
together. Then, join us later in April in Austin, Texas, U.S.A. at the 
OpenStack Summit to get re-acquainted & celebrate our accomplishments!

OUR GOAL
Our key goal is to collaborate round-the-clock and around the world to fix as 
many bugs as possible across the wide range of OpenStack projects. In the 
process, we'll also help onboard and grow the number of OpenStack developers, 
and increase our collective knowledge of OpenStack tools and processes. To ease 
collaboration among all of the participants and ensure that core reviews can be 
conducted promptly, we will use the IRC channel, the mailing list, and Gerrit 
and enlist core reviewers in the event.

GET INVOLVED
Simply choose a place near you-and register by Friday, February 24. 
Registration is free, and we encourage you to invite others who may be 
interested.

* Australia
* China
* India

* Russia
* United Kingdom
* United States


Visit the link below for additional details:
https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka

Come make the Mitaka release a grand success through your contributions, and 
ease the journey for newcomers!

Regards.
--
OpenStack Bug Smash team

__
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] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-01-29 Thread Doug Hellmann
Excerpts from Wang, Shane's message of 2016-01-28 09:11:36 +:
> Save the Date:
> Global OpenStack Bug Smash
> Wednesday-Friday, March 2-4, 2016
> RSVP by Friday, February 19
> 
> How can you help make the OpenStack Mitaka release stable and bug-free while 
> having fun with your peers? Join Intel, Rackspace, Mirantis, IBM, HP, Huawei, 
> CESI and others in a global bug smash across four continents as we work 
> together. Then, join us later in April in Austin, Texas, U.S.A. at the 
> OpenStack Summit to get re-acquainted & celebrate our accomplishments!
> 
> OUR GOAL
> Our key goal is to collaborate round-the-clock and around the world to fix as 
> many bugs as possible across the wide range of OpenStack projects. In the 
> process, we'll also help onboard and grow the number of OpenStack developers, 
> and increase our collective knowledge of OpenStack tools and processes. To 
> ease collaboration among all of the participants and ensure that core reviews 
> can be conducted promptly, we will use the IRC channel, the mailing list, and 
> Gerrit and enlist core reviewers in the event.
> 
> GET INVOLVED
> Simply choose a place near you-and register by Friday, February 19. 
> Registration is free, and we encourage you to invite others who may be 
> interested.
> 
> *   Australia
> *   China
> *   India   *   Russia
> *   United Kingdom
> *   United States
> 
> Visit the link below for additional details:
> https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka
> 
> Come make the Mitaka release a grand success through your contributions, and 
> ease the journey for newcomers!
> 
> Regards.

I know there is quite a lot of concern in the community about this
event being scheduled for the same dates as our feature freeze and
the Mitaka 3 milestone. I am working with the organizers to try to
reschedule. We will post more info here when we have it.

Doug

__
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] [bug-smash] Global OpenStack Bug Smash Mitaka

2016-01-28 Thread Wang, Shane
Save the Date:
Global OpenStack Bug Smash
Wednesday-Friday, March 2-4, 2016
RSVP by Friday, February 19

How can you help make the OpenStack Mitaka release stable and bug-free while 
having fun with your peers? Join Intel, Rackspace, Mirantis, IBM, HP, Huawei, 
CESI and others in a global bug smash across four continents as we work 
together. Then, join us later in April in Austin, Texas, U.S.A. at the 
OpenStack Summit to get re-acquainted & celebrate our accomplishments!

OUR GOAL
Our key goal is to collaborate round-the-clock and around the world to fix as 
many bugs as possible across the wide range of OpenStack projects. In the 
process, we'll also help onboard and grow the number of OpenStack developers, 
and increase our collective knowledge of OpenStack tools and processes. To ease 
collaboration among all of the participants and ensure that core reviews can be 
conducted promptly, we will use the IRC channel, the mailing list, and Gerrit 
and enlist core reviewers in the event.

GET INVOLVED
Simply choose a place near you-and register by Friday, February 19. 
Registration is free, and we encourage you to invite others who may be 
interested.

*   Australia
*   China
*   India   *   Russia
*   United Kingdom
*   United States

Visit the link below for additional details:
https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka

Come make the Mitaka release a grand success through your contributions, and 
ease the journey for newcomers!

Regards.
--
OpenStack Bug Smash team

__
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