15
edits
Changes
→Wordpress (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 i.e., managing editor) of a journal issue. For the duration of their tenure, the Coordinating Editor is generally responsible for tying 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). The Coordinating Editor is also responsible for writing an introductory editorial and publishing the journal issue.
Everyone on the EC may is expected to 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 EC members may volunteer to be the primary editor or second reader for an article during the voting process or once voting is accepted for publication, an EC member volunteers to take completed. The primary editor takes on editorial the responsibility for that of shepherding the article and shepherds it from proposal to publication, acting as the journal's single point of contact with the author. Most The second editor/reader for an article serves as another pair of eyes early in the process by reading and providing feedback on drafts. Committee members are generally expected to 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 usually 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.
* [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 on the [http://groupswiki.googlecode4lib.comorg/groupindex.php/c4lj-articles/web/templates-for-email-responses pageCode4Lib_Journal_Email_Templates wiki] . All of the Code4Lib Journal information on the wiki can be seen in the c4lj-articles Google group[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!
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) ==
New editors need to request a Wordpress account:
# Go Contact c4lj-articles@googlegroups.com and specify your preferred ''email'' and preferred ''username'' for the account. The technical administrator will create your account and send you information to login and reset the password. Once you have an active WordPress account, please add your name to the list of Editorial Committee members at [http://journal.code4lib.org/wp/wpeditorial-logincommittee http://journal.php?action=register# Register# Send your username to c4lj-articles@googlegroupscode4lib.com so the technical editor can grant you Wordpress privilegesorg/editorial-committee].
== Google Analytics (Optional) ==
