[openstack-community] Proposal: remove voting on speaking proposals for Barcelona Summit

Margaret Dawson mdawson at redhat.com
Wed May 18 13:15:54 UTC 2016

Maybe we can involve the community more in the selection of track chairs so
there is still an ability to participate but then leave it to track chairs
to pick the best sessions. I also noticed we had a huge difference in
attendance across sessions, so i would think we would want to use data and
past session success (or not) to influence our decisions, which people
voting would not have access to.

On Tue, May 17, 2016 at 3:40 PM, Claire Massey <claire at openstack.org> wrote:

> Hi everyone,
> For the past few Summits, we've received mixed feedback about having the
> community vote on proposed sessions as part of the call for speakers
> process. Historically, after the call for speakers closes, we publish all
> submitted sessions for community voting before the track chairs review
> them. The track chairs then choose how much weight to put on the voting
> resuls, if any, because they make the ultimate decision about which
> sessions are selected. More info on Track Chairs can be found at the bottom
> of this email.
> With the growing number of speaking submissions (we had 1,300 for Austin),
> some community members have expressed concerns about social media channels
> and email getting spammed during the week of voting. We also think many
> community members are unclear as to how much the votes weigh on the final
> decision. For example, some think that if someone campaigns for votes or
> asks their colleagues to vote, the session will likely be accepted (which
> may not be the case).
> We would like to propose removing voting from the selection process for
> the October 2016 Barcelona Summit, but want to get your input before making
> a final decision. Our thinking is that by removing voting from the process,
> we will:
> - Save valuable time during the overall Summit programming process, which
> should allow us to publish the final agenda and notify speakers sooner
> - Allow our development teams more time to focus on improving the mobile
> app and web schedule developed during the last Summit cycle
> - Reduce the spam and noise around voting, so we don't cause Twitter
> fatigue before we're promoting the final agenda and key themes
> - Level the playing field for speakers from startups, new community
> members, etc. who may not have an established network in the community for
> voting
> We initially started the voting process for good reasons and we do think
> there's value, but we're reaching a point where the costs are starting to
> outweigh the benefits. We'd like to get your input before we open the call
> for speakers in early June for the Barcelona Summit.
> Thanks,
> Claire
> Track Chair Info
> Track Chairs are subject matter experts who review submissions to their
> particular track, for example "storage" or "cloud applications." There are
> typically 3-4 chairs per track who review and collaboratively decide which
> presentations are ultimately accepted for inclusion on the final agenda.
> The Foundation strives to recruit Track Chairs from a diverse set of
> companies, regions, roles in the community (i.e., contributing developers,
> users and business leaders) and areas of expertise. Information on how to
> nominate yourself or someone else to serve as a track chair for the
> Barcelona Summit will be published when the call for speakers goes live in
> early June. For reference, here's information on the Track Chairs from the
> Austin Summit: https://etherpad.openstack.org/p/Austin_Summit_Track_Chairs
>  and
> https://www.openstack.org/summit/austin-2016/categories/selection-process.
> _______________________________________________
> Community mailing list
> Community at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community

Margaret Dawson
Global Product Marketing
Infrastructure Business Group
Red Hat
Cel:  206-355-6872
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/community/attachments/20160518/888d853f/attachment-0001.html>

More information about the Community mailing list