Upgrade community site OpenAtrium [#2112977]

Someday we need to upgrade the http://community.aegirproject.org/ away from OpenAtrium on Drupal 6.

I've opened this issue to investigate the options...

As there is no apparent upgrade path, we could use the migrate module.

What elements do we have to migrate:

Documentation - book pages
discussion
Calendar - events
Feed reader - Feeds and imported nodes?
users

I don't like this the absences of an upgrade path....
What do we need OpenAtrium for? We could do this on core++ ... right?

Comments

Comment #1

helmo CreditAttribution: helmo commented 16 October 2013 at 10:18

Some notes on my first try with migrate_d2d:

install clean oa site 2.0-beta4
drush dl migrate_d2d-7.x-2.x-dev
drush dl migrate-7.x-2.x-dev
drush en migrate_d2d_ui
drush en migrate_ui

The wizard seems to work nice, apart form a few notices...

Outcome:
* Book pages lost their hierarchy ... not supported: #763880: Import Hierarchy as Book
* groups to groups mapping ... should that have been to spaces?

My dummy source site did not have events, discussion or feeds.
But lets discuss what we need... the events could be imported from a single ical file right?

Do we want to preserve the old feed items?

I do think we should not lose the discussion pages... but I prefer to keep stuff like that in an issue queue...

Comment #2

anarcat CreditAttribution: anarcat commented 16 October 2013 at 15:14

Should we consider migrating to a different, more long-term platform if we are to do a full migration anyways?

Because Drupal 7 will be basically obsolete when D8 is released, supposedly in 2014, I am not sure I would want to go through all that trouble every 3 years.

Here's another alternative we could consider:

1. archive the current site
2. migrate from discussion page to an email forum, with gmane as a web gateway
3. migrate the handbook into a Real Wiki (insert flamewar here)
4. drop "events"

I am frankly tired of applications that are not supported by their upstream. OpenAtrium is clearly not setting an example in properly managing a community by not supporting that upgrade path properly, and I am not sure we should continue encouraging that project by bending over backwards to migrating to the new version.

What does the D7 version bring that the D6 version doesn't have anyways?

Comment #3

FMB CreditAttribution: FMB commented 2 January 2014 at 10:00

Apparently some Migrate scripts should be released later this month, according to mpotter.

Comment #4

jonreid CreditAttribution: jonreid commented 17 March 2014 at 15:47

Issue summary:

View changes

helmo, neither Drupal 7 nor Drupal 6 will be obsolete with the release of Drupal 8. In the case of Drupal 7 we can look forward to at least 2 to 5 years of ongoing support. With Drupal 6, there has been a lot of discussion around extending the official support period (https://drupal.org/node/2136029), and even more evidence that the community will continue to offer support.

To understand your question better, are you looking to migrate your current content from a Drupal 6, Open Atrium installation to a Drupal 7 or 8, non-OA installation?

I'll be working with mpotter over the next couple of weeks on migrating a site to OA2.

Comment #5

helmo CreditAttribution: helmo commented 26 March 2014 at 08:38

@jonreid: I'm aware of the extended support for D6, this issue was from before that started ;)

The main reason for me is to stay on a supported platform. So we have a bit more time now.

Having it on D7 would lower the barrier to new developments... but I don't have any planned.

The motivation for non-OA was the lack of an upgrade path.

Comment #6

ergonlogic

he/him

English

Montréal, Québec 🇨🇦

CreditAttribution: ergonlogic commented 26 March 2014 at 12:21

There appears to have been some progress on migration scripts, according to https://drupal.org/comment/8515935#comment-8515935.

That said, our OA1, which we inherited from DevSeed (back when they were the lead shop behind Aegir) has been customized in a number of ways. The most radical being that Atrium Groups was disabled, which normally wouldn't even be possible in OA1. Any migration script is likely to assume the presence of groups, which will complicate our upgrade.

My preference remains to move to OA2, despite these challenges, though I agree that it's less pressing with extended D6 support. I think the greatest value of the community site is the documentation, which we'd put quite a bit of effort into making more wiki-like. At Praxis, we use OA2 extensively, and have built extensions to improve the built-in wiki functionality, which could be re-used here. The calendar and discussions work just fine as is, and setting up the ability to reply to discussions by email is pretty straight-forward. So that would be a benefit to upgrading.

Unless I'm mistaken, the feeds on the community site haven't really worked for a while now. I don't believe that OA2 has any built-in functionality for that, but it shouldn't be too difficult to add it.