no edit summary
## '''Registration Opening Date''': Target date to open registration is Dec 10th. However that may be pushed back to early January depending on how firm the budget numbers are. This should not change our plans to have ready list of pre-conferences by December 10th. See the main trello for more info: trello 'master schedule' and other information workspace: https://trello.com/b/rTeC8Bgx/master-planning-schedule
## '''Proposal Form:''' Proposals to be accepted this year via Google Form. Google form instructions forthcoming from Anna. The Google Form will be structured following the wiki page proposal format seen here http://wiki.code4lib.org/2016_Preconference_Proposals , with an additional space for presentation needs, and that wiki page will be deleted once the form is made. Christina will make a draft and give to the group for review before putting updated link in the Call text. The updated Call text will also be shared with the group at that time for review. Once proposals form and call are reviewed and approved by group, we will each claim a listserv to email the call to. This will be that person's listserv for further emails throughout rest of organizing work.
# Voting: Mechanism to be determined. The Dieboldatron had some issues with structure of preconference proposals - wanted to have broken into AM/PM/Full day; need yes/no voting instead of 0-3 ranking. We will need at least a business week (5 days) of voting to gauge interest, make decisions if there are space constraints. At present, the default is to take the Proposals from the Google form backend and put in some structured way into the wiki, then have people add their names there.## Accepted timeframe:
### '''Week of 9/30:''' Call for proposals sent, immediately post group review of draft Google form for proposals, review of updated Call text.
### '''11/15''': Proposals deadline - Midnight PST.
### '''12/1-12/5''': Confirm selected sessions along with needs, space, etc with session leaders
### '''12/5''': Have pre-conference schedule in place for public view
# Preconference spaces
## Overview of space will equal how many sessions can we accept: Looking primarily as using a volunteered small conference center (CHF?) a few blocks from the hotel. This conference center offers free A/V. The hotel has some rooms, but we will need to pay for A/V. Finally, there is a (1) lecture hall a few more blocks away at the American Philosophical Society that is available for use too. Anna will get us details on the spaces for helping sort proposals as they start to come in. Depending on space issues and the number of proposals, we will see if we need to actually not accept any proposals.
## Will we need registration limits (and how to determine this in registration page) - see above. Confirmed that there will be spaces held for all preconference leaders to register.
## What will presenters need to bring (projects, computers, etc.) - will be added to the google form (see above) then touched on further in confirmation process.
# Allyship session - Ada Initiative Ally Training## Participation interest - if the organizer of this event wants to send out separate interest, the group is fine. Uncertainty with this pre-conf group about us officially sending out interest for this one preconference separate from regular preconference proposal and voting procedure. Noted: agreement that is it impossible to tell definite interest in this session until there is a full list of pre-conferences available, as people will change their minds/move aboue. Will defer to the main organizing committee.## Extra fee / Sponsorship - the group is fine with charging an extra fee for this session if the proposal is accepted/LPC decides to hold as code4lib sponsored or special event. Will need to fall to the registration team. ## Overall preference: if the organizer of this event was to get sponsorship to cover costs, then put in a proposal following the normal route above, that would be easiest. Additionally, putting in a proposal then asking extra money be charged in the registration, that's okay but not preferred (as it runs the possibility that the Code4lib org will be stuck paying the remainder if turnout doesn't hit a certain number). However, the preconf group is ready to defer on this question to the decision of the main organizing committee.
# Text of call for proposals - to be updated following this meeting and creation of the proposal form.
'''Subject line:''' Call for Code4Lib 2016 Pre-Conference Proposals