Dear Code4Libbers: While I am personally wishy-washy on the title chosen (it's kind of neat, but doesn't really feel like a title or one easy to find), I think the semantics of publishing a title like that is enough to reconsider using it. I admit I did not vote because I wasn't too fond of any names provided, but now that people are definitely showing disinterest in the results, maybe a second round of voting should occur with more semantically-friendly options?
I realize this is probably a late suggestion, but if it is accepted I would be more than happy to contribute some snappy ideas and volunteer with the journal as well. I suppose I could volunteer regardless if my suggestion is taken... An idea I can think of off the top of my head, which I personally find cute :-D, is "Carrot Code (or ^Code): code for programmers to chew on." Hee hee. We could have Bugs Bunny as a mascot. Okay, maybe not that far, but the point is we can find semantically-friendlier titles. I hope we are able to agree on a course of action! Please let me know if I can be of any help. Thank you and have a good day. In peace, Amy M Ostrom Web Interface Designer [EMAIL PROTECTED] On 5/3/06, Davis, Jeffrey <[EMAIL PROTECTED]> wrote:
Here's the latest on the code4lib journal: "/lib/dev: A Journal for Library Programmers" won the journal name vote. (See http://www.code4lib.org/node/96 for more details.) I've been talking to Simon Fraser University about hosting the journal and looking into using Open Journal Systems to host it. A default OJS install doesn't do all the things we've been talking about doing with the journal ( e.g. allowing for open commenting). Theoretically, we could write plugins that would add the features we want. I'm not familiar enough with OJS at the code level to know if that's the route we want to take (as opposed to building the extra features we're looking for outside of the OJS framework, which might be easier), but the OJS developers are interested in feedback on the plugin capability and would welcome any plugins that we write. I've moved the draft editorial policy statement to the code4lib.org site [1]. It would be great if people with actual experience starting/running journals could take a look at it and provide feedback. For example, I've suggested releasing an issue every two months -- is that feasible? [1]: http://code4lib.org/journal/policies/ About half a dozen people have volunteered to help out so far, and more are always welcome. I think the next step is for people with more programming expertise than myself to take a look at OJS and see how to enable open pre-publication commenting (i.e. not limited to official editors, and with the option to comment anonymously), and integrated version tracking (so that for any given comment, you can tell which revision of an article it refers to). I'll be bugging some of the volunteers about this, but if anyone has prior experience with this sort of thing, please let me know. I'd like to have an at least partially functional OJS install up and running before releasing a formal call for submissions, but if you think you'll want to contribute an article, this would be a good time to think about what you're going to write. (Sorry for the delay on this reply -- I'm on vacation this week, so I haven't been checking my email regularly.) -- Jeff Davis Public Services Librarian University of Alberta Libraries Edmonton, Alberta, Canada -----Original Message----- From: Code for Libraries on behalf of Eric Lease Morgan Sent: Sat 4/29/2006 2:12 PM To: [email protected] Subject: [CODE4LIB] code4lib journal What is the status of the Code4Lib journal? What can I do to help it move to the next step? -- Eric Lease Morgan University Libraries of Notre Dame
