The Askbot XML import consumes a larger amount of RAM, takes a longer amount of time, and then fails. The OSQA JSON export consumes a large amount of RAM and takes a long time. The XML and JSON exports were both failing until I removed some bot-created tags. at, but I'd rather let someone else have the title of 'Earth's last OSQA The data migration path is long and winding: OSQA DB → OSQA Django ORM → XML or JSON export → Askbot Django ORM → Askbot DB. I suppose we could try to preserve the current environment by setting up a separate read-only instance, e.g. I had to go through the password recovery process for my account. The import script I'm using assumes we're using LDAP authentication and doesn't migrate passwords.

New account registration has been disabled on osqa-ask and other updates will probably be disabled at some I didn't configure any of the antispam options after yesterday's test import. UPDATE October 29: was migrated to Askbot. One person suggested moving to Stack Exchange, but other comments there roughly echo the SE comments below. They're having issues maintaining ASKBOT, but Evgeny Fadeev (ASKBOT's main developer) seems to want to help. UPDATE March 31: I just ran across this discussion on Ask Fedora. Please add votes, comments, and other options as needed. I will post some options for a future home below. I would like to migrate to a different platform before OSQA degrades even further. It also fills an important role in supporting Wireshark by providing a quick and easy way for users and developers to get answers. It depends on an old, EOLed version of Django. Over time features such as external authentication and spam filtering have degraded.

runs on OSQA, which is no longer maintained or supported.

Wireshark ubuntu install stack exchange