Changes between Version 15 and Version 16 of projects/crm_review/report


Ignore:
Timestamp:
Oct 23, 2008, 5:11:55 PM (15 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • projects/crm_review/report

    v15 v16  
    1111 * is still capable of being modified and customized for the particular organization
    1212
    13 We've broken down the project into three discrete projects:
     13The project should provide a public facing web site, explaining the goals and providing links to download the components so that anyone can use it. Ideally, the configuration files and code generated should be kept in a revision control system and an issue tracker should be setup to track problems and provide for an easy method to fix problems and release new versions that can be tracked against new versions of CiviCRM.
    1414
    15  * 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.
     15We've broken down the common project into following components:
     16
     17 * 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. This component will include a human readable file explaining what changes were made along with a sql file that can be automatically imported into a fresh CiviCRM installation.
    1618
    1719 * 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).
    … …  
    1921 * Themes. We will develop a custom Drupal theme for the project designed to meet our own design/layout needs.
    2022
    21  * Support. How will groups be supported?
     23 * Hosting. The project will develop components that can be hosted on any typical, free-software hosting provider. However, we may want to consider using a dedicated virtual server for a few reasons, including: control over system resources, ability to configure custom mail options, and ensuring that we have the required versions of supporting software (like PHP, MySQL, etc). Part of getting a dedicated virtual server should include the labor to maintain, backup, and trouble-shoot problems related to the server and the installations.
    2224
    23  * Hosting.
     25In addition to the common parts of the project, there will also be individual parts based on the number of groups who will implement the database:
    2426
     27 * Setup: installation the components and setting up the initial database
     28 * Import: importing data from existing data sources
     29 * Training: initial training on how to use the system
     30 * Ongoing support and training: answering questions and providing continued support
     31
     32
     33
     34