Code4Lib - User contributions [en]

Code4Lib Journal Email Templates

2009-08-04T17:48:15Z

Jodi: /* Proposal Accepted */

''See also [[Code4Lib_Journal_Deadlines]]''

== Call for proposals ==

'''Change what's in bold...'''

----

Call for Papers (and apologies for cross-posting):

The Code4Lib Journal (C4LJ) exists to foster community and share
information among those interested in the intersection of libraries,
technology, and the future.

The Code4Lib Journal is now accepting proposals for publication in its
8th issue. Don't miss out on this opportunity to share your ideas and
experiences. To be included in the '''8th issue''', which is scheduled for
publication in '''mid November 2009''', please submit articles, abstracts,
or proposals to c4lj-articles@googlegroups.com by '''Friday, August 14, 2009'''.
When submitting, please include the title or subject of the
proposal in the subject line of the email message.

C4LJ encourages creativity and flexibility, and the editors welcome
submissions across a broad variety of topics that support the mission
of the journal. Possible topics include, but are not limited to:

* Practical applications of library technology (both actual and hypothetical)
* Technology projects (failed, successful, or proposed), including how they were done and challenges faced
* Case studies
* Best practices
* Reviews
* Comparisons of third party software or libraries
* Analyses of library metadata for use with technology
* Project management and communication within the library environment
* Assessment and user studies

C4LJ strives to promote professional communication by minimizing the
barriers to publication. While articles should be of a high quality,
they need not follow any formal structure. Writers should aim for the
middle ground between blog posts and articles in traditional refereed
journals. Where appropriate, we encourage authors to submit code
samples, algorithms, and pseudo-code. For more information, visit
C4LJ's Article Guidelines or browse articles from the first '''7''' issues
published on our website: http://journal.code4lib.org.

Remember, for consideration for the '''8th issue''', please send proposals,
abstracts, or draft articles to c4lj-articles@googlegroups.com no
later than '''Friday, August 14, 2009'''.

Send in a submission. Your peers would like to hear what you are doing.

Code4Lib Journal Editorial Committee

== Submission Acknowledgement ==

Thanks for submitting a proposal to the Code4Lib Journal. We appreciate your participation in the code4lib community. The editors have received your proposal and should be in touch with you in 2-4 weeks regarding its appropriateness for publication in C4LJ. We will notify you if we need additional information to make this decision. Please feel free to contact us at c4lj-articles@googlegroups.com if you have additional questions.

== Need More Information ==

Thank you for your interest in publishing in the Code4Lib Journal. The Journal is primarily focused on technological issues in libraries. In order to help the editors determine if your proposal is appropriate for this publication, could you share more details about the intended audience for the the article and how it will address issues surrounding technology in libraries? Please respond to c4lj-articles@googlegroups.com with the additional information requested.

You may also contact the editors at c4lj-articles@googlegroups.com if you have any additional questions. We look forward to hearing from you.

== Proposal Accepted ==

'''See also [[Code4Lib_Journal_Deadlines]]'''

I'm pleased to tell you that your recent proposal for an article about
<insert topic/title> has been provisionally accepted to the Code4Lib
Journal. The editorial committee is interested in your proposal, and
would like to see a draft.

<insert any additional comments about focus we'd like to see in the
article or editorial committee concerns. Sample language "We're
especially interested in X, and we'd like you to make sure to flesh
this out when you write the article." "We're interested in this
proposal if you can do X, Y, or Z.">

As a member of the Code4Lib Journal editorial committee, I will be
your contact for this article, and will work with you to get it ready
for publication.

We hope to publish your article in issue <#> of the Journal, which is
scheduled to appear on <insert date here>. The deadline for submission
of a complete draft is <deadline for draft>, but the sooner you can
get us a draft the better, and the more likely we'll be able to get
your article into issue <#>. Upon receipt of the draft, I will work
with you to address any changes recommended by the Editorial
Committee. More information about our author guidelines may be found
at http://journal.code4lib.org/article-guidelines.

Please note that final drafts must be approved by a vote of the
Editorial Committee before being published.

We also require all authors to agree to CC-BY licensing for the
articles we publish in the journal. We recommend that any included
code also have some type of code-specific open source license (such as
the GPL).

We look forward to seeing a complete draft and hope to include it in
the Journal. Thank you for submitting to us, and feel free to contact
me directly with any questions.

== Proposal Rejected ==

We regret to inform you that your recent proposal to the Code4Lib Journal for an article about <insert topic/title> has not been accepted for publication. This is likely because the Editorial Committee determined that it was not an appropriate match for the audience, mission, or scope of the Code4Lib Journal. [optional - insert comment here about why it's not appropriate]

For more information about the mission of the Code4Lib Journal, please see http://journal.code4lib.org/mission/.

Thanks for considering us, and please do not hesitate to contact the editors at c4lj-articles@googlegroups.com in the future with a new or revised proposal.

[[Category: Code4Lib Journal]]

Code4Lib Journal Email Templates

2009-08-04T17:47:46Z

Jodi: /* Proposal Accepted */ linking to deadlines page

''See also [[Code4Lib_Journal_Deadlines]]''

== Call for proposals ==

'''Change what's in bold...'''

----

Call for Papers (and apologies for cross-posting):

The Code4Lib Journal (C4LJ) exists to foster community and share
information among those interested in the intersection of libraries,
technology, and the future.

The Code4Lib Journal is now accepting proposals for publication in its
8th issue. Don't miss out on this opportunity to share your ideas and
experiences. To be included in the '''8th issue''', which is scheduled for
publication in '''mid November 2009''', please submit articles, abstracts,
or proposals to c4lj-articles@googlegroups.com by '''Friday, August 14, 2009'''.
When submitting, please include the title or subject of the
proposal in the subject line of the email message.

C4LJ encourages creativity and flexibility, and the editors welcome
submissions across a broad variety of topics that support the mission
of the journal. Possible topics include, but are not limited to:

* Practical applications of library technology (both actual and hypothetical)
* Technology projects (failed, successful, or proposed), including how they were done and challenges faced
* Case studies
* Best practices
* Reviews
* Comparisons of third party software or libraries
* Analyses of library metadata for use with technology
* Project management and communication within the library environment
* Assessment and user studies

C4LJ strives to promote professional communication by minimizing the
barriers to publication. While articles should be of a high quality,
they need not follow any formal structure. Writers should aim for the
middle ground between blog posts and articles in traditional refereed
journals. Where appropriate, we encourage authors to submit code
samples, algorithms, and pseudo-code. For more information, visit
C4LJ's Article Guidelines or browse articles from the first '''7''' issues
published on our website: http://journal.code4lib.org.

Remember, for consideration for the '''8th issue''', please send proposals,
abstracts, or draft articles to c4lj-articles@googlegroups.com no
later than '''Friday, August 14, 2009'''.

Send in a submission. Your peers would like to hear what you are doing.

Code4Lib Journal Editorial Committee

== Submission Acknowledgement ==

Thanks for submitting a proposal to the Code4Lib Journal. We appreciate your participation in the code4lib community. The editors have received your proposal and should be in touch with you in 2-4 weeks regarding its appropriateness for publication in C4LJ. We will notify you if we need additional information to make this decision. Please feel free to contact us at c4lj-articles@googlegroups.com if you have additional questions.

== Need More Information ==

Thank you for your interest in publishing in the Code4Lib Journal. The Journal is primarily focused on technological issues in libraries. In order to help the editors determine if your proposal is appropriate for this publication, could you share more details about the intended audience for the the article and how it will address issues surrounding technology in libraries? Please respond to c4lj-articles@googlegroups.com with the additional information requested.

You may also contact the editors at c4lj-articles@googlegroups.com if you have any additional questions. We look forward to hearing from you.

== Proposal Accepted ==

'''See also [Code4Lib_Journal_Deadlines]'''

I'm pleased to tell you that your recent proposal for an article about
<insert topic/title> has been provisionally accepted to the Code4Lib
Journal. The editorial committee is interested in your proposal, and
would like to see a draft.

<insert any additional comments about focus we'd like to see in the
article or editorial committee concerns. Sample language "We're
especially interested in X, and we'd like you to make sure to flesh
this out when you write the article." "We're interested in this
proposal if you can do X, Y, or Z.">

As a member of the Code4Lib Journal editorial committee, I will be
your contact for this article, and will work with you to get it ready
for publication.

We hope to publish your article in issue <#> of the Journal, which is
scheduled to appear on <insert date here>. The deadline for submission
of a complete draft is <deadline for draft>, but the sooner you can
get us a draft the better, and the more likely we'll be able to get
your article into issue <#>. Upon receipt of the draft, I will work
with you to address any changes recommended by the Editorial
Committee. More information about our author guidelines may be found
at http://journal.code4lib.org/article-guidelines.

Please note that final drafts must be approved by a vote of the
Editorial Committee before being published.

We also require all authors to agree to CC-BY licensing for the
articles we publish in the journal. We recommend that any included
code also have some type of code-specific open source license (such as
the GPL).

We look forward to seeing a complete draft and hope to include it in
the Journal. Thank you for submitting to us, and feel free to contact
me directly with any questions.

== Proposal Rejected ==

We regret to inform you that your recent proposal to the Code4Lib Journal for an article about <insert topic/title> has not been accepted for publication. This is likely because the Editorial Committee determined that it was not an appropriate match for the audience, mission, or scope of the Code4Lib Journal. [optional - insert comment here about why it's not appropriate]

For more information about the mission of the Code4Lib Journal, please see http://journal.code4lib.org/mission/.

Thanks for considering us, and please do not hesitate to contact the editors at c4lj-articles@googlegroups.com in the future with a new or revised proposal.

[[Category: Code4Lib Journal]]

Code4Lib Journal Deadlines

2009-08-04T17:33:39Z

Jodi: /* Deadlines for Issues */ linking to Tom's script

''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

=== Ninth issue ===
TBD

=== 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]]

Code4Lib Journal Deadlines

2009-08-04T17:29:31Z

Jodi: /* Eighth issue */ updating dates (based on slippage & editors' article spreadsheet)

''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 ==

=== 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]]

Code4Lib Journal Email Templates

2009-08-04T17:23:55Z

Jodi: /* Call for proposals */ adding bold to make the things that need to change stand out

''See also [[Code4Lib_Journal_Deadlines]]''

== Call for proposals ==

'''Change what's in bold...'''

