Changes

Jump to: navigation, search

ProgramCommittee

4,878 bytes added, 14:19, 8 June 2015
Add new page for Program committee

== Program Committtee==
The program committee is a self-selected group that manages talk proposals and other aspects of the program.
The process works something like this:

# Draft the call for proposals (searching the mailing list archives should provide some good templates) and send it out.
# People put their proposals on the Code4Lib wiki (see the [[2013 talks proposals]] page as a template)
#* One idea that's been thrown around to help diversity is for people to self-identify as female/minority/first-timer/first-time presenter, etc. (see the Guidelines below)
# After the proposal period ends, contact Ross Singer (rsinger) to get voting set up.
# After the voting closes, we talk about where to place the dividing line between accepted and declined proposals. There is a bit of negotiation between us and the host committee on scheduling depending on how many talks we want to accept and any scheduling juggling that is required.

===Program Voting===
Pre-conf voting may need to take place if there are more proposals than spaces.

Based on past discussions (such as the [http://serials.infomotions.com/code4lib/archive/2011/201111/thread.html pandering votes thread]), for next year, consider a notification for voters 'briefly
explaining how the ballot works and to reiterate the voting criteria that's on the proposal page.

There has also been discussions about whether voting should be done without names, but it was inconclusive as there are pros and cons to each.

If possible, it has been suggested that talks be grouped by topic so there is more consideration by people on giving too many votes to a single topic.

===Guidelines===
For 2014, you may want to make this a bit more clear on the talk proposals page, but this is what the community agreed on through mailing list discussion:
* Max 2 presenters per talk (this should be checked at the proposal stage)
* Max 1 talk per person
* (at least) 15% talks to be decided by the program committee with "diversity" in mind. Diversity may be any of these (not an exhaustive list):
** first-time presenter (should be major consideration)
** gender
** visible minority
** technology/tool

Based on [http://serials.infomotions.com/code4lib/archive/2012/201211/thread.html Proposed Changes thread].

Based on the comments from the 2013 feedback, the program committee may also consider proposing limiting the number of talks on a particular topic or technology used (e.g. Hydra, Solr) unless the next conference host proposes to turn the conference into a multi-track conference.

===Schedule===
While always posted on the website, consider putting it on lanyrd like in 2013. Worked great of adding links to sessions, which can then be copied to the website if needed.

===Keynoter logistics===

See [[Keynote Committee Duties]].

===Talk Acceptance Letter (samples)===

<pre>
Dear <<first name last name>>,

On behalf of the Code4Lib Program Planning Committee, I am pleased to
notify you that your proposal, <<proposal title>> has been accepted for
the Code4Lib <<year>> in <<location>>. Please reply to this message to
confirm your intention to present the approved session at the Conference.
If at any time in the future you need to bow out or have any program
changes, please notify us immediately. You will be sent a letter of
agreement soon.

The schedule for the conference is here:

http://code4lib.org/conference/2011/schedule

You will have 20 minutes for your talk, including questions and answers.
A quick transition between speakers will be necessary.

It is very important that you focus your presentation on the more unique
and technical aspects of your topic whenever possible. Although Code4Lib
attendees come from many different work environments, they attend Code4Lib
events for information technology education.

Experts like you are the heart of Code4Lib. We really appreciate your contribution
and look forward to working with you.

Sincerely,

</pre>

===Talk Rejection Letter (sample)===
<pre>
I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:

- The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.
- Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special "Ask Anything" (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.

Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.
Roy
</pre>


[[Category:Code4LibCon_Planning]]

Navigation menu
https://wiki.code4lib.org/Special:MobileDiff/43107
wiki.code4lib.org
crawl=CC-MAIN-2019-43
17097
application/http; msgtype=response
sha1:VESQXR2HBILV73WHYGGGOUWV4DVSOVW4
<urn:uuid:d39c76c1-d312-4370-a786-8428c97b61ad>
2019-10-21T16:32:18Z
128.193.164.120
text/html
sha1:J7PL3NLHN6BOJLVX7J4APH6AJ6TJXINW
<urn:uuid:7710bd8c-2312-44ee-ae0d-061450dd9617>
https://wiki.code4lib.org/Special:MobileDiff/43107
response
<urn:uuid:81b33081-0372-4816-a62f-dffa596c8d57>
isPartOf: CC-MAIN-2019-43
publisher: Common Crawl
description: Wide crawl of the web for October 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-97.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-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/