Changes

Code4Lib Editorial Committee Introduction

891 bytes added, 13:07, 25 March 2008
How the Editorial Committee Functions
== How the Editorial Committee Functions ==
The Code4Lib Journal Editorial Committee works much as Code4Lib does: informally and collaboratively. One member of the Editorial Committee (EC) volunteers to be Coordinating Editor (ie managing editor) of a journal issue and is responsible for distributing the call for papers, communicating with potential authors, opening and closing editorial committee voting on submissions, notifying authors as to whether proposals are accepted/rejected, and making sure that accepted articles have volunteer editors. 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.
Everyone on the EC may vote on article proposals as they come in. The Coordinating Editor generally sets a deadline of about 2 weeks to get your vote in. Voting is straightforward and recorded in the [http://spreadsheets.google.com/ccc?key=p9UJm5vMnLh84uUz50moiaw&inv=c4lj-articles@googlegroups.com&t=340928040055520379&guest 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 responsiblity responsibility for at least 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 http://journal.code4lib.org. 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 that every EC member votes 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!
Anonymous user