55
edits
Changes
m
→How the Editorial Committee Functions
== 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 i.e., 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 two 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 as the first editor. The first editor shepherds the from proposal to publication, acting as the journal's single point of contact with the author. Each article also has a second editor/reader, who serves as another pair of eyes early in the process by reading and providing feedback on drafts. Most Committee members take primary responsibility for about one article per issue and serve as second reader on another one, though the committee is large enough that there is some flexibility with editorial responsibility.
