Skip to content

CiviCRM for BackdropCMS.org Planning Meeting Notes, 2022 03 14

Jump to bottom Edit New page
Jack Aponte edited this page Mar 14, 2022 · 1 revision

AGENDA:

Notes from last meeting: https://github.com/backdrop-ops/backdropcms.org/wiki/CiviCRM-for-BackdropCMS.org-Planning-Meeting-Notes,-2022-02-28 Github Project: https://github.com/backdrop-ops/backdropcms.org/projects/3

Where to put sensitive information for ongoing civi updates

  • CIVICRM.txt file (ajacent to MYSQL.txt file on server) can contain private info
  • non-sensitive info can go into publically accessible wiki

GDPR extension

  • should be installed before launch on live
  • RJL will install GDPR extension into codebase & deploy to beta
  • Has a number of different levels of what users are allowed to do in terms of deleting their own data, setting cookie restrictions, etc.
  • Security concerns, need to rollback, things to talk about!
  • We'll need to test and then discuss what we want to allow
  • Minimal configuration would at least involve cookie management
  • Eric has agreed to get manage the initial config of this module.

How to move beta functionality onto b.org when we're ready:

  • Probably can do a commit squash to create a single PR that we then apply to b.org.
  • Open question: do we need to have the CiviCRM db moved over at the same time?

Sanitization Script

  • Current plan is to create a script that sanitizes the CIVI database and dumps it into our usual database storage location. If that does not work, we'll just try to accomodate our process to work without the Civi database for general b.org maintenance.
  • Justin has agreed to take a look at that. He has not had time yet, but will look at it tonight.

Backdrop User Profile integration with civi

Github Issue - https://github.com/backdrop-ops/backdropcms.org/issues/829

  • Tim: we only want to track information we have use for; not sure we have a use for Employer field unless we've got a directory of Backdrop workplaces
  • Tim: we have things about who's a contractor, etc, not sure we're using that data well, it's displayed on a view, quite possibly out of date. Will Civi help us keep that info up to date? Figuring out how we're using that data and whether it's part of Civi is interesting.
  • Tim: groups we might need: Newsletter, Events (notification of events); how do groups fit in with volunteer roles? If someone's saying they can do design, is that a group or...?
  • Eric: saw a discussion about CiviVolunteer, which operates on top of groups. Suggest thinking about groups for almost all of these things.
  • Consensus: most of the Backdrop fields can stay in Backdrop unless we're planning to use that specific information. We can always import that data later into Civi if we need it. (We'll already need some custom importer code, maybe?).
  • Spam: there are LOTS of spam accounts created on b.org. Those will create contacts? in Civi. What are we going to do about that? Probably a bigger issue of spam users on b.org, many of us doing it in different ways, would be helpful to have a set policy.
  • Tim volunteered to help reactivate the SPAM issue in the Backdrop CMS github issue queue. https://github.com/backdrop-ops/backdropcms.org/issues/815

Next meeting: Mon Mar 28 2022, 2-3:30pm PDT

Add a custom footer
Add a custom sidebar
Clone this wiki locally