Find below the revised user group page based on feedback from last week's planning meeting. There are a few links that still need to be filled in. Definition of a user group: The OpenStack User Groups are informal associations of people around the world that meet to discuss about OpenStack, share knowledge and experiences. These are important entities for the OpenStack project as they help by spreading awareness, recruit developers and users and more. The user groups don't have a direct relation with the OpenStack Foundation even though the members of the user groups can be members of the OpenStack Foundation and/or be a member of the OpenStack User Committee. It is important to note that these user groups include developers, operators, end-users, ecosystem partners, and distribution providers. So we are defining a user more broadly than usual. Starting up a new user group: We have been running a the San Francisco OpenStack user group for over two and half years (since OpenStack was formed) and we want to provide some guidance. The questions and answers below should help guide you to your happy user group place. Some user group owners that are willing to mentor new user groups and find that list here <-link here->. 1. Join the OpenStack Community: Add yourself to openstack-community mailing list 2. User Group List: Will your group be unique or can you lend your time to an existing user group rather than creating a new one? It takes a lot of work to start and operate a well-run user group. You could instead focus your time in helping an existing user group. Look here for existing OpenStack user groups http://wiki.openstack.org/OpenStackUserGroups. 3. Get help: Make sure that you get an additional person to help you and act as a backup, so if you drop out for any reason, someone else will be there to take your place. 4. Audience: Who do you want to attract to your user group meetings? Figure out from below what attributes you are interested in. The OpenStack User Committee has defined different user attributes as roles, types of organizations, market segments, and geographies. Find the attributes and values here https://docs.google.com/a/yahoo-inc.com/document/d/1yD8TfqUik2dt5xo_jMVHMl7t.... We need to define another attribute OpenStack skill level. We assume there are three skill levels: beginner, intermediate, and advanced. * Beginner: If you want to attract new users to OpenStack then you will want to discuss the architecture and the basics of how to use OpenStack. Mirantis has put together a good workflow presentation, review it here http://www.slideshare.net/mirantis/openstack-cloud-request-flow. You can create your own standard slidedeck as a speaking guide as well. * Intermediate: We call this our hackathon meetup. Developers and operators that want to understand how to make OpenStack production ready for their organization need a place to discuss developer setups. Review and share topics like details on APIs, where code gets installed, checking in code, and configurations. We call our intermediate level meetups Hackathons. We teach new guys how to use devstack, hold bug squash days, and focus on a blueprints. We are talking about making the first meetup of each month as bug squash competition between user groups for free summit passes and a quarterly install fest. We have plans to create tool kits/slidedeck for bug squash and intall fest. * Advanced: We tend to call this our devOps meetup. Our topics are generally about blueprints, advanced operations, or specific deep dive into part of OpenStack like Quantum. We have been discussing the idea of getting the PTLs involved with the Advanced meetups to promote blueprints needing help, status of the project, and anything else the PTL wants to talk about. drive better quality developmentoutreach into python user groupsencourage code partipation, commits 5. Topics: Your topics will your different types of users want to listen and interact with based on the attributes above? You can review these active meetup locations for ideas http://www.meetup.com/openstack/events/past/, http://www.meetup.com/Openstack-Boston/events/past/, http://www.meetup.com/OpenStack-Austin/events/past/, http://www.meetup.com/OpenStack-LA/events/past/ 6. Location: This is critical part of your user group. Find a location that will be there long term. Start by contacting the OpenStack sponsoring companies in your area. Network with other OpenStack interested locals. Contact your local university, small technical colleges, and/or college extensions. Are there any startup sharing locations near you? 7. Materials: There are some basic meeting materials and preparation you will want to go through. Food, drink, security, white boards, projectors, tables and chairs are the basics. The location you secured may have a few of these things, but don't assume they do. Consider after-hours HVAC, lighting, and security. A small room can get hot, very quickly with the air conditioning turned off. Sometimes our security forgets and remotely locks our doors. 8. Sponsorship: You may need to find a sponsor to pay for the location, food, and/or drink. Again, you can hit up your local OpenStack sponsoring company as a first option. Consider ongoing commitment vs onetime event. Encourage long term participation by making sure the sponsor has something to gain through the user group. 9. Speakers: Review the community speaker list here <-link here->, mark the speakers and dates you are interested in, and then contact your proposed speakers for their buyin. If you have your own speaker, feel free to add new speakers to the same list. 10. Publish: The recommended way for publishing your intent to meet is using http://meetup.com. Create a new meetup with the name starting with OpenStack-, follow the example of the past SF Bay OpenStack meetups for content structure and configuration. Our meetups reoccur every one to two weeks. You probably want to create each event one at a time instead. Get attendees by announcing over openstack and openstack community mailing lists, linkedin, twitter, facebook, and/or google groups. Post your user group to the http://wiki.openstack.org/OpenStackUserGroups. Operating a user group: You will need make a checklist of things to do and when. Below is the checklist for the SFBay OpenStack meetups. 1. Establish dates and times at least 6 months in advance 2. Schedule speakers, assistants at least a month in advance 3. Schedule tweets and emails to go out 7, 2, 1, and 0 days before the meetup reminding possible attendees of the meetup. Example below * T-7 day 11:30: @OpenStack hackathon meetup happening next Thursday at #Yahoo Sunnyvale, RSVP http://meetup.com/Openstack, webex avail * T-2 day 11:30: @OpenStack hackathon meetup happening next Thursday at #Yahoo Sunnyvale, RSVP http://meetup.com/Openstack, webex avail * T-1 day 11:30: @OpenStack hackathon meetup happening tomorrow at #Yahoo Sunnyvale, RSVP http://meetup.com/Openstack, webex avail * T-0 day 11:30: @OpenStack hackathon meetup happening today at #Yahoo Sunnyvale, RSVP http://meetup.com/Openstack, webex avail 4. Schedule an email to go out to the openstack-community@ilists.launchpad.net mailing list with the same content 5. Book your meeting space at least 1 month in advance 6. Notify security about the meetup and so they can provide directions so visitors do not get lost 7. Order the food at least 3 days in advance. A good gauge is about 50-70% of the RSVPs actually show up. Better topics get a higher percentage turnout. 8. Prep the room about an hour before the meetup. Check the AV equipment, power strips, seats, food, drink, and white boards are ready to go. 9. Post Meetup: After the meetup, send images [jpg] to <-link here->, video [mpg] to <-link here->, marketing updates to <-link here->, and/or update the User Group page http://wiki.openstack.org/OpenStackUserGroups if necessary. Sean Roberts Infrastructure Strategy seanrob@yahoo-inc.com Direct (408) 349-5234 Mobile (925) 980-4729 701 First Avenue, Sunnyvale, CA, 94089-0703, US Phone (408) 349-3300 Fax (408) 349-3301 [http://forgood.zenfs.com/logos/yahoo.png] On 1/15/13 9:39 AM, "Sean Roberts" <seanrob@yahoo-inc.com<mailto:seanrob@yahoo-inc.com>> wrote: Here is my take on the first agenda item, user group / meetup template, for today's meeting. After we clean it up, this would become part of the http://wiki.openstack.org/OpenStackUserGroups page. Definition of a user group: The OpenStack User Groups are informal associations of people around the world that meet to discuss about OpenStack, share knowledge and experiences. These are important entities for the OpenStack project as they help by spreading awareness, recruit developers and users and more. The user groups don't have a direct relation with the OpenStack Foundation even though the members of the user groups can be members of the OpenStack Foundation and/or be a member of the OpenStack User Committee. Starting up a new user group: When starting a new group, you need to first ask what is the purpose of this group and is there another existing group that already serves these needs? It takes a lot of work to start and operate a well-run user group. You could instead focus your time in helping an existing user group. Make sure that you get an additional person to help you and act as a backup, so if you drop out for any reason, someone else will be there to take your place. We have been running a the San Francisco OpenStack user group for over two and half years (since OpenStack was formed) and we want to provide some guidance. The questions and answers below should help guide you to your happy user group place. Some user group owners that are willing to mentor new user groups and find that list here <-link here-> 1. User Group List: Will your group be unique or can you lend your time to an existing user group rather than creating a new one? Look here for existing OpenStack user groups http://wiki.openstack.org/OpenStackUserGroups 2. Topics: What topics do you want to support? Architecture overview, hacking code, vendor support, production operations, blueprints, an excuse to drink beer, or all of the above? Review these active meetup locations for ideas http://www.meetup.com/openstack/events/past/, http://www.meetup.com/Openstack-Boston/events/past/, http://www.meetup.com/OpenStack-Austin/events/past/, http://www.meetup.com/OpenStack-LA/events/past/ 3. Location: This is critical part of your user group. Find a location that will be there long term. Start with contacting the OpenStack sponsoring companies in your area. Network with other OpenStack interested locals. Contact your local university. Are there any startup sharing locations near you? 4. Materials: There are some basic meeting materials and preparation you will want to go through. Food, drink, security, white boards, projectors, tables and chairs are the basics. The location you secured may have a few of these things, but don't assume they do. 5. Sponsorship: You may need to find a sponsor to pay for the location, food, and/or drink. Again, you can hit up your local OpenStack sponsoring company as a first option. 6. Speakers: Review the community speaker list here <-link here->, mark the speakers and dates you are interested in, and then contact your proposed speakers for their buyin. If you have your own speaker, feel free to add new speakers to the same list. 7. Publish: The recommended way for publishing your intent to meet is using http://meetup.com. Create a new meetup with the name starting with OpenStack, follow the example of the past SF Bay OpenStack meetups for content structure and configuration. Our meetups reoccur every one to two weeks. You probably want to create each event one at a time instead. Post the meetup description and meetup link to the OpenStack User Group community page http://wiki.openstack.org/OpenStackUserGroups 8. Attendees: Get attendees by announcing over openstack and openstack community mailing lists, linkedin, twitter, facebook, and/or google groups. 9. Structure: Structure your meetup through standard slidedeck or templates for each and by three common meetup types. 10. * Beginner: If you want to attract new users to OpenStack then you will want to discuss the architecture and the basics of how to use OpenStack. Mirantis has put together a good workflow presentation, review it here http://www.slideshare.net/mirantis/openstack-cloud-request-flow. You can create your own standard slidedeck as a speaking guide as well. * Intermediate: Developers and operators that want to understand how to make OpenStack production ready for their organization need a place to discuss developer setups. Review and share topics like details on APIs, where code gets installed, checking in code, and configurations. We call our intermediate level meetups Hackathons. We teach new guys how to use devstack, hold bug squash days, and focus on a blueprints. We are talking about making the first meetup of each month as bug squash competition between user groups for free summit passes and a quarterly install fest. We have plans to create tool kits/slidedeck for bug squash and intall fest. * Advanced: We tend to call this our devOps meetup. Our topics are generally about blueprints, advanced operations, or specific deep dive into part of OpenStack like Quantum. We have been discussing the idea of getting the PTLs involved with the Advanced meetups to promote blueprints needing help, status of the project, and anything else the PTL wants to talk about. Operating a user group: You will need make a checklist of things to do and when. Below is the checklist for the SFBay OpenStack meetups. 1. Establish dates and times at least 6 months in advance 2. Schedule speakers, assistants at least a month in advance 3. Schedule tweets and emails to go out 7, 2, 1, and 0 days before the meetup reminding possible attendees of the meetup. Example below * T-7 day 13:00: 17May2012 SF South Bay OpenStack Advanced session meetup with Mike Pittaro Dell, #cloud @openstack RSVP via http://www.meetup.com/openstack/ * T-2 day 13:00: 17May2012 SF South Bay OpenStack Advanced session meetup with Mike Pittaro Dell, #cloud @openstack RSVP via http://www.meetup.com/openstack/ * T-1 day 13:00: 17May2012 SF South Bay OpenStack Advanced session meetup with Mike Pittaro Dell, #cloud @openstack RSVP via http://www.meetup.com/openstack/ * T-0 day 13:00: 17May2012 SF South Bay OpenStack Advanced session meetup with Mike Pittaro Dell, #cloud @openstack RSVP via http://www.meetup.com/openstack/ 4. Schedule an email to go out to the openstack-community@ilists.launchpad.net<mailto:openstack-community@ilists.launchpad.net> mailing list with the same content 5. Book your meeting space at least 1 month in advance 6. Notify security about the meetup and so they can provide directions so visitors do not get lost 7. Order the food at least 3 days in advance. A good gauge is about 50-70% of the RSVPs actually show up. Better topics get a higher percentage turnout. 8. Prep the room about an hour before the meetup. Check the AV equipment, power strips, seats, food, drink, and white boards are ready to go. 9. Post Meetup: After the meetup, send images [jpg] to <-link here->, video [mpg] to <-link here->, marketing updates to <-link here->, and/or update the User Group community page if necessary. Sean Roberts Infrastructure Strategy seanrob@yahoo-inc.com<mailto:seanrob@yahoo-inc.com> Direct (408) 349-5234 Mobile (925) 980-4729 701 First Avenue, Sunnyvale, CA, 94089-0703, US Phone (408) 349-3300 Fax (408) 349-3301 [http://forgood.zenfs.com/logos/yahoo.png] On 1/15/13 7:30 AM, "Yujie Du" <duyujie.dyj@gmail.com<mailto:duyujie.dyj@gmail.com>> wrote: Great! I will add some requirements that our community events needed. 2013/1/15 Stefano Maffulli <stefano@openstack.org<mailto:stefano@openstack.org>> [please join the mailing list and keep the CC limited: there are over 20 people in CC and mailman chokes http://lists.openstack.org/cgi-bin/mailman/listinfo/community] On 01/15/2013 03:15 PM, Andi_Abes@Dell.com<mailto:Andi_Abes@Dell.com> wrote: Feedback I’ve gotten from multiple folks is that it would be useful to make available technical experts on up and coming projects (ceilometer, heat, new quantum services , cinder etc). While in the past I coordinated with project PTL’s to locate local experts, it might be more efficient (and less troubling to PTL’s) to have a community effort around this. If local presence is less than possible, then various collaboration tools could work. This is definitely something we're doing. We have a project at the Foundation to create a 'spaker list' where organisers of events can go and select speakers based on their needs. Basically we're extending the Foundation's Members database to include information about availability to speak at events (with travelling options), topics the speaker is comfortable covering and more. We're also working on a new tool to collect all the information about user groups around the world, to aggregate data in a single place (groups.openstack.org<http://groups.openstack.org>) about existence of a group in a given geographic area (doh!), expertise, events, material produced, etc. Stay tuned for more. We have started tracking feature requests as blueprints on this launchpad project: https://launchpad.net/openstack-community Please add your needs to it. /stef _______________________________________________ Community mailing list Community@lists.openstack.org<mailto:Community@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/community -- --Ben OSI Individual Member OpenStack Foundation Board Member Co-founder and Leader of China OpenStack User Group( COSUG ) Mobile: +86 15921531026 WEIBO: http://weibo.com/u/1716287123<http://www.weibo.com/u/1716287123?from=profile&wvr=4&loc=infweihao> TWITTER: https://twitter.com/ben_Duyujie LINKEDIN: cn.linkedin.com/in/duyujie<http://cn.linkedin.com/in/duyujie>