Difference between revisions of "Code4Lib Editorial Committee Introduction"
(→How the Editorial Committee Functions) |
|||
| Line 1: | Line 1: | ||
== 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, 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. | + | 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. | + | 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 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 http://journal.code4lib.org. | + | 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: | 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 General outline of process and structure] | ||
* [http://journal.code4lib.org/process-and-structure/editors More detailed information for editors] (requires Wordpress login) | * [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! | Above all, the Editorial Committee is informal and egalitarian. Jump in with your opinion and ideas! | ||
Revision as of 13:07, 25 March 2008
Contents
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 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 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:
- General outline of process and structure
- More detailed information for editors (requires Wordpress login)
Templates for notifying authors about the status of their proposals are available as a page in the c4lj-articles google group.
Above all, the Editorial Committee is informal and egalitarian. Jump in with your opinion and ideas!
Article Tracking Spreadsheet (Required)
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.
Editorial Committee Discussion Lists (Required)
Much of the Editorial Committee's business is conducted via email on the 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.
All other Journal business is discussed on the C4LJ-Discuss Google Group. If there's no reason to keep a conversation private, use this group.
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 wiki. We also maintain basic information about the Journal using pages in Wordpress (Mission, Editorial Committee, Process and Structure, Call for Submissions, Article Guidelines).
New editors need to request a Wordpress account:
- Go to http://journal.code4lib.org/wp/wp-login.php?action=register
- Register
- Send your username to c4lj-articles@googlegroups.com so the technical editor can grant you Wordpress privileges.
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.
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. To join, use this invitation URL
