Difference between revisions of "Preconference2016Workspace"

From Code4Lib
Jump to: navigation, search
(added draft email)
Line 10: Line 10:
 
## Where/how do we need to put this data so website guys will be happy?
 
## Where/how do we need to put this data so website guys will be happy?
 
# Contact session leaders
 
# Contact session leaders
 +
## (new) Max held spots
 
## Divide list
 
## Divide list
 
## Email session leaders for confirmation of participation by December 7th
 
## Email session leaders for confirmation of participation by December 7th

Revision as of 20:34, 3 December 2015

Fourth meeting agenda

Google hangout, December 3rd, 3:30 PM Eastern time

  1. Voting Results
    1. Tabulated results here: https://docs.google.com/spreadsheets/d/1yHvr5gprYQSB0u-gVfARQC2IqZrONzrADknWiSaTyWI/edit#gid=857047949&vpid=A2 (see tabs at bottom)
    2. Draft schedule/room assignment (including overflow) here: https://docs.google.com/spreadsheets/d/1KURH5h7dMwnZRPlNKUTJg2Don__veS51prstwOTcf1Q/edit#gid=0&vpid=A2
    3. Do we keep the overflow sessions?
    4. Approve draft schedule/room assignment?
    5. Where/how do we need to put this data so website guys will be happy?
  2. Contact session leaders
    1. (new) Max held spots
    2. Divide list
    3. Email session leaders for confirmation of participation by December 7th
    4. Confirmation part of filling out form?
    5. As people confirm, mark on shared Google doc here: https://docs.google.com/spreadsheets/d/1KURH5h7dMwnZRPlNKUTJg2Don__veS51prstwOTcf1Q/edit#gid=0&vpid=A2
    6. Email session leaders form asking for profile information + session requirements, giving room assignment (with warning it may change)
    7. Warn 1. auditorium folks (code4arc) that they are in an auditorium 2. no AV overflow folks they must provide their own AV
    8. Ask if 2 geospatial morning workshops would join?
    9. Say we're working on core space for documentation and they will be notified.
  3. Shared Documentation Space
  4. Day of duties
  5. To do going forward

Draft email to session leaders:

Good afternoon:

We're happy to say that your pre-conference session, [Title], has been voted in for Code4Lib 2016. Thank you again for proposing it.

We currently have you in the [building], room [room name], though this may change between now and the conference. We will alert you to any changes, and you can expect the room assignment to be confirmed at least two weeks before the conference, if not earlier. We are also working on a shared space for pre-conference leaders to share documentation for their sessions - including installation and preparation guidelines - and we will let you know where that is by the end of January, 2016. We will also keep you up-to-date on the number and names of participants for your session, with a final list sent out two weeks before the conference.

To proceed, however, we need you to confirm that you and your co-presenters will be leading this pre-conference session by December 7th, 5 PM Pacific. You do not need to attend the Code4Lib Conference to lead your pre-conference session.

Please confirm by filling out this form, which will ask also for additional information 1. about your pre-conference session needs and requests and 2. about the presenters, to be displayed on the Code4Lib 2016 website. Note, all of the presenter profile information is optional beyond name.

If you have any questions, feel free to respond to this email - I will be your pre-conference contact for any issues between now and the conference.

Thank you again for your participation.

Best, [name]

Code4Lib 2016 Preconference Committee

Third meeting agenda

Google hangout, November 16th, 1 PM Eastern time

  1. Voting mechanism
    1. Move forward with choices
    2. Assign to someone for working with Chris or other to get that set up
  2. Review proposals
    1. Decide if more space available or can accept all
    2. Get framework in place for moving preconferences to spaces as voting/interest measures come in
  3. Contact point people
    1. Assign folks to particular sessions for contact/follow-up purposes
  4. Other?

Third meeting Notes

Google hangout, November 16th, 1 PM Eastern time

Review proposals

Decide if more space available or can accept all

  • We would like more rooms to accommodate most / all proposals. This needs to go through LPC, budget-wise. Anna will bring it to that meeting. Will act on assumption that we won't have extra space at the hotels.
  • We will also base this decision on voting.
  • We can also look at topic area duplication if anything seems egregious.

Get framework in place for moving preconferences to spaces as voting/interest measures come in

Christina showed us the spreadsheet she was using.

Voting mechanism

We will not use the dieboldatron. We will use a google form, with the following organization:

  • 2 questions, only one answer on each.
  • Duplicate "either AM or PM" entries into both questions.
  • Duplicate full-day sessions with a note to vote in both time slots.
  • Explain the form in pretty significant detail on the form itself.
  • specify that we won't be able to take all proposals.
  • We will try to open voting noon tomorrow.

Move forward with choices

