Code4Lib - User contributions [en]

Code4Lib Editorial Committee Introduction

2010-03-12T16:48:27Z

192.231.234.1: /* Editorial Committee Discussion Lists (Required) */

[[Category: Code4Lib Journal]]

== How the Editorial Committee Functions ==

The Code4Lib Journal Editorial Committee works much as Code4Lib does: informally and collaboratively. For each issue, one member of the Editorial Committee (EC) volunteers to be Coordinating Editor (ie managing editor) of a journal issue. For the duration of their tenure, the Coordinating Editor is generally responsible for any loose ends tying, and making sure everything proceeds smoothly, coordinating all of the rest of us. This includes distributing the call for papers, communicating with potential authors, opening and closing editorial committee voting on submissions, notifying authors of rejected articles, and making sure that accepted articles have volunteer editors (and that those editors notify authors of accepted articles).

Everyone on the EC may vote on article proposals as they come in. The Coordinating Editor generally sets a deadline of 1-2 weeks for voting. Voting is straightforward and recorded in the Article Tracking spreadsheet. An article must have at least two 'yes' votes and more 'yes' votes than 'no' votes to be accepted. Once an article is accepted for publication, an EC member volunteers to take on editorial responsibility for that article and shepherds it from proposal to publication, acting as the journal's single point of contact with the author. Most Committee members take responsibility for about one article per issue, though the committee is large enough that there is some flexibility with editorial responsibility.

