[[Category: Code4Lib Journal]]
== Very Brief Application Announcement Text ==
Answer each question with just a few sentencesThe [http://journal.code4lib.org Code4lib Journal] is looking for volunteers to join its editorial committee. Editorial committee members work collaboratively to produce the quarterly Code4Lib Journal. Editors are expected to:
* What is your vision for the Code4Lib Journal? Why are you interested in it? Read, discuss, and vote on incoming proposals.* How can you contribute Volunteer to be the Code4Lib Journal? What do you have to offer?assigned editor or second reader for specific proposals.
Send Assigned editors work with the author(s) to make sure the article is as strong as possible, that the copy is clean, and deadlines are met. They also enter the article into WordPress, making sure the formatting is okay, all images and tables look good, etc. Second readers act as a second set of eyes for the assigned editor:* Read and comment on any other article that interests you.* Volunteer for administrative tasks and projects as they crop up.* Take a turn as Coordinating Editor for an Issue. The Coordinating Editor shepherds the issue through its life cycle. We seek an individual who is self-motivated, organized and able to meet deadlines; is familiar with ideas and trends in the field; and has an interest in the mechanics of writing. There is a sometimes significant time commitment involved; expect to set aside ten or more hours a month. It sounds like a lot of work, but it's also a lot of fun (if editing is your responses idea of fun). Intrigued? Please send a letter of interest by Monday, April 30 to [mailto:journal@code4lib.org journal@code4lib.org]. Your letter should address these two basic questions: # What is your vision for the Code4Lib Journal? Why are you interested in it?# How can you contribute to the Code4Lib Journal, i.e. what do you have to offer? We encourage people who have previously applied and who are still interested to re-apply. We have had to turn down a lot of highly-qualified people in the past due to the large number of applications. If you have any questions, contact us by email at [mailto:journal@code4lib.org journal@code4lib.org] or ask any member of the editorial committee (listed at http://journal.code4lib.org/editorial-committee). We plan to make decisions about additional editors by mid-May. Text of 2010 call for new editors: http://serials.infomotions.com/code4lib/archive/2010/201002/0246.html
== Announcement Venues ==
* [http://twitter.com/code4lib code4lib twitter account] contact [http://twitter.com/MrDys MrDys]
* [httpshttp://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@listserv.nd.edu* [http://listserv.uic.edu/htbin/wa?A0=drupal4lib Drupal4Lib] drupal4lib@listserv.uic.edu* [http://lists.ala.org/wws/arc/litac4lj-l LITA-L] lita-ldiscuss@ala.org* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchosgooglegroups.com* [https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu* [http://lists.sourceforge.net/lists/listinfo/oss4lib-discuss OSS4Lib] oss4lib-discuss@lists.sourceforge.net* [https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu,* [http://lists.webjunction.org/web4lib/ Web4Lib] web4lib@webjunction.org* [http://home.olemiss.edu/~noe/llfaq.html Law-Lib] law-lib@ucdavis.edu* [http://www.mlanet.org/discussion/medlibl.html MedLib] medlib-l@list.uvm.edu* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.educode4lib website
