From mrhillsman at gmail.com Fri May 4 16:58:17 2018 From: mrhillsman at gmail.com (Melvin Hillsman) Date: Fri, 04 May 2018 16:58:17 +0000 Subject: [User-committee] Reminder: UC Meeting Monday 1800UTC Message-ID: Hey everyone, Please see https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee for UC meeting info and add additional agenda items if needed. -- Kind regards, Melvin Hillsman mrhillsman at gmail.com mobile: (832) 264-2646 -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Mon May 7 20:45:25 2018 From: amy at demarco.com (Amy Marrich) Date: Mon, 7 May 2018 15:45:25 -0500 Subject: [User-committee] OpenStack User Survey Message-ID: Hi everyone, If you’re running OpenStack, please participate in the User Survey to share more about your technology implementations and provide feedback for the community. Please help us spread the word. We're trying to gather as much real-world deployment data as possible to share back with both the operator and developer communities. We have made it easier to complete, and the survey is* now available in 7 languages*—English, German, Indonesian, Japanese, Korean, traditional Chinese and simplified Chinese. Based on feedback from the operator community, we are only conducting one survey this year, collecting submissions until early August. The report will then be published in October prior to the Berlin Summit If you would like OpenStack user data in the meantime, check out the analytics dashboard 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 *Friday, August 3 at 23:59 UTC.* - You can login and complete the OpenStack User Survey here: 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 - Help us promote the User Survey: https://twitter.com/OpenStack/status/ 993589356312088577 Please let me know if you have any questions. Cheers, Amy Amy Marrich (spotz) OpenStack User Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From ianyrchoi at gmail.com Fri May 11 02:31:43 2018 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Fri, 11 May 2018 11:31:43 +0900 Subject: [User-committee] Fwd: OpenStack User Survey In-Reply-To: References: Message-ID: <10af741f-c5bb-6b3f-2da3-108982dd962b@gmail.com> Yeah! Thanks a lot for sharing this. I now would like to forward this good news to I18n mailing list. Translators, translated user survey is currently available :) Thanks a lot for translation efforts. And if someone would like to contribute user survey translation for fixing incorrect translation or for other languages, you can fix easily through https://translate.openstack.org/project/view/openstack-user-survey or please contact to I18n team if anyone has questions on translation issues. With many thanks, /Ian -------- Original Message -------- Subject: [User-committee] OpenStack User Survey Date: Mon, 7 May 2018 15:45:25 -0500 From: Amy Marrich To: openstack-operators , user-committee Hi everyone, If you’re running OpenStack, please participate in the User Survey  to share more about your technology implementations and provide feedback for the community. Please help us spread the word. We're trying to gather as much real-world deployment data as possible to share back with both the operator and developer communities. We have made it easier to complete, and the survey is* now available in 7 languages*—English, German, Indonesian, Japanese, Korean, traditional Chinese and simplified Chinese. Based on feedback from the operator community, we are only conducting one survey this year, collecting submissions until early August. The report will then be published in October prior to the Berlin Summit   If you would like OpenStack user data in the meantime, check out the analytics dashboard 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 *Friday, August 3 at 23:59 UTC.* * You can login and complete the OpenStack User Survey here: 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 * Help us promote the User Survey: https://twitter.com/OpenStack/status/993589356312088577 Please let me know if you have any questions. Cheers, Amy Amy Marrich (spotz) OpenStack User Committee -------------- next part -------------- _______________________________________________ User-committee mailing list User-committee at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee From mvanwink at rackspace.com Wed May 16 18:21:26 2018 From: mvanwink at rackspace.com (Matt Van Winkle) Date: Wed, 16 May 2018 18:21:26 +0000 Subject: [User-committee] FW: OpenStack NA User Group Scorecard In-Reply-To: <1634c401e0b.1070e113f471034.5005340425275563214@openstacksandiego.org> References: <16024e9f443.1240e7b8a376387.4300952693164275133@openstacksandiego.org> <1634c1fa7e5.10b9244f1466938.1440470362351010696@openstacksandiego.org> <1634c401e0b.1070e113f471034.5005340425275563214@openstacksandiego.org> Message-ID: Forwarding this as requested by John VW From: John Studarus Date: Thursday, May 10, 2018 at 5:52 PM To: Matt Van Winkle , MelvinHillsman , amy Subject: Fwd: OpenStack NA User Group Scorecard Adding Matt. Feel free to forward to the rest of the user committee. John ---- John Studarus - OpenStack Ambassador - John at OpenStackSanDiego.org ============ Forwarded message ============ From : John Studarus To : "melvinhillsman", "amy" Date : Thu, 10 May 2018 15:15:33 -0700 Subject : Fwd: OpenStack NA User Group Scorecard ============ Forwarded message ============ I put this report card together last December showing the current state of affairs across the US OpenStack meetup groups (basically that the majority of groups are defunct and things are only getting worse). At the time, I sent it to the foundation staff but I really think the members of the user committee should be aware of the status. Chicago going defunct last year was the start. Since then, NY and DC went silent and last month, the LA organizer stepped down with no replacement in sight. I've been keeping several groups alive (life support) by running a road show across San Diego, New York, Chicago, and NoVA. Unfortunately, this is a unfunded initiative that isn't feasible in the long term. In general, the groups have been disappearing since it is tough for organizers to promote the groups, find space/funding to run the group and find speakers/content to present. Then, once a group is up and running, the organizers changes careers (i.e. a sales engineer switching out of cloud sales) and the group gets dropped. In general, the user groups/meetup groups need help in the following to address these issues: * Lack of a central working User Group Website - The OpenStack "Groups" website doesn't have a critical mass of users, is not a draw of new users and has a number of technical issues with a lack of technical support available (the website developer has since moved on). Organizers instead pay for Meetup groups out their pocket fragmenting the user base. And once an organizer leaves, the group disappears. The CNCF provides organizers with paid meetup accounts that are under the greater CNCF meetup umbrella account. We'd like to see a similar model. This would solve the problem of groups disappearing when the organizer changes careers. * Speaker Bureau Searching - We'd like to see the Speaker Bureau have some sort of search by city/state/zip code area so that meetups can find speakers. Right now, the smallest granularity is by country which doesn't help a someone in SoCal find a local speaker. * Funding - We'd like to see funding for the groups that is commensurate with the number of group events and members. Currently, each group receives $500 for a yearly birthday party regardless of the size of the group or the number of events. This could include covering expenses for space. * Content - Well put together content (other than marketing slides) - perhaps hands on workshops - put together by the Foundation or through Foundation outreach, that local organizers can present. This is what I've been doing for the four groups I've been running. I put together the content once and then present it across the four groups. Let me know your thoughts! I've of discussions with the Foundation staff through the year and longer but these core issues remain. I'm hoping you might have some thoughts on how we can push this along. John ---- John Studarus - OpenStack Ambassador - John at OpenStackSanDiego.org ============ Forwarded message ============ From : John Studarus > To : "Sonia Ramza">, "lnamphy">, "Shilla Saebi"> Date : Mon, 04 Dec 2017 20:23:20 -0800 Subject : OpenStack NA User Group Scorecard ============ Forwarded message ============ Here are some statics on the US OpenStack user groups. This information was gathered from groups.openstack.org and meetup.com. Having good measurements of our current situation is crucial in determining how to proceed. The statistics tell us a lot. Chicago being abandoned is the tip of the iceberg. After gathering the statistics, it is apparent that NY, Seattle, and North Carolina will be next. Since it is unclear if the Foundation is willing to step in and support the groups, we need to figure out an alternate funding strategy. This may include marketing out to other interested parties to see if they would be willing to step in and fund these groups. Without some mechanism to cover these meetup costs, these groups will disappear. It is unreasonable to ask organizers to cover fees for multiple groups. I've started contacting these inactive groups and 100% of the responses have been receptive to receiving support. Majority of Groups are Inactive There are quite a few user groups (62%) that aren't active (>= 3 meetups in 2017). 43% didn't meet at all in 2017. Sample size is 37 groups in total. There are a few (3) that no longer exist at all but OpenStack.org lists as existing. The minority of the groups (14 or 38%) are active having at least 3 meetups in 2017. It is easy to see these inactive groups being abandoned in the next 12 months as organizers pass on pay the meetup fees. Large Groups are in Peril There are a number (4) of very large groups (> 900 members) that had zero or one meetup in 2017. This extends to ten user groups with > 300 members that had zero or one meetup in 2017. These groups are in peril of being abandoned unless action is taken to step in and rescue these groups. These groups are in major geographies (NY, Seattle, DC, NoVA, Research Triangle/North Carolina). NY and Seattle, the top two groups in peril of being abandoned, are the 2nd and 3rd largest OpenStack groups (second only to SF/Bay Area). Name Official Ambassador Members 2017 Meetups Count New York Yes Lisa 2229 0 Seattle No Lisa 1565 1 North Carolina No None 1047 1 DC Yes Lisa 979 0 Northern Virginia Yes Shilla 648 2 Philadelphia Yes Lisa 487 0 Houston No Sean Roberts 463 0 Portland (PDX) No Lisa 421 2 Chicago No None 369 0 Baltimore No Lisa 307 0 Here are my suggestions: * Actively step in for the largest of the "in peril" groups and take over the membership fees and leadership before the group defaults * Start recruiting new leadership for these inactive groups * Reach out and provide content to the remaining smaller and delist them if they go insolvent * Raise awareness at the Foundation on the need to support meetup groups (paying fees/Meetup Pro); OR * Gather up funding from outside parties to cover meetup fees through group sponsorships * Push the Foundation to provider a speaker list by US zipcode/state to better provide regional content; OR * Start building a North America speaker bureau broken out by zipcode/state * Rework the Foundation's cloud trial program for longer durations than 30 days to better support the user groups; OR * Contact North American public OpenStack providers (Rackspace, OVH, Packet) to see about direct support for the user groups * Purge the dead groups from OpenStack.org * Remove ex-Ambassadors from the listing. Most have moved on from OpenStack. * Get the Foundation to fix the functionality in groups.openstack.org. Seems that various workflows are broken (web errors) including the ability to request/approve new groups. * Get the Foundation to provide access to the email/contact info of the listed organizers * Revisit the definition of "Official" user-group and the process of how and why a group should become Official. What's the value? Stickers? * Push "Squatters" (organizers sitting on OpenStack groups but not using them) to release the group to organizers willing to host events I'm sure everyone is busy through the end of the year but the numbers are interesting. We can pickup in the new year and discuss how to proceed. John -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenStack US Group Scorecard.xlsx Type: application/octet-stream Size: 12693 bytes Desc: OpenStack US Group Scorecard.xlsx URL: From lauren at openstack.org Wed May 16 21:16:29 2018 From: lauren at openstack.org (Lauren Sell) Date: Wed, 16 May 2018 16:16:29 -0500 Subject: [User-committee] FW: OpenStack NA User Group Scorecard In-Reply-To: References: <16024e9f443.1240e7b8a376387.4300952693164275133@openstacksandiego.org> <1634c1fa7e5.10b9244f1466938.1440470362351010696@openstacksandiego.org> <1634c401e0b.1070e113f471034.5005340425275563214@openstacksandiego.org> Message-ID: Thanks Matt and John. All good topics to raise, and I believe are represented on the agenda Ashlee has been working on with Ambassadors and User Group leaders for the meeting in Vancouver: https://etherpad.openstack.org/p/YVR-UG-Ambassador For those on the list who are interested in attending, it’s scheduled for Thursday at 2:40 pm in room 207. I think a big discussion topic will be whether the current “groups" site (groups.openstack.org) is useful and worth investing in updating, or if we should go a different route. We’ve been in touch with Meetup and have some proposals for funding MeetupPro ready for discussion next week. FWIW I agree we should revisit the “official” user group criteria. Cheers, Lauren > On May 16, 2018, at 1:21 PM, Matt Van Winkle wrote: > > Forwarding this as requested by John > > VW > > From: John Studarus > > Date: Thursday, May 10, 2018 at 5:52 PM > To: Matt Van Winkle >, MelvinHillsman >, amy > > Subject: Fwd: OpenStack NA User Group Scorecard > > Adding Matt. Feel free to forward to the rest of the user committee. <> > > John > > > ---- > John Studarus - OpenStack Ambassador - John at OpenStackSanDiego.org > > ============ Forwarded message ============ > From : John Studarus > > To : "melvinhillsman">, "amy"> > Date : Thu, 10 May 2018 15:15:33 -0700 > Subject : Fwd: OpenStack NA User Group Scorecard > ============ Forwarded message ============ > >> >> I put this report card together last December showing the current state of affairs across the US OpenStack meetup groups (basically that the majority of groups are defunct and things are only getting worse). At the time, I sent it to the foundation staff but I really think the members of the user committee should be aware of the status. Chicago going defunct last year was the start. Since then, NY and DC went silent and last month, the LA organizer stepped down with no replacement in sight. >> >> I've been keeping several groups alive (life support) by running a road show across San Diego, New York, Chicago, and NoVA. Unfortunately, this is a unfunded initiative that isn't feasible in the long term. >> >> In general, the groups have been disappearing since it is tough for organizers to promote the groups, find space/funding to run the group and find speakers/content to present. Then, once a group is up and running, the organizers changes careers (i.e. a sales engineer switching out of cloud sales) and the group gets dropped. >> >> In general, the user groups/meetup groups need help in the following to address these issues: >> >> * Lack of a central working User Group Website - The OpenStack "Groups" website doesn't have a critical mass of users, is not a draw of new users and has a number of technical issues with a lack of technical support available (the website developer has since moved on). Organizers instead pay for Meetup groups out their pocket fragmenting the user base. And once an organizer leaves, the group disappears. The CNCF provides organizers with paid meetup accounts that are under the greater CNCF meetup umbrella account. We'd like to see a similar model. This would solve the problem of groups disappearing when the organizer changes careers. >> >> * Speaker Bureau Searching - We'd like to see the Speaker Bureau have some sort of search by city/state/zip code area so that meetups can find speakers. Right now, the smallest granularity is by country which doesn't help a someone in SoCal find a local speaker. >> >> * Funding - We'd like to see funding for the groups that is commensurate with the number of group events and members. Currently, each group receives $500 for a yearly birthday party regardless of the size of the group or the number of events. This could include covering expenses for space. >> >> * Content - Well put together content (other than marketing slides) - perhaps hands on workshops - put together by the Foundation or through Foundation outreach, that local organizers can present. This is what I've been doing for the four groups I've been running. I put together the content once and then present it across the four groups. >> >> Let me know your thoughts! I've of discussions with the Foundation staff through the year and longer but these core issues remain. I'm hoping you might have some thoughts on how we can push this along. >> >> John >> >> >> >> >> >> >> >> ---- >> John Studarus - OpenStack Ambassador - John at OpenStackSanDiego.org >> >> ============ Forwarded message ============ >> From : John Studarus > >> To : "Sonia Ramza">, "lnamphy">, "Shilla Saebi"> >> Date : Mon, 04 Dec 2017 20:23:20 -0800 >> Subject : OpenStack NA User Group Scorecard >> ============ Forwarded message ============ >> >> >> >>> Here are some statics on the US OpenStack user groups. This information was gathered from groups.openstack.org and meetup.com . >>> Having good measurements of our current situation is crucial in determining how to proceed. The statistics tell us a lot. >>> >>> Chicago being abandoned is the tip of the iceberg. After gathering the statistics, it is apparent that NY, Seattle, and North Carolina will be next. >>> Since it is unclear if the Foundation is willing to step in and support the groups, we need to figure out an alternate funding strategy. >>> This may include marketing out to other interested parties to see if they would be willing to step in and fund these groups. >>> Without some mechanism to cover these meetup costs, these groups will disappear. It is unreasonable to ask organizers to cover fees for multiple groups. >>> >>> I've started contacting these inactive groups and 100% of the responses have been receptive to receiving support. >>> >>> >>> Majority of Groups are Inactive >>> >>> There are quite a few user groups (62%) that aren't active (>= 3 meetups in 2017). 43% didn't meet at all in 2017. Sample size is 37 groups in total. >>> There are a few (3) that no longer exist at all but OpenStack.org lists as existing. >>> The minority of the groups (14 or 38%) are active having at least 3 meetups in 2017. >>> It is easy to see these inactive groups being abandoned in the next 12 months as organizers pass on pay the meetup fees. >>> >>> Large Groups are in Peril >>> >>> There are a number (4) of very large groups (> 900 members) that had zero or one meetup in 2017. >>> This extends to ten user groups with > 300 members that had zero or one meetup in 2017. >>> These groups are in peril of being abandoned unless action is taken to step in and rescue these groups. >>> These groups are in major geographies (NY, Seattle, DC, NoVA, Research Triangle/North Carolina). >>> NY and Seattle, the top two groups in peril of being abandoned, are the 2nd and 3rd largest OpenStack groups (second only to SF/Bay Area). >>> >>> >>> Name >>> Official >>> Ambassador >>> Members >>> 2017 Meetups Count >>> New York >>> Yes >>> Lisa >>> 2229 >>> 0 >>> Seattle >>> No >>> Lisa >>> 1565 >>> 1 >>> North Carolina >>> No >>> None >>> 1047 >>> 1 >>> DC >>> Yes >>> Lisa >>> 979 >>> 0 >>> Northern Virginia >>> Yes >>> Shilla >>> 648 >>> 2 >>> Philadelphia >>> Yes >>> Lisa >>> 487 >>> 0 >>> Houston >>> No >>> Sean Roberts >>> 463 >>> 0 >>> Portland (PDX) >>> No >>> Lisa >>> 421 >>> 2 >>> Chicago >>> No >>> None >>> 369 >>> 0 >>> Baltimore >>> No >>> Lisa >>> 307 >>> 0 >>> >>> Here are my suggestions: >>> >>> * Actively step in for the largest of the "in peril" groups and take over the membership fees and leadership before the group defaults >>> * Start recruiting new leadership for these inactive groups >>> * Reach out and provide content to the remaining smaller and delist them if they go insolvent >>> * Raise awareness at the Foundation on the need to support meetup groups (paying fees/Meetup Pro); OR >>> * Gather up funding from outside parties to cover meetup fees through group sponsorships >>> * Push the Foundation to provider a speaker list by US zipcode/state to better provide regional content; OR >>> * Start building a North America speaker bureau broken out by zipcode/state >>> * Rework the Foundation's cloud trial program for longer durations than 30 days to better support the user groups; OR >>> * Contact North American public OpenStack providers (Rackspace, OVH, Packet) to see about direct support for the user groups >>> * Purge the dead groups from OpenStack.org >>> * Remove ex-Ambassadors from the listing. Most have moved on from OpenStack. >>> * Get the Foundation to fix the functionality in groups.openstack.org . Seems that various workflows are broken (web errors) including the ability to request/approve new groups. >>> * Get the Foundation to provide access to the email/contact info of the listed organizers >>> * Revisit the definition of "Official" user-group and the process of how and why a group should become Official. What's the value? Stickers? >>> * Push "Squatters" (organizers sitting on OpenStack groups but not using them) to release the group to organizers willing to host events >>> >>> I'm sure everyone is busy through the end of the year but the numbers are interesting. We can pickup in the new year and discuss how to proceed. >>> >>> John > > > > > _______________________________________________ > User-committee mailing list > User-committee at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From Arkady.Kanevsky at dell.com Wed May 16 21:44:28 2018 From: Arkady.Kanevsky at dell.com (Arkady.Kanevsky at dell.com) Date: Wed, 16 May 2018 21:44:28 +0000 Subject: [User-committee] FW: OpenStack NA User Group Scorecard In-Reply-To: References: <16024e9f443.1240e7b8a376387.4300952693164275133@openstacksandiego.org> <1634c1fa7e5.10b9244f1466938.1440470362351010696@openstacksandiego.org> <1634c401e0b.1070e113f471034.5005340425275563214@openstacksandiego.org> Message-ID: <200b9febd0a94b4e8238e057c3ead8ea@AUSX13MPS308.AMER.DELL.COM> Will be happy to participate in this discussion at the summit. My team is running OpenStack meetups in Boston and Austin. As hype of OpenStack subsided the meetup participation dwindled. From: Lauren Sell [mailto:lauren at openstack.org] Sent: Wednesday, May 16, 2018 4:16 PM To: Matt Van Winkle Cc: user-committee Subject: Re: [User-committee] FW: OpenStack NA User Group Scorecard Thanks Matt and John. All good topics to raise, and I believe are represented on the agenda Ashlee has been working on with Ambassadors and User Group leaders for the meeting in Vancouver: https://etherpad.openstack.org/p/YVR-UG-Ambassador For those on the list who are interested in attending, it’s scheduled for Thursday at 2:40 pm in room 207. I think a big discussion topic will be whether the current “groups" site (groups.openstack.org) is useful and worth investing in updating, or if we should go a different route. We’ve been in touch with Meetup and have some proposals for funding MeetupPro ready for discussion next week. FWIW I agree we should revisit the “official” user group criteria. Cheers, Lauren On May 16, 2018, at 1:21 PM, Matt Van Winkle > wrote: Forwarding this as requested by John VW From: John Studarus > Date: Thursday, May 10, 2018 at 5:52 PM To: Matt Van Winkle >, MelvinHillsman >, amy > Subject: Fwd: OpenStack NA User Group Scorecard Adding Matt. Feel free to forward to the rest of the user committee. John ---- John Studarus - OpenStack Ambassador - John at OpenStackSanDiego.org ============ Forwarded message ============ From : John Studarus > To : "melvinhillsman">, "amy"> Date : Thu, 10 May 2018 15:15:33 -0700 Subject : Fwd: OpenStack NA User Group Scorecard ============ Forwarded message ============ I put this report card together last December showing the current state of affairs across the US OpenStack meetup groups (basically that the majority of groups are defunct and things are only getting worse). At the time, I sent it to the foundation staff but I really think the members of the user committee should be aware of the status. Chicago going defunct last year was the start. Since then, NY and DC went silent and last month, the LA organizer stepped down with no replacement in sight. I've been keeping several groups alive (life support) by running a road show across San Diego, New York, Chicago, and NoVA. Unfortunately, this is a unfunded initiative that isn't feasible in the long term. In general, the groups have been disappearing since it is tough for organizers to promote the groups, find space/funding to run the group and find speakers/content to present. Then, once a group is up and running, the organizers changes careers (i.e. a sales engineer switching out of cloud sales) and the group gets dropped. In general, the user groups/meetup groups need help in the following to address these issues: * Lack of a central working User Group Website - The OpenStack "Groups" website doesn't have a critical mass of users, is not a draw of new users and has a number of technical issues with a lack of technical support available (the website developer has since moved on). Organizers instead pay for Meetup groups out their pocket fragmenting the user base. And once an organizer leaves, the group disappears. The CNCF provides organizers with paid meetup accounts that are under the greater CNCF meetup umbrella account. We'd like to see a similar model. This would solve the problem of groups disappearing when the organizer changes careers. * Speaker Bureau Searching - We'd like to see the Speaker Bureau have some sort of search by city/state/zip code area so that meetups can find speakers. Right now, the smallest granularity is by country which doesn't help a someone in SoCal find a local speaker. * Funding - We'd like to see funding for the groups that is commensurate with the number of group events and members. Currently, each group receives $500 for a yearly birthday party regardless of the size of the group or the number of events. This could include covering expenses for space. * Content - Well put together content (other than marketing slides) - perhaps hands on workshops - put together by the Foundation or through Foundation outreach, that local organizers can present. This is what I've been doing for the four groups I've been running. I put together the content once and then present it across the four groups. Let me know your thoughts! I've of discussions with the Foundation staff through the year and longer but these core issues remain. I'm hoping you might have some thoughts on how we can push this along. John ---- John Studarus - OpenStack Ambassador - John at OpenStackSanDiego.org ============ Forwarded message ============ From : John Studarus > To : "Sonia Ramza">, "lnamphy">, "Shilla Saebi"> Date : Mon, 04 Dec 2017 20:23:20 -0800 Subject : OpenStack NA User Group Scorecard ============ Forwarded message ============ Here are some statics on the US OpenStack user groups. This information was gathered from groups.openstack.org and meetup.com. Having good measurements of our current situation is crucial in determining how to proceed. The statistics tell us a lot. Chicago being abandoned is the tip of the iceberg. After gathering the statistics, it is apparent that NY, Seattle, and North Carolina will be next. Since it is unclear if the Foundation is willing to step in and support the groups, we need to figure out an alternate funding strategy. This may include marketing out to other interested parties to see if they would be willing to step in and fund these groups. Without some mechanism to cover these meetup costs, these groups will disappear. It is unreasonable to ask organizers to cover fees for multiple groups. I've started contacting these inactive groups and 100% of the responses have been receptive to receiving support. Majority of Groups are Inactive There are quite a few user groups (62%) that aren't active (>= 3 meetups in 2017). 43% didn't meet at all in 2017. Sample size is 37 groups in total. There are a few (3) that no longer exist at all but OpenStack.org lists as existing. The minority of the groups (14 or 38%) are active having at least 3 meetups in 2017. It is easy to see these inactive groups being abandoned in the next 12 months as organizers pass on pay the meetup fees. Large Groups are in Peril There are a number (4) of very large groups (> 900 members) that had zero or one meetup in 2017. This extends to ten user groups with > 300 members that had zero or one meetup in 2017. These groups are in peril of being abandoned unless action is taken to step in and rescue these groups. These groups are in major geographies (NY, Seattle, DC, NoVA, Research Triangle/North Carolina). NY and Seattle, the top two groups in peril of being abandoned, are the 2nd and 3rd largest OpenStack groups (second only to SF/Bay Area). Name Official Ambassador Members 2017 Meetups Count New York Yes Lisa 2229 0 Seattle No Lisa 1565 1 North Carolina No None 1047 1 DC Yes Lisa 979 0 Northern Virginia Yes Shilla 648 2 Philadelphia Yes Lisa 487 0 Houston No Sean Roberts 463 0 Portland (PDX) No Lisa 421 2 Chicago No None 369 0 Baltimore No Lisa 307 0 Here are my suggestions: * Actively step in for the largest of the "in peril" groups and take over the membership fees and leadership before the group defaults * Start recruiting new leadership for these inactive groups * Reach out and provide content to the remaining smaller and delist them if they go insolvent * Raise awareness at the Foundation on the need to support meetup groups (paying fees/Meetup Pro); OR * Gather up funding from outside parties to cover meetup fees through group sponsorships * Push the Foundation to provider a speaker list by US zipcode/state to better provide regional content; OR * Start building a North America speaker bureau broken out by zipcode/state * Rework the Foundation's cloud trial program for longer durations than 30 days to better support the user groups; OR * Contact North American public OpenStack providers (Rackspace, OVH, Packet) to see about direct support for the user groups * Purge the dead groups from OpenStack.org * Remove ex-Ambassadors from the listing. Most have moved on from OpenStack. * Get the Foundation to fix the functionality in groups.openstack.org. Seems that various workflows are broken (web errors) including the ability to request/approve new groups. * Get the Foundation to provide access to the email/contact info of the listed organizers * Revisit the definition of "Official" user-group and the process of how and why a group should become Official. What's the value? Stickers? * Push "Squatters" (organizers sitting on OpenStack groups but not using them) to release the group to organizers willing to host events I'm sure everyone is busy through the end of the year but the numbers are interesting. We can pickup in the new year and discuss how to proceed. John _______________________________________________ User-committee mailing list User-committee at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Thu May 17 16:00:27 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Thu, 17 May 2018 11:00:27 -0500 Subject: [User-committee] Important UC Related Events in Vancouver Message-ID: <5AFDA71B.1020508@openstack.org> Hi all - Wanted to flag the big events in Vancouver where we could really use at least one, if not all, UC members there to listen/support. Monday afternoon is going to be the busiest. Looking forward to seeing everyone at these sessions :) Cheers, Jimmy Sunday 20, Board Meeting Mon 21, 2:10pm - 2:30pm https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21862/state-of-the-user-committee - Lightning Talk by Melvin & Matt re: SotU for UC Mon 21, 4:20pm - 5:00pm https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21747/opsdevs-one-community - Ops/Devs One Community Mon 21, 5:10pm - 5:40pm https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21788/ops-meetups-team-catch-up-and-ptg-merger-discussion - PTG Merger Discussion Monday, May 21, 6:00pm-7:00pm https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21865/ambassador-meet-and-greet-at-the-openinfra-mixer - Meet ambassadors. Have cocktails. Wednesday, May 23, 11:50am-12:35pm https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21876/openstack-ambassador-panel - This is where we're trying to set the agenda for the Ambassador and Community Manager program Thu 24, 7:30am - 9:00am https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21837/user-committee-breakfast-meet-and-greet - UC Breakfast meet & greet From rochelle.grober at huawei.com Fri May 18 00:55:22 2018 From: rochelle.grober at huawei.com (Rochelle Grober) Date: Fri, 18 May 2018 00:55:22 +0000 Subject: [User-committee] [Forum] [all] [Stable] OpenStack is "mature" -- time to get serious on Maintainers -- Session etherpad and food for thought for discussion Message-ID: Folks, TL;DR The last session related to extended releases is: OpenStack is "mature" -- time to get serious on Maintainers It will be in room 220 at 11:00-11:40 The etherpad for the last session in the series on Extended releases is here: https://etherpad.openstack.org/p/YVR-openstack-maintainers-maint-pt3 There are links to info on other communities’ maintainer process/role/responsibilities also, as reference material on how other have made it work (or not). The nitty gritty details: The upcoming Forum is filled with sessions that are focused on issues needed to improve and maintain the sustainability of OpenStack projects for the long term. We have discussion on reducing technical debt, extended releases, fast forward installs, bringing Ops and User communities closer together, etc. The community is showing it is now invested in activities that are often part of “Sustaining Engineering” teams (corporate speak) or “Maintainers (OSS speak). We are doing this; we are thinking about the moving parts to do this; let’s think about the contributors who want to do these and bring some clarity to their roles and the processes they need to be successful. I am hoping you read this and keep these ideas in mind as you participate in the various Forum sessions. Then you can bring the ideas generated during all these discussions to the Maintainers session near the end of the Summit to brainstorm how to visualize and define this new(ish) component of our technical community. So, who has been doing the maintenance work so far? Mostly (mostly) unsung heroes like the Stable Release team, Release team, Oslo team, project liaisons and the community goals champions (yes, moving to py3 is a sustaining/maintenance type of activity). And some operators (Hi, mnaser!). We need to lean on their experience and what we think the community will need to reduce that technical debt to outline what the common tasks of maintainers should be, what else might fall in their purview, and how to partner with them to better serve them. With API lower limits, new tool versions, placement, py3, and even projects reaching “code complete” or “maintenance mode,” there is a lot of work for maintainers to do (I really don’t like that term, but is there one that fits OpenStack’s community?). It would be great if we could find a way to share the load such that we can have part time contributors here. We know that operators know how to cherrypick, test in there clouds, do bug fixes. How do we pair with them to get fixes upstreamed without requiring them to be full on developers? We have a bunch of alumni who have stopped being “cores” and sometimes even developers, but who love our community and might be willing and able to put in a few hours a week, maybe reviewing small patches, providing help with user/ops submitted patch requests, or whatever. They were trusted with +2 and +W in the past, so we should at least be able to trust they know what they know. We would need some way to identify them to Cores, since they would be sort of 1.5 on the voting scale, but…… So, burn out is high in other communities for maintainers. We need to find a way to make sustaining the stable parts of OpenStack sustainable. Hope you can make the talk, or add to the etherpad, or both. The etherpad is very musch still a work in progress (trying to organize it to make sense). If you want to jump in now, go for it, otherwise it should be in reasonable shape for use at the session. I hope we get a good mix of community and a good collection of those who are already doing the job without title. Thanks and see you next week. --rocky ________________________________ 华为技术有限公司 Huawei Technologies Co., Ltd. [Company_logo] Rochelle Grober Sr. Staff Architect, Open Source Office Phone:408-330-5472 Email:rochelle.grober at huawei.com ________________________________  本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5474 bytes Desc: image001.png URL: From lbragstad at gmail.com Fri May 18 21:02:47 2018 From: lbragstad at gmail.com (Lance Bragstad) Date: Fri, 18 May 2018 16:02:47 -0500 Subject: [User-committee] [Forum] [all] [Stable] OpenStack is "mature" -- time to get serious on Maintainers -- Session etherpad and food for thought for discussion In-Reply-To: References: Message-ID: <1d7a6055-df34-c0f6-98a0-d8a8f9cfafa8@gmail.com> Here is the link to the session in case you'd like to add it to your schedule [0]. [0] https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21759/openstack-is-mature-time-to-get-serious-on-maintainers On 05/17/2018 07:55 PM, Rochelle Grober wrote: > > Folks, > >   > > TL;DR > > The last session related to extended releases is: OpenStack is > "mature" -- time to get serious on Maintainers > It will be in room 220 at 11:00-11:40 > > The etherpad for the last session in the series on Extended releases > is here: > > https://etherpad.openstack.org/p/YVR-openstack-maintainers-maint-pt3 > >   > > There are links to info on other communities’ maintainer > process/role/responsibilities also, as reference material on how other > have made it work (or not). > >   > > The nitty gritty details: > >   > > The upcoming Forum is filled with sessions that are focused on issues > needed to improve and maintain the sustainability of OpenStack > projects for the long term.  We have discussion on reducing technical > debt, extended releases, fast forward installs, bringing Ops and User > communities closer together, etc.  The community is showing it is now > invested in activities that are often part of “Sustaining Engineering” > teams (corporate speak) or “Maintainers (OSS speak).  We are doing > this; we are thinking about the moving parts to do this; let’s think > about the contributors who want to do these and bring some clarity to > their roles and the processes they need to be successful.  I am hoping > you read this and keep these ideas in mind as you participate in the > various Forum sessions.  Then you can bring the ideas generated during > all these discussions to the Maintainers session near the end of the > Summit to brainstorm how to visualize and define this new(ish) > component of our technical community. > >   > > So, who has been doing the maintenance work so far?  Mostly (mostly) > unsung heroes like the Stable Release team, Release team, Oslo team, > project liaisons and the community goals champions (yes, moving to py3 > is a sustaining/maintenance type of activity).  And some operators > (Hi, mnaser!).  We need to lean on their experience and what we think > the community will need to reduce that technical debt to outline what > the common tasks of maintainers should be, what else might fall in > their purview, and how to partner with them to better serve them. > >   > > With API lower limits, new tool versions, placement, py3, and even > projects reaching “code complete” or “maintenance mode,” there is a > lot of work for maintainers to do (I really don’t like that term, but > is there one that fits OpenStack’s community?).  It would be great if > we could find a way to share the load such that we can have part time > contributors here.  We know that operators know how to cherrypick, > test in there clouds, do bug fixes.  How do we pair with them to get > fixes upstreamed without requiring them to be full on developers?  We > have a bunch of alumni who have stopped being “cores” and sometimes > even developers, but who love our community and might be willing and > able to put in a few hours a week, maybe reviewing small patches, > providing help with user/ops submitted patch requests, or whatever.  > They were trusted with +2 and +W in the past, so we should at least be > able to trust they know what they know.  We  would need some way to > identify them to Cores, since they would be sort of 1.5 on the voting > scale, but…… > >   > > So, burn out is high in other communities for maintainers.  We need to > find a way to make sustaining the stable parts of OpenStack sustainable. > >   > > Hope you can make the talk, or add to the etherpad, or both.  The > etherpad is very musch still a work in progress (trying to organize it > to make sense).  If you want to jump in now, go for it, otherwise it > should be in reasonable shape for use at the session.  I hope we get a > good mix of community and a good collection of those who are already > doing the job without title. > >   > > Thanks and see you next week. > > --rocky > >   > >   > >   > > ------------------------------------------------------------------------ > > 华为技术有限公司 Huawei Technologies Co., Ltd. > > Company_logo > > Rochelle Grober > > Sr. Staff Architect, Open Source > Office Phone:408-330-5472 > Email:rochelle.grober at huawei.com > > ------------------------------------------------------------------------ > > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁 > 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中 > 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ > This e-mail and its attachments contain confidential information from > HUAWEI, which > is intended only for the person or entity whose address is listed > above. Any use of the > information contained herein in any way (including, but not limited > to, total or partial > disclosure, reproduction, or dissemination) by persons other than the > intended > recipient(s) is prohibited. If you receive this e-mail in error, > please notify the sender by > phone or email immediately and delete it! > >   > > > > _______________________________________________ > User-committee mailing list > User-committee at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5474 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From rochelle.grober at huawei.com Fri May 18 21:07:46 2018 From: rochelle.grober at huawei.com (Rochelle Grober) Date: Fri, 18 May 2018 21:07:46 +0000 Subject: [User-committee] [Forum] [all] [Stable] OpenStack is "mature" -- time to get serious on Maintainers -- Session etherpad and food for thought for discussion In-Reply-To: <1d7a6055-df34-c0f6-98a0-d8a8f9cfafa8@gmail.com> References: <1d7a6055-df34-c0f6-98a0-d8a8f9cfafa8@gmail.com> Message-ID: Thanks, Lance! Also, the more I think about it, the more I think Maintainer has too much baggage to use that term for this role. It really is “continuity” that we are looking for. Continuous important fixes, continuous updates of tools used to produce the SW. Keep this in the back of your minds for the discussion. And yes, this is a discussion to see if we are interested, and only if there is interest, how to move forward. --Rocky From: Lance Bragstad [mailto:lbragstad at gmail.com] Sent: Friday, May 18, 2018 2:03 PM To: Rochelle Grober ; openstack-dev ; openstack-operators ; user-committee Subject: Re: [User-committee] [Forum] [all] [Stable] OpenStack is "mature" -- time to get serious on Maintainers -- Session etherpad and food for thought for discussion Here is the link to the session in case you'd like to add it to your schedule [0]. [0] https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21759/openstack-is-mature-time-to-get-serious-on-maintainers On 05/17/2018 07:55 PM, Rochelle Grober wrote: Folks, TL;DR The last session related to extended releases is: OpenStack is "mature" -- time to get serious on Maintainers It will be in room 220 at 11:00-11:40 The etherpad for the last session in the series on Extended releases is here: https://etherpad.openstack.org/p/YVR-openstack-maintainers-maint-pt3 There are links to info on other communities’ maintainer process/role/responsibilities also, as reference material on how other have made it work (or not). The nitty gritty details: The upcoming Forum is filled with sessions that are focused on issues needed to improve and maintain the sustainability of OpenStack projects for the long term. We have discussion on reducing technical debt, extended releases, fast forward installs, bringing Ops and User communities closer together, etc. The community is showing it is now invested in activities that are often part of “Sustaining Engineering” teams (corporate speak) or “Maintainers (OSS speak). We are doing this; we are thinking about the moving parts to do this; let’s think about the contributors who want to do these and bring some clarity to their roles and the processes they need to be successful. I am hoping you read this and keep these ideas in mind as you participate in the various Forum sessions. Then you can bring the ideas generated during all these discussions to the Maintainers session near the end of the Summit to brainstorm how to visualize and define this new(ish) component of our technical community. So, who has been doing the maintenance work so far? Mostly (mostly) unsung heroes like the Stable Release team, Release team, Oslo team, project liaisons and the community goals champions (yes, moving to py3 is a sustaining/maintenance type of activity). And some operators (Hi, mnaser!). We need to lean on their experience and what we think the community will need to reduce that technical debt to outline what the common tasks of maintainers should be, what else might fall in their purview, and how to partner with them to better serve them. With API lower limits, new tool versions, placement, py3, and even projects reaching “code complete” or “maintenance mode,” there is a lot of work for maintainers to do (I really don’t like that term, but is there one that fits OpenStack’s community?). It would be great if we could find a way to share the load such that we can have part time contributors here. We know that operators know how to cherrypick, test in there clouds, do bug fixes. How do we pair with them to get fixes upstreamed without requiring them to be full on developers? We have a bunch of alumni who have stopped being “cores” and sometimes even developers, but who love our community and might be willing and able to put in a few hours a week, maybe reviewing small patches, providing help with user/ops submitted patch requests, or whatever. They were trusted with +2 and +W in the past, so we should at least be able to trust they know what they know. We would need some way to identify them to Cores, since they would be sort of 1.5 on the voting scale, but…… So, burn out is high in other communities for maintainers. We need to find a way to make sustaining the stable parts of OpenStack sustainable. Hope you can make the talk, or add to the etherpad, or both. The etherpad is very musch still a work in progress (trying to organize it to make sense). If you want to jump in now, go for it, otherwise it should be in reasonable shape for use at the session. I hope we get a good mix of community and a good collection of those who are already doing the job without title. Thanks and see you next week. --rocky ________________________________ 华为技术有限公司 Huawei Technologies Co., Ltd. [Company_logo] Rochelle Grober Sr. Staff Architect, Open Source Office Phone:408-330-5472 Email:rochelle.grober at huawei.com ________________________________  本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! _______________________________________________ User-committee mailing list User-committee at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5474 bytes Desc: image001.png URL: From amy at demarco.com Sun May 20 16:18:22 2018 From: amy at demarco.com (Amy Marrich) Date: Sun, 20 May 2018 09:18:22 -0700 Subject: [User-committee] OPs and User Sessions at Summit Message-ID: <614A0623-1D14-43FA-8EC4-AE71FCEA4BCD@demarco.com> Hi everyone, There are a lot of great events and sessions going on at Summit next week that I wanted to bring your attention to! Forum sessions are extremely important for starting and continuing conversations and really are a can't miss! For those of you who may not know what the forum is, it’s the opportunities for operators and developers to gather together to discuss requirements for the release, provide feedback and have strategic discussions. Amy (spotz) User Committee Diversity WG Chair Sunday, May 20 - All day Board Meeting Sunday, May 20 @6:00 - 8:00pm https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21791/weareopenstack-diversity-happy-hour-sponsored-by-red-hat-rsvp-required - Diversity Happy Hour Monday, May 21 @2:10 - 2:30 https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21862/state-of-the-user-committee - Lightning Talk by Melvin & Matt Monday, May 21 @ 2:20 https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21712/first-contact-sig-operator-inclusion - First Contact SIG Operator Inclusion Monday, May 21 @ 4:20 https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21747/opsdevs-one-community - Ops/Devs One Community Monday, May 21 @5:10pm - 5: https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21788/ops-meetups-team-catch-up-and-ptg-merger-discussion - PTG Merger Discussion Monday, May 21, 6:00pm-7:00pm https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21865/ambassador-meet-and-greet-at-the-openinfra-mixer - Meet ambassadors. Have cocktails. Tuesday, May 22, 1:50 https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21785/upgrading-openstack-war-stories - Upgrading War Stories, Wednesday, May 23 @ 5:30 https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21725/openstack-operators-community-documentation - OpenStack Operators Community Documentation Thursday May 24 @ 9:00 and 9:50amam https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21721/extended-maintenance-part-i-past-present-and-future - Extended Maintenance: Parts I and II -------------- next part -------------- An HTML attachment was scrubbed... URL: From jean-daniel.bonnetot at corp.ovh.com Thu May 24 23:47:36 2018 From: jean-daniel.bonnetot at corp.ovh.com (Jean-Daniel Bonnetot) Date: Thu, 24 May 2018 23:47:36 +0000 Subject: [User-committee] [publiccloud-wg][passport] hosting workshops for user groups Message-ID: Hi, Some discussions and interests around Passport program are about providing free resources for workshops. Many ambassadors report they often need 101 content for new comers and workshops are really interesting actions they can handle. We (Passport program member) agreed on the idea that providing token on events is a good second step. I do that with OVH infra since a long time and it works really well and it's a good opportunities to promote OpenStack in the same time that having new user. We should focus on that for or next meetings. What do you think? Jean-Daniel Bonnetot ovh.com | @pilgrimstack From mrhillsman at gmail.com Fri May 25 03:07:09 2018 From: mrhillsman at gmail.com (Melvin Hillsman) Date: Thu, 24 May 2018 20:07:09 -0700 Subject: [User-committee] [publiccloud-wg][passport] hosting workshops for user groups In-Reply-To: References: Message-ID: Personally I think this is a good way to make an immediate impact as it seems to be low hanging fruit. Possibly it makes sense to use this thread as a way to curate the first "meetup in a box" which would be a workshop on Getting Started with OpenStack. I do not know how much we want to go with a getting started with OpenStack workshop but maybe depending on how long the meetup is, if a workshop I would think maybe a couple of hours so... Something for a general overview - https://www.youtube.com/watch?v=8kADjGCuSVI - which could get folks familiar with where OpenStack fits in. Could ask Ben for the deck and permission to reference him as you present the content in your own way. Maybe like a 30 minute intro and 15 minute q/a. Move on to something like https://github.com/PacktPublishing/OpenStack-Cloud-Computing-Cookbook-Fourth-Edition which could be used as a workshop manual with one pdf copy the UG leader has as the "instructor"/leader of the workshop. There could be other collateral as part of this one meetup in a box like a half page push card/flyer with general information on front and back like groups.o.o, docs.o.o, o.o/community, etc. X number of passcodes or one to rule them all. Just some thoughts to keep the conversation going. On Thu, May 24, 2018 at 4:47 PM, Jean-Daniel Bonnetot < jean-daniel.bonnetot at corp.ovh.com> wrote: > Hi, > > Some discussions and interests around Passport program are about providing > free resources for workshops. > Many ambassadors report they often need 101 content for new comers and > workshops are really interesting actions they can handle. > > We (Passport program member) agreed on the idea that providing token on > events is a good second step. > > I do that with OVH infra since a long time and it works really well and > it's a good opportunities to promote OpenStack in the same time that having > new user. > > We should focus on that for or next meetings. What do you think? > > Jean-Daniel Bonnetot > ovh.com | @pilgrimstack > > > > > > > _______________________________________________ > User-committee mailing list > User-committee at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee > -- Kind regards, Melvin Hillsman mrhillsman at gmail.com mobile: (832) 264-2646 -------------- next part -------------- An HTML attachment was scrubbed... URL: