Changes between Version 18 and Version 19 of projects/crm_review/report


Ignore:
Timestamp:
Oct 23, 2008, 5:16:41 PM (17 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • projects/crm_review/report

    v18 v19  
    1111 * is still capable of being modified and customized for the particular organization
    1212
    13 The 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.
     13== Components ==
    1414
    1515We've broken down the common project into following components:
    … …  
    2323 * '''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.
    2424
     25== Customizations ==
     26
    2527In 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:
    2628
    … …  
    3032 * '''Ongoing support and training:''' answering questions and providing continued support
    3133
     34== Ongoing ==
     35
     36The 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.
    3237
    3338