Code4Lib Editorial Committee Introduction - Revision history

RuthKitchinTillman: /* Wordpress (Required) */

2020-12-18T13:48:06Z

‎Wordpress (Required)

RuthKitchinTillman: /* Wordpress (Required) */ Fixing long out of date info.

2020-12-18T13:47:38Z

‎Wordpress (Required): Fixing long out of date info.

Tomkeays: /* Wordpress (Required) */

2020-11-03T19:56:22Z

‎Wordpress (Required)

Bean: /* How the Editorial Committee Functions */

2017-06-01T22:13:54Z

‎How the Editorial Committee Functions

Bean: /* How the Editorial Committee Functions */

2017-06-01T21:56:07Z

‎How the Editorial Committee Functions

Samato: /* Wordpress (Required) */

2013-11-11T20:53:05Z

‎Wordpress (Required)

Kelleym at 21:04, 17 May 2012

2012-05-17T21:04:04Z

Kelleym at 20:56, 17 May 2012

2012-05-17T20:56:24Z

Ejlynema: /* How the Editorial Committee Functions */

2010-03-18T20:05:40Z

‎How the Editorial Committee Functions

152.1.190.106: /* Wordpress (Required) */

2010-03-12T18:04:18Z

‎Wordpress (Required)

@@ Line 35: / Line 35: @@
 New editors need to request a Wordpress account:
-# 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.
+# 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/editorial-committee http://journal.code4lib.org/editorial-committee].

@@ Line 35: / Line 35: @@
 New editors need to request a Wordpress account:
-# Go to http://journal.code4lib.org/wp/wp-login.php?action=register  - if this link does not work, please contact the Technical Editor to request access.
+# 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.
-# Register
-# Send your username to c4lj-articles@googlegroups.com so the technical editor can grant you Wordpress privileges.
 Once you have an active WordPress account, please add your name to the list of Editorial Committee members at [http://journal.code4lib.org/editorial-committee http://journal.code4lib.org/editorial-committee].

@@ Line 35: / Line 35: @@
 New editors need to request a Wordpress account:
-# Go to http://journal.code4lib.org/wp/wp-login.php?action=register  - if this link does not work, please contact either Carol Bean <beanworks@gmail.com> or Tom Keays <tomkeays@gmail.com> to request access.
+# Go to http://journal.code4lib.org/wp/wp-login.php?action=register  - if this link does not work, please contact the Technical Editor to request access.
 # Register
 # Send your username to c4lj-articles@googlegroups.com so the technical editor can grant you Wordpress privileges.

@@ Line 3: / Line 3: @@
 == 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 (i.e., 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).
+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 (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, 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 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 as the first editor. The first editor shepherds the from proposal to publication, acting as the journal's single point of contact with the author. Each article also has a second editor/reader, 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 issue and serve as second reader on another one, though the committee is large enough that there is some flexibility with editorial responsibility.
+Everyone on the EC 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.  EC members may volunteer to be the primary editor or second reader for an article during the voting process or once voting is completed.  The primary editor takes on the responsibility of shepherding the article from proposal to publication,  acting as the journal's single point of contact with the author. 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 one article per issue and 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.

@@ Line 3: / Line 3: @@
 == 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 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).
+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 (i.e., 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 as the first editor. The first editor shepherds the from proposal to publication, acting as the journal's single point of contact with the author. Each article also has a second editor/reader, 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 issue and serve as second reader on another one, though the committee is large enough that there is some flexibility with editorial responsibility.

@@ Line 5: / Line 5: @@
 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 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.
+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 as the first editor. The first editor shepherds 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 issue and 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.
@@ Line 14: / Line 14: @@
 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].
 Above all, the Editorial Committee is informal and egalitarian.  Jump in with your opinion and ideas!