----

Call for Papers (and apologies for cross-posting):

The Code4Lib Journal (C4LJ) exists to foster community and share
information among those interested in the intersection of libraries,
technology, and the future.

The Code4Lib Journal is now accepting proposals for publication in its
8th issue. Don't miss out on this opportunity to share your ideas and
experiences. To be included in the '''8th issue''', which is scheduled for
publication in '''mid November 2009''', please submit articles, abstracts,
or proposals to c4lj-articles@googlegroups.com by '''Friday, August 14, 2009'''.
When submitting, please include the title or subject of the
proposal in the subject line of the email message.

C4LJ encourages creativity and flexibility, and the editors welcome
submissions across a broad variety of topics that support the mission
of the journal. Possible topics include, but are not limited to:

* Practical applications of library technology (both actual and hypothetical)
* Technology projects (failed, successful, or proposed), including how they were done and challenges faced
* Case studies
* Best practices
* Reviews
* Comparisons of third party software or libraries
* Analyses of library metadata for use with technology
* Project management and communication within the library environment
* Assessment and user studies

C4LJ strives to promote professional communication by minimizing the
barriers to publication. While articles should be of a high quality,
they need not follow any formal structure. Writers should aim for the
middle ground between blog posts and articles in traditional refereed
journals. Where appropriate, we encourage authors to submit code
samples, algorithms, and pseudo-code. For more information, visit
C4LJ's Article Guidelines or browse articles from the first '''7''' issues
published on our website: http://journal.code4lib.org.

Remember, for consideration for the '''8th issue''', please send proposals,
abstracts, or draft articles to c4lj-articles@googlegroups.com no
later than '''Friday, August 14, 2009'''.

Send in a submission. Your peers would like to hear what you are doing.

Code4Lib Journal Editorial Committee

== Submission Acknowledgement ==

Thanks for submitting a proposal to the Code4Lib Journal. We appreciate your participation in the code4lib community. The editors have received your proposal and should be in touch with you in 2-4 weeks regarding its appropriateness for publication in C4LJ. We will notify you if we need additional information to make this decision. Please feel free to contact us at c4lj-articles@googlegroups.com if you have additional questions.

== Need More Information ==

Thank you for your interest in publishing in the Code4Lib Journal. The Journal is primarily focused on technological issues in libraries. In order to help the editors determine if your proposal is appropriate for this publication, could you share more details about the intended audience for the the article and how it will address issues surrounding technology in libraries? Please respond to c4lj-articles@googlegroups.com with the additional information requested.

You may also contact the editors at c4lj-articles@googlegroups.com if you have any additional questions. We look forward to hearing from you.

== Proposal Accepted ==

I'm pleased to tell you that your recent proposal for an article about
<insert topic/title> has been provisionally accepted to the Code4Lib
Journal. The editorial committee is interested in your proposal, and
would like to see a draft.

<insert any additional comments about focus we'd like to see in the
article or editorial committee concerns. Sample language "We're
especially interested in X, and we'd like you to make sure to flesh
this out when you write the article." "We're interested in this
proposal if you can do X, Y, or Z.">

As a member of the Code4Lib Journal editorial committee, I will be
your contact for this article, and will work with you to get it ready
for publication.

We hope to publish your article in issue <#> of the Journal, which is
scheduled to appear on <insert date here>. The deadline for submission
of a complete draft is <deadline for draft>, but the sooner you can
get us a draft the better, and the more likely we'll be able to get
your article into issue <#>. Upon receipt of the draft, I will work
with you to address any changes recommended by the Editorial
Committee. More information about our author guidelines may be found
at http://journal.code4lib.org/article-guidelines.

Please note that final drafts must be approved by a vote of the
Editorial Committee before being published.

We also require all authors to agree to CC-BY licensing for the
articles we publish in the journal. We recommend that any included
code also have some type of code-specific open source license (such as
the GPL).

We look forward to seeing a complete draft and hope to include it in
the Journal. Thank you for submitting to us, and feel free to contact
me directly with any questions.

== Proposal Rejected ==

We regret to inform you that your recent proposal to the Code4Lib Journal for an article about <insert topic/title> has not been accepted for publication. This is likely because the Editorial Committee determined that it was not an appropriate match for the audience, mission, or scope of the Code4Lib Journal. [optional - insert comment here about why it's not appropriate]

For more information about the mission of the Code4Lib Journal, please see http://journal.code4lib.org/mission/.

Thanks for considering us, and please do not hesitate to contact the editors at c4lj-articles@googlegroups.com in the future with a new or revised proposal.

[[Category: Code4Lib Journal]]

C4L2010planning

2009-07-24T18:18:18Z

Jodi: /* Draft Timeline '''DO NOT TRUST THESE DATES''' */

== Tasks ==
* sponsorships (see [[committees sign-up page]])
* keynote speakers (see [[committees sign-up page]] and [[nominations list]])
* program committee (20-minute talks) (see [[committees sign-up page]])
* scholarship committee (see [[committees sign-up page]])
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future) (see [[How To Plan A Code4LibCon]] )
* T-shirt committee (see [[committees sign-up page]])
* social activities (see [[committees sign-up page]])
* voting coordination (see [[committees sign-up page]])
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning

== Draft Timeline '''DO NOT TRUST THESE DATES'''==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June: Choose Conference planners

May to June: Negotiate Hotel contract

May to June: Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs) see also [[Nominations_list]]

July 15th – Formally solicit sponsors

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

August 20th – Follow up with sponsors

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

==When do these things happen?==

*Making T-shirts
*Planning conference menus
*Arranging videotaping
*Securing conference networking
*Getting A/V supplies
*Arranging 3 OS laptop for presenters (ask mbklein)

==Other things to be done?==

==Random stuff==
[http://digital.library.appstate.edu/code4lib2010.html Original Proposal]

[http://vote.code4lib.org/election/results/9 Voting results]
[[Category: Code4Lib2010]]

2010 Nominations list

2009-07-24T18:16:58Z

Jodi: adding category

Nominations for invited speakers for Code4Lib 2010. Alphabetical order. Not yet complete

== Mitchell Baker ==

"Chair of the Mozilla Foundation is an excellent speaker, and perhaps a more modern evangelist for open source and a gimmick-free web."

== Stephen Downes ==

"[http://www.downes.ca/] a great speaker and works with the Canadian National Research Council. He would definitely bring a more teaching and learning perspective to his talk."

"I've also seen Stephen talk and he offers a nice blend of tech, metadata, and end-user perspective."

== Paul Jones ==

"Paul Jones, the director of ibiblio.org. He's a poet, teaches at a journalism school and a library school, he's a part of internet and open source history (how many of you downloaded your first linux distro from sunsite.unc.edu?) and he's a fantastic public speaker. Here's an extract from his website (http://www.ibiblio.org/pjones/): "Although often mistaken for other unreconstructed relics of the failed social policies of the Sixties, Paul Jones is the Director of ibiblio.org, a project that includes the Site Formerly Known as MetaLab and SunSITE, The Public's Library -- a large contributor-run digital library. Besides speaking at several conferences world-wide, Paul teaches on the faculties of the School of Journalism and Mass Communication and the School of Information and Library Science. He can be found many places on the Internet. He was the original manager of SunSITE.unc.edu, one of the first WWW sites in North America and is co-author of The Web Server Book (Ventana, 1995) (rereleased as The Unix Web Server Book, Second Edition Ventana, 1997). Jones has an additional on-going research interest in Open Source and Sharing Communities and Information policy issues as well as being an actively publishing poet. Paul is the editor of the Internet Poetry Archives, published with UNC Press. Paul is a founding board member of the American Open Technology Consortium, a member of the Board of Trustees of Chapel Hill Public Library, and a board member of the Linux Documentation Project. But he is most pleased to have been admitted into the Luxuriant Flowing Hair Club for Scientists and to have been selected in April 2003 as Best Geek in the Research Triangle by the Independent Weekly. "

"I've known Paul for years, although unfortunately my interactions with him in recent years have been few. In addition to the bio below, he's funny and his sense of humor gains an additional kick by being delivered in a Southern drawl. <hyperbole>I'd run over kids in strollers to hear him speak.</hyperbole>"

== Penny Leach ==

"2009 Google Open Source Award winner in the "Best Education Hacker" category, and a contributor to both Moodle and Mahara. From her blog: "This is a website about me. I am just this girl, who works on open source web based education stuff, and drinks too much."

== Andy Lester ==

author of ack "a grep replacement" and itinerant speaker on "Technical Debt" and employment in the tech world. He's a Perl guru working in the publishing indsutry. Andy's "Technical Debt" lecture would be a good fit, IMO, for the code4lib group.

* Technical Debt Talk: http://www.media-landscape.com/yapc/2006-06-26.AndyLester/

* Employment Stuff: http://theworkinggeek.com/

* He spoke at OSCON year on a couple of topics: http://en.oreilly.com/oscon2009/public/schedule/speaker/6552

* find him at twitter at: http://twitter.com/PetDance

== Joe Lucia ==

"at Villanova. He is a Library Director who fully supports Open Source software and speaks on it from time to time. He was the keynote speaker at the recent Evergreen conference."

== Clifford Lynch ==

== Cathy Marshall ==

"Senior Researcher at Microsoft Research. She's working in personal digital archiving and personal information management.I've been really impressed with two of her recent projects: a talk at ASIST '08 about myths of digital archiving [1] and her JCDL 2009 paper "No bull, No spin"[2]--which examined zillions of flickr photos of a particular tourist attraction to understand how they used tags. Despite being a serious researcher, Cathy is very down-to-earth (check her twitter feed http://twitter.com/ccmarshall or her older and sometimes bizarre hypertext art). I think she'd be a great keynoter for Code4Lib.

Her homepages:
http://research.microsoft.com/en-us/people/cathymar/
http://www.csdl.tamu.edu/~marshall/

[1] http://research.microsoft.com/en-us/people/cathymar/asist-marshall.pdf
[2] http://research.microsoft.com/apps/pubs/default.aspx?id=80591

== Peter Morville ==

"most commonly known as the author of 'Ambient Findability', and co-author of 'Information Architecture for the World Wide Web'. He's president and founder of [http://www.semanticstudios.com Semantic Studios ] [1], teacher at UMich, and blogger at [http://findability.org findability.org].

== Randall Munroe ==
"programmer/math geek/xkcd creator/all-around genius. His Authors@Google talk was pretty entertaining, and he seems like the kind of guy who would put some effort into surprising and engaging the crowd he's talking to."

== Mark Pilgrim ==

* He knows (real world, not necessarily library) standards about as well as anyone and advocates strongly for what's simple and practical (check out his work on Atom and HTML5), but he's also an advocate for doing what's right even when it's not necessarily easy (http://diveintoaccessibility.org/)

* He's updating Dive Into Python (http://diveintopython3.org/)

* He's funny, writes well, and seems to be articulate in person (based on his short-lived video log)

* He lives in NC

* His mother was a librarian (http://diveintomark.org/archives/2002/06/02/more_on_social_networks)

== Daniel Pitti ==

"[http://iath.virginia.edu/~dvp4c] - formerly an authority control librarian, now a co-director for University of Virginia's Institute for Advanced Technology in the Humanities. He's been the chief technical architect for EAD and EAC (Encoded Archival Context), a companion data model thats much more machine-oriented and linked data-friendly. He's also worked on some really great, innovative digital humanities projects.."

== Richard Stallman ==

"he has repeatedly expressed an interest in attending; he apparently wants to tell us the real/ true meaning of free and open source software."

== Joan Frye Williams ==

"She's not a developer-type, but Joan Frye Williams has a lot of insights that she might be willing to turn towards the issues C4L discusses. They might not be what we want to hear, but sometimes that's a good thing."

"mostly because I know of few people with such a practical bent and I think it would be helpful to hear her perspective on what library coders might be able to do to help the largest number of people."

== Jonathan Zittrain ==
[1]
"co-founder of Harvard's Berkman Center for Internet and Society [2] (where David Weinberger is a fellow [3]) and author of "The Future of the Internet and How to Stop It" [4]. I heard him speak at a conference last year, largely on the implications of the Google Book deal. He was speaking without notes, very entertaining and knowledgeable both on technical and legal details. Also, according to his bio [1]," He was co-counsel with Lawrence Lessig in Eldred v. Ashcroft, challenging the Sonny Bono Copyright Term Extension Act of 1998." And "performed the first large-scale tests of Internet filtering in China and Saudi Arabia in 2002"

[1] http://futureoftheinternet.org/about
[2] http://cyber.law.harvard.edu/
[3] http://cyber.law.harvard.edu/people/dweinberger
[4] http://futureoftheinternet.org/

[[Code4Lib2010]]

How To Plan A Code4LibCon

2009-07-10T01:52:47Z

Jodi: /* Important Resources */ linking listservs

* Apply to be a host
* Get approved by the community
* Find a hotel, negotiate and sign a contract with them
* Invite the community to help with
* Have a timeline

== Important Resources ==
* Past calls for host sites: [http://code4lib.org/node/275 2010] -
* [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]
* [http://groups.google.com/group/code4libcon Code4LibCon listserv]
* Sponsorship info (public)

== Important Private Resources ==
* Code4LibCon-hostsite listserv
* Budgets from previous years
* Sponsorship info (private)

== Suggested Timeline ==
* See [[C4L2010planning]] for an example

[[Category: Code4Lib2010]]

Committees sign-up page

2009-07-01T18:09:44Z

Jodi:

__NOTOC__
= Code4Lib 2010 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2010 conference, 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 will take place on the Code4LibCon mailing list. Please feel free to improve the summary statements for each of the committees.

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it is comprised of 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.

* Kevin Clarke
* Andrew Nagy

== 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.

* Kevin Clarke
* Mike Giarlo (interested in liaising re: voting--will send email and reminders about voting)

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.

* Roy Tennant
* Susan Teague-Rector
* Mike Giarlo (interested in liaising re: voting--will send email and reminders about voting)

== 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.

* Edward M. Corrado
* Jean Rainwater

== T-Shirt Committee ==

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

* Mike Giarlo (interested in liaising re: voting--will send email and reminders about voting)

== Social Activities Committee ==

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

* Kevin Clarke
* Susan Teague-Rector

== 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.

* Ross Singer
* Mike Giarlo

= 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.

* Jodi Schneider
* Daniel Lovins
[[Category: Code4Lib2010]]

Committees sign-up page

2009-07-01T14:59:05Z

Jodi:

__NOTOC__
= Code4Lib 2010 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2010 conference, 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 will take place on the Code4LibCon mailing list. Please feel free to improve the summary statements for each of the committees.

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it is comprised of 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.

* Kevin Clarke

== 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.

* Kevin Clarke

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc.

* Kevin Clarke

== 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.

* Edward M. Corrado

== T-Shirt Committee ==

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

== Social Activities Committee ==

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

* Kevin Clarke

== 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.

* Ross Singer

= 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.

* Jodi Schneider
[[Category: Code4Lib2010]]

C4L2010planning

2009-07-01T14:57:30Z

Jodi: /* Tasks */

== Tasks ==
* sponsorships (see [[committees sign-up page]])
* keynote speakers (see [[committees sign-up page]])
* program committee (20-minute talks) (see [[committees sign-up page]])
* scholarship committee (see [[committees sign-up page]])
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future) (see [[How To Plan A Code4LibCon]] )
* T-shirt committee (see [[committees sign-up page]])
* social activities (see [[committees sign-up page]])
* voting coordination (see [[committees sign-up page]])
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning

== Draft Timeline '''DO NOT TRUST THESE DATES'''==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June: Choose Conference planners

May to June: Negotiate Hotel contract

May to June: Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

July 15th – Formally solicit sponsors

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

August 20th – Follow up with sponsors

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

==When do these things happen?==

*Making T-shirts
*Planning conference menus
*Arranging videotaping
*Securing conference networking
*Getting A/V supplies
*Arranging 3 OS laptop for presenters (ask mbklein)

==Other things to be done?==

[[Category: Code4Lib2010]]

C4L2010planning

2009-07-01T14:57:16Z

Jodi: /* Tasks */

== Tasks ==
* sponsorships (see [[committees sign-up page]])
* keynote speakers (see [[committees sign-up page]])
* program committee (20-minute talks) (see [[committees sign-up page]])
* scholarship committee (see [[committees sign-up page]])
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future) (see [[How To Plan A Code4LibCon]]
* T-shirt committee (see [[committees sign-up page]])
* social activities (see [[committees sign-up page]])
* voting coordination (see [[committees sign-up page]])
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning

== Draft Timeline '''DO NOT TRUST THESE DATES'''==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June: Choose Conference planners

May to June: Negotiate Hotel contract

May to June: Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

July 15th – Formally solicit sponsors

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

August 20th – Follow up with sponsors

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

==When do these things happen?==

*Making T-shirts
*Planning conference menus
*Arranging videotaping
*Securing conference networking
*Getting A/V supplies
*Arranging 3 OS laptop for presenters (ask mbklein)

==Other things to be done?==

[[Category: Code4Lib2010]]

How To Plan A Code4LibCon

2009-07-01T14:56:29Z

Jodi:

* Apply to be a host
* Get approved by the community
* Find a hotel, negotiate and sign a contract with them
* Invite the community to help with
* Have a timeline

== Important Resources ==
* Past calls for hostsites
* Code4Lib listserv
* Code4LibCon listserv
* Sponsorship info (public)

== Important Private Resources ==
* Code4LibCon-hostsite listserv
* Budgets from previous years
* Sponsorship info (private)

== Suggested Timeline ==
* Do this
* Then that
* Then some other thing

[[Category: Code4Lib2010]]

How To Plan A Code4LibCon

2009-07-01T14:56:06Z

Jodi: New page: * Apply to be a host * Get approved by the community * Find a hotel, negotiate and sign a contract with them * Invite the community to help with * Have a timeline == Important Resources...

* Apply to be a host
* Get approved by the community
* Find a hotel, negotiate and sign a contract with them
* Invite the community to help with
* Have a timeline

== Important Resources ==
* Past calls for hostsites
* Code4Lib listserv
* Code4LibCon listserv
* Sponsorship info (public)

== Important Private Resources ==
* Code4LibCon-hostsite listserv
* Budgets from previous years
* Sponsorship info (private)

== Suggested Timeline ==
* Do this
* Then that
* Then some other thing

Committees sign-up page

2009-07-01T14:42:25Z

Jodi: /* Voting Activities Committee */

__NOTOC__
= Code4Lib 2010 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2010 conference, 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 will take place on the Code4LibCon mailing list. Please feel free to improve the summary statements for each of the committees.

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it is comprised of 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.

* Kevin Clarke

== 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.

* Kevin Clarke

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc.

* Kevin Clarke

== 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.

== T-Shirt Committee ==

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

== Social Activities Committee ==

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

* Kevin Clarke

== 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.

* Ross Singer

[[Category: Code4Lib2010]]

Committees sign-up page

2009-07-01T14:41:29Z

Jodi: /* Keynote Speakers Committee */

__NOTOC__
= Code4Lib 2010 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2010 conference, 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 will take place on the Code4LibCon mailing list. Please feel free to improve the summary statements for each of the committees.

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it is comprised of 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.

* Kevin Clarke

== 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.

* Kevin Clarke

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc.

* Kevin Clarke

== 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.

== T-Shirt Committee ==

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

== Social Activities Committee ==

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

* Kevin Clarke

== Voting Activities Committee ==

This committee organizes the voting process and works with the other committees that involve voting to ensure a relatively smooth process.

* Ross Singer

[[Category: Code4Lib2010]]

Committees sign-up page

2009-07-01T14:40:19Z

Jodi: removed TOC

__NOTOC__
= Code4Lib 2010 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2010 conference, 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 will take place on the Code4LibCon mailing list. Please feel free to improve the summary statements for each of the committees.

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it is comprised of 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.

* Kevin Clarke

== Keynote Speakers Committee ==

This committee plans who to invite for the keynote speakers. They gather possibilities and work with the speakers to arrange their travel and arrangements.

* Kevin Clarke

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc.

* Kevin Clarke

== 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.

== T-Shirt Committee ==

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

== Social Activities Committee ==

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

* Kevin Clarke

== Voting Activities Committee ==

This committee organizes the voting process and works with the other committees that involve voting to ensure a relatively smooth process.

* Ross Singer

[[Category: Code4Lib2010]]

Main Page

2009-07-01T14:38:46Z

Jodi: /* Code4libcon 2010 */

__NOTOC__
= Code4Lib Wiki =

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest

== Interest Groups ==

* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Getting Started with Zebra]] - indexing and searching MARC records
* [[ruby-marc]] - some notes and recipes for processing MARC files in ruby
* [[Rogue]] - principles for standards creation

== Conference/Workshop Materials ==

=== Code4libcon 2010 ===
* [[Committees sign-up page]] - '''Volunteer to help'''
* [[C4L2010planning]] - current planning
* [[C4L2010planning:_wishlist]] - planning page for issues, expectations, etc. for the 2010 conference
* See also [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 the Code4lib2010 category]

=== Code4libcon 2009 ===
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Code4lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[Logo Design Process]]
* [[OCLC Policy Change]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

Main Page

2009-07-01T14:36:43Z

Jodi: /* Code4libcon 2010 */

__NOTOC__
= Code4Lib Wiki =

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest

== Interest Groups ==

* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Getting Started with Zebra]] - indexing and searching MARC records
* [[ruby-marc]] - some notes and recipes for processing MARC files in ruby
* [[Rogue]] - principles for standards creation

== Conference/Workshop Materials ==

=== Code4libcon 2010 ===
* [[Committees sign-up page]] - '''Volunteer to help'''
* [[C4L2010planning]] - current planning
* [[C4L2010planning:_wishlist]] - planning page for issues, expectations, etc. for the 2010 conference
* See also [http://wiki.code4lib.org/index.php/Category:Code4Lib2010]

=== Code4libcon 2009 ===
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Code4lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[Logo Design Process]]
* [[OCLC Policy Change]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

Committees sign-up page

2009-07-01T14:35:09Z

Jodi:

= Code4Lib 2010 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2010 conference, 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 will take place on the Code4LibCon mailing list. Please feel free to improve the summary statements for each of the committees.

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it is comprised of 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.

* Kevin Clarke

== Keynote Speakers Committee ==

This committee plans who to invite for the keynote speakers. They gather possibilities and work with the speakers to arrange their travel and arrangements.

* Kevin Clarke

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc.

* Kevin Clarke

== 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.

== T-Shirt Committee ==

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

== Social Activities Committee ==

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

* Kevin Clarke

== Voting Activities Committee ==

This committee organizes the voting process and works with the other committees that involve voting to ensure a relatively smooth process.

* Ross Singer

[[Category: Code4Lib2010]]

C4L2010planning

2009-06-30T21:15:22Z

Jodi: /* Tasks */

== Tasks ==
* sponsorships
* keynote speakers
* program committee (20-minute talks)
* scholarship committee
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)
* T-shirt committee
* social activities
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning

== Draft Timeline '''DO NOT TRUST THESE DATES'''==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June: Choose Conference planners

May to June: Negotiate Hotel contract

May to June: Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

July 15th – Formally solicit sponsors

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

August 20th – Follow up with sponsors

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

==When do these things happen?==

*Making T-shirts
*Planning conference menus
*Arranging videotaping
*Securing conference networking
*Getting A/V supplies
*Arranging 3 OS laptop for presenters (ask mbklein)

==Other things to be done?==

[[Category: Code4Lib2010]]

C4L2010planning

2009-06-30T21:15:08Z

Jodi: /* == */

== Tasks ==
* sponsorships
* keynote speakers
* program committee (20-minute talks)
* scholarship committee
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)
* social activities
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning

== Draft Timeline '''DO NOT TRUST THESE DATES'''==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June: Choose Conference planners

May to June: Negotiate Hotel contract

May to June: Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

July 15th – Formally solicit sponsors

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

August 20th – Follow up with sponsors

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

==When do these things happen?==

*Making T-shirts
*Planning conference menus
*Arranging videotaping
*Securing conference networking
*Getting A/V supplies
*Arranging 3 OS laptop for presenters (ask mbklein)

==Other things to be done?==

[[Category: Code4Lib2010]]

C4L2010planning

2009-06-30T21:14:19Z

Jodi: /* Draft Timeline '''DO NOT TRUST THESE DATES''' */

== Tasks ==
* sponsorships
* keynote speakers
* program committee (20-minute talks)
* scholarship committee
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)
* social activities
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning

== Draft Timeline '''DO NOT TRUST THESE DATES'''==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June: Choose Conference planners

May to June: Negotiate Hotel contract

May to June: Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

July 15th – Formally solicit sponsors

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

August 20th – Follow up with sponsors

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

[[Category: Code4Lib2010]]

Main Page

2009-06-30T21:12:58Z

Jodi: /* Code4libcon 2010 */

__NOTOC__
= Code4Lib Wiki =

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest

== Interest Groups ==

* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Getting Started with Zebra]] - indexing and searching MARC records
* [[ruby-marc]] - some notes and recipes for processing MARC files in ruby
* [[Rogue]] - principles for standards creation

== Conference/Workshop Materials ==

=== Code4libcon 2010 ===
* See also [[Category:Code4Lib2010]]
* [[C4L2010planning]] - current planning
* [[C4L2010planning:_wishlist]] - planning page for issues, expectations, etc. for the 2010 conference

=== Code4libcon 2009 ===
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Code4lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[Logo Design Process]]
* [[OCLC Policy Change]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

Main Page

2009-06-30T21:12:11Z

Jodi: /* Code4libcon 2010 */

__NOTOC__
= Code4Lib Wiki =

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest

== Interest Groups ==

* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Getting Started with Zebra]] - indexing and searching MARC records
* [[ruby-marc]] - some notes and recipes for processing MARC files in ruby
* [[Rogue]] - principles for standards creation

== Conference/Workshop Materials ==

=== Code4libcon 2010 ===
* See also [Category: Code4Lib2010]
* [[C4L2010planning]] - current planning
* [[C4L2010planning:_wishlist]] - planning page for issues, expectations, etc. for the 2010 conference

=== Code4libcon 2009 ===
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Code4lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[Logo Design Process]]
* [[OCLC Policy Change]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

Main Page

2009-06-30T21:11:39Z

Jodi: /* Code4libcon 2010 */

__NOTOC__
= Code4Lib Wiki =

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest

== Interest Groups ==

* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Getting Started with Zebra]] - indexing and searching MARC records
* [[ruby-marc]] - some notes and recipes for processing MARC files in ruby
* [[Rogue]] - principles for standards creation

== Conference/Workshop Materials ==

=== Code4libcon 2010 ===
* See also [[Category: Code4Lib2010]]
* [[C4L2010planning]] - current planning
* [[C4L2010planning:wishlist]] - planning page for issues, expectations, etc. for the 2010 conference

=== Code4libcon 2009 ===
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Code4lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[Logo Design Process]]
* [[OCLC Policy Change]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

Main Page

2009-06-30T21:11:12Z

Jodi: /* Code4libcon 2010 */

__NOTOC__
= Code4Lib Wiki =

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest

== Interest Groups ==

* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Getting Started with Zebra]] - indexing and searching MARC records
* [[ruby-marc]] - some notes and recipes for processing MARC files in ruby
* [[Rogue]] - principles for standards creation

== Conference/Workshop Materials ==

=== Code4libcon 2010 ===
* [[Category: Code4Lib2010]]
* [[C4L2010planning]] - current planning
* [[C4L2010planning:wishlist]] - planning page for issues, expectations, etc. for the 2010 conference

=== Code4libcon 2009 ===
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Code4lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[Logo Design Process]]
* [[OCLC Policy Change]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

C4L2010planning: wishlist

2009-06-30T21:10:06Z

Jodi:

Planning for Code4Lib 2010 in Asheville, NC

=== Critical things that must work ===

* Internet access (i.e. wifi) with good bandwidth
* Internet access (i.e. wifi) with good bandwidth
* Internet access (i.e. wifi) with good bandwidth
* Food must accommodate special dietary needs

Everything else, including quality of hotel rooms, is secondary.

=== Internet ===

* Host local mirror of #code4lib IRC - http://www.tummy.com/Community/Articles/pycon2007-network/
* Rent G3 line for dedicated access for speakers (?)
* Have a contingency aircard so at least speakers can go online (?)
* Hook up to UNCA's Internet connection from the hotel (?)
* bridge server (between outside and local wireless)?
* forwarding server?
* VPN needs to work
* higher ports need to work
* some wired access in room?

=== Technology (non-internet) ===
* Multi-platform computer for presenters--mbklein has Mac/Windows, Ubuntu, Ctrl-key to swich beteween them
* One person suggests a google docs acct to pull presentations together (still need them offline and downloadable)
* Encourage those doing demos to do screencast backups
* Post all info in several places. Emailed info needs to be posted to website

=== Social Activities ===

* Signup sheet for nightly dinner activities
** pick out, say, 5 restaurants, encourage new attendees to connect
** make reservations!
* code4lib revue?
* Big enough hospitality suite/spare room for evening/break activities
* Provide paper maps for participants, info on places to go
* Game night (esp. board games and games like Werewolf)
* Bess' brother-in-law works at a microbrewery. Possible tour?

=== Food & Drink ===
* solicit info about dietary needs
** vegan
** vegetarian
** other needs specified on registration forms

* Requests
** sweet tea
** more beer (code4lib brew for the hospitality suite?)
** more happy hours (possibly a HH before LT?)
** hot breakfast
** candy
** hot soft pretzels & mustard

=== Sponsorship ===

* Potential sponsor and contact list
* Conference scholarships
** Consider scholarship for LIS graduate students, CS undergrads
* Andrew Nagy says: vendors want value, something tangible; can hit them up for more $

=== Choosing speakers ===
* Ask people to write why they nominated keynote speakers
* Do we need more gender diversity of keynote & 20 minute talks? (Is this important to us?)
* Do we want to limit the number of speakers from any one organization?
* Do we want topic-based categories when voting?
** e.g. 5 high-geekiness talks
** e.g. 5 theory talks
** e.g. 5 UI/usability/design-centered talks
* Voting needs 2 criteria: geekiness and vote preference. (In 2008 the sum of these was the total IIRC)
* Reserve 1-2 spots in 20-minute talks for cutting edge speakers
* How do we ensure we get fresh topics?
* Do we combine pre-voting to avoid duplication?

=== Attendees ===
* Who gets to come and how do we decide?
** Some suggestions included: require involvement if not previous attendance
** Some suggestions included: open to previous attendees a day before the main conference
** Some suggestions included: keep it as is
* How do we encourage international participation when we're not in the same town as an international airport?
* Can it be bigger? Do we want it to be? Or do we value the smaller crowd and the more personal, professional connections it affords?
* Who is the conference for?
** library systems
** software engineers
** programmers
** librarians
** designers
** ???
* "This is the only conference for coders"; "Saw no code, so I'm here to give a LT"
* Do-it-yourself crowd

=== Choosing 2011 venue ===
* Announce the process early in the conference so that people can get set up with logins
* Reminder during the last day of voting
* Evaluate internet from 2010: do we need to be at a university for internet conference support?

=== Integration with IRC, twitter stream, and other backstreams ===
* Is IRC the 'backchannel'? OR is the conference the once-yearly 'frontchannel'?
* Consider suggestions from http://pistachioconsulting.com/twitter-presentations/ regarding integration with backchannel.
** e.g. offer speakers help monitoring the channel ('an ombudsman for the audience')
* Advice from dev8 via BenO:
** @davetaz setup projection/feed of the twittered #dev8d tags + @andymcg set up a netvibe channel to follow the tags elsewhere @jschneider Twitter feed screen in bkgd of these photos: http://is.gd/jOwW http://is.gd/jOxd & see @jvvw review of event: http://is.gd/jOxy
* Make it easier for people to find IRC
** "code4lib station" with signup info and help?
* Not everybody multistreams. Would multiple rooms help (reduce volume)? Or...?
* Publish backchannel, e.g. http://reallywow.com/c4l09/logslice/20090225/14:00-14:20

=== Openness & transparency, getting to know people ===
* a code4lib program/conference committee providing support and accumulated wisdom to the organizing committee
* Wordle nametags (popular at dev8. what happens if people don't have blogs/twitterstreams/friendfeed/etc?)

=== Video ===
* Sync the timecode in the video with the IRC logs
* 3rd camera for IRC?
* Highlights reel from previous year at end of 2010 conference?

=== Lightning Talks Do's and Don'ts ===

* Have an MC/cat herder lined up in advance
* Don't have one entity do two LTs back to back
* Ask those who've already spoken to "go last"
** e.g. only present if there's time)-- "share the air"
** Do we need a policy or clarity on expectations? (e.g. no repeats)
* Create a LT do's and dont's page in the conference webspace
** link to existing LT advice
* 2 projectors, minimum. 3 if possible (3rd to display backchannels)
* make transitions to LT during coffeebreak or other downtime

=== Advice for speakers ===
* Font up
* Speak up
* Introduce yourself

=== Breakouts ===
* Consider setting 2-3 breakouts in advance
* Have 1-2 'unbreakout' sessions
* 11 is too many, IMO
* Trouble when different people are at different levels with a software discussed
** how to know in advance?
** Fedora access controls

=== List of Interesting things in Asheville, for future reference ===
''see also [http://maps.google.com/maps/ms?ie=UTF&msa=0&msid=107701218656997471821.00046117cc493635eebc1 Google Map], [http://digital.library.appstate.edu/code4lib2010.html proposal]''
* The Chocolate Fetish
* Woolworth Gallery (collaborative arts and crafts sale space in an old Woolworth's, with intact, functional lunch bar and a Swedish furniture shop in the basement)

[[Category: Code4Lib2010]]

Category:Code4Lib2010

2009-06-30T21:09:14Z

Jodi: New page: Pages related to Code4Lib2010

Pages related to Code4Lib2010

C4L2010planning

2009-06-30T21:08:55Z

Jodi: /* == */

== Tasks ==
* sponsorships
* keynote speakers
* program committee (20-minute talks)
* scholarship committee
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)
* social activities
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning

== Draft Timeline '''DO NOT TRUST THESE DATES'''==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June –

Choose Conference planners

Negotiate Hotel contract

Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

[[Category: Code4Lib2010]]

C4L2010planning

2009-06-30T21:08:11Z

Jodi:

== Tasks ==
* sponsorships
* keynote speakers
* program committee (20-minute talks)
* scholarship committee
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)
* social activities
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning

== Draft Timeline '''DO NOT TRUST THESE DATES'''==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June –

Choose Conference planners

Negotiate Hotel contract

Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

[Category: Code4Lib2010]

C4L2010planning

2009-06-30T21:07:45Z

Jodi: /* Draft Timeline DO NOT TRUST THESE DATES */

== Tasks ==
* sponsorships
* keynote speakers
* program committee (20-minute talks)
* scholarship committee
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)
* social activities
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning

== Draft Timeline '''DO NOT TRUST THESE DATES'''==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June –

Choose Conference planners

Negotiate Hotel contract

Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

C4L2010planning

2009-06-30T21:07:31Z

Jodi: /* Tasks */

== Tasks ==
* sponsorships
* keynote speakers
* program committee (20-minute talks)
* scholarship committee
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)
* social activities
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning

== Draft Timeline DO NOT TRUST THESE DATES==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June –

Choose Conference planners

Negotiate Hotel contract

Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

C4L2010planning

2009-06-30T21:07:10Z

Jodi: /* Tasks */

== Tasks ==
* sponsorships
* keynote speakers
* program committee (20-minute talks)
* social activities
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)
* scholarship committee

== Draft Timeline DO NOT TRUST THESE DATES==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June –

Choose Conference planners

Negotiate Hotel contract

Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

C4L2010planning

2009-06-30T21:06:12Z

Jodi: /* Tasks */

== Tasks ==
* sponsorships
* keynote speakers
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* program committee
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)
* scholarship committee

== Draft Timeline DO NOT TRUST THESE DATES==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June –

Choose Conference planners

Negotiate Hotel contract

Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

C4L2010planning

2009-06-30T21:04:29Z

Jodi: /* Draft Timeline DO NOT TRUST THESE DATES */

== Tasks ==
* sponsorships
* keynote speakers
* wifi
* program committee
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)

== Draft Timeline DO NOT TRUST THESE DATES==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June –

Choose Conference planners

Negotiate Hotel contract

Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

C4L2010planning

2009-06-30T21:04:04Z

Jodi: /* Draft Timeline DO NOT TRUST THESE DATES */

== Tasks ==
* sponsorships
* keynote speakers
* wifi
* program committee
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)

== Draft Timeline DO NOT TRUST THESE DATES==
Monday February 22 (preconference) – Thursday February 25
'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June –
Choose Conference planners
Negotiate Hotel contract
Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

C4L2010planning

2009-06-30T21:03:21Z

Jodi: /* Tasks */

== Tasks ==
* sponsorships
* keynote speakers
* wifi
* program committee
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future)

== Draft Timeline DO NOT TRUST THESE DATES==
***Code4Lib 2010 Timeline***
Monday February 22 (preconference) – Thursday February 25
**Calls and posts are to code4lib listserv unless otherwise specified**

May to June –
Choose Conference planners
Negotiate Hotel contract
Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

C4L2010planning

2009-06-30T21:02:25Z

Jodi: /* Tasks */

== Tasks ==
* sponsorships
* keynote speakers
* wifi
* program committee
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground

== Draft Timeline DO NOT TRUST THESE DATES==
***Code4Lib 2010 Timeline***
Monday February 22 (preconference) – Thursday February 25
**Calls and posts are to code4lib listserv unless otherwise specified**

May to June –
Choose Conference planners
Negotiate Hotel contract
Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

C4L2010planning

2009-06-30T21:00:50Z

Jodi: /* Draft Timeline DO NOT TRUST THESE DATES */

== Tasks ==
* sponsorships
* keynote speakers
* wifi
* program committee

== Draft Timeline DO NOT TRUST THESE DATES==
***Code4Lib 2010 Timeline***
Monday February 22 (preconference) – Thursday February 25
**Calls and posts are to code4lib listserv unless otherwise specified**

May to June –
Choose Conference planners
Negotiate Hotel contract
Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 1st – Call for 20-minute talk proposals

Oct 15 —Posted reminder with presenter-guarantee policy

Oct 31 – 20-minute talk proposals due

Nov 4-Nov 12 – voting on 20-minute talk proposals

Nov 4 – Call for preconference proposals

Nov 5 – Begin testing registration

Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Nov 16th – List of top 22ish talk titles posted

Nov 16th – Scholarship announcement ***post beyond code4lib list???***

Nov 16th – Preconference reminder

Nov 16th – Registration opens Dec 2nd

Nov 23 – Preconference proposals due

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

C4L2010planning

2009-06-30T21:00:15Z

Jodi: adding timeline

== Tasks ==
* sponsorships
* keynote speakers
* wifi
* program committee

== Draft Timeline DO NOT TRUST THESE DATES==
***Code4Lib 2010 Timeline***
Monday February 22 (preconference) – Thursday February 25
**Calls and posts are to code4lib listserv unless otherwise specified**

May to June –
Choose Conference planners
Negotiate Hotel contract
Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs)
August 17th – Tally of keynote speaker suggestions, final call to code4lib list
Sept 9th-Septh18th – keynote speaker vote
Sept 22nd – Keynote speaker invitations begin
Oct 1st – Call for 20-minute talk proposals
Oct 15 —Posted reminder with presenter-guarantee policy
Oct 31 – 20-minute talk proposals due
Nov 4-Nov 12 – voting on 20-minute talk proposals
Nov 4 – Call for preconference proposals
Nov 5 – Begin testing registration
Nov 13 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)
Nov 16th – List of top 22ish talk titles posted
Nov 16th – Scholarship announcement ***post beyond code4lib list???***
Nov 16th – Preconference reminder
Nov 16th – Registration opens Dec 2nd
Nov 23 – Preconference proposals due
Dec 1 – Reminder, Registration opens Dec 2
Dec 2 – Registration opens
Dec 2 – Post when registration opens
Dec 2 – Share waitlist & preconf count info???
Dec 7—Registration deadline for presenter-reserved spots
Jan 5 – Scholarship deadline
Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals
Jan 5 – Call for t-shirt design submissions
Jan 12 – Scholarship recipients notified
Jan 12 – call for code4lib2011 hosting proposals
Jan 15 – T-shirt design deadline
Jan 20-28 T-shirt vote
Feb 8 – discussion of volunteer needs
Feb 12 – deadline for code4lib2011 hosting proposals
Feb 15 – Call for Breakout Session ideas
Feb 15 – Call for conference volunteers
Feb 17 – Reminder to participants with travel info, conference social info
Feb 17-24 – vote for 2011 host
March 1-31–Videos converted, compressed, uploaded, and linked

====
When do these things happen?

Making T-shirts
Planning conference menus
Arranging videotaping
Securing conference networking
Getting A/V supplies
Arranging 3 OS laptop for presenters (ask mbklein)

Other things?

C4L2010planning

2009-06-30T20:59:02Z

Jodi: /* Tasks */

== Tasks ==
* sponsorships
* keynote speakers
* wifi
* program committee

C4L2010planning

2009-06-30T20:58:26Z

Jodi: starting page

== Tasks ==
* sponsorships
* jaf: keynote speakers
* wifi (optional)

C4l2010planning

2009-06-30T20:57:46Z

Jodi: Redirecting to C4L2010planning

#REDIRECT [[C4L2010planning]]

C4L2010planning: wishlist

2009-06-30T20:57:23Z

Jodi: C4l2010planning moved to C4L2010planning: wishlist: Freeing up C4L2010planning for main uses, changing capitalization

C4l2010planning

2009-06-30T20:57:23Z

Jodi: C4l2010planning moved to C4L2010planning: wishlist: Freeing up C4L2010planning for main uses, changing capitalization

#REDIRECT [[C4L2010planning: wishlist]]

MDC

2009-03-11T22:49:47Z

Jodi: added info from listserv (except email address)

= Maryland, Washington D.C etc. =

First meeting scheduled for Friday April 3, at the
National Agricultural Library located at 10301 Baltimore Ave,
Beltsville MD from 9:30 a.m. - 11:30 a.m.

Directions available at: http://tinyurl.com/dae6w7
Refreshments will be provided starting at 9:00 a.m.

Please RSVP to Vernon Chapman.

Code4Lib Journal WordPress Input Guidelines

2009-03-09T21:01:31Z

Jodi: /* Images and Attached Content */ adding centering instructions

Please follow the guidelines below when creating or editing Code4Lib Journal articles in WordPress. Enter all articles as "Posts".

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

==Title==
Title, including the subtitle, goes in the "Title" field.

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html. Fortunately, WP has a built-in feature to help with this. Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon. This transforms Word's html into really nice pretty html.

===Images and Attached Content===
In-line images should be no wider than 500px.
If you want to center images use:
<nowiki><p style="text-align: center">This is a centered, captioned image.</p>
</nowiki>

Two options for images and other attached content/media:
# use WordPress uploaded content managing feature, or
# upload the content to our host manually.

jrochkind found the WordPress content managing feature to be more of a pain than it was worth, so is uploading content manually. To do that, sftp to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/7d66327ef69c507a/6dceb7d578676334?lnk=gst&q=account+upload#6dceb7d578676334 post] on c4lj-articles).

Change directory to:
/public/vhost/c/c4lj/html/media

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc.

===Code===

Put all code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). To make this work, you still wrap your code in <code><pre></code> tags. Inside of the <code><pre></code> tags, but around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work).

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
<pre>[sourcecode language='css']body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}[/sourcecode]</pre>

==Abstract==

While you are editing the article, there is a box labeled "Optional Excerpt" a little ways below the "Post" field. Put the abstract here. Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

==Bibliographies/Endnotes==
We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.
* Recommended COinS generator: http://generator.ocoins.info/
* Another option is to use the WP COinS plugin. Open the Code tab, put the cursor before the citation, and click COinS. Enter the appropriate information. This works so-so for journals, and not at all for books.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets that are not part of the link. HTML coding example: [<a href="#note1">1</a>]

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Every article in issue 1 should be put in a category "Issue 1". Etc. This should make it easier to generate issue specific RSS feeds and do other stuff at a later date.

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'.
# Click on Manage -> Issues after logging into WordPress
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Don't see all the articles you think you should see? Either they are still in Draft status or they're not in the Issue 5 category.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.

Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.

[[Category:Code4Lib Journal]]

C4L2010planning: wishlist

2009-03-09T17:43:48Z

Jodi:

Planning for Code4Lib 2010 in Asheville, NC

=== Critical things that must work ===

* Internet access (i.e. wifi) with good bandwidth
* Internet access (i.e. wifi) with good bandwidth
* Internet access (i.e. wifi) with good bandwidth
* Food must accommodate special dietary needs

Everything else, including quality of hotel rooms, is secondary.

=== Internet ===

* Host local mirror of #code4lib IRC - http://www.tummy.com/Community/Articles/pycon2007-network/
* Rent G3 line for dedicated access for speakers (?)
* Have a contingency aircard so at least speakers can go online (?)
* Hook up to UNCA's Internet connection from the hotel (?)
* bridge server (between outside and local wireless)?
* forwarding server?
* VPN needs to work
* higher ports need to work
* some wired access in room?

=== Technology (non-internet) ===
* Multi-platform computer for presenters--mbklein has Mac/Windows, Ubuntu, Ctrl-key to swich beteween them
* One person suggests a google docs acct to pull presentations together (still need them offline and downloadable)
* Encourage those doing demos to do screencast backups
* Post all info in several places. Emailed info needs to be posted to website

=== Social Activities ===

* Signup sheet for nightly dinner activities
** pick out, say, 5 restaurants, encourage new attendees to connect
** make reservations!
* code4lib revue?
* Big enough hospitality suite/spare room for evening/break activities
* Provide paper maps for participants, info on places to go
* Game night (esp. board games and games like Werewolf)
* Bess' brother-in-law works at a microbrewery. Possible tour?

=== Food & Drink ===
* solicit info about dietary needs
** vegan
** vegetarian
** other needs specified on registration forms

* Requests
** sweet tea
** more beer (code4lib brew for the hospitality suite?)
** more happy hours (possibly a HH before LT?)
** hot breakfast
** candy
** hot soft pretzels & mustard

=== Sponsorship ===

* Potential sponsor and contact list
* Conference scholarships
** Consider scholarship for LIS graduate students, CS undergrads
* Andrew Nagy says: vendors want value, something tangible; can hit them up for more $

=== Choosing speakers ===
* Ask people to write why they nominated keynote speakers
* Can we get more gender diversity of keynote & 20 minute talks? (Is this important to us?)
* Do we want to limit the number of speakers from any one organization?
* Do we want topic-based categories when voting?
** e.g. 5 high-geekiness talks
** e.g. 5 theory talks
* Voting needs 2 criteria: geekiness and vote preference. (In 2008 the sum of these was the total IIRC)
* Reserve 1-2 spots in 20-minute talks for cutting edge speakers
* How do we ensure we get fresh topics?
* Do we combine pre-voting to avoid duplication?

=== Attendees ===
* Who gets to come and how do we decide?
** Some suggestions included: require involvement if not previous attendance
** Some suggestions included: open to previous attendees a day before the main conference
** Some suggestions included: keep it as is
* How do we encourage international participation when we're not in the same town as an international airport?
* Can it be bigger? Do we want it to be?
* Who is the conference for?
** library systems
** software engineers
** programmers
** librarians
** ???
* "This is the only conference for coders"; "Saw no code, so I'm here to give a LT"
* Do-it-yourself crowd

=== Choosing 2011 venue ===
* Announce the process early in the conference so that people can get set up with logins
* Reminder during the last day of voting
* Evaluate internet from 2010: do we need to be at a university for internet conference support?

=== Integration with IRC, twitter stream, and other backstreams ===
* Is IRC the 'backchannel'? OR is the conference the once-yearly 'frontchannel'?
* Consider suggestions from http://pistachioconsulting.com/twitter-presentations/ regarding integration with backchannel.
** e.g. offer speakers help monitoring the channel ('an ombudsman for the audience')
* Advice from dev8 via BenO:
** @davetaz setup projection/feed of the twittered #dev8d tags + @andymcg set up a netvibe channel to follow the tags elsewhere @jschneider Twitter feed screen in bkgd of these photos: http://is.gd/jOwW http://is.gd/jOxd & see @jvvw review of event: http://is.gd/jOxy
* Make it easier for people to find IRC
** "code4lib station" with signup info and help?
* Not everybody multistreams. Would multiple rooms help (reduce volume)? Or...?
* Publish backchannel, e.g. http://reallywow.com/c4l09/logslice/20090225/14:00-14:20

=== Openness & transparency, getting to know people ===
* a code4lib program/conference committee providing support and accumulated wisdom to the organizing committee
* Wordle nametags (popular at dev8. what happens if people don't have blogs/twitterstreams/friendfeed/etc?)

=== Video ===
* Sync the timecode in the video with the IRC logs
* 3rd camera for IRC?

=== Lightning Talks Do's and Don'ts ===

* Have an MC/cat herder lined up in advance
* Don't have one entity do two LTs back to back
* Ask those who've already spoken to "go last"
** e.g. only present if there's time)-- "share the air"
** Do we need a policy or clarity on expectations? (e.g. no repeats)
* Create a LT do's and dont's page in the conference webspace
** link to existing LT advice
* 2 projectors, minimum. 3 if possible (3rd to display backchannels)
* make transitions to LT during coffeebreak or other downtime

=== Advice for speakers ===
* Font up

=== Breakouts ===
* Consider setting 2-3 breakouts in advance
* Have 1-2 'unbreakout' sessions
* 11 is too many, IMO
* Trouble when different people are at different levels with a software discussed
** how to know in advance?
** Fedora access controls

=== List of Interesting things in Asheville, for future reference ===
''see also [http://maps.google.com/maps/ms?ie=UTF&msa=0&msid=107701218656997471821.00046117cc493635eebc1 Google Map], [http://digital.library.appstate.edu/code4lib2010.html proposal]''
* The Chocolate Fetish
* Woolworth Gallery (collaborative arts and crafts sale space in an old Woolworth's, with intact, functional lunch bar and a Swedish furniture shop in the basement)

C4L2010planning: wishlist

2009-03-09T17:43:06Z

Jodi: /* Food & Drink Requests */

Planning for Code4Lib 2010 in Asheville, NC

=== Critical things that must work ===

* Internet access (i.e. wifi) with good bandwidth
* Internet access (i.e. wifi) with good bandwidth
* Internet access (i.e. wifi) with good bandwidth
* Food must accommodate special dietary needs

Everything else, including quality of hotel rooms, is secondary.

=== Internet ===

* Host local mirror of #code4lib IRC - http://www.tummy.com/Community/Articles/pycon2007-network/
* Rent G3 line for dedicated access for speakers (?)
* Have a contingency aircard so at least speakers can go online (?)
* Hook up to UNCA's Internet connection from the hotel (?)
* bridge server (between outside and local wireless)?
* forwarding server?
* VPN needs to work
* higher ports need to work
* some wired access in room?

=== Technology (non-internet) ===
* Multi-platform computer for presenters--mbklein has Mac/Windows, Ubuntu, Ctrl-key to swich beteween them
* One person suggests a google docs acct to pull presentations together (still need them offline and downloadable)
* Encourage those doing demos to do screencast backups
* Post all info in several places. Emailed info needs to be posted to website

=== Social Activities ===

* Signup sheet for nightly dinner activities
** pick out, say, 5 restaurants, encourage new attendees to connect
** make reservations!
* code4lib revue?
* Big enough hospitality suite/spare room for evening/break activities
* Provide paper maps for participants, info on places to go
* Game night (esp. board games and games like Werewolf)
* Bess' brother-in-law works at a microbrewery. Possible tour?

=== Food & Drink ===
* solicit info about dietary needs
** vegan
** vegetarian
** other needs specified on registration forms

* Requests
** sweet tea
** more beer (code4lib brew for the hospitality suite?)
** more happy hours (possibly a HH before LT?)
** hot breakfast
** candy
** hot soft pretzels & mustard

=== Sponsorship ===

* Potential sponsor and contact list
* Conference scholarships
** Consider scholarship for LIS graduate students, CS undergrads
* Andrew Nagy says: vendors want value, something tangible; can hit them up for more $

=== Choosing speakers ===
* Ask people to write why they nominated keynote speakers
* Can we get more gender diversity of keynote & 20 minute talks? (Is this important to us?)
* Do we want to limit the number of speakers from any one organization?
* Do we want topic-based categories when voting?
** e.g. 5 high-geekiness talks
** e.g. 5 theory talks
* Voting needs 2 criteria: geekiness and vote preference. (In 2008 the sum of these was the total IIRC)
* Reserve 1-2 spots in 20-minute talks for cutting edge speakers
* How do we ensure we get fresh topics?
* Do we combine pre-voting to avoid duplication?

=== Attendees ===
* Who gets to come and how do we decide?
** Some suggestions included: require involvement if not previous attendance
** Some suggestions included: open to previous attendees a day before the main conference
** Some suggestions included: keep it as is
* How do we encourage international participation when we're not in the same town as an international airport?
* Can it be bigger? Do we want it to be?
* Who is the conference for?
** library systems
** software engineers
** programmers
** librarians
** ???
* "This is the only conference for coders"; "Saw no code, so I'm here to give a LT"
* Do-it-yourself crowd

=== Choosing 2011 venue ===
* Announce the process early in the conference so that people can get set up with logins
* Reminder during the last day of voting
* Evaluate internet from 2010: do we need to be at a university for internet conference support?

=== Integration with IRC, twitter stream, and other backstreams ===
* Is IRC the 'backchannel'? OR is the conference the once-yearly 'frontchannel'?
* Consider suggestions from http://pistachioconsulting.com/twitter-presentations/ regarding integration with backchannel.
** e.g. offer speakers help monitoring the channel ('an ombudsman for the audience')
* Advice from dev8 via BenO:
** @davetaz setup projection/feed of the twittered #dev8d tags + @andymcg set up a netvibe channel to follow the tags elsewhere @jschneider Twitter feed screen in bkgd of these photos: http://is.gd/jOwW http://is.gd/jOxd & see @jvvw review of event: http://is.gd/jOxy
* Make it easier for people to find IRC
** "code4lib station" with signup info and help?
* Not everybody multistreams. Would multiple rooms help (reduce volume)? Or...?
* Publish backchannel, e.g. http://reallywow.com/c4l09/logslice/20090225/14:00-14:20

=== Openness & transparency, getting to know people ===
* a code4lib program/conference committee providing support and accumulated wisdom to the organizing committee
* Wordle nametags (popular at dev8. what happens if people don't have blogs/twitterstreams/friendfeed/etc?)

=== Video ===
* Sync the timecode in the video with the IRC logs
* 3rd camera for IRC?

=== Lightning Talks Do's and Don'ts ===

* Have an MC/cat herder lined up in advance
* Don't have one entity do two LTs back to back
* Ask those who've already spoken to "go last"
** e.g. only present if there's time)-- "share the air"
** Do we need a policy or clarity on expectations? (e.g. no repeats)
* Create a LT do's and dont's page in the conference webspace
** link to existing LT advice
* 2 projectors, minimum. 3 if possible (3rd to display backchannels)
* make transitions to LT during coffeebreak or other downtime

=== Breakouts ===
* Consider setting 2-3 breakouts in advance
* Have 1-2 'unbreakout' sessions
* 11 is too many, IMO
* Trouble when different people are at different levels with a software discussed
** how to know in advance?
** Fedora access controls

=== List of Interesting things in Asheville, for future reference ===
''see also [http://maps.google.com/maps/ms?ie=UTF&msa=0&msid=107701218656997471821.00046117cc493635eebc1 Google Map], [http://digital.library.appstate.edu/code4lib2010.html proposal]''
* The Chocolate Fetish
* Woolworth Gallery (collaborative arts and crafts sale space in an old Woolworth's, with intact, functional lunch bar and a Swedish furniture shop in the basement)