Reply to comment
- Not Just a Contact Database
-
These optional components give you more power to connect and engage your supporters.
civiCASE
Case management for clients and constituents.
civiCONTRIBUTE
Online fundraising and donor management.
civiEVENT
Online event registration and participant tracking.
civiMEMBER
Online signup and membership management.
civiMAIL
Personalized email blasts and newsletters.
civiREPORT
Report generation and template management.
We hope not
We hope this isn't a fork which is why we are blogging about it.
Throughout our development with PTP, we offered advice along the way to help prevent this from being a fork. We want the community to reuse the effort - it's a value of ours - but we're not quite sure how, seeing that:
When we began to wrap up the project, we asked the core team how we should contribute our code back to trunk. The response was "blog about it." So we're doing that, hoping this blog fosters a discussion that provides an approach for incorporating all of our work back into core.
The code is in our svn repository. It references custom tables in the PTP configuration so you would need to either create the same custom tables or modify the code to not reference them.
Thanks for your thoughts!