-
Notifications
You must be signed in to change notification settings - Fork 21
CiviCRM for BackdropCMS.org Planning Meeting Notes, 2021 09 24
Jack Aponte edited this page Feb 28, 2022
·
1 revision
- https://github.com/backdrop-ops/backdropcms.org/projects/3
- https://github.com/backdrop-ops/backdropcms.org/issues/782
- https://github.com/backdrop-ops/backdropcms.org/issues/789
- https://github.com/backdrop-ops/backdropcms.org/issues/790
- https://github.com/backdrop-ops/backdropcms.org/wiki/CiviCRM-for-Backdrop-Planning-Meeting-Notes,-April-13-2021
- https://github.com/backdrop-ops/backdropcms.org/wiki/End-user-planning-for-CiviCRM-on-backdropcms.org,-May-14-2021
- https://github.com/backdrop-ops/backdropcms.org/wiki/End-user-planning-for-CiviCRM-on-backdropcms.org,-Aug-27-2021
- Get everyone caught up and on the same page about CiviCRM for BackdropCMS.org work to date, plans and next steps
- Finish our the CiviCRM policy discussion we started at our last meeting (see https://github.com/backdrop-ops/backdropcms.org/wiki/End-user-planning-for-CiviCRM-on-backdropcms.org,-Aug-27-2021#policy-decisions-we-need-to-make for what we discussed last time)
- Have some show-and-tell of our existing CiviCRM installations to explore what's possible and consider what we might want to do with our own Civi instance.
Present: Jack, Robert, Jen, Tim, Luke, Eric, Justin, Laryn
- Current civi + backdrop test site: https://backdropcms.palantetech.coop/
- The current test Civi setup is a basic installation, no particular customization.
- Civi will be in a separate db from the Backdrop db.
- JACK DONE: get Eric access to his user on the test site
- JACK DONE: get Luke access to his user on the test site
- A potential issue is syncing of the Civi contacts to the Backdrop users if we're moving the Civi site from a dev server to the live server.
- JA: plan is to do a minimal setup, and to do most of the config on the live site. Not experimental things, of course. Don't worry about user sync, don't need to import users.
- Civi is setup so that most config is done by clicking on live site, versus moving config files.
- Open question: how do we sanitize Backdrop data when we create a sanitized db?
- Also an open question: how to sanitize the Civi db when we generate data? That's a big open issue (and potentially complex). Eric may have a tool to make available for sanitization.
- #828 : come up with a sanitization plan for Civi db.
- LKB: there a GDPR extension for anonymization that we might be able to use to anonymize the Civi db.
- JC: an alternative strategy is to not sanitize and distribute the Civi db and just disable Civi for when they're working on borg on their local.
- JA: Note, though, that some people will be doing development for Civi on borg, so there will be some people who need to work with active CiviCRM.
- JA: as soon as we get a Civi installation running on a Backdrop-owned site, we can start using our own development workflow (Github PRs) to develop it.
- JA: let's finish "kicking the tires" on the https://backdropcms.palantetech.coop site.
- JC: use the new backdrop beta server as a test of the deploy to production. Run the installer there (and document anything special that needs to happen in conjuncion, like changing mysql permissions, etc). Then repeat the proces on the live server.
- JACK DONE: Close scattered Civi Github issues to put them all in the project https://github.com/backdrop-ops/backdropcms.org/projects/3. JA will take this on.
- An issue is that eventually we'll want to move user data from Backdrop fields into the CiviCRM contact records. This can be done before it's ever exposed to the users (which is done by creating a Profile in Civi to expose the data on the user page). So either some custom code to move the data (Eric says it's pretty simple), or (possibly, per JA) doing a CSV import of the data into CiviCRM.
Finish tire-kicking on https://backdropcms.palantetech.coop server, but strive to get a Civi installation on the Backdrop test server as soon as is convenient. Finalize testing there, then move Civi to live backdropcms.org site.