== Call for proposals ==
'''Change what's in bold. ..''' ----
Call for Papers (and apologies for cross-posting):
technology, and the future.
The Code4Lib Journal is now accepting proposals for publication in its 8th issue. Don't miss out on this opportunity to share your ideas andexperiences. To be included in the '''8th issue ''', which is scheduled for publication in '''mid November 2009''', please submit articles, abstracts,or proposals at http://journal.code4lib.org/submit-proposal or to email@example.com by '''Friday, August 14, 2009'''. When submitting, please include the title or subject of theproposal in the subject line of the email message.
C4LJ encourages creativity and flexibility, and the editors welcome
submissions across a broad variety of topics that support the mission
of the journal. Possible topics include, but are not limited to:
* Practical applications of library technology (both actual and hypothetical) * Technology projects (failed, successful, or proposed), including how they were done and challenges faced * Case studies * Best practices * Reviews * Comparisons of third party software or libraries * Analyses of library metadata for use with technology * Project management and communication within the library environment * Assessment and user studies
C4LJ strives to promote professional communication by minimizing the
barriers to publication. While articles should be of a high quality,they need not follow any formal structure. Writers should aim for the
middle ground between blog posts and articles in traditional refereed
journals. Where appropriate, we encourage authors to submit codesamples, algorithms, and pseudo-code.
For more information, visit C4LJ's Article Guidelines or browse articles from the first '''7''' issuespublished on our website: http://journal.code4lib.org.
Remember, for consideration for the
'''8th issue ''', please send proposals,abstracts, or draft articles to journal @code4lib.org nolater than '''Friday, August 14, 2009''' .
Send in a submission. Your peers would like to hear what you are doing.
Code4Lib Journal Editorial Committee
== Submission Acknowledgement ==
Thank you for submitting a proposal to the Code4Lib Journal. We appreciate your participation in the
code4lib community. The editors have received your proposal and should be in touch with you in 2 -4 weeks regarding its appropriateness for publication in C4LJ. We will notify you if we need additional information to make this decision. Please feel free to contact us at firstname.lastname@example.org if you have additional questions.
== Need More Information ==
Thank you for your interest in publishing in the Code4Lib Journal. The Journal is primarily focused on technological issues in libraries. In order to help the editors determine if your proposal is appropriate for this publication, could you share more details about the intended audience for
the the article and how it will address issues surrounding technology in libraries? Please respond to email@example.com with the additional information requested.
You may also contact the editors at firstname.lastname@example.org if you have any additional questions. We look forward to hearing from you.
== Proposal Accepted ==
'''See also [[ Code4Lib_Journal_Deadlines]] '''
I'm pleased to tell you that your recent proposal for an article about
insert topic/title> has been provisionally accepted to the Code4LibJournal. The editorial committee is interested in your proposal, andwould like to see a draft.
insert any additional comments about focus we'd like to see in thearticle or editorial committee concerns. Sample language "We'reespecially interested in X, and we'd like you to make sure to fleshthis out when you write the article." "We're interested in thisproposal if you can do X, Y, or Z.">
As a member of the Code4Lib Journal editorial committee, I will be
We hope to publish your article in issue <
#> of the Journal, which isscheduled to appear on < insert date here>. The deadline for submissionof a complete draft is < deadline for draft>, but the sooner you canget us a draft the better, and the more likely we'll be able to getyour article into issue < #>. Upon receipt of the draft, I will workwith you to address any changes recommended by the EditorialCommittee. 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 CC-BY licensing for thearticles we publish in the journal. We recommend that any included
code also have some type of code-specific open source license (such as
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, that would be great.
== Proposal Rejected ==
We regret to inform you that your recent proposal to the Code4Lib Journal for an article about <
insert topic/title> has not been accepted for publication. This is likely because the Editorial Committee determined that it was not an appropriate match for the audience, mission, or scope of the Code4Lib Journal. [optional - insert comment here about why it's not appropriate]
For more information about the mission of the Code4Lib Journal, please see http://journal.code4lib. org/mission/.
Thanks for considering us, and please do not hesitate to contact the editors at journal@code4lib. org in the future with a new or revised proposal.
[[Category: Code4Lib Journal]]