Now that Call for Papers for BriForum 2012 London has ended, we're set to begin the hardest part of the process: selecting the actual sessions for BriForum. This year, we have 67 submissions (well, 76, but 9 of them were immediately disqualified for various rules violations), and we have to cut that number down to around 30 for the show.
To do this, we dump the results of the survey into a spreadsheet and hide the columns that contain identifiers like email address, name, and company. Then, Brian and I each look at the spreadsheet separately and assign each session a Yes, No, or Maybe vote, as well as make any notes that we feel are relevant. When we're done, we combine our ratings, unhide the columns, and spend several hours deliberating the merits of each of the sessions. In general, sessions that receive "Yes" votes from both of us are automatically in, but there's usually some disagreements that require some late night horse trading.
This year, we thought we'd include the community in this since BriForum is, after all, a community-driven show. We've created a survey that includes each session title and abstract, along with "Yes," "No," and "Maybe" answers and a notes field (so you can tell us what you think of the session idea, good, bad, or otherwise). It's long–68 pages–but each page is a standalone session, so it should only take ten minutes to get through.
If you want to have an impact on the content at BriForum beyond the ability to submit a session, here's your chance. We'd very much appreciate your honest response to this survey (even if you don't plan on attending), and if we get enough results we'll use the information to help us choose sessions.
We'll know if you're cheating, either by stuffing the ballot box or by voting multiple times for just your session, so please, only take the survey once!
(Note: You must be logged in to post a comment.)
If you log in and nothing happens, delete your cookies from BrianMadden.com and try again. Sorry about that, but we had to make a one-time change to the cookie path when we migrated web servers.