Published
2007-07-13 12:28
We've had Deepak and Manish from India and Michal from Poland visiting San Francisco. We've been thinking about the various things we need to accomplish for 2.0 and having a few design / schema meetings. We'll be blogging in detail about various sub-projects over the next few weeks.
The feature set for 2.0 is on our wiki. This is an initial feature list and is subject to change (all usual disclaimers apply). We dont expect 2.0 to have a lot of new features, but more to set the stage for some larger changes later in the 2.x cycle. To a large extent, this seems to be the right time and place to do such changes. As most of you are aware, 2.x will only support PHP 5.2 and MySQL 5.0.x
With regard to the schema, we are planning changes in the following areas:
- CiviCRM Custom Group, Field and Value: Some thoughts on this were posted as a blog entry a few months back.
- CiviCRM Location, Address, Phone, Email, IM: There is encapsulation out here which is not very efficient in search. We are planning to flatten the structure and make it a bit looser
- CiviCRM Entity Table / Entity ID: While this method is quite generic and allows us to reuse a fair amount of code, in a few key places it introduces some inefficiency. We'll take a closer look at the schema and flatten the structure as needed (see location above)
- CiviCRM Activities / Phonecall / Meetings / History: We are planning to potentially merge the activities into one table and extend the functionality to allow a person a schedule an activity between two other contacts.
- Nestable groups? Wes and the team at Code for change have started exploring this to address the multiple orgs (and chapters) dealing with one contact database. You can find some more information here and some fairly informative mysql database theory here. We are also hoping to use Views and Stored Procedures a fair amount in v2.0
Filed under
