http://wiki.code4lib.org/index.php/Code4Lib_Journal_Deadlines#Fifth_issue
* Monday, August 18 -- call for proposals
* Friday, September 12 -- proposals due (after issue 4 is published)
* Friday, September 19 -- finish voting on proposals; notify authors
* Friday, October 17 -- first draft due
* Friday, November 14 -- second draft due
* Monday, December 15 -- publication
I have given exactly 4 weeks between each of these dates: our final
voting date for proposals, the first draft deadline, the second draft
deadline, and the publication date. We got a lot of those second drafts
in way late this time around, which made getting things ready for
publication difficult, so I think it will be best if we have some sort
of hard deadline across editors for the second draft.
Does this seem reasonable? The only thing I wonder is if we should push
the first draft deadline back 1 week (and everything before it back) so
that we have a week to gather feedback and send to the authors and then
they still have 4 weeks for re-writing.
I might be willing to take on issue 5. However, I'm going to be out of
town and completely out of email on Sep. 4 - 12. So I won't be around to
remind folks of the status of voting on articles that week, etc.
(Tentatively the proposals are due Sep. 12 with voting done by Sep. 19).
If that's going to be an issue, maybe someone else should be the
coordinating editor.
-emily
Ron Peterson wrote:
> Speaking of issue 5, it's about time to start thinking about who will be
> coordinating editor. Any volunteers?
>
>
--
Emily Lynema
Systems Librarian for Digital Projects
Information Technology, NCSU Libraries
919-513-8031
emily_...@ncsu.edu
--
Jonathan Rochkind
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
410.516.8886
rochkind (at) jhu.edu