[openstack-community] Speakers Bureau
Hi all - I've recently been hired to work with the Foundation to support the OpenStack web properties. Previously, I was a project lead at Tipit, and was supporting the Foundation in a similar capacity. I'm very familiar with the speaker submission process for the Summit, from start to finish, having worked directly with Todd Morey and the rest of the Foundation crew for the last few summits. I would love to leverage that work and the data we've already collected to help build a speakers bureau for the community. I'll summarize below some of the requirements I've gathered from reviewing all the outstanding requests. Below that, I'll add a few comments about the general development that has already begun. Information that we currently have in Speaker Profile - Date Joined - Country / City of origin - Funded travel - Registered for upcoming Summit - Past OpenStack Summit presentations / related material - Bio - Affiliations / Job history - Opt-In to Speakers Bureau Community Requests for additional information - Areas of expertise* - Prior speaking topics* - Links to previous presentations / event names* - Is the speaker willing to travel? To which regions / countries?* - In which languages is the speaker fluent?* - Professional references - Sponsorship opportunities (travel, food/drink) - Dates of availability / unavailability Contact form* - Name of organizer - Email of organizer - Event name - Format / length - Expected attendance - Date(s) of event - Location - Topic(s) - General Request Add option to Sort / Search - Name - Company - Region, country, city where the speaker lives/works - Areas of expertise As you can see from the first list, the Foundation already collects a fair amount of information when we do our Call for Speakers ahead of each summit. Earlier this month, we began work on the speaker's bureau, leveraging that information. I suggest we focus on getting a minimum viable product out as soon as possible, with the data that we've already collected. I've put an asterisk next to the items that are easy adds. We could aim to get as much of that into a Phase I as possible. There are some more complex pieces (Professional references, Dates of availability / unavailability) that have potential privacy concerns or could complicate things. Additionally, I think we should keep the form as short and simple as possible, so speakers fill it out. IMO we should be cautious about overreaching when asking for data and ensure it's easy for people to manage. My suggestion is to get some of these more simple items out the door so we at least have a searchable list. From there, we can solicit feedback and iterate. Please let me know your thoughts and I look forward to working with everyone! Cheers, Jimmy McArthur
Forgot to add... if you all want to follow along on progress on the public repo: https://github.com/OpenStackweb/openstack-org/commit/65738783ee457c2f36728ec... Thanks again! Jimmy Jimmy McArthur wrote:
Hi all -
I've recently been hired to work with the Foundation to support the OpenStack web properties. Previously, I was a project lead at Tipit, and was supporting the Foundation in a similar capacity. I'm very familiar with the speaker submission process for the Summit, from start to finish, having worked directly with Todd Morey and the rest of the Foundation crew for the last few summits. I would love to leverage that work and the data we've already collected to help build a speakers bureau for the community.
I'll summarize below some of the requirements I've gathered from reviewing all the outstanding requests. Below that, I'll add a few comments about the general development that has already begun.
Information that we currently have in Speaker Profile - Date Joined - Country / City of origin - Funded travel - Registered for upcoming Summit - Past OpenStack Summit presentations / related material - Bio - Affiliations / Job history - Opt-In to Speakers Bureau
Community Requests for additional information - Areas of expertise* - Prior speaking topics* - Links to previous presentations / event names* - Is the speaker willing to travel? To which regions / countries?* - In which languages is the speaker fluent?* - Professional references - Sponsorship opportunities (travel, food/drink) - Dates of availability / unavailability
Contact form* - Name of organizer - Email of organizer - Event name - Format / length - Expected attendance - Date(s) of event - Location - Topic(s) - General Request
Add option to Sort / Search - Name - Company - Region, country, city where the speaker lives/works - Areas of expertise
As you can see from the first list, the Foundation already collects a fair amount of information when we do our Call for Speakers ahead of each summit. Earlier this month, we began work on the speaker's bureau, leveraging that information. I suggest we focus on getting a minimum viable product out as soon as possible, with the data that we've already collected.
I've put an asterisk next to the items that are easy adds. We could aim to get as much of that into a Phase I as possible. There are some more complex pieces (Professional references, Dates of availability / unavailability) that have potential privacy concerns or could complicate things. Additionally, I think we should keep the form as short and simple as possible, so speakers fill it out. IMO we should be cautious about overreaching when asking for data and ensure it's easy for people to manage.
My suggestion is to get some of these more simple items out the door so we at least have a searchable list. From there, we can solicit feedback and iterate.
Please let me know your thoughts and I look forward to working with everyone!
Cheers, Jimmy McArthur _______________________________________________ Community mailing list Community@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/community
Hi Jimmy, Sounds great, as we like to make this speaker tool available for user group leaders as a part of user group tools, can we design an API that helps to consume the speaker data from the openstack.org website? As a practicing user group leader, it is very important for us to make that list filterable by region / country. I think it is much easier to connect local regions first than expect someone from Asia or US to travel to EU. But in a future milestone we should implement a "road trip" feature, if a speaker is going to a trip, he have a good chance to visit local user groups. Brgds, Marton On Thu, Nov 19, 2015 at 8:19 PM Jimmy McArthur <jimmy@openstack.org> wrote:
Forgot to add... if you all want to follow along on progress on the public repo: https://github.com/OpenStackweb/openstack-org/commit/65738783ee457c2f36728ec...
Thanks again!
Jimmy
Jimmy McArthur wrote:
Hi all -
I've recently been hired to work with the Foundation to support the OpenStack web properties. Previously, I was a project lead at Tipit, and was supporting the Foundation in a similar capacity. I'm very familiar with the speaker submission process for the Summit, from start to finish, having worked directly with Todd Morey and the rest of the Foundation crew for the last few summits. I would love to leverage that work and the data we've already collected to help build a speakers bureau for the community.
I'll summarize below some of the requirements I've gathered from reviewing all the outstanding requests. Below that, I'll add a few comments about the general development that has already begun.
Information that we currently have in Speaker Profile - Date Joined - Country / City of origin - Funded travel - Registered for upcoming Summit - Past OpenStack Summit presentations / related material - Bio - Affiliations / Job history - Opt-In to Speakers Bureau
Community Requests for additional information - Areas of expertise* - Prior speaking topics* - Links to previous presentations / event names* - Is the speaker willing to travel? To which regions / countries?* - In which languages is the speaker fluent?* - Professional references - Sponsorship opportunities (travel, food/drink) - Dates of availability / unavailability
Contact form* - Name of organizer - Email of organizer - Event name - Format / length - Expected attendance - Date(s) of event - Location - Topic(s) - General Request
Add option to Sort / Search - Name - Company - Region, country, city where the speaker lives/works - Areas of expertise
As you can see from the first list, the Foundation already collects a fair amount of information when we do our Call for Speakers ahead of each summit. Earlier this month, we began work on the speaker’s bureau, leveraging that information. I suggest we focus on getting a minimum viable product out as soon as possible, with the data that we've already collected.
I've put an asterisk next to the items that are easy adds. We could aim to get as much of that into a Phase I as possible. There are some more complex pieces (Professional references, Dates of availability / unavailability) that have potential privacy concerns or could complicate things. Additionally, I think we should keep the form as short and simple as possible, so speakers fill it out. IMO we should be cautious about overreaching when asking for data and ensure it's easy for people to manage.
My suggestion is to get some of these more simple items out the door so we at least have a searchable list. From there, we can solicit feedback and iterate.
Please let me know your thoughts and I look forward to working with everyone!
Cheers, Jimmy McArthur
_______________________________________________ Community mailing listCommunity@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/community
_______________________________________________ Community mailing list Community@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/community
Marton - thanks for the feedback!
Sounds great, as we like to make this speaker tool available for user group leaders as a part of user group tools, can we design an API that helps to consume the speaker data from the openstack.org <http://openstack.org> website? Great suggestion on the API. I'll add that to the list for a Phase II.
As a practicing user group leader, it is very important for us to make that list filterable by region / country. I think it is much easier to connect local regions first than expect someone from Asia or US to travel to EU. Yes, this will be built into the first rev. But in a future milestone we should implement a "road trip" feature, if a speaker is going to a trip, he have a good chance to visit local user groups. Solid idea. We've thought about tying the page into openstack.org/events. This might be a nice add-on that feature.
Marton
On Thu, Nov 19, 2015 at 8:19 PM Jimmy McArthur <jimmy@openstack.org <mailto:jimmy@openstack.org>> wrote:
Forgot to add... if you all want to follow along on progress on the public repo: https://github.com/OpenStackweb/openstack-org/commit/65738783ee457c2f36728ec...
Thanks again!
Jimmy
Jimmy McArthur wrote:
Hi all -
I've recently been hired to work with the Foundation to support the OpenStack web properties. Previously, I was a project lead at Tipit, and was supporting the Foundation in a similar capacity. I'm very familiar with the speaker submission process for the Summit, from start to finish, having worked directly with Todd Morey and the rest of the Foundation crew for the last few summits. I would love to leverage that work and the data we've already collected to help build a speakers bureau for the community.
I'll summarize below some of the requirements I've gathered from reviewing all the outstanding requests. Below that, I'll add a few comments about the general development that has already begun.
Information that we currently have in Speaker Profile - Date Joined - Country / City of origin - Funded travel - Registered for upcoming Summit - Past OpenStack Summit presentations / related material - Bio - Affiliations / Job history - Opt-In to Speakers Bureau
Community Requests for additional information - Areas of expertise* - Prior speaking topics* - Links to previous presentations / event names* - Is the speaker willing to travel? To which regions / countries?* - In which languages is the speaker fluent?* - Professional references - Sponsorship opportunities (travel, food/drink) - Dates of availability / unavailability
Contact form* - Name of organizer - Email of organizer - Event name - Format / length - Expected attendance - Date(s) of event - Location - Topic(s) - General Request
Add option to Sort / Search - Name - Company - Region, country, city where the speaker lives/works - Areas of expertise
As you can see from the first list, the Foundation already collects a fair amount of information when we do our Call for Speakers ahead of each summit. Earlier this month, we began work on the speaker’s bureau, leveraging that information. I suggest we focus on getting a minimum viable product out as soon as possible, with the data that we've already collected.
I've put an asterisk next to the items that are easy adds. We could aim to get as much of that into a Phase I as possible. There are some more complex pieces (Professional references, Dates of availability / unavailability) that have potential privacy concerns or could complicate things. Additionally, I think we should keep the form as short and simple as possible, so speakers fill it out. IMO we should be cautious about overreaching when asking for data and ensure it's easy for people to manage.
My suggestion is to get some of these more simple items out the door so we at least have a searchable list. From there, we can solicit feedback and iterate.
Please let me know your thoughts and I look forward to working with everyone!
Cheers, Jimmy McArthur _______________________________________________ Community mailing list Community@lists.openstack.org <mailto:Community@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
_______________________________________________ Community mailing list Community@lists.openstack.org <mailto:Community@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
Hi all - Wanted to follow up on this and give you all a first look at the Speakers Bureau. I want to stress that this is a first rev. As we start collecting more data from Speakers, we'll be able to offer a more fully featured Bureau. That said, we've tried to take all the major requests from the community and incorporate them into this round. The page is currently live, but hidden. We'll do an unveiling after everyone has a chance to comment :) A few features that we've added: Speaker Profile (https://www.openstack.org/profile/speaker) - Willing to Travel - Countries willing to travel to - Languages Spoken - Areas of Expertise - Links to previous presentations Speakers Bureau (https://www.openstack.org/community/speakers) - Search by name, expertise, company - Filter by Language Spoken, Country of Origin, - Countries willing to travel to Speaker Profile (https://www.openstack.org/community/speakers/profile/398) - Front End of Speaker Profile - Ability to contact speakers through an online form Looking forward to your feedback! Thanks much, Jimmy McArthur Jimmy McArthur wrote:
Marton - thanks for the feedback!
Sounds great, as we like to make this speaker tool available for user group leaders as a part of user group tools, can we design an API that helps to consume the speaker data from the openstack.org <http://openstack.org> website? Great suggestion on the API. I'll add that to the list for a Phase II.
As a practicing user group leader, it is very important for us to make that list filterable by region / country. I think it is much easier to connect local regions first than expect someone from Asia or US to travel to EU. Yes, this will be built into the first rev. But in a future milestone we should implement a "road trip" feature, if a speaker is going to a trip, he have a good chance to visit local user groups. Solid idea. We've thought about tying the page into openstack.org/events. This might be a nice add-on that feature.
Marton
On Thu, Nov 19, 2015 at 8:19 PM Jimmy McArthur <jimmy@openstack.org <mailto:jimmy@openstack.org>> wrote:
Forgot to add... if you all want to follow along on progress on the public repo: https://github.com/OpenStackweb/openstack-org/commit/65738783ee457c2f36728ec...
Thanks again!
Jimmy
Jimmy McArthur wrote:
Hi all -
I've recently been hired to work with the Foundation to support the OpenStack web properties. Previously, I was a project lead at Tipit, and was supporting the Foundation in a similar capacity. I'm very familiar with the speaker submission process for the Summit, from start to finish, having worked directly with Todd Morey and the rest of the Foundation crew for the last few summits. I would love to leverage that work and the data we've already collected to help build a speakers bureau for the community.
I'll summarize below some of the requirements I've gathered from reviewing all the outstanding requests. Below that, I'll add a few comments about the general development that has already begun.
Information that we currently have in Speaker Profile - Date Joined - Country / City of origin - Funded travel - Registered for upcoming Summit - Past OpenStack Summit presentations / related material - Bio - Affiliations / Job history - Opt-In to Speakers Bureau
Community Requests for additional information - Areas of expertise* - Prior speaking topics* - Links to previous presentations / event names* - Is the speaker willing to travel? To which regions / countries?* - In which languages is the speaker fluent?* - Professional references - Sponsorship opportunities (travel, food/drink) - Dates of availability / unavailability
Contact form* - Name of organizer - Email of organizer - Event name - Format / length - Expected attendance - Date(s) of event - Location - Topic(s) - General Request
Add option to Sort / Search - Name - Company - Region, country, city where the speaker lives/works - Areas of expertise
As you can see from the first list, the Foundation already collects a fair amount of information when we do our Call for Speakers ahead of each summit. Earlier this month, we began work on the speaker’s bureau, leveraging that information. I suggest we focus on getting a minimum viable product out as soon as possible, with the data that we've already collected.
I've put an asterisk next to the items that are easy adds. We could aim to get as much of that into a Phase I as possible. There are some more complex pieces (Professional references, Dates of availability / unavailability) that have potential privacy concerns or could complicate things. Additionally, I think we should keep the form as short and simple as possible, so speakers fill it out. IMO we should be cautious about overreaching when asking for data and ensure it's easy for people to manage.
My suggestion is to get some of these more simple items out the door so we at least have a searchable list. From there, we can solicit feedback and iterate.
Please let me know your thoughts and I look forward to working with everyone!
Cheers, Jimmy McArthur _______________________________________________ Community mailing list Community@lists.openstack.org <mailto:Community@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
_______________________________________________ Community mailing list Community@lists.openstack.org <mailto:Community@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
_______________________________________________ Community mailing list Community@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/community
Nice work here! If/When you do get around to providing an API for it, I recommend giving the Conference Talk Media Type [1] a serious consideration. You can find the source for that IETF draft in this repo [2]. And you can see Darrel Miller give a talk on it at APIStrat here [3]. Cheers, Everett [1] http://restfest.github.io/2015-apidays-conference-talk-api/ [2] https://github.com/RESTFest/2015-apidays-conference-talk-api [3] https://youtu.be/iBFKMyzEAXM?t=43m On Dec 14, 2015, at 12:05 PM, Jimmy McArthur <jimmy@openstack.org<mailto:jimmy@openstack.org>> wrote: Hi all - Wanted to follow up on this and give you all a first look at the Speakers Bureau. I want to stress that this is a first rev. As we start collecting more data from Speakers, we'll be able to offer a more fully featured Bureau. That said, we've tried to take all the major requests from the community and incorporate them into this round. The page is currently live, but hidden. We'll do an unveiling after everyone has a chance to comment :) A few features that we've added: Speaker Profile (https://www.openstack.org/profile/speaker) - Willing to Travel - Countries willing to travel to - Languages Spoken - Areas of Expertise - Links to previous presentations Speakers Bureau (https://www.openstack.org/community/speakers) - Search by name, expertise, company - Filter by Language Spoken, Country of Origin, - Countries willing to travel to Speaker Profile (https://www.openstack.org/community/speakers/profile/398) - Front End of Speaker Profile - Ability to contact speakers through an online form Looking forward to your feedback! Thanks much, Jimmy McArthur Jimmy McArthur wrote: Marton - thanks for the feedback! Sounds great, as we like to make this speaker tool available for user group leaders as a part of user group tools, can we design an API that helps to consume the speaker data from the openstack.org<http://openstack.org/> website? Great suggestion on the API. I'll add that to the list for a Phase II. As a practicing user group leader, it is very important for us to make that list filterable by region / country. I think it is much easier to connect local regions first than expect someone from Asia or US to travel to EU. Yes, this will be built into the first rev. But in a future milestone we should implement a "road trip" feature, if a speaker is going to a trip, he have a good chance to visit local user groups. Solid idea. We've thought about tying the page into openstack.org/events<http://openstack.org/events>. This might be a nice add-on that feature. Marton On Thu, Nov 19, 2015 at 8:19 PM Jimmy McArthur <jimmy@openstack.org<mailto:jimmy@openstack.org>> wrote: Forgot to add... if you all want to follow along on progress on the public repo: https://github.com/OpenStackweb/openstack-org/commit/65738783ee457c2f36728ec... Thanks again! Jimmy Jimmy McArthur wrote: Hi all - I've recently been hired to work with the Foundation to support the OpenStack web properties. Previously, I was a project lead at Tipit, and was supporting the Foundation in a similar capacity. I'm very familiar with the speaker submission process for the Summit, from start to finish, having worked directly with Todd Morey and the rest of the Foundation crew for the last few summits. I would love to leverage that work and the data we've already collected to help build a speakers bureau for the community. I'll summarize below some of the requirements I've gathered from reviewing all the outstanding requests. Below that, I'll add a few comments about the general development that has already begun. Information that we currently have in Speaker Profile - Date Joined - Country / City of origin - Funded travel - Registered for upcoming Summit - Past OpenStack Summit presentations / related material - Bio - Affiliations / Job history - Opt-In to Speakers Bureau Community Requests for additional information - Areas of expertise* - Prior speaking topics* - Links to previous presentations / event names* - Is the speaker willing to travel? To which regions / countries?* - In which languages is the speaker fluent?* - Professional references - Sponsorship opportunities (travel, food/drink) - Dates of availability / unavailability Contact form* - Name of organizer - Email of organizer - Event name - Format / length - Expected attendance - Date(s) of event - Location - Topic(s) - General Request Add option to Sort / Search - Name - Company - Region, country, city where the speaker lives/works - Areas of expertise As you can see from the first list, the Foundation already collects a fair amount of information when we do our Call for Speakers ahead of each summit. Earlier this month, we began work on the speaker’s bureau, leveraging that information. I suggest we focus on getting a minimum viable product out as soon as possible, with the data that we've already collected. I've put an asterisk next to the items that are easy adds. We could aim to get as much of that into a Phase I as possible. There are some more complex pieces (Professional references, Dates of availability / unavailability) that have potential privacy concerns or could complicate things. Additionally, I think we should keep the form as short and simple as possible, so speakers fill it out. IMO we should be cautious about overreaching when asking for data and ensure it's easy for people to manage. My suggestion is to get some of these more simple items out the door so we at least have a searchable list. From there, we can solicit feedback and iterate. Please let me know your thoughts and I look forward to working with everyone! Cheers, Jimmy McArthur _______________________________________________ Community mailing list Community@lists.openstack.org<mailto:Community@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/community _______________________________________________ Community mailing list Community@lists.openstack.org<mailto:Community@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/community _______________________________________________ Community mailing list Community@lists.openstack.org<mailto:Community@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/community _______________________________________________ Community mailing list Community@lists.openstack.org<mailto:Community@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
participants (3)
-
Everett Toews
-
Jimmy McArthur
-
Marton Kiss