Drupal Association members fund grants that make connections all over the world.
How do we accomplish long-term maintainability of sites build with the OpenOutreach profile?
At Koumbit, we've been building sites for non-profits for almost a decade, most of them on Drupal. While we haven't built any new sites on Drupal 6 for over a year, we still have several hundred Drupal 6 sites in our Aegir hosting system. When Drupal 8 is released, support for Drupal 6 will be dropped, so we need to upgrade these sites to D7 (or something), which in many cases will cost about the same as the initial site build. This scenario will play out again for each major version upgrade.
Since one of our primary goals is to provide affordable websites to non-profits, we need a long-term maintenance solution that will take major version upgrades into account.
There has been some talk about integrating the Migrate module into core, and then treating major version upgrades as a migration. It seems to me that this is a viable solution for distribution authors. Perhaps we could provide Migrate integration, to ensure smoother transitions.
This is not an immediate requirement, but we should take it into account as we move forward. Otherwise, there'll be a bunch of non-profits with sites built on OpenOutreach, facing a major expense just to keep on using their sites.