Code4Lib - User contributions [en]

Code4Lib Journal Deadlines

2021-03-05T19:47:36Z

Ecorrado: Edited Issue 51 dates.

''See also [[Code4Lib Journal Voting]]''

== Formula for calculating deadlines ==

A rough guideline based on recent issues:

{| border="1" cellpadding="2" cellspacing="0"
|-
! Weeks before
! Task
! Day offset
! On
|-
| style="text-align:right" | '''-18'''
| Call for proposals
| style="text-align:right" | -126
| Monday
|-
| style="text-align:right" | '''-14'''
| Proposals due
| style="text-align:right" | -94
| Friday
|-
| style="text-align:right" | '''-13'''
| Publication of previous issue
| style="text-align:right" | -91
| Monday
|-
| style="text-align:right" | '''-13'''
| Finish voting on proposals; notify authors
| style="text-align:right" | -87
| Friday
|-
| style="text-align:right" | '''-9'''
| First draft due
| style="text-align:right" | -59
| Friday
|-
| style="text-align:right" | '''-5'''
| Second draft due
| style="text-align:right" | -31
| Friday
|-
| style="text-align:right" | '''0'''
| Publication
| style="text-align:right" | 0
| Monday
|}

'''Note:''' Week numbers assume week begins on Monday.

'''See also:''' [[Code4Lib_Journal_Email_Templates]] (formerly at [http://groups.google.com/group/c4lj-articles/web/templates-for-email-responses Templates for Email Responses])

== Deadlines for Issues ==
Editors: see also http://tomkeays.com/library/c4ljpubdate/ for Tom's calculator

===Fifty-first issue===
Coordinating Editor: Edward Corrado

Note date changes from originally published schedule

* Call for proposals: Thursday, February 4, 2021
* Second call for proposals: Thursday, February 25, 2021 (if necessary)
* Proposals due: Monday, March 15, 2021
* Proposals accepted: Monday, March 22, 2021
* First draft due: Monday, April 19, 2021
* Second draft due: Monday, May 10, 2021
* Publication date: Thursday, June 10, 2021

===Fiftieth issue===

Coordinating Editor: Eric Hanson

''Note: Issue dates adjusted to skip one quarter's publication.''
* Call for proposals: Monday, October 5, 2020 <del>July 6, 2020</del>
* Second call for proposals: Monday, October 26, 2020 <del>July 27, 2020</del> (if necessary)
* Proposals due: Friday, November 6, 2020 <del>August 7, 2020</del>
* Proposals accepted: Friday, November 13, 2020 <del>August 14, 2020</del>
* First draft due: Friday, December 11, 2020 <del>September 11, 2020</del>
* Second draft due: Friday, January 8, 2021 <del>October 9, 2020</del>
* Publication date: Monday, February 8, 2021 <del>November 9, 2020</del>

===Forty-ninth issue===

Coordinating Editor: Peter Murray

* Call for proposals: Monday, March 30, 2020
* Second call for proposals: Monday, April 20, 2020 (if necessary)
* Proposals due: Friday, May 1, 2020
* Proposals accepted: Friday, May 8, 2020
* First draft due: Friday, June 5, 2020
* Second draft due: Friday, July 3, 2020
* Publication date: Monday, August 3, 2020

===Forty-eighth issue===

Coordinating Editor: Brighid M. Gonzales

* Call for proposals: Monday, January 6, 2020
* Second call for proposals: Monday, January 27, 2020 (if necessary)
* Proposals due: Friday, February 7, 2020
* Proposals accepted: Friday, February 14, 2020
* First draft due: Friday, March 13, 2020
* Second draft due: Friday, April 10, 2020
* Publication date: Monday, May 11, 2020

===Forty-seventh issue===

Coordinating Editor: Péter Király

* Call for proposals: Monday, September 30, 2019
* Second call for proposals: Monday, October 21, 2019 (if necessary)
* Proposals due: Friday, November 1, 2019
* Proposals accepted: Friday, November 15, 2019
* First draft due: Friday, December 13, 2019
* Second draft due: Friday, January 10, 2020
* Publication date: Monday, February 10, 2020

===Forty-sixth issue===

Coordinating Editor: Sara Amato
* Call for proposals: Monday, July 1, 2019
* Second call for proposals: Monday, July 22, 2019 (if necessary)
* Proposals due: Friday, August 2, 2019
* Proposals accepted: Friday, August 9, 2019
* First draft due: Friday, September 6, 2019
* Second draft due: Friday, October 4, 2019
* Publication date: Monday, November 4, 2019

===Forty-fifth issue===

Coordinating Editor: Eric Hanson
* Call for proposals: Monday, April 1, 2019
* Second call for proposals: Monday, April 22, 2019 (if necessary)
* Proposals due: Friday, May 3, 2019
* Proposals accepted: Friday, May 10, 2019
* First draft due: Friday, June 7, 2019
* Second draft due: Friday, July 5, 2019
* Publication date: Monday, August 5, 2019

===Forty-fourth issue===

Coordinating Editor: Junior Tidal
* Call for proposals: Monday, December 31, 2018
* Second call for proposals: Monday, January 21, 2019 (if necessary)
* Proposals due: Friday, February 1, 2019
* Proposals accepted: Friday, February 8, 2019
* First draft due: Friday, March 8, 2019
* Second draft due: Friday, April 5, 2019
* Publication date: Monday, May 6, 2019

===Forty-third issue===

Coordinating Editor: Peter Murray
* Call for proposals: Monday, October 1, 2018
* Second call for proposals: Monday, October 22, 2018 (if necessary)
* Proposals due: Friday, November 2, 2018
* Proposals accepted: Friday, November 9, 2018
* First draft due: Friday, December 7, 2018
* Second draft due: Friday, January 11, 2019
* Publication date: Monday, February 11, 2019

===Forty-second issue===

Coordinating Editor: Andrew Darby
* Call for proposals: Monday, July 2, 2018
* Second call for proposals: Monday, July 23, 2018 (if necessary)
* Proposals due: Friday, August 3, 2018
* Proposals accepted: Friday, August 10, 2018
* First draft due: Friday, September 7, 2018
* Second draft due: Friday, October 5, 2018
* Publication date: Monday, November 5, 2018

===Forty-first issue===

Coordinating Editor: Ron Peterson
*Call for proposals: Monday, April 17, 2017
*Second call for proposals: Monday, April 30, 2017 (if necessary)
*Proposals due: Friday, May 11, 2017
*Proposals accepted: Friday, May 18, 2017
*First draft due: Friday, June 8, 2017
*Second draft due: Friday, July 6, 2017
*Publication date: Monday, August 6, 2018

===Fortieth issue===

Coordinating Editor: Ruth Kitchin Tillman
*Call for proposals: Friday, December 29, 2017
*Second call for proposals: Friday, January 19, 2018 (if necessary)
*Proposals due: Tuesday, January 30, 2018
*Proposals accepted: Tuesday, February 6, 2018
*First draft due: Tuesday, March 6, 2018
*Second draft due: Tuesday, April 3, 2018
*Publication date: Friday, May 4, 2018

===Thirty-ninth issue===
Coordinating Editor: Terry Reese
*Call for proposals: Monday, September 25, 2017
*Second call for proposals: Monday, October 16, 2017 (if necessary)
*Proposals due: Friday, November 3, 2017
*Proposals accepted: Friday, November 17, 2017
*First draft due: Friday, December 8, 2017
*Second draft due: Friday, January 5, 2017
*Publication date: Monday, January 29, 2018

===Thirty-eighth issue===
Coordinating Editor: Carol Bean
*Call for proposals: Monday, June 12, 2017
*Second call for proposals: Monday, July 3, 2017 (if necessary)
*Proposals due: Friday, July 14, 2017
*Proposals accepted: Friday, July 21, 2017
*First draft due: Friday, August 18, 2017
*Second draft due: Friday, September 15, 2017
*Publication date: Monday, October 16, 2017

===Thirty-seventh issue===
Coordinating Editor: Sara Amato
*Call for proposals: Monday, March 13, 2017
*Second call for proposals: Monday, April 3, 2017 (if necessary)
*Proposals due: Friday, April 14, 2017
*Proposals accepted: Friday, April 21, 2017
*First draft due: Friday, May 19, 2017
*Second draft due: Friday, June 16, 2017
*Publication date: Monday, July 17, 2017

===Thirty-sixth issue===
Coordinating Editor: Peter Murray
*Call for proposals: Thursday, December 15, 2016
*Second call for proposals: Thursday, January 5, 2017 (if necessary)
*Proposals due: Tuesday, January 17, 2017
*Proposals accepted: Monday, January 23, 2017
*First draft due: Monday, February 20, 2017
*Second draft due: Monday, March 20, 2017
*Publication date: Monday, April 17, 2017

===Thirty-fifth issue===

Coordinating Editor: Ruth Kitchin Tillman

* Call for proposals: Monday, September 26, 2016
* Second call for proposals: Monday, October 17, 2016 (if necessary)
* Proposals due: Friday, October 28, 2016
* Proposals accepted: Friday, November 4, 2016
* First draft due: Friday, December 2, 2016
* Second draft due: Friday, December 30, 2016
* Publication date: Monday, January 30, 2017

===Thirty-fourth issue===
Coordinating Editor: Andrew Darby

* Call for proposals: Monday, June 20, 2016
* Second call for proposals: Monday, July 11, 2016 (if necessary)
* Proposals due: Friday, July 22, 2016
* Proposals accepted: Friday, July 29, 2016
* First draft due: Friday, August 26, 2016
* Second draft due: Friday, September 23, 2016
* Publication date: Monday, October 24, 2016

===Thirty-third issue===
Coordinating Editor: Ron Peterson

* Call for proposals: Monday, March 14, 2016
* Second call for proposals: Monday, April 4, 2016 (if necessary)
* Proposals due: Friday, April 15, 2016
* Proposals accepted: Friday, April 29, 2016
* First draft due: Friday, May 20, 2016
* Second draft due: Friday, June 17, 2016
* Publication date: Monday, July 18, 2016

===Thirty-second issue===
Coordinating Editor: Meghan Finch
* Call for proposals: Monday, December 14, 2015
* Second call for proposals: Monday, January 4, 2016 (if necessary)
* Proposals due: Friday, January 15, 2016
* Proposals accepted: Friday, January 22, 2016
* First draft due: Friday, February 19, 2016
* Second draft due: Friday, March 18, 2016
* Publication date: Monday, April 25, 2016

===Thirty-first issue===
Coordinating Editor: Terry Reese
* Call for proposals: Monday, September 21, 2015
* Second call for proposals: Thursday, October 8, 2015 (if necessary)
* Proposals due: Friday, October 23, 2015
* Proposals accepted: Friday, October 30, 2015
* First draft due: Monday, November 23, 2015
* Second draft due: Monday, December 21, 2015
* Publication date: Monday, January 25, 2016

===Thirtieth issue===
Coordinating editor for issue #30: Carol Bean

* Call for proposals: Thursday, June 11, 2015
* Second call for proposals: Thursday, July 2, 2015 (if necessary)
* Proposals due: Monday, July 13, 2015
* Proposals accepted: Monday, July 20, 2015
* First draft due: Monday, August 17, 2015
* Second draft due: Monday, September 14, 2015
* Publication date: Monday, October 19, 2015

===Twenty-ninth issue===
Coordinating editor for issue #29: Sara Amato

* Call for proposals: Wednesday, March 11, 2015
* Second call for proposals: Wednesday, April 1, 2015 (if necessary)
* Proposals due: Friday, April 10, 2015
* Proposals accepted: Monday, April 20, 2015
* First draft due: Monday, May 18, 2015
* Second draft due: Monday, June 15, 2015
* Publication date: Monday, July 13, 2015

===Twenty-eighth issue===
Coordinating editor for issue #28: Heidi Dowding

Special issue on diversity in library technology.

* Call for proposals: Wednesday, December 10, 2014
* Second call for proposals: Monday, January 5, 2015 (if necessary, adjusted from 31-Dec-2014)
* Proposals due: Monday, January 12, 2015
* Proposals accepted: Monday, January 19, 2015
* First draft due: Monday, February 16, 2015
* Second draft due: Monday, March 16, 2015
* Publication date: Wednesday, April 15, 2015

===Twenty-seventh issue===
Coordinating editor for issue #27: Terry Reese

*Call for proposals: Monday, September 27, 2014
*Second call for proposals: Monday, October 6, 2014 (if necessary)
*Proposals due: Friday, October 24, 2014
*Proposals accepted: Friday, October 31, 2014
*First draft due: Friday, November 21, 2014
*Second draft due: Friday, December 19, 2014
*Publication date: Monday, January 19, 2015

===Twenty-sixth issue===
Coordinating editor for issue #26: Kelley McGrath

*Call for proposals: Monday, June 9, 2014
*Second call for proposals: Monday, June 30, 2014 (if necessary)
*Proposals due: Friday, July 11, 2014
*Proposals accepted: Friday, July 18, 2014
*First draft due: Friday, August 15, 2014
*Second draft due: Friday, September 12, 2014
*Publication date: Monday, October 20, 2014

===Twenty-fifth issue===
Coordinating editor for issue #25: Dan Scott

*Call for proposals: Monday, March 10, 2014
*Second call for proposals: Monday, March 31, 2014 (if necessary)
*Proposals due: Friday, April 11, 2014
*Proposals accepted: Friday, April 18, 2014
*First draft due: Friday, May 16, 2014
*Second draft due: Friday, June 13, 2014
*Publication date: Monday, July 14, 2014

===Twenty-fourth issue===
Coordinating editor for issue #24: Ron Peterson

*Call for proposals: Monday, December 9, 2013
*Call for proposals #2: Monday, December 30, 2013 (if necessary)
*Proposals due: Friday, January 10, 2014
*Proposals accepted: Friday, January 17, 2014
*First draft due: Friday, February 14, 2014
*Second draft due: Friday, March 14, 2014
*Publication date: Monday, April 14, 2014

===Twenty-third issue===
Coordinating editor for issue #23: Shawn Averkamp
* Call for proposals: Monday, September 9, 2013
* Call for proposals #2: Monday September 30, 2013 (if necessary)
* Proposals due: Friday, October 11, 2013
* Proposals accepted: Friday, October 18, 2013
* First draft due: Friday, November 15, 2013
* Second draft due: Friday, December 13, 2013
* Publication date: Monday, January 13, 2014

===Twenty-second issue===
Coordinating editor for issue #22: Sara Amato
* Call for proposals: Monday, June 10, 2013
* Call for proposals #2: July 5, 2013 (if necessary)
* Proposals due: Friday, July 12, 2013
* Proposals accepted: Friday, July 19, 2013
* First draft due: Friday, August 16, 2013
* Second draft due: Friday, September 13, 2013
* Publication date: Monday, October 14, 2013

===Twenty-first issue===
Coordinating editor for issue #21: Terry Reese
* Call for proposals: Monday, March 11, 2013
* Call for proposals #2: Monday, April 1, 2013
* Proposals due: Friday, April 12, 2013
* Proposals accepted: Friday, April 19, 2013
* First draft due: Friday, May 17, 2013
* Second draft due: Friday, June 14, 2013
* Publication date: Monday, July 15, 2013

===Twentieth issue===
Coordinating editor for issue #20: [[User:DataGazetteer|Peter Murray]]
* Call for proposals:     Monday, December 10, 2012
* Call for proposals #2: Monday, January 7, 2013 (if necessary)
* Proposals due:          Friday, January 18, 2013
* Proposals accepted:     Friday, January 25, 2013
* First draft due:        Friday, February 22, 2013
* Second draft due:       Friday, March 22, 2013
* Publication date:       Monday, April 15, 2013

===Nineteenth issue===
Coordinating editor for issue #19: Andrew Darby
* Call for proposals: Monday, September 10, 2012
* Proposals due: Friday, October 12, 2012
* Proposals accepted: Friday, October 19, 2012
* First draft due: Friday, November 16, 2012
* Second draft due: Friday, December 14, 2012
* Publication date: Monday, January 14, 2013

===Eighteenth issue===
Coordinating editor for issue #18: Ron Peterson
* Call for proposals: Monday, May 28, 2012
* Proposals due: Friday, June 29, 2012
* Proposals accepted: Friday, July 6, 2012
* First draft due: Friday, August 3, 2012
* Second draft due: Friday, August 31, 2012
* Publication date: Monday, October 1, 2012

===Seventeenth issue===
Coordinating editor for issue #17: Tim Lepczyk
* Call for proposals: Wednesday, February 8, 2012
* Proposals due: Tuesday, February 28, 2012
* Proposals accepted: Tuesday, March 6, 2012
* First draft due: Tuesday, April 3, 2012
* Second draft due: Tuesday, May 1, 2012
* Publication date: Friday, June 1, 2012

===Sixteenth issue===
Coordinating editor for issue #16: Carol Bean
* Call for proposals: Monday, September 26, 2011
* Proposals due: Friday, October 28, 2011
* Proposals accepted: Friday, November 4, 2011
* First draft due: Friday, December 2, 2011
* Second draft due: Friday, December 30, 2011
* Publication date: Monday, January 30, 2012

===Fifteenth issue===
Coordinating editor for issue #15: Tod Olson
* Call for proposals: Monday, June 27, 2011
* Proposals due: Friday, July 29, 2011
* Proposals accepted: Friday, August 5, 2011
* First draft due: Friday, September 2, 2011
* Second draft due: Friday, September 30, 2011
* Publication date: Monday, October 31, 2011

===Fourteenth issue===

* Call for proposals: Monday, March 21, 2011
* Proposals due: Friday, April 22, 2011
* Proposals accepted: Friday, April 29, 2011
* First draft due: Friday, May 27, 2011
* Second draft due: Friday, June 24, 2011
* Publication date: Monday, July 25, 2011

===Thirteenth issue===

* Call for proposals: Monday, December 6, 2010
* Proposals due: Friday, January 7, 2011
* Proposals accepted: Friday, January 14, 2011
* First draft due: Friday, February 11, 2011
* Second draft due: Friday, March 11, 2011
* Publication date: Monday, April 11, 2011

===Twelfth issue===

* Call for proposals: Monday, August 16, 2010
* Proposals due: Friday, September 17, 2010
* Proposals accepted: Friday, September 24, 2010
* First draft due: Friday, October 22, 2010
* Second draft due: Friday, November 19, 2010
* Publication date: Monday, December 20, 2010

===Eleventh issue===

* Call for proposals: Monday, May 17, 2010
* Proposals due: Friday, June 18, 2010
* Proposals accepted: Friday, June 25, 2010
* First draft due: Friday, July 23, 2010
* Second draft due: Friday, August 20, 2010
* Publication date: Monday, September 20, 2010

=== Tenth issue ===

* Call for proposals: Monday, February 15, 2010
* Proposals due: Friday, March 19, 2010
* Proposals accepted: Friday, March 26, 2010
* First draft due: Friday, April 23, 2010
* Second draft due: Friday, May 21, 2010
* Publication date: Monday, June 21, 2010

=== Ninth issue ===

* Monday, November 9, 2009 -- Call for proposals
* Friday, December 11, 2009 -- Proposals due
* Friday, December 18, 2009 -- Finish voting on proposals, notify authors
* Friday, January 15, 2010 -- First draft due
* Friday, February 12, 2010 -- Second draft due
* Monday, March 15, 2010 -- Publication date

=== Eighth issue ===

* Monday, July 27 -- call for proposals
* Friday, August 14 -- proposals due
* Friday, August 21 -- finish voting on proposals; notify authors
* Friday, September 25 -- first draft due
* Friday, October 23 -- second draft due
* Monday, November 23 -- publication

=== Seventh issue ===

* Monday, February 16 -- call for proposals
* Friday, March 20 -- proposals due
* Monday, March 30 -- publication of issue 6
* Friday, March 27 -- finish voting on proposals; notify authors
* Friday, April 24 -- first draft due
* Friday, May 22 -- second draft due
* Monday, June 22 -- publication

=== Sixth issue ===

* Monday, November 10 -- call for proposals
* Friday, December 12 -- proposals due
* Monday, December 15 -- publication of issue 5
* Friday, December 19 -- finish voting on proposals; notify authors
* Friday, January 23 -- first draft due
* Friday, February 20 -- second draft due
* Monday, March 30 -- publication (originally scheduled for March 23)

=== Fifth issue ===

* Monday, August 18 -- call for proposals
* Friday, September 12 -- proposals due
* Friday, September 19 -- finish voting on proposals; notify authors
* Monday, September 22 -- issue 4 published
* Friday, October 17 -- first draft due
* Friday, November 14 -- second draft due
* Monday, December 15 -- publication

=== Fourth issue ===

* Friday, May 16 -- call for proposals
* Friday, June 20 -- extended proposal deadline (originally 6/13, before issue 3 is published)
* Friday, July 18 -- first draft due
* Friday, August 15 -- second draft due
* Monday, September 22 -- publication

=== Third issue ===

* Wednesday February 13th -- call for proposals
* Friday March 14th -- proposals due (after con, before issue 2)
* Friday April 25 -- first draft due
* Saturday June 21 -- publication (tentative)

=== Second issue ===

* Friday November 9th -- call for proposals
* Friday January 11 -- article draft deadline (or Thurs Jan 21, from EM)
* Thursday February 21 -- revisions/second draft deadline
* Friday March 21 -- publication (tentative)

=== First issue ===

* Friday August 31st -- call for proposals
* Friday October 12th -- article draft deadline
* Monday December 17th -- publication

[[Category: Code4Lib Journal]]

2013 committees sign-up page

2012-10-28T14:45:23Z

Ecorrado: /* Scholarships Committee */

= Code4Lib 2013 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2013 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.

[[2013 During the Conference Volunteers | During the Conference Volunteers]]

== Book Give-Away Committee ==
*Kevin S. Clarke, ksclarke@gmail.com
*Anjanette Young

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.

* Margaret Heller mheller@dom.edu
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org
* Kyle Banerjee banerjek@uoregon.edu
* Bohyun Kim kimb et fiu dot edu
* [http://roytennant.com/ Roy Tennant], roytennant@gmail.com
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail
* [[User:highermath|Cary Gordon]], cgordon@chillco.com

== Keynote Speakers Committee ==

This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community) and work with the speakers to arrange their travel and arrangements.

*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu
*Anjanette Young
*Kevin Reiss kr2 @ princeton . edu
*Jim Rible rible@sou.edu

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org
* [http://twitter.com/ranti Ranti Junus], ranti.junus@gmail.com
* Ray Schwartz, schwartzr2@wpunj.edu
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail
* Tom Johnson, thomas.johnson@oregonstate.edu

== Scholarships Committee ==

This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.
* [http://jodischneider.com/jodi.html Jodi Schneider]
* [http://ecorrado.us/ Edward M. Corrado]

== T-Shirt Committee ==

This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.

* akorphan (akorphan AT ncsu DOT edu)
* [[User:Pberry|Pberry]] Patrick Berry (pberry@csuchico.edu)

== Social Activities Committee ==

The committee plans, proposes, and organizes the evening activities.

*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu
*Ray Schwartz, schwartzr2@wpunj.edu
*Bohyun Kim kimb et fiu dot edu
*Shane Beers, sbeers depaul edu
*[[User:JonGorman|Jon Gorman]], jtgorman @ illinois dot edu
*Becky Yoose, b.yoose cinnamon roll gmail speck com

== Voting Activities Committee ==

This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

* [[User:highermath|Cary Gordon]], cgordon@chillco.com
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail
* [[User:Wolf29|Wolf Halton]], wolf.halton@lyrasis.org./dev/null
* [[User:crowesn|Sean Crowe]], sean.crowe@ uc dot edu
* [[User:shawnc12|Shawn Carraway]], carraways@ midlandstech dot edu

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2013]]

2012 nominations list

2011-08-15T13:01:04Z

Ecorrado:

Nominations for invited speakers for Code4Lib 2012. Alphabetical order.

==Daniel Chudnov==
Let's get back to basics and back to community. Instead of a name from outside of the community lets go with someone from the community. Besides his many accomplishments as a coder for libraries, Dan Chudnov is also one of a handful of people responsible for he first code4lib conference. From hs web site:

Daniel Chudnov is a librarian and programmer in the Office of Strategic Initiatives at the Library of Congress. Previously, he worked as a software developer at the Yale Center for Medical Informatics, and contributed to several free software projects for libraries while working at the MIT Libraries and the Cushing/Whitney Medical Library at the Yale University School of Medicine. He is a frequent speaker and author on technology and the importance of free software in libraries, and he writes a monthly column for Computers in Libraries magazine. He started the oss4lib weblog and listserv in 1999 to promote the use of free software in our community.

Daniel earned an MS at the School of Information in 1997 and studied Economics and Japanese as an undergraduate, both at the University of Michigan. In 2005, he received the LITA/Brett Butler Entrepreneurship Award from the Library & Information Technology Association of the American Library Association.

He has been cancer-free since 1993.

==Brian Fitzpatrick==
Brian leads several of Google's Chicago engineering efforts, including Transparency Engineering and The Google Affiliate Network. He also started and leads Google's Data Liberation Front, a team that systematically works to make it easy for users to move their data both to and from Google. Lastly, he serves as internal advisor for Google's open source efforts.
Prior to joining Google, Brian was a senior software engineer on the version control team at CollabNet, working on Subversion, cvs2svn, and CVS. He has also worked at Apple Computer as a senior engineer in their professional services division, developing both client and web applications for Apple's largest corporate customers.
Brian has been an active open source contributor for over thirteen years. After years of writing small open source programs and bugfixes, he became a core Subversion developer in 2000, and then the lead developer of the cvs2svn utility. He was nominated as a member of the Apache Software Foundation in 2002 and spent two years as the ASF's VP of Public Relations. He is also a member of the Open Web Foundation. Brian has written numerous articles and given many presentations on a wide variety of subjects from version control to software development, including co-writing "Version Control with Subversion" (now in its second edition) as well as chapters for "Unix in a Nutshell" and "Linux in a Nutshell."
Brian has an A.B. in Classics from Loyola University Chicago with a major in Latin, a minor in Greek, and a concentration in Fine Arts and Ceramics. Despite growing up in New Orleans and working for Silicon Valley companies for most of his career, he decided years ago that Chicago was his home and stubbornly refuses to move to California.

==Tony Hirst==
AKA Psychemedia, Tony's job is to help redistribute the future. He does interesting things with library, government and education data. Here is his own bio which describes things pretty well.

Tony Hirst is a Lecturer in the Department of Communication and Systems at The Open University and regular blogger at [http://blog.ouseful.info/ OUseful.info]. With a background in electronics and artificial intelligence, he has authored on OU courses ranging from robotics to information skills, and most recently a course on computer game design and appreciation. He is passionate about open and lifelong education, and is actively involved in developing course models to support informal as well as formal education. As a self-proclaimed mashup artist, he gives regular workshop and conference presentations on how to create novel information services from freely available web tools and applications such as Google Spreadsheets and Yahoo Pipes, as well as creating compelling network visualisations using tools such as a Gephi. An Arcadia Fellow at the University Library, Cambridge in 2009, he has spent many years berating academic libraries about the changing world of information around them. Since posting a widely circulated map based visualisation of MPs’ travel expenses in Spring 2009, he has become increasingly interested in the practice of data journalism and the use of visualisation techniques as a way of making sense of complex data sets, as well as co-founder of [http://getthedata.org/ getTheData.org], an open public data question and answer site. This approach is complemented by his work on the public document consultation platform [http://writetoreply.org/ WriteToReply] which is helping government departments and policy makers think differently about the nature of commentable documents. (source: [http://blog.ouseful.info/about/ | OUseful.Info, the blog…])

== Damon Horowitz ==
Damon Horowitz is a philosophy professor and serial entrepreneur. He recently joined Google as In-House Philosopher / Director of Engineering, heading development of several initiatives involving social and search. He came to Google from Aardvark, the social search engine, where he was co-founder and CTO, overseeing product development and research strategy. Prior to Aardvark, Horowitz built several companies around applications of intelligent language processing. He co-founded Perspecta (acquired by Excite), was lead architect for Novation Biosciences (acquired by Agilent), and co-founded NewsDB (now Daylife).
Horowitz teaches courses in philosophy, cognitive science, and computer science at several institutions, including Stanford, NYU, University of Pennsylvania and San Quentin State Prison (source: [http://www.ted.com/speakers/damon_horowitz.html | TED Profiles])

See this excellent article Damon wrote for the Chronicle of Higher Education. His thesis is why he would be a perfect keynote for Code4Lib 2012: http://chronicle.com/article/From-Technologist-to/128231/?sid=wc&utm_source=wc&utm_medium=en His [http://www.ted.com/talks/damon_horowitz.html TED Talk] is also worth 15 minutes of your life ...

==Hanson Hosein==

Hanson Hosein is the Director of the Master of Communication in Digital Media program at the University of Washington in Seattle. He’s also an award-winning journalist and filmmaker. He specializes in storytelling, social media strategies and business models of communication.

His film, Independent America: The Two-Lane Search for Mom & Pop was an early exercise in the use of digital technology in storytelling and an ongoing interaction with an audience. Self-produced and self-financed, the award-winning documentary has been broadcast internationally, and airs regularly on the Sundance Channel in the United States. Perhaps more importantly, grassroots groups across America continue to screen the film as a tool to promote local economies. Hanson’s latest film, Independent America: Rising from Ruins focuses on how small business helped resurrect New Orleans after Hurricane Katrina, despite ruinous city policies favoring big box stores.

Hanson won Emmy and Overseas Press Club awards for his NBC News coverage “The Fall of Kosovo.” He was NBC’s Middle East Producer and MSNBC.com correspondent from 1997 to 2001. Prior to that served as an investigative producer at “NBC Nightly News with Tom Brokaw.”

==Adam Jacob==
"Adam Jacob is a co-founder of Opscode and the creator of Chef. Prior to Opscode, he founded HJK Solutions, an automated infrastructure consultancy. During two years at HJK, he built new infrastructures for 15 different startups. Including his time at HJK, Adam has 13 years of experience as a systems administrator, systems architect, and tools developer. He has been responsible for large production infrastructures, internal corporate automation, and Sarbanes-Oxley compliance efforts."
[http://www.youtube.com/watch?v=Fx8OBeNmaWw| Adam is a good speaker.] --Anjanette
==Hilary Mason==
A software engineer with http://bit.ly. From her web site: "Hilary is a computer science professor with a background in machine learning, data mining, and web applications. She is currently on sabbatical to explore real-world implementations of these technologies. She is widely published and regularly speaks at academic and industry conferences, and recently realized her dream of delivering a talk on algorithms while drinking a dry ice martini. She is an enthusiastic developer and often releases code on her personal site, http://www.hilarymason.com. Hilary is also a co-founder of HACKNY-http://hackny.org" --mcdonald

==Bethany Nowviskie==
Bethany Nowviskie is the Director of the Scholars' Lab at UVA. From the website:

"Bethany helps shape UVA’s support for digital scholarship by running a Library department that includes the Scholars’ Lab and a crack R&D team devoted to scholarly interfaces. The SLab combines the services and resources of UVA Library’s former GeoStat and Etext Centers with end-user assistance from ITC’s Research Computing Support group. She is Associate Director of the Scholarly Information Institute (SCI), a Mellon funded think tank. Additionally, she is current Vice President of the Association for Computers and the Humanities (ACH), a member of the MLA's Committee on Information Technology, and is Senior Advisor to NINES, for which she designed the Collex tool. Her doctorate is in English, and she has worked in the digital humanities as a designer, manager, and editor since 1995. Bethany's own research lies in the intersection of traditional interpretive methods with innovative social and algorithmic tools."

Bethany thinks deeply and she's an awesome public speaker. Her recent address to the Center for Digital Research in the Humanities at the University of Nebraska Library is a good example of her work: [http://nowviskie.org/2011/a-skunk-in-the-library/ “A Skunk in the Library: the Path to Production for Scholarly R&D.”] . She also edits ''[http://mediacommons.futureofthebook.org/alt-ac/ Alternative Academic Careers for Humanities Scholars]''

==George Oates==
George is the lead for the Internet Archive Open Library and has worked on the web since 1996, in a variety of roles that normally revolve around front-end design and online community. She is entirely comfortable with "amateur" metadata creation and hopes to explore this within the context of Open Library. Prior to her work at IA George was a lead on the Flickr Commons Initiative. Currently George also serves as a Research Associate at the Smithsonian Institution Libraries. You can see more on her at http://www.abitofgeorge.com/ and http://www.archive.org/about/bios.php. She has a great article about software community on A List Apart - http://www.alistapart.com/articles/fromlittlethings. --mcdonald

==Kam Woods==
very exciting work on digital forensics
http://digitalcorpora.org/
His info: http://www.digpres.com/

==Steve Yegge==
Staff Software Engineer, Google

"Steve started high school at age 11 and graduated at 14. He then made the only logical choice, which was to play guitar in garage bands until he was 18, when he joined the U.S. Navy as a nuclear reactor operator. Steve went on to earn his B.S. in computer science from the University of Washington, then spent five years at Geoworks developing operating systems software in 8086 assembly language. He worked at various startups, then spent just under seven years at Amazon.com as a senior software development manager. In his spare time Steve built a massively multiplayer RPG that garnered him a grand prize at Comdex in 2002. Steve has been a Googler since 2005 and plans to stay there forever." -- http://conferences.oreillynet.com/cs/user/view/e_spkr/3489

Yegge recently delivered a keynote at OSCON Data 2011: http://www.youtube.com/watch?v=vKmQW_Nkfk8

==Jason Scott==
Jason Scott is an American archivist and computer historian. He is maintains [http://textfiles.com textfiles.com], a web site which archives files from historic bulletin board systems. He is also the creator of a 2005 documentary film about BBSes, [http://www.bbsdocumentary.com/ BBS: The Documentary], and a 2010 documentary film about interactive fiction, [http://www.getlamp.com/ GET LAMP]. He is also one of the responsible folks behind [http://archiveteam.org/index.php?title=Main_Page Archive Team] (who are here to rescue your shit), and writes often in his weblog [http://ascii.textfiles.com/ ASCII by Jason Scott]. He [http://ascii.textfiles.com/archives/3024 recently started working for the Internet Archive], too.

==William Turkel==
From his page at http://history.uwo.ca/faculty/turkel/ - Project Director, Digital Infrastructure for the SSHRC Strategic Knowledge Cluster

NiCHE: Network in Canadian History & Environment

"In my research and teaching I draw on, integrate and try to extend a number of different disciplines: environmental and public history, the histories of science and technology, 'big history', STS, computation, and studies of place and social memory."

Bill is an engaging and inspiring speaker who groks what we are trying to do with code4lib. I've seen him speak at THATCamp, Access 2009, and at code4lib north; his ability to bridge his interdisciplinary interests with what matters to us library hackers is unparalleled. He'd be a perfect fit and when I asked him this past spring if he'd consider speaking at code4lib he was willing and interested. --dchud

C4L2010draftschedule

2009-12-03T14:24:38Z

Ecorrado:

'''Monday'''

{|
|+ ''Day 0: Pre-conferences''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/coffee
|-
| 09:00 - 12:00 || morning sessions
|-
| 12:00 - 13:30 || lunch (on your own dime)
|-
| 13:30 - 16:30 || afternoon sessions
|}

'''Tuesday'''

{|
|+ ''Day 1: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/breakfast
|-
| 09:00 - 09:15 || welcome/orientation/housekeeping
|-
| 09:15 - 10:00 || keynote 1
|-
| 10:00 - 10:20 || talk 1
|-
| 10:20 - 10:40 || break
|-
| 10:40 - 12:00 || talks 2, 3, 4, 5
|-
| 12:00 - 13:00 || lunch (provided)
|-
| 13:00 - 14:20 || talks 6, 7, 8, 9
|-
| 14:20 - 14:40 || break || ''At beginning of this break, presenters can start signing up for Day 1 Lightning Talks''
|-
| 14:40 - 15:50 || breakouts 1
|-
| 15:50 - 17:00 || lightning talks 1
|-
| 17:00 - 17:15 || wrap-up (include breakout reports? or not useful?)
|}

'''Wednesday'''

{|
|+ ''Day 2: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:15 || housekeeping
|-
| 09:15 - 10:15 || talks 10, 11, 12
|-
| 10:15 - 10:35 || break
|-
| 10:35 - 11:15 || talks 13, 14
|-
| 11:15 - 12:00 || "Ask Anything!"
|-
| 12:00 - 13:00 || lunch (provided) || ''At beginning of this lunch, presenters can start signing up for Day 2 Lightning Talks''
|-
| 13:00 - 14:20 || talks 15, 16, 17, 18
|-
| 14:20 - 14:40 || break
|-
| 14:40 - 15:50 || breakouts 2
|-
| 15:50 - 17:00 || lightning talks 2
|-
| 17:00 - 17:15 || wrap-up (include breakout reports? or not useful?)
|}

'''Thursday'''

{|
|+ ''Day 3: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:15 || housekeeping || ''Presenters can begin to sign up for Day 3 Lightning Talks starting with Breakfast on Day 3''
|-
| 09:15 - 10:00 || keynote 2
|-
| 10:00 - 10:15|| break (short)
|-
| 10:15 - 11:00 || lightning talks 3 (short)
|-
| 11:00 - 11:20 || talk 19
|-
| 11:20 - 11:40 || talk 20
|-
| 11:40 - 12:00 || talk 21
|-
| 12:00 - 12:15 || wrap-up
|}

[[Category:Code4Lib2010]]

C4L2010draftschedule

2009-12-03T14:24:19Z

Ecorrado: Add presenter lightning sign up times.

'''Monday'''

{|
|+ ''Day 0: Pre-conferences''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/coffee
|-
| 09:00 - 12:00 || morning sessions
|-
| 12:00 - 13:30 || lunch (on your own dime)
|-
| 13:30 - 16:30 || afternoon sessions
|}

'''Tuesday'''

{|
|+ ''Day 1: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/breakfast
|-
| 09:00 - 09:15 || welcome/orientation/housekeeping
|-
| 09:15 - 10:00 || keynote 1
|-
| 10:00 - 10:20 || talk 1
|-
| 10:20 - 10:40 || break
|-
| 10:40 - 12:00 || talks 2, 3, 4, 5
|-
| 12:00 - 13:00 || lunch (provided)
|-
| 13:00 - 14:20 || talks 6, 7, 8, 9
|-
| 14:20 - 14:40 || break || 'At beginning of this break, presenters can start signing up for Day 1 Lightning Talks''
|-
| 14:40 - 15:50 || breakouts 1
|-
| 15:50 - 17:00 || lightning talks 1
|-
| 17:00 - 17:15 || wrap-up (include breakout reports? or not useful?)
|}

'''Wednesday'''

{|
|+ ''Day 2: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:15 || housekeeping
|-
| 09:15 - 10:15 || talks 10, 11, 12
|-
| 10:15 - 10:35 || break
|-
| 10:35 - 11:15 || talks 13, 14
|-
| 11:15 - 12:00 || "Ask Anything!"
|-
| 12:00 - 13:00 || lunch (provided) || ''At beginning of this lunch, presenters can start signing up for Day 2 Lightning Talks''
|-
| 13:00 - 14:20 || talks 15, 16, 17, 18
|-
| 14:20 - 14:40 || break
|-
| 14:40 - 15:50 || breakouts 2
|-
| 15:50 - 17:00 || lightning talks 2
|-
| 17:00 - 17:15 || wrap-up (include breakout reports? or not useful?)
|}

'''Thursday'''

{|
|+ ''Day 3: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:15 || housekeeping || ''Presenters can begin to sign up for Day 3 Lightning Talks starting with Breakfast on Day 3''
|-
| 09:15 - 10:00 || keynote 2
|-
| 10:00 - 10:15|| break (short)
|-
| 10:15 - 11:00 || lightning talks 3 (short)
|-
| 11:00 - 11:20 || talk 19
|-
| 11:20 - 11:40 || talk 20
|-
| 11:40 - 12:00 || talk 21
|-
| 12:00 - 12:15 || wrap-up
|}

[[Category:Code4Lib2010]]

C4L2010draftschedule

2009-11-30T17:27:14Z

Ecorrado:

'''Monday'''

{|
|+ ''Day 0: Pre-conferences''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/coffee
|-
| 09:00 - 12:00 || morning sessions
|-
| 12:00 - 13:30 || lunch (on your own dime)
|-
| 13:30 - 16:30 || afternoon sessions
|}

'''Tuesday'''

{|
|+ ''Day 1: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/breakfast
|-
| 09:00 - 09:15 || welcome/orientation/housekeeping
|-
| 09:15 - 10:00 || keynote 1
|-
| 10:00 - 10:20 || talk 1
|-
| 10:20 - 10:40 || break
|-
| 10:40 - 12:00 || talks 2, 3, 4, 5
|-
| 12:00 - 13:00 || lunch (provided)
|-
| 13:00 - 14:20 || talks 6, 7, 8, 9
|-
| 14:20 - 14:40 || break
|-
| 14:40 - 15:50 || breakouts 1
|-
| 15:50 - 17:00 || lightning talks 1
|-
| 17:00 - 17:15 || wrap-up (breakout reports? or not useful?)
|}

'''Wednesday'''

{|
|+ ''Day 2: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:15 || housekeeping
|-
| 09:15 - 10:15 || talks 10, 11, 12
|-
| 10:15 - 10:35 || break
|-
| 10:35 - 11:15 || talks 13, 14
|-
| 11:15 - 12:00 || "Ask Anything" || ''or'' talks 22, 23
|-
| 12:00 - 13:00 || lunch (provided)
|-
| 13:00 - 14:20 || talks 15, 16, 17, 18
|-
| 14:20 - 14:40 || break
|-
| 14:40 - 15:50 || breakouts 2
|-
| 15:50 - 17:00 || lightning talks 2
|-
| 17:00 - 17:15 || wrap-up (breakout reports? or not useful?)
|}

'''Thursday'''

{|
|+ ''Day 3: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:05 || housekeeping (short)
|-
| 09:10 - 9:50 || keynote 2
|-
| 9:50 - 10:00 || break (short)
|-
| 10:00 - 11:00 || lightning talks 3
|-
| 11:00 - 11:20 || talk 19
|-
| 11:20 - 11:40 || talk 20
|-
| 11:40 - noon || talk 21
|-
| noon - 12:10 || wrap-up (short)
|}

[[Category:Code4Lib2010]]

C4L2010draftschedule

2009-11-30T17:24:32Z

Ecorrado: Changed Ask Anything to 45 minutes.

'''Monday'''

{|
|+ ''Day 0: Pre-conferences''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/coffee
|-
| 09:00 - 12:00 || morning sessions
|-
| 12:00 - 13:30 || lunch (on your own dime)
|-
| 13:30 - 16:30 || afternoon sessions
|}

'''Tuesday'''

{|
|+ ''Day 1: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/breakfast
|-
| 09:00 - 09:15 || welcome/orientation/housekeeping
|-
| 09:15 - 10:00 || keynote 1
|-
| 10:00 - 10:20 || talk 1
|-
| 10:20 - 10:40 || break
|-
| 10:40 - 12:00 || talks 2, 3, 4, 5
|-
| 12:00 - 13:00 || lunch (provided)
|-
| 13:00 - 14:20 || talks 6, 7, 8, 9
|-
| 14:20 - 14:40 || break
|-
| 14:40 - 15:50 || breakouts 1
|-
| 15:50 - 17:00 || lightning talks 1
|-
| 17:00 - 17:15 || wrap-up (breakout reports? or not useful?)
|}

'''Wednesday'''

{|
|+ ''Day 2: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:15 || housekeeping
|-
| 09:15 - 10:15 || talks 10, 11, 12
|-
| 10:15 - 10:35 || break
|-
| 10:35 - 11:15 || talks 13, 14
|-
| 11:15 - 12:00 || "Ask Anything" || ''or'' talks 15, 16
|-
| 12:00 - 13:00 || lunch (provided)
|-
| 13:00 - 14:20 || talks 17, 18, 19, 20
|-
| 14:20 - 14:40 || break
|-
| 14:40 - 15:50 || breakouts 2
|-
| 15:50 - 17:00 || lightning talks 2
|-
| 17:00 - 17:15 || wrap-up (breakout reports? or not useful?)
|}

'''Thursday'''

{|
|+ ''Day 3: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:05 || housekeeping (short)
|-
| 09:10 - 9:50 || keynote 2
|-
| 9:50 - 10:00 || break (short)
|-
| 10:00 - 11:00 || lightning talks 3
|-
| 11:00 - 11:20 || talk 21
|-
| 11:20 - 11:40 || talk 22
|-
| 11:40 - noon || talk 23
|-
| noon - 12:10 || wrap-up (short)
|}

[[Category:Code4Lib2010]]

C4L2010draftschedule

2009-11-30T16:20:03Z

Ecorrado:

'''Monday'''

{|
|+ ''Day 0: Pre-conferences''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/coffee
|-
| 09:00 - 12:00 || morning sessions
|-
| 12:00 - 13:30 || lunch (on your own dime)
|-
| 13:30 - 16:30 || afternoon sessions
|}

'''Tuesday'''

{|
|+ ''Day 1: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/breakfast
|-
| 09:00 - 09:15 || welcome/orientation/housekeeping
|-
| 09:15 - 10:00 || keynote 1
|-
| 10:00 - 10:20 || talk 1
|-
| 10:20 - 10:40 || break
|-
| 10:40 - 12:00 || talks 2, 3, 4, 5
|-
| 12:00 - 13:00 || lunch (provided)
|-
| 13:00 - 14:20 || talks 6, 7, 8, 9
|-
| 14:20 - 14:40 || break
|-
| 14:40 - 15:50 || breakouts 1
|-
| 15:50 - 17:00 || lightning talks 1
|-
| 17:00 - 17:15 || wrap-up (breakout reports? or not useful?)
|}

'''Wednesday'''

{|
|+ ''Day 2: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:15 || housekeeping
|-
| 09:15 - 10:15 || talks 10, 11, 12
|-
| 10:15 - 10:35 || break
|-
| 10:35 - 12:00 || talks 13, 14, 15, 16 ||'' or'' "Ask Anything" || ''or'' talks 13, 14 and 45 minutes of "Ask Anything"
|-
| 12:00 - 13:00 || lunch (provided)
|-
| 13:00 - 14:20 || talks 17, 18, 19, 20
|-
| 14:20 - 14:40 || break
|-
| 14:40 - 15:50 || breakouts 2
|-
| 15:50 - 17:00 || lightning talks 2
|-
| 17:00 - 17:15 || wrap-up (breakout reports? or not useful?)
|}

'''Thursday'''

{|
|+ ''Day 3: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:05 || housekeeping (short)
|-
| 09:10 - 9:50 || keynote 2
|-
| 9:50 - 10:00 || break (short)
|-
| 10:00 - 11:00 || lightning talks 3
|-
| 11:00 - 11:20 || talk 21
|-
| 11:20 - 11:40 || talk 22
|-
| 11:40 - noon || talk 23
|-
| noon - 12:10 || wrap-up (short)
|}

[[Category:Code4Lib2010]]

C4L2010draftschedule

2009-11-30T16:19:10Z

Ecorrado:

'''Monday'''

{|
|+ ''Day 0: Pre-conferences''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/coffee
|-
| 09:00 - 12:00 || morning sessions
|-
| 12:00 - 13:30 || lunch (on your own dime)
|-
| 13:30 - 16:30 || afternoon sessions
|}

'''Tuesday'''

{|
|+ ''Day 1: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| registration/breakfast
|-
| 09:00 - 09:15 || welcome/orientation/housekeeping
|-
| 09:15 - 10:00 || keynote 1
|-
| 10:00 - 10:20 || talk 1
|-
| 10:20 - 10:40 || break
|-
| 10:40 - 12:00 || talks 2, 3, 4, 5
|-
| 12:00 - 13:00 || lunch (provided)
|-
| 13:00 - 14:20 || talks 6, 7, 8, 9
|-
| 14:20 - 14:40 || break
|-
| 14:40 - 15:50 || breakouts 1
|-
| 15:50 - 17:00 || lightning talks 1
|-
| 17:00 - 17:15 || wrap-up (breakout reports? or not useful?)
|}

'''Wednesday'''

{|
|+ ''Day 2: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:15 || housekeeping
|-
| 09:15 - 10:15 || talks 10, 11, 12
|-
| 10:15 - 10:35 || break
|-
| 10:35 - 12:00 || talks 13, 14, 15, 16 || "Ask Anything" || talks 13, 14 and 45 minutes of "Ask Anything"
|-
| 12:00 - 13:00 || lunch (provided)
|-
| 13:00 - 14:20 || talks 17, 18, 19, 20
|-
| 14:20 - 14:40 || break
|-
| 14:40 - 15:50 || breakouts 2
|-
| 15:50 - 17:00 || lightning talks 2
|-
| 17:00 - 17:15 || wrap-up (breakout reports? or not useful?)
|}

'''Thursday'''

{|
|+ ''Day 3: Conference''
|-
|width="130pt"| 08:00 - 09:00
|width="170pt"| breakfast
|-
| 09:00 - 09:05 || housekeeping (short)
|-
| 09:10 - 9:50 || keynote 2
|-
| 9:50 - 10:00 || break (short)
|-
| 10:00 - 11:00 || lightning talks 3
|-
| 11:00 - 11:20 || talk 21
|-
| 11:20 - 11:40 || talk 22
|-
| 11:40 - noon || talk 23
|-
| noon - 12:10 || wrap-up (short)
|}

[[Category:Code4Lib2010]]

C4L2010draftschedule

2009-11-17T21:18:05Z

Ecorrado:

'''Monday'''

preconferences

8-9 registration/coffee
9-12 morning
12-1:30 lunch on your own
1:30-4:30 afternoon

'''Tuesday'''

8-9 registration/breakfast
9-9:15 welcome/announcements
9:15-10 keynote
10-10:20 talk 1
10:20-10:40 break
10:40-12 talks 2, 3, 4, 5
12-1 lunch (provided)
1-2:20 talks 6, 7, 8, 9
2:20-2:40 break
2:40-3:50 lightning talks 1
3:50-5 breakouts 1
5-5:15 wrap up

'''Wednesday'''

8-9 breakfast
9-9:15 housekeeping
9:15-10:15 talks 10, 11, 12
10:15-10:35 break
10:35-12 talks 13, 14, 15, 16
12-1 lunch (provided)
1-2:20 talks 17, 18, 19, 20
2:20-2:40 break
2:40-3:50 breakouts 2
3:50-5 lightning talks 2
5-5:15 wrap up

'''Thursday'''

8-9 breakfast
9-9:15 housekeeping
9:15-10:20 keynote 2
10:20-10:40 break
10:40-12 lightning talks 3

Code4Lib Corrections

2009-01-07T17:25:39Z

Ecorrado:

There are three approaches to correcting a published article, depending on the impact of the correction.

Corrections to spelling or simple grammar (a change in punctuation, etc.) should simply be made.

Corrections that change the wording of the article should be made inline, with a "Corrections" section added at the end of the article outlining the date and the change made. This should be done only if absolutely necessary.

A clarification or explanation of the text should be made in the "Corrections" section, with a note added to the original text to "See Correction", linked to the explanation/clarification. See, for example, [http://journal.code4lib.org/articles/527 We Love Open Source Software. No, You Can’t Have Our Code] (Issue 5).

[[Category: Code4Lib Journal]]