Editing an article includes making sure the article draft is submitted on time, distributing drafts to the full committee for comment, making editorial suggestions or recommendations to the author(s), tracking and enforcing submission deadlines, requesting full Editorial Committee approval of the final draft, and inputting the finished article into our [http://wiki.code4lib.org/index.php/Code4Lib_Editorial_Committee_Introduction#Wordpress_.28Required.29 WordPress site]. Once the assigned editor recommends the final draft for publication, the EC again votes on whether to include that article in the current issue. Again, this requires at least two 'yes' votes and more 'yes' votes than 'no' votes for publication. We do not expect every EC member to vote on every article, but we do ask that you read an article thoroughly before voting on it for inclusion in the issue.

More detailed information describing the entire process from sending out the call for proposals to publishing a new issue is available on the Journal site:
* [http://journal.code4lib.org/process-and-structure General outline of process and structure]
* [http://journal.code4lib.org/process-and-structure/editors More detailed information for editors] (requires Wordpress login)

Templates for notifying authors about the status of their proposals are available as a [http://groups.google.com/group/c4lj-articles/web/templates-for-email-responses page] in the c4lj-articles Google group.

Above all, the Editorial Committee is informal and egalitarian. Jump in with your opinion and ideas!

== Editorial Committee Discussion Lists (Required) ==

Much of the Editorial Committee's business is conducted via email on the [http://groups.google.com/group/c4lj-articles C4LJ-Articles] Google Group. This list is where we debate article submissions, volunteer to be editor or managing editor, discuss acceptance of articles, and take care of any other tasks in front of us that might be of a sensitive nature. Anyone may post to this list, but only editors can read the list activity. To join this list, please visit the URL and request membership, using your preferred email associated with a Google account. If that doesn't work for some reason, you can join the c4lj-discuss group (see below) and send an email requesting membership to c4lj-articles.

All other Journal business is discussed on the [http://groups.google.com/group/c4lj-discuss C4LJ-Discuss] Google Group. If the conversation is unrelated to specific authors, proposals, or articles, it should probably happen on this list. We prefer to discuss other decisions about how the Journal is handled in public where anyone can participate. This list is open for anyone to join and is publicly viewable. Only list members can post. Use the URL above to join this discussion list. Due to spam, authors are moderated the first time they post.

== Article Tracking Spreadsheet (Required) ==

Articles, from proposal submission through to publication, are tracked using the C4LJ Article Tracking spreadsheet in Google Docs. This Google document is private; only Editorial Committee members may view or edit it. Proposal votes and tentative issue assignments for accepted articles are tracked in this spreadsheet. The [http://groups.google.com/group/c4lj-articles/browse_thread/thread/ec4c9701401ce94c/70079ef809a6a9da invitation] to become a collaborator is available on the c4lj-articles list. Please use this invitation to add yourself as a collaborator for this document (you must already be a member of c4lj-articles).

== Wordpress (Required) ==

Code4Lib Journal articles are published in a Wordpress installation hosted by ibiblio (http://journal.code4lib.org). The assigned editor for an article is responsible for entering the content into Wordpress, formatting it, and adding images and code snippets. Guidelines on entering articles are available on the [[Code4Lib_Journal_WordPress_Input_Guidelines|wiki]]. We also maintain basic information about the Journal using pages in Wordpress (Mission, Editorial Committee, Process and Structure, Call for Submissions, Article Guidelines).

New editors need to request a Wordpress account:

# Go to http://journal.code4lib.org/wp/wp-login.php?action=register
# Register
# Send your username to c4lj-articles@googlegroups.com so the technical editor can grant you Wordpress privileges.

== Google Analytics (Optional) ==

Google Analytics is used to gather statistics for the Code4Lib Journal. If you are interested in being able to view these statistics, just send your preferred Google Account information to the c4lj-articles@googlegroups.com discussion list, and the technical editor will enable your access.

== Other Shared Documents (Optional) ==

The C4LJ Article/Author Ideas spreadsheet is used to track ideas for have for specific articles we'd like to recruit or specific authors we want to recruit for the Journal. The [http://groups.google.com/group/c4lj-articles/browse_thread/thread/425165428b88e2ee invitation] to become a collaborative editor is available on the c4lj-articles list.

C4L2010 social activities

2010-02-08T21:07:59Z

192.231.234.1: /* Newcomer Dinner Signup */

==Code4Lib 2010 social activities ==

==Ideas==
[http://www.citizen-times.com/apps/pbcs.dll/article?AID=2009912010314 New breweries opening]

[http://digital.library.appstate.edu/code4lib2010.html Original Proposal (suggests some nearby events)]

[http://ashevilletwitterhashtags.blogspot.com/2009/09/asheville-beer-avlbeer.html Asheville Beer Hashtag]

==Planned events==

Plan one if you like! Either on your own or you can [[Committees_sign-up_page|join the social activities committee]].

== Asheville Brews Cruise ==

"Experience a taste of Asheville’s thriving local beer scene with an exclusive tour of three of our award-winning microbreweries." - http://www.brewscruise.com/asheville/

This activity will be Tuesday night starting at 6pm and leaving from the hotel. First stop will be the Asheville Pizza & Brewing Co. to sample 16-20 different beers and eat some pizza (food billed separately). Then two more stops at the French Broad Brewery and the Highland Brewing Company for more beer sampling and learning about their brewery process.

The cost will be $40/person (not including pizza). The minimum number of folks we need is 16. There is no maximum.

==== Beer Cruise Signup ====

Please indicate interest in the Beer Cruise by adding your name to the list below. We'll figure out a way to coordinate and communicate the details somewhere down the line.

# Jay Luker (organizer)
# Mike Giarlo (inebriator)
# Rob Casson (drunk)
# Declan Fleming (beer receptacle)
# Jim Safley (recovering teetotaler)
# Ian Walls (epicurean of ale)
# Bill Erickson (burp)
# Christopher Spalding (thirsty)
# Jon Gorman (imbiber of that which is good)
# Lori Stethers (token female)
# Carol Ou (beer enthusiast)
# Cristóbal Palmer (Reinheitsgebot skeptic)
# Tod Olson (enabler)
# Mark Matienzo (alefounder)
# Sibyl Schaefer (barfly)
# Laney McGlohon (brewmaster's assistant)
# Tania Fersenheim (Gold Medalist - Ithaca Beerlympics - Summer 1993)
# Melissa Manolis (Beer lacky and Librarian Groupie)
# Greg McClellan (brews hound)
# Cary Gordon (hip hoppist)
# Mark Gallagher (Thing 1)
# Matt Bachtell (Thing 2)
# Sarah Kahn (has no title)
# Thom Cox (afraid of rectangles)
# Eric James (pour)
# Ray Schwartz (mighty thirsty)
# Jason Stirnaman (all about the stout)
# Mike Flakus (ipa all the way)
# Ben Florin (sounds neat--what's "beer"?)
# Ryan Wick (it comes in pints?)
# Sam Kome (have churchkey, will travel)
# Joe Atzberger
# Brendan Gallagher
# Chris Beer
# Tom Keays (growler)
# Ross Singer (empty vessel waiting to be filled)
# Eric Hellman (49 IBU)
# Paul Joseph (i bike leer)
# Cody Hennesy (don't mind if i do)

== 12 Bones BBQ Dinner Excursion ==
(was a lunch excursion)

[http://www.12bones.com/ 12 Bones BBQ] is widely considered the best BBQ in Asheville [[http://www.yelp.com/biz/12-bones-smokehouse-asheville *]]. However it is only open from 11-4, M-F. We would like to organize a group so that we can rent out the place on Wednesday night. If we get at least 50 people, it will be doable.

This excursion is tentatively scheduled for dinnertime on Wednesday, February 24th.

==== BBQ Excursion Signup ====

For the time being please indicate interest in the BBQ excursion by adding your name to the list below. We'll figure out a way to coordinate and communicate the details somewhere down the line.

# Rosalyn Metz (the new organizer)
# Jay Luker (organizer)
# Mike Giarlo (consumer)
# Rob Casson (glutton)
# Declan Fleming (condor)
# Erik Hatcher (carnivore)
# Christopher Spalding (digs swine)
# Mike Durbin (Porkaholic)
# Jeremy Frumkin (alloftheabove)
# Jon Gorman (Aficionado of smoke, flame, and good sauces)
# Michael Klein (EAT PIG)
# Mark Matienzo (saucy fellow)
# Cary Gordon (do they have vegan pig?)
# Sibyl Schaefer (finger licker)
# Greg McClellan (Mmmm... Pig)
# Ranti Junus (beef and chicken cheerleader)
# Tania Fersenheim (can't think of any non-vulgar tag lines)
# Matt Bachtell (hope they have vinegar based BBQ)
# Ray Schwartz (I eat vegetarians)
# Dileshni Jayasinghe (I just like to eat)
# Joe Atzberger (con carne)
# Michael Doran (a YES for Wednesday night)
# Thom Cox (ancho pepper addict)
# Chris Strauber (meat and flame!)
# Cindy Harper (I'm sorry, Babe)
# Brendan Gallagher
# Chris Beer
# Alexander O'Neill
# Bess Sadler
# Joyce Ouchida
# Ross Singer (Some Pig)
# Tod Olson (omnivore sans dilemma)
# Paul Joseph
# Vinita Tuteja
# Robin Hitch
# Ryan Wick
# Becky Yoose (bringing the wetwipe napkins)
# Joyce Chapman
# Andrew Darby

== Newcomer Dinner ==
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating discussions about the many uses of bacon.

Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!

'''Tentative plans (more information to come)'''
* When: Monday evening
* Time: 6 PM
* Where: Meet in hotel lobby, restaurants TBA. We're expecting a big crowd, so we may split up and go to multiple restaurants.
* Mastermind (if you have any questions): [mailto:yoosebj@muohio.edu Becky Yoose]

=== Newcomer Dinner Signup ===
* Becky Yoose (Herder of newbies, librarians, and cats)
* Emily Lynema
* Rosalyn Metz
* Ranti Junus
* Declan Fleming
* Ross Singer
* Mike Giarlo (impromptu Civil War re-enactor)
* Michael Klein
* Chris Strauber (newbie Prime)
* Maccabee Levine
* Cindy Harper
* Monica Claassen-Wilson
* Sam Kome
* Brendan Gallagher
* Alexander O'Neill
* Bess Sadler
* Leland Deeds
* Cory Rockliff
* Joyce Ouchida
* Yuka Egusa
* Masao Takaku
* Schuyler Erle
* Tim Shearer
* Michael Silver
* Rod McFarland
* Jason Stirnaman
* Patrick Hochstenbach
* Eric Celeste (spy)
* Joyce Chapman
* Thom Cox
* Julia Bauder
* Sarah Kahn
* Emily King
* David Kennedy
* Paul Joseph
* Vinita Tuteja
* Janis Mathewson
* Rick Johnson
* Mark Mounts
* Banurekha Lakshminarayanan
* Tom Bennett
* Dan Lucas
* Sean Chen
* Clint Bellanger
* Shawn Averkamp
* Cory Lown
* Dileshni Jayasinghe
* Kossivi Bessou
* Kenny Ketner
* Erin White
* Jason Battles
* Joe Marquez
* John Yorio
* Jeff Silvis
* Cody Hennesy
* Robin Hitch
* Jill Ellern
* Joel Marchesoni
* Sibyl Schaefer
* Cary Gordon (likes anything that involves food)
* Andrew Darby

== Werewolf! ==
It wouldn't be a tech conference unless we got together one evening to turn into a gang of murdering beasts and hyper-suspicious victims. Facilitated by the one and only mbklein.

* When: Wednesday evening
* Time: 8 PM
* Where: TBA. Watch this space.

=== Werewolf signup ===
* Michael Klein
* Alexander O'Neill
* Bess Sadler
* Leland Deeds

== Working Out ==
Gotta make up for that BBQ excursion somehow. Let's work out! Ideas: jogging or [http://www.crossfitasheville.com CrossFitting] (Monday evening, 5:30pm or 6:30pm). Signup:

* Erik Hatcher (game for both jogging and CrossFitting, bring it!)
* Erik Mitchell (Run downtown asheville or the parkway? - great 12 mile climb up the parkway around Pisgah Mtn.), How about a Code4Lib half-marathon? (Why NOT! Let's do a Half Marathon) - Ray Schwartz
**Bike riding - yes might be sketchy given our current weather
**Hike up Looking Glass Rock [http://www.hikewnc.info/trailheads/pisgah/pisgah/guidedhikes/lookingglassrock.html]
* Emily Lynema (game for jogging, hiking, walking, jumping jacks; not crazy enough for parkway running!)
* Ray Schwartz (game for a run - why not a half marathon?!).
[[Category: Code4Lib2010]]
* Rick Johnson (Looking to fit in a 10, 12 ,and 8 mile run while in town. Was originally thinking I would go early in the morning: 6:30 or 7. May not be able to run together everytime but definitely looking for suggestions on good routes)
* Thom Cox (lifting, cardio, yoga--all good)
* Jason Stirnaman (hiking, biking - don't mind the weather, lifting, cross-fitting)

== Sitting in a room together and half the time talking to each other out loud and half the time talking in IRC ==

Because you know it's going to happen

* William Denton
* Mike Giarlo (fulfiller of destinies)

North

2010-01-13T14:04:41Z

192.231.234.1: /* Who's interested? Put your name here... */

Welcome to the wiki home of the new Ontario/Canada "chapter" of [http://code4lib.org/ code4lib]. Our aim is to create more opportunities for code4lib folks in the Ontario/Quebec/Manitoba/Northeast USA area to meet up in person.

===Mailing list?===

There's no mailing list for the chapter yet, but we can make one when we need one. Until then, we can use the main mailing list. No-one will mind.

== First Meeting ==

=== When ===

Spring... May?

=== Meeting location suggestions ===

* Kingston, Ontario
* ...

=== Format ===

1 or 1.5 days of lightning talks and discussion.

=== Suggest lighting talks and discussion topics ===

* ...

== Who's interested? Put your name here... ==

Feel free to declare your interest in a code4lib North chapter:

* Wendy Huot, Queen's University
* Michael Vandenburg, Queen's University
* [http://www.miskatonic.org/ William Denton], York University
* John Fink, McMaster University
* [http://ruebot.net/ Nick Ruest], McMaster University
* Walter Lewis, Halton Hills/OurOntario
* Edward Corrado, Binghamton University (NY, USA)
* Warren Layton, NRCan Library (Ottawa)
* Pascal Calarco, University of Notre Dame (IN, USA)
* Mita Williams, University of Windsor
* John Fereira, Cornell University
* MJ Suhonos, Toronto Public Library
* Dianne Dietrich, Cornell University
* David Fiander, University of Western Ontario
* Peter Schlumpf, [http://www.avantilibrarysystems.com/ Avanti Library Systems]
* Roy Zimmer, Western Michigan University
* Kimberly Silk, Martin Prosperity Institute, University of Toronto
* Andrew Darby, Ithaca College (Ithaca, NY)

Code4Lib Journal Email Templates

2009-03-16T16:15:22Z

192.231.234.1:

''See also [[Code4Lib_Journal_Deadlines]]''

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

Code4Lib Journal Email Templates

2009-03-16T16:13:44Z

192.231.234.1: /* Proposal Accepted */

''See also [[Code4Lib_Journal_Deadlines]]''

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

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