Voting starts in March for the Drupal Association Board election.
Panopoly is mapping out solutions to a lot of key problems. Making Open Oureach at compatible with - or even based on - Panoply would have major pluses:
- Access a bunch of great functionality not yet in OO, like responsive layouts and image styles, faceted search, and Solr integration.
- Get a lot more flexibility in site design.
- Free up OO development time to focus on nonprofit-specific problems rather than general distro ones.
- Provide continuity for site admins using other Pantheon-based distros.
There are also of course some potential barriers to consider:
- How to handle block placement? This is probably the biggest question. Currently we're using Context. Yes, we can switch to Panels, but there are several holes. Panels doesn't do site-wide block placement, which we have several instances of, and doesn't handle block placement in theme regions. A couple of related issues here: , . Also relevant is the interesting code by sun in .
- We're already into release candidates for OO. Switching now to Panopoly would be a major swerve and introduce a lot of instability, plus unexpected changes for existing OO sites.
- Panopoly would increase the base footprint of Open Outreach. Would it push OO beyond what many shared hosts provide?
- What to do with overlapping functionality? Luckily there isn't a lot. One however is debut_wysiwyg and panopoly_wysiwyg. If we were to switch from the former to the latter we'd need, at least, an update to migrate existing content's text formats.
- More short-term work focused on general distro issues and detracting from some pressing OO-specific ones like CRM integration.
Work is underway mainly in the Debut issue queue, see.