Re: [CODE4LIB] python developer jobs in DC
May be too late on this one... -Original Message- From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of Daniel Chudnov Sent: Thursday, February 04, 2010 6:15 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] python developer jobs in DC Posted on behalf of a colleague. Note from the descriptions, these could be right up the alley of many subscribers of this list. Please reply to the contact person listed at the bottom if you're interested. -Dan -=-=- CACI (Washington, DC, US) Posted 22-Jan-2010 Job Description: CACI Position 43399: Software Developer - Python: Python developer supporting all aspects of several digital preservation and Web access projects. Must be experienced in all phases of Web development from front-end to back-end, especially: * Development and deployment of Python-based applications using contemporary Web frameworks (such as Django) * RDBMS model design and SQL * Implementation and debugging of cross-platform Web browser compatibility issues in HTML, CSS, JavaScript * Experience solving deployment issues regarding scale, performance, administration, OS/platform Additional/Preferred Technical Experience: * Experience developing and deploying applications in additional languages (Ruby, Perl, Java, C/C++) * Experience developing and deploying applications on multiple platforms (Solaris, GNU/Linux) * Experience using integrated version control and ticket tracking tools (such as Trac) * Familiarity with library software systems and metadata standards (MARC, MODS, METS) * Experience developing and integrating GIS and information visualization tools into diverse applications Job Description: CACI Position 43400: Software Developer - Python: Serve as a member of a web development team and will be responsible for participating in the definition, design, and development of the software, tools and technologies that satisfy functional requirements, within the scope, schedule, and priorities as assigned by the project manager and/or technical lead. Must be familiar with the entire lifecycle of software development, and have experience creating and maintaining applications for production environments. Required Qualifications and Skills: * Experience developing and deploying Python-based applications using contemporary Web frameworks (such as Django) * Experience developing and deploying applications in additional languages (such as Ruby, Perl, Java, C/C++) * Experience developing and deploying applications on multiple platforms (Solaris, GNU/Linux) * Experience with test-driven design (TDD), and code reviews * Experience with addressing deployment issues regarding scale, performance, and administration throughout the development lifecycle * Experience using version control (such as Subversion) and ticket tracking tools (such as Trac and/or JIRA) * Familiarity with library software systems and metadata standards (MARC, MODS, METS) Job Description: CACI Position 43401: Senior Software Developer - Python: Serve as the technical lead for a web development effort, responsible for leading and participating in the definition, design, and development of the software, tools and technologies that satisfy functional requirements, within the scope, schedule, and priorities as assigned by the project manager. Must be familiar with the entire lifecycle of software development, and have experience leading development teams in creating and maintaining applications for production environments. Required Qualifications and Skills: * Experience leading small to medium sized development teams through the design, development, deployment, and maintenance of high availability web sites and/or applications. Experience with Content Delivery Networks (CDNs) a plus. * Experience with implementing test-driven design (TDD), leading code reviews, and coordinating with Quality Assurance (QA) teams * Experience with planning and coordinating the release of versioned development builds to QA and production environments * Experience with planning and coordinating the development team's work using ticket tracking tools (such as Trac and/or JIRA) * Experience with addressing deployment issues regarding scale, performance, and administration throughout the development lifecycle * Experience developing and deploying Python-based applications using contemporary Web frameworks (such as Django) * Familiarity with library software systems and metadata standards (MARC, MODS, METS) For further details, and to apply: * Contact: Perry Stone * E-mail contact: pst...@caci.com * Web: CACI Job Search - Search using Requistion ID numbers from above (43399, 43400, 43401)
Re: [CODE4LIB] open source software ideascale
On Feb 11, 2010, at 9:56 PM, Ryan Eby wrote: http://libraryideaforum.ideascale.com/ I'm guessing that you are, but I'm wondering if you plan on compiling some of the comments and votes and writing more about them. I'd hate to see some of these comments go the way of a survey. Alas, we haven't gotten that far yet. -- Earache Least Moron
Re: [CODE4LIB] change management system
Walker, David wrote: Thanks to everyone who responded. The comments have been very helpful! Is anyone using RT? [1] In my limited experience RT is powerful but has grown rather over the years to the point where some investment in time is needed to set it up usably. A PHP oriented person (ahem) might prefer eventum (which is also fairly configurable, but through the web interface). However, it's definitely a ticketing system rather than a full change management system. Graham PS We're too small to justify the kind of separation of roles you're asking about internally to the library (as opposed to between library and campus IT). However, I'd definitely like to see more formally documented procedures: at the moment we just use a wiki and a remote-hosted commercial ticketing system called kayako which is more appropriate for help-desk calls than for development work. Also, I'm curious how many academic libraries are following a formal change management process? By that, I mean: Do you maintain a strict separation between developers and operations staff (the people who put the changes into production)? And do you have something like a Change Advisory Board that reviews changes before they can be put into production? Just as background to these questions: We've been asked to come-up with a change management procedure/system for a variety of academic technology groups here that have not previously had such (at least nothing formal). But find the process that the business (i.e., PeopleSoft ) folks here follow to be a bit too elaborate for our purposes. They use Remedy. --Dave [1] http://bestpractical.com/rt == David Walker Library Web Services Manager California State University http://xerxes.calstate.edu From: Code for Libraries [code4...@listserv.nd.edu] On Behalf Of Mark A. Matienzo [m...@matienzo.org] Sent: Thursday, February 11, 2010 5:47 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] change management system I'm inclined to say that any sort of tracking software could be used for this - it's mostly an issue of creating sticking with policy decisions about what the various workflow states are, how things become triaged, etc. I believe if you define that up front, you could find Trac or any other tracking/issue system adaptable to what you want to do. Mark A. Matienzo Digital Archivist, Manuscripts and Archives Yale University Library
[CODE4LIB] Developer positions available at Indiana University
(Please excuse cross-posting) The Indiana University Digital Library Program is seeking a skilled software developer to join our team and contribute to the ongoing development and management of Indiana University's Fedora-based digital library infrastructure. See below for a copy of the posting. Applications may be submitted online at https://jobs.iu.edu/joblisting/index.cfm?jlnum=1315. In addition to this continuing position, we also have several other job openings for grant-funded positions with one- and two-year appointments. For more information about these opportunities or about the IU Digital Library Program, please visit http://www.dlib.indiana.edu/employment/. If you have any questions about any of the positions, please don't hesitate to contact me. Regards, Jon --- Jon Dunn Associate Director for Technology Indiana University Digital Library Program IU Libraries / University Information Technology Services j...@indiana.edumailto:j...@indiana.edu (812) 855-0953 -- Analyst/Programmer, Digital Library Tools Indiana University Digital Library Program Bloomington, Indiana Job# 1315, Rank PAE3IT Job Description: Participates in the development and management of IU's digital repository system (based on the Fedora open source software platform) and associated software tools for ingestion, management, and delivery of digital library content. Designs, evaluates, programs, and implements Web-based software tools supporting access to and ingestion of digital library collections. Works with other Digital Library Programs and IU staff to define requirements for tools to support delivery of image, text, audio, video, and data collections; evaluates potential commercial and open-source solutions; designs and tests user interfaces; designs, codes, and tests software; and defines and implements interfaces with other IU systems. Qualifications: Bachelor's degree in computer science, information science, or related technical field with two to three years experience in the development of complex software systems, including work in Java, required. An equivalent combination of education and experience may be considered. Must have experience in Java web application development; XML and XML-related technologies; and HTML, CSS, and JavaScript. Excellent oral and written communication skills needed. Good interpersonal skills and ability to work as part of a team required. Experience with library systems and metadata standards; digital image, audio, and video formats; relational database design and programming; and Web Services preferred. Experience working in a Unix/Linux environment preferred. Indiana University is an Equal Opportunity/Affirmative Action Employer. Indiana University has a strong commitment to principles of diversity and in that spirit seeks a broad spectrum of candidates including women, minorities, and persons with disabilities.
Re: [CODE4LIB] change management system
FogBugz seems really fabulous. In my previous career as a QA engineer, my team was planning to try it out, but our employer went out of business before we had a chance to pilot it. -marijane On Thu, Feb 11, 2010 at 11:54 PM, Boheemen, Peter van peter.vanbohee...@wur.nl wrote: We have chosen to use FogBugz. A great product. Very easy to use. Integrates well with version control systems, can also be used as agile project management system and can create wiki's to write documentation. It is great to be able to search documentation and all case history with one search interface. Not open source, but very reasonably priced. Peter -Original Message- From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of Fleming, Declan Sent: vrijdag 12 februari 2010 0:52 To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] change management system Hi - Service Desk Express (SDE) from BMC. Not cheap, but I bet an OSS could do similar stuff. D -Original Message- From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of Walker, David Sent: Thursday, February 11, 2010 11:57 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] change management system What are you using for that ticketing system? --Dave == David Walker Library Web Services Manager California State University http://xerxes.calstate.edu From: Code for Libraries [code4...@listserv.nd.edu] On Behalf Of Fleming, Declan [dflem...@ucsd.edu] Sent: Thursday, February 11, 2010 11:52 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] change management system Hi - it's primarily designed for things we develop. We have a Change Management ticketing system following ITIL principles that tracks change requests for anything in production, from working apps we've developed, to III, to the public infestations, and even account adds/moves/changes. Tickets from this system will sometimes be moved into JIRA when they ask for a change to something we've developed. D -Original Message- From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of Walker, David Sent: Thursday, February 11, 2010 9:49 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] change management system Hey Declan, Does that process only apply to applications you develop yourselves? How about the Innovative system, or open source applications developed elsewhere? --Dave == David Walker Library Web Services Manager California State University http://xerxes.calstate.edu From: Code for Libraries [code4...@listserv.nd.edu] On Behalf Of Fleming, Declan [dflem...@ucsd.edu] Sent: Thursday, February 11, 2010 9:31 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] change management system Hey Dave! We need to go grab lunch sometime... We use JIRA for our bug tracking and tracking feature requests (to some extent). UCSD Libraries IT has a strict Development/Operations split, with a weak Test phase in the middle - weak because I don't have a QA or config manager, and I'm teaching academics the processes I learned while working in the software industry. We follow a 2 week deploy process where Dev can submit any packages to Ops every other Friday. On Monday or Tuesday (depending on what's on fire in Ops), these packages are then staged to a Test server that only Ops has admin privs on. If the project people have a test plan, they have the rest of the week to say whether the package passes or not. If yes, we roll the package to production on the next Monday or Tuesday. If not, we kick the package back to Dev and they do their fixes and unit tests and wait for the next cycle. This system keeps production (and thus, customers) from being thrashed with not-quite-ready builds. There is a lot of natural tension in our system, especially with the lack of a QA manager, and most of the config management being done by Ops. We require a high degree of communication between the Ops and Dev managers on dates, test pass/fail conditions, code quality, process mgt, etc. This can be a challenge as Ops and Dev have different missions at times. D -Original Message- From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of Walker, David Sent: Thursday, February 11, 2010 8:55 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] change management system Thanks to everyone who responded. The comments have been very helpful! Is anyone using RT? [1] Also, I'm curious how many academic libraries are following a formal change management process? By that, I mean: Do you maintain a strict separation between developers and operations staff (the people who put the changes into production)? And do you have something like a Change Advisory Board that reviews changes before they can be put into
