Difference between revisions of "Code4Lib Journal Recruit New Editors"

From Code4Lib
Jump to: navigation, search
(Announcement Venues)
(Announcement Text)
 
(6 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
== Announcement Text ==
 
== Announcement Text ==
  
Have you ever wanted to help shape the conversation about what libraries, archives and museums can be like today and tomorrow? If you have, please consider joining the editorial team at Code4lib Journal. Code4lib Journal is a quarterly, open access (CC-BY) peer reviewed, WordPress driven, journal that serves the community of technologists working in the cultural heritage sector. The journal is in its 5th year of publication, and sees thousands of visitors a month from around the world.  
+
The [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:
  
As an editor you would be instrumental in deciding what content gets presented in the journal, and working with authors to help get their content online. There is also an opportunity for innovation in how the journal presents itself online. If you would like to know more about what an editor for journal performs please see [http://journal.code4lib.org/process-and-structure Code4lib Journal: Process and Structure].
+
* Read, discuss, and vote on incoming proposals.
+
* Volunteer to be the assigned editor or second reader for specific proposals.
If your interest is piqued please answer each question with just a few sentences:
+
  
* What is your vision for the Code4Lib Journal? Why are you interested in it?
+
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.
* How can you contribute to the Code4Lib Journal? What do you have to offer?
+
  
Please send your responses to [mailto:journal@code4lib.org journal@code4lib.org]
+
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.
  
Sincerely,
+
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.
The Editors.
+
 
 +
It sounds like a lot of work, but it's also a lot of fun (if editing is your 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 ==
 
== Announcement Venues ==
  
When you make an announcement please add your initials and the date to the right of the list item:
 
  
 
* [http://twitter.com/code4lib code4lib twitter account] contact [http://twitter.com/MrDys MrDys]
 
* [http://twitter.com/code4lib code4lib twitter account] contact [http://twitter.com/MrDys MrDys]
* [https://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@listserv.nd.edu
+
* [http://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
+
* c4lj-discuss@googlegroups.com
* [http://lists.ala.org/wws/arc/lita-l LITA-L] lita-l@ala.org
+
* code4lib website
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.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.edu
+

Latest revision as of 18:27, 10 April 2012


Announcement Text

The 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:

  • Read, discuss, and vote on incoming proposals.
  • Volunteer to be the assigned editor or second reader for specific proposals.

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 idea of fun).

Intrigued? Please send a letter of interest by Monday, April 30 to journal@code4lib.org. Your letter should address these two basic questions:

  1. What is your vision for the Code4Lib Journal? Why are you interested in it?
  2. 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 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