Changes

The Code4Lib Journal Editorial Committee works much as Code4Lib does: informally and collaboratively. One For each issue, one member of the Editorial Committee (EC) volunteers to be Coordinating Editor (ie i.e., managing editor) of a journal issue and . For the duration of their tenure, the Coordinating Editor is generally responsible for tying any loose ends, 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). For the duration of their tenure, the The Coordinating Editor is generally also responsible for any loose ends tying, writing an introductory editorial and making sure everything proceeds smoothly, coordinating all of publishing the rest of usjournal 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 tracking 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 responsiblity primary responsibility for at least 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://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.

# * [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 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].

== Article Tracking Spreadsheet Editorial Committee Discussion Lists (Required) ==

Articles, from proposal submission through to publication, are tracked using Much of the Editorial Committee's business is conducted via email on the [http://spreadsheetsgroups.google.com/ccc?key=p9UJm5vMnLh84uUz50moiaw&hl=en group/c4lj-articles C4LJ Article Tracking-Articles] spreadsheet in Google DocsGroup. This Google document list is private; only Editorial Committee members may view where we debate article submissions, volunteer to be editor or edit itmanaging editor, discuss acceptance of articles, and take care of any other tasks in front of us that might be of a sensitive nature. Proposal votes Anyone may post to this list, but only editors can read the list activity. To join this list, please visit the URL and tentative issue assignments request membership, using your preferred email associated with a Google account. If that doesn't work for accepted some reason, you can join the c4lj-discuss group (see below) and send an email requesting membership to c4lj-articles are tracked in this spreadsheet.

All other Journal business is discussed on Articles, from proposal submission through to publication, are tracked using the C4LJ Article Tracking spreadsheet in Google Docs. This Google document is private; only Editorial Committee members may view or edit it. Proposal votes and tentative issue assignments for accepted articles are tracked in this spreadsheet. The [http://groups.google.com/group/c4lj-discuss C4LJ-Discussarticles/browse_thread/thread/ec4c9701401ce94c/70079ef809a6a9da invitation] Google Group. If there's no reason to keep become a conversation private, collaborator is available on the c4lj-articles list. Please use this groupinvitation to add yourself as a collaborator for this document (you must already be a member of c4lj-articles).

== Wordpress (Required) ==

Code4Lib Journal articles are published in a Wordpress installation hosted by ibiblio (http://journal.code4lib.org). The assigned editor for an article is responsible for entering the content into Wordpress, formatting it, and adding images and code snippets. Guidelines on entering articles are available on the [[Code4Lib_Journal_WordPress_Input_Guidelines|wiki]]. We also maintain basic information about the Journal using pages in Wordpress (Mission, Editorial Committee, Process and Structure, Call for Submissions, Article Guidelines).

# Go to http://journal.code4lib.org/wp/wp-login.php?action=register# Register# Send your username to Contact c4lj-articles@googlegroups.com so and specify your preferred ''email'' and preferred ''username'' for the account. The technical editor can grant administrator will create your account and send you Wordpress privilegesinformation 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 [[Categoryhttp: //journal.code4lib.org/editorial-committee http://journal.code4lib.org/editorial-committee]. == Google Analytics (Optional) == Google Analytics is used to gather statistics for the Code4Lib Journal. If you are interested in being able to view these statistics, just send your preferred Google Account information to the c4lj-articles@googlegroups.com discussion list, and the technical editor will enable your access.  == Other Shared Documents (Optional) == The C4LJ Article/Author Ideas spreadsheet is used to track ideas for have for specific articles we'd like to recruit or specific authors we want to recruit for the Journal. The [http://groups.google.com/group/c4lj-articles/browse_thread/thread/425165428b88e2ee invitation]]to become a collaborative editor is available on the c4lj-articles list.