Version 15 (modified by 15 years ago) ( diff ) | ,
---|
Report
Based on our experiences with CiviCRM and our use cases, we identified a plan for moving forward.
The goal is to enable community-based organizations to run their own version of CiviCRM that is:
- pre-configured to address common organizing needs
- retains commonality so a shared skill set can be used across organizations
- is still capable of being modified and customized for the particular organization
We've broken down the project into three discrete projects:
- Common configuration. We will take a default CiviCRM installation and configure it with all the database-stored settings, field list, etc. that make sense for a community organizing group. We will then dump the database in a form that can be easily imported into any fresh CiviCRM installation.
- Template, language file changes, and Drupal modules. CiviCRM provides separate directories - local to the installation - that can hold customized templates and customized internationalization files (allowing us to use more organizer-friendly lingo in the database interface). We will prepare templates and internationalization files that are customized for organizing groups, allowing a common set of changes to be used by all participating organization in a way that does not require modifications to core CiviCRM code. In addition, we will include Drupal modules for added functionality (like reports or a custom dashboard).
- Themes. We will develop a custom Drupal theme for the project designed to meet our own design/layout needs.
- Support. How will groups be supported?
- Hosting.
Note:
See TracWiki
for help on using the wiki.