Charles Crossan

@chiebert relating to "Properties" - Might (optionally) adding "custom properties" via a setting on the property to the fields queried by the multi-search box solve this dilemma?

Looks related to #3999

In addition to the group-per-year approach, I wonder if we could explore a type of "group action log" where additions, removals, and role-changes are persisted to the database in a...

This is not universally true. As "stone-age" as it sounds, some families still share an email address. I'm open to suggestions on how to account for this.

I propose this: - Abandon the idea of having a separate table for every group that has specific properties - Create a column in the group table. the column will...

I won't have time to build it by this Sunday though. Probably include with 2.3.0. At end of October.

It will be a db change. Should we increment to 2.3 anyway? Just sooner?

tracking this in https://github.com/ChurchCRM/CRM/tree/1092_group_specific_properties Probably won't be done by end of month though.

Have you checked that all families have been assigned lat / long coordinates?

@dleigh how does this relate to the discussion in #5174? Do any of the measures discussed there (API key restrictions, geocoding, etc) affect this scenario?