Changes

Jump to: navigation, search

Code4Lib Journal Email Templates

1,028 bytes added, 26 June
Proposal Accepted: Added a choice to send a link to an online collaborative document
See also [[Code4Lib Journal Deadlines]].
<pre>I'm pleased to tell you that your recent proposal for an article about<topicTOPIC/titleTITLE> has been provisionally accepted to the Code4Lib Journal.The editorial committee is interested in your proposal, and would liketo see a draft.
<Additional comments ADDITIONAL COMMENTS about focus we'd like to see in the article or
editorial committee concerns. Sample language: "We're especially
interested in X, and we'd like you to make sure to flesh this out when
can do X, Y, or Z.">
As a member of the Code4Lib Journal editorial committee, I will beyour contact for this article, and will work with you to get it readyfor publication.  Working with me is second reader <SECOND READER>.  
We hope to publish your article in issue <nPICK_ONE> of the Journal, which isscheduled to appear mid <Month YYYY>. The deadline for submissionof a complete draft is Friday, <Month DD, YYYY>, but the sooner youcan get us a draft the better, and the more likely we'll be able toget your article into issue <n>. Upon receipt of the draft, I willwork with you to address any changes recommended by the EditorialCommittee. More information about our author guidelines may be foundat http://journal.code4lib.org/article-guidelines.
Please note that final drafts must be approved by Publishing an article in the Code4Lib Journal is a vote of collaborative effort between theEditorial Committee before being publishedauthors and editors.  The journal's editors work with authors throughout the draft-writing process to create a clear and useful article for the Code4Lib Journal audience.  That works best when a collaborative editing environment is used; we typically use Google Docs, but other tools such as Office 365 and even Etherpad can work as well.  When you have a draft ready for us to look at, please send me a link.
We also require all authors to agree to US CC-BY licensing for thearticles we publish in the journal. We recommend that any includedcode also have some type of code-specific open source license (such asthe GPL). Also please consider whether any of your images or screenshots require attributions.<OR>
Publishing an article in the Code4Lib Journal is a collaborative effort between the authors and editors. When you have a draft ready for us to look at, please send it to me in a common word processor format (for instance, DOCX for Microsoft Word or ODT for LibreOffice/OpenOffice). I will return it to you with my comments and the comments from other journal editors.
We look forward to seeing a complete draft and hope to include it inthe Journal. Thank you for submitting to us, and feel free to contactme directly with any questions.</PICK_ONE>
We hope to publish your article in issue <ISSUE> of the Journal, which is scheduled to appear <APPROXIMATE PUBLICATION DATE>.  To keep us on that publishing schedule, we have a series of deadlines—the first is the submission of a draft is <FIRST DRAFT DUE DATE>, but the sooner you can get us a draft the better—and the more likely we'll be able to get your article into the issue. Upon receipt of the draft, I will work with you to address any changes recommended by the Editorial Committee.  More information about our author guidelines may be found at http://journal.code4lib.org/article-guidelines. Please note that final drafts must be approved by a vote of the Editorial Committee before being published. We also require all authors to agree to US CC-BY licensing for the articles we publish in the journal. We recommend that any included code also have some type of code-specific open source license (such as the GPL). Also please consider whether any of your images or screenshots require attributions. We look forward to seeing a complete draft and hope to include it in the Journal. Thank you for submitting to us, and feel free to contact me directly with any questions. If you could drop me a line acknowledging receipt of this email, thatwould be great.</pre>
== Proposal Rejected ==
357
edits

Navigation menu