332
edits
Changes
→How the Editorial Committee Functions: link to WordPress site description
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 [http://wiki.code4lib.org/index.php/Code4Lib_Editorial_Committee_Introduction#Article_Tracking_Spreadsheet_.28Required.29| 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 WordPress site [http://journalwiki.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:
