Jump to: navigation, search

Difference between revisions of "OpenStackUsersGroup/EssexGlobalHackIn"

(fix table: need spaces around times it seems)
Line 31: Line 31:
 
== Planned Events ==
 
== Planned Events ==
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
|< >|UTC
+
|< >|UTC  
| Duration (hours)
+
| Duration (hours)  
| Location
+
| Location  
| URL
+
| URL  
| Local Time
+
| Local Time  
| Site Facilitator
+
| Site Facilitator  
 
|-
 
|-
|< >|
+
|
 
|   
 
|   
 
|   
 
|   
Line 47: Line 47:
 
|   
 
|   
 
|   
 
|   
 +
| Seattle
 
|   
 
|   
 
|   
 
|   
|
+
| of Nebula<<BR>>
 
 
|-
 
|-
 
| 19:00  
 
| 19:00  
| 6
+
| 6  
| San Francisco
+
| San Francisco  
 
| http://www.meetup.com/openstack/events/52682022/  
 
| http://www.meetup.com/openstack/events/52682022/  
| 11:00-17:00  
+
| 11:00-17:00  
| Dallas Kashuba of [[DreamHost|DreamHos]]t
+
| Dallas Kashuba of [[DreamHost|DreamHos]]t  
 
|-
 
|-
 
| 19:00  
 
| 19:00  
| 6
+
| 6  
| Silicon Valley
+
| Silicon Valley  
 
| http://www.meetup.com/openstack/events/52682572/  
 
| http://www.meetup.com/openstack/events/52682572/  
| 11:00-17:00  
+
| 11:00-17:00  
| Sean Roberts of Yahoo
+
| Sean Roberts of Yahoo  
 
|-
 
|-
 
|   
 
|   

Revision as of 04:31, 22 February 2012

Essex OpenStack Global Hack-In

DRAFT - Please email additions and suggestions to lloydostack@gmail.com

Essex is a release focused on improving the integrity of OpenStack, so our first Global Hack-In is right at the start of the release candidate cycle, the start of March. The event is focused on testing and getting familiar with the release and exploring areas outside of your expertise.

Collaborators will be working on resolving high priority bugs, and exploring, reviewing and testing OpenStack Essex.

Activities might include:

  • Bug Triage
  • Patch Review
  • Peer Code Review
  • Ad-hoc Testing of use cases
  • Test Automation

Global

This will be a loosely coupled, highly cohesive global event ;-)

Each event will be organized and ran by the local development user communities. Although, overlapping the timing of the events is desirable, more important is that the timing of the events serve the local communities.

Running an Event

Hosting organizations should expect 15-40 contributors to work at the host's office collaborate on resolving high priority bugs, and exploring, reviewing and testing OpenStack Essex.

The host team should be made up of a site facilitator and a technical host.

  • The site facilitator is responsible for making sure the doors are open (security notified), the lights are on, the temperature is comfortable, washrooms are decent, and there is food and drink.
  • The technical host at a minimum someone who is familiar with devstack and has submitted a valid bug report to OpenStack, so they can at least organize people's exploration and testing around the area they've investigated before.
  • Many hands make light work. It's a great idea to have a backup, and collaborators.

Planned Events

UTC Duration (hours) Location URL Local Time Site Facilitator
Seattle of Nebula<
>
19:00 6 San Francisco http://www.meetup.com/openstack/events/52682022/ 11:00-17:00 Dallas Kashuba of DreamHost
19:00 6 Silicon Valley http://www.meetup.com/openstack/events/52682572/ 11:00-17:00 Sean Roberts of Yahoo