oehive upgrade efforts

Just a few notes in case anybody else is interested.

There will be a few of us volunteers working on this, but it's going to be an evenings and weekends effort, so we don't expect anything to move real fast.

Oehive's Drupal+modules source code is all in a public SVN repository. We also took a snapshot of the database. So, I think we all have what we need to get going (all the code and data).

The idea is to experiment with the migration of the database, experiment with Drupal 7 core features, and experiment with supporting modules. Because we've found that add-on modules are often poorly supported and fall behind, I have a preference for using core Drupal features as much as possible, and add-on modules as little as possible. We also have a preference for Drupal 7, but we recognize that it might be more practical to just go to Drupal 6 for now. We're going to try for 7, and 6 will be a fall back position.

We'll set up a repository for collaborating on our efforts, including scripts, upgrade procedures, modules, etc.

We also recognize that some of the modules we currently have on oehive are not fully used, and there might be simpler ways of doing things. For example, we installed a Project module which is not yet supported in Drupal 7. Well, the only thing we really needed from Project is the issue tracker, and there might be something else we can use for the tiny bit of issue tracking that is really done on the site.

Well, there we go. We'll play and experiment on our computers, collaborate, and share our findings. We'll write an upgrade checklist, write some upgrade scripts, and put a new version of Drupal+modules under source control. It should be fun.