Detailed timeline: (It's tight)

  • Voting ends December 2nd (5pm Pacific).
  • Notification on the 4th.
  • Confirmation by the 7th .
  • Final confirmed list ready by end of day on the 7th.


Contact point people

Assign folks to particular sessions for contact/follow-up purposes

We will split up the point-presenters among us so that each workshop has a point of contact for info (in both directions)

Other?

  • Future agenda item: Central page on website where we / organizers can post links and instructions.
  • What are we responsible for day-of?
    • Make sure everyone knows where they're going (between different buildings)
    • Once workshops are distributed into rooms, each committee member should be point-person for co-located presenters.

Action items

  • Eric will start putting together our follow-up / confirmation form.
  • Anna will send a link to previously-discussed profile info along with the link to meeting minutes (see links added above).
  • Christina will keep working on the form, please help (it's a shared google doc)
  • Christina will send out a group email notifying everyone who sent in proposals letting them know that we have a vote / won't accept all workshops this year. This will go out today.
  • Anna will communicate with website committee so they can update the site with the timeline.
  • Anna will communicate with LPC about hotel space.

Second meeting agenda

Google hangout, October 7th, 1 PM Eastern time

  1. Voting mechanism
    1. Get responses from LPC
  2. Allyship Preconference Question
    1. Get responses from LPC

Second Meeting Notes

Updates from Christina

  • Form was sent out - hooray!
  • Taking responses until November 11/15
  • Request from Luke to share email generation script

Voting Mechanism

  • We can do whatever we want in this regard (Anna)
    • Multiple systems available for vote counting
    • Decide what is most useful for the committee and go with that
    • Can't just do voting based on what is most popular because of concurrent sessions
    • Data does not need to be distributed, does not need to be in a structured format
    • Have to make sure that people know they are not actually signing up for a pre-conference session, only an expression of interest
  • Options: wiki sign up, Google Form, etc.
    • Wiki is a backup plan
    • Explore Google form option through testing
    • Look at other possible voting mechanisms and communicate via email
  • Christina will set up a test Google Form

Allyship Preconference

  • Anna communicated that the LPC is responsible for making this decision
  • General sense that we'd like it to happen but that logistics are a problem
  • Drupal pre-con in Raleigh that required a registration fee?
  • Background Info
    • Pull request to create specific policies for Code of Conduct
    • comment thread had a suggestion for training that would be useful to committees
    • LPC began to explore options
  • Sponsorship committee will continue to solicit potential sponsors
  • LPC will contact presenter
  • Wait to see what the main committee decides

Other Items

  • Send pre-conference proposal reminder one week ahead of deadline: 11/9
    • Everyone will send to the same email lists as for the inital CFP
  • Meet again shortly after deadline: 11/16 1PM Eastern

First meeting notes

  1. Group documentarian
    1. Christina for this meeting; someone else in the future (to be determined at start of each meeting)
  2. Timeframe
    1. 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
    2. 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.
    3. 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 (or pick top AM, top PM, or top all-day) 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.
    4. Accepted timeframe:
      1. Week of 9/30: Call for proposals sent, immediately post group review of draft Google form for proposals, review of updated Call text.
      2. 11/15: Proposals deadline - Midnight PST.
      3. 11/16-11/24: Current plan: migrate proposals from Google form backend to structure on the wiki, have voting occur there through 'add your name to what you want to attend'.
      4. 12/1-12/5: Confirm selected sessions along with needs, space, etc with session leaders
      5. 12/5: Have pre-conference schedule in place for public view
  3. Preconference spaces
    1. 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.
    2. 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.
    3. 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.
  4. Allyship session - Ada Initiative Ally Training
    1. Participation interest - if the organizer of this event wants to send out separate interest, we are okay with that. Uncertainty however about us officially sending out an email asking about interest for this one preconference separate from regular preconference proposal and voting procedure. Noted: agreement amongst ourselves 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.
    2. Extra fee / Sponsorship - we are 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.
    3. 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

Text: Code4Lib 2015 Pre-Conference Proposals:

We are now accepting pre-conference proposals for the 2016 Code4Lib in Philadelphia, Pennsylvania - read more about the conference here: http://2016.code4lib.org/. These pre-conferences can either be a 1-day or a 1/2-day session and will occur on Monday, March 7, 2016.

To propose a session, please add the proposal to this wiki page directly, following the proposal formatting guidelines: http://wiki.code4lib.org/2016_Preconference_Proposals If you cannot or do not wish to edit the wiki directly, you can email one of us listed below your proposal and we will add it for you.

We are taking proposals until November 15th, and we hope to confirm sessions with the leaders starting November 21st.

If there are any questions, please do not hesitate to email us.

Best, Names, Emails of pre-conf committee

Action Items:

  1. Anna:
    1. send google forms information
    2. send list of spaces, other space info
    3. take this group's thought re: allyship preconf, voting issues, back to LPC
  2. Christina:
    1. Post notes
    2. Get proposal form made based off of wiki, share with group
    3. Get updated call for proposals text, share with group
  3. All:
    1. review above info, form, call for proposals this week
    2. tell group which listservs you'll be contact person for
https://wiki.code4lib.org/index.php?title=Preconference2016Workspace&diff=prev&oldid=43735
wiki.code4lib.org
crawl=CC-MAIN-2019-13
38888
application/http; msgtype=response
sha1:BPY7A6PD24KQVLMXHTLCFFKRSPZKTANX
<urn:uuid:3f531d54-bc39-47d9-ab83-9104c3ba9883>
2019-03-25T21:08:32Z
128.193.164.120
text/html
sha1:3423JC7ROQA2DPKOBS3LXHOAL3NW3UV2
<urn:uuid:be96084c-e51d-4aa8-b60e-47094d85fa5f>
https://wiki.code4lib.org/index.php?title=Preconference2016Workspace&diff=prev&oldid=43735
response
<urn:uuid:10adb8c7-dca0-4cf1-9f2a-824e0a7fd8e5>
isPartOf: CC-MAIN-2019-13
publisher: Common Crawl
description: Wide crawl of the web for March 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-33-242-24.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/