migration

Here it is: http://drupal.org/node/570906

Let me know if there are any grievous errors.

-glass.dimly

Digital Services Specialist, Boulder Public Library, Boulder Public Library - Main Branch

This is a 2 year temporary position.

40 hours per week

Apply by May 07, 2009

Salary Range: $21.88 - $26.25/hr

Required Education: Bachelor's Degree

Preferred Education: Master's Degree

Masters Degree in a program of Library and Information Studies preferred

Application requirements:
Applications are required and must be received by 12 noon at 1101 Arapahoe on the closing date of the recruitment period. No exceptions.

An application is required for all city of Boulder jobs.

The Data Import/Export and Migration to Drupal groups are being merged together. Data Import/Export was devoted to one project in this area while Migrate to Drupal was started for more general discussion - what we're going to do is close the group now known as Migration to Drupal and alter the charter for Data Import/Export to be more general (this is the easiest way to handle it, since Data Import/Export has the larger membership).

If you are a member of Migration to Drupal, you should join Data Import/Export to stay involved.

Thanks.

Develop and maintain the Coop Library Services website; develop site design; coordinate and work with staff developing documents for publication on the Coop Library's website; assist in migration of site to Drupal; work under the direction of the Web Administrator; team environment. For full job description and application, see the posting under "Human Resources/Jobs"

Do you plan on including turn-key solutions for migrating from specific CMSes, e.g. Wordpress? Please see a discussion I've started elsewhere about how to handle improvements I've made to a related module that currently is not already on d.o. Ultimately I'd like to merge wp2drupal into a more general app but if Migrate isn't intended to be like that then there's no point. Thanks.

I've been updating the wp2drupal module and wanted to make the changes available to the greater audience via d.o. But my changes mark at least the fourth developer who's worked on it - it was originally created by Borek Bernard, then updated by someone by the name of teodorani (who used to own teodorani.com but which is no longer working), and then partially upgraded to D6 by DenRaf.

The Migrate module is already garnering some good feedback. My immediate plan is to stablize the current code base of V1 - please discuss ideas for further extension and refactoring here.

Thanks.

I pushed through with some of the changes I was making on monday, and implemented a mechanism for provision to conditionally include version specific code. What this means, is that 1 checkout of provision, will now have all the information it needs to manage any supported version of Drupal you throw at it.

Lead Drupal Developer contract position (with the possibility of turning into full-time employment) available immediately in Santa Monica, California. Developer will lead the migration of Causecast's existing site to Drupal. If you want a job that makes a difference, Causecast is the place for you! Causecast will also provide selected candidate with 2009 DrupalCon registration, airfare, and hotel (up to $1000).

Requirements:
Expert-level experience with Drupal:
Drupal 6 and porting modules from 5 to 6.
Drupal API (especially Form)
CCK / Views integration
Themes / phptemplate

I'm not a MySQL fun, so some troubles with MySQL database (MyISAM data corruption and too slow InnoDB) force migration of three existing Drupal 6 sites from MySQL to PostgreSQL. Since Drupal 6.2 some PgSQL-related bugs (sample) in core modules has been fixed, so I have a try.

Drupal 6.5 and PostgreSQL 8.3 compatibility

Drupal Core Modules

I've installed clean Drupal 6.5 on top of PostgreSQL 8.3.3 (with UTF8 database encoding) and played with it a lot. There is no heavy troubles, only minor ones: