As some of you might know, CiviCRM Standalone came out of a project we did with US PIRG
. The project lead was Wes Morgan who also was supporting the standalone version along with a few other features he worked on in Civi (SQL Import, REST API etc).
Wes has moved on from PIRG and his new position does not allow him the time to maintain and improve the standalone version. The core team does not have the energy or resources to maintain the standalone version either. There is one high priority issue of upgrading the OpenID library and adding support for Yahoo!/Google login. We need to fix this for 3.2 if we want to continue supporting standalone.
If you are currently using standalone and want to support it and be the maintainer, please contact us on CiviCRM's IRC channel
. We suspect it will be 50 hours per release to maintain and support CiviCRM Standalone. Some of the responsibilities include:
- Patching the code to allow Yahoo!/Google openid's to be used for 3.2. This is important and will be your first project.
- Fixing high priority issues and security fixes for the next minor/major release.
- Responding to forum posts and user issues on a regular basis (5-7 times a week)
- Testing the upgrade / install path for all major CiviCRM releases.
- Working with the community of users and adding features if/when needed.
- Regular meetings with the core team members to discuss issues and potential solutions.
If we do not find a maintainer, we will not have a standalone release for CiviCRM v3.2. We will document a migration path to Drupal for current CiviCRM Standalone users