7
edits
Changes
no edit summary
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 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 and as the first editor. The first editor shepherds it the from proposal to publication, acting as the journal's single point of contact with the author. Each article also has a second editor, 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 issueand serve as second reader on another one, 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.
Templates for notifying authors about the status of their proposals are available as on the [http://wiki.code4lib.org/index.php/Code4Lib_Journal_Email_Templates wiki].
All of the Code4Lib Journal information on the wiki can be seen in the [http://wiki.code4lib.org/index.php/Category:Code4Lib_Journal Code4Lib category].
Above all, the Editorial Committee is informal and egalitarian. Jump in with your opinion and ideas!
