>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3577358. --> Reported by: [jdleonard](https://www.drupal.org/user/80902) >>> <h2>0&#65039;&#8419; Who is here today? Please post your <a href="http://Drupal.org">Drupal.org</a> username if you have one. We provide issue credit for those contributing to the meeting beyond this thread. Especially if this is your first meeting, please mention a club, association, meetup group, non-profit or other membership organization (MO) you think could benefit from this initiative and/or tell us why you&rsquo;re joining us.</h2> <table> <tr> <td>mradamjohn</td> <td>Here. MrAdamJohn</td> </tr> <tr> <td>Scott Wolpow</td> <td>Present Scott Wolpow (scottwolpow)</td> </tr> <tr> <td>paulmckibben</td> <td>paulmckibben - lurking as usual!</td> </tr> <tr> <td>jdleonard</td> <td>JD Leonard (jdleonard), Zilker Neighborhood Association</td> </tr> <tr> <td>Steve Ayers</td> <td>bluegeek9</td> </tr> <tr> <td>svendecabooter</td> <td>svendecabooter</td> </tr> <tr> <td>James Shields</td> <td>lostcarpark - sorry I haven't been very involved lately.</td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>Bob Snodgrass (bsnodgrass) Fox Valley Drupal Chicago area</td> </tr> <tr> <td>mradamjohn</td> <td>We all can only do what we can do, @James Shields&nbsp; ... Decades of working with volunteers and I'll say this - we all go through what I call "ebbs and flows" where we want or can only do so much or even can't do anything in something we still genuinely care about. It's okay. The best organizations find ways to let that happen with warmth and resilience. You're always welcome here as long as I'm around, and I'm sure others feel the same. :wink: Do what you can, no problem. Thanks for being here!</td> </tr> </table> <h2>1&#65039;&#8419; Please open your own thread in the next numeric order to start a discussion on a topic/track. Or, reply to this thread and I'll do it.</h2> <table> <tr> <td>mradamjohn</td> <td>Can you do one on my track please JD ty</td> </tr> </table> <h2>2&#65039;&#8419; Catching up on past meetings</h2> <table> <tr> <td>jdleonard</td> <td>I'll post the past meetings' notes and recordings here shortly</td> </tr> <tr> <td>jdleonard</td> <td><a href="https://www.drupal.org/project/member/issues/3570707">https://www.drupal.org/project/member/issues/3570707</a></td> </tr> <tr> <td>jdleonard</td> <td><a href="https://www.drupal.org/node/3570708">https://www.drupal.org/node/3570708</a></td> </tr> <tr> <td>jdleonard</td> <td><a href="https://www.drupal.org/project/member/issues/3577339">https://www.drupal.org/project/member/issues/3577339</a></td> </tr> </table> <h2>3&#65039;&#8419; Work on CRM Membership. We should start creating issues in the crm_membership issue queue.</h2> <table> <tr> <td>Steve Ayers</td> <td>I want to plan our first alpha release.</td> </tr> <tr> <td>mradamjohn</td> <td>So, architecture and approach question here... Do we put some basic essential (member profile member directory) form elements or settings into an independent module or does it really fit somewhere here (crm_membership) a bit better "for now" while things start to take shape, we gain contributors, and continue producing working useful code...?</td> </tr> <tr> <td>mradamjohn</td> <td>My thinking is here - for now, if that wasn't obvious.</td> </tr> <tr> <td>jdleonard</td> <td>I think the scope of CRM Membership is probably limited to representing/tracking/managing memberships themselves.</td> </tr> <tr> <td>jdleonard</td> <td>Here's the link to the CRM Membership project so folks can find the issue queue... <a href="https://www.drupal.org/project/crm_membership">https://www.drupal.org/project/crm_membership</a></td> </tr> <tr> <td>jdleonard</td> <td>I would expect there to be at least one additional module that covers member directory</td> </tr> <tr> <td>Steve Ayers</td> <td>Could the Membership Directory ond the Office Directory be the same code?</td> </tr> <tr> <td>mradamjohn</td> <td>Fair, JD. The functional element here, and I've probably cycled on this more than most, is that management of a member may include decisions on whether, when, and how they appear in a directory. Whether they can opt out of a directory, what they can do with a directory entry and so forth. There is something to the relationship. We can keep it light, if needed, but I have gone a bit further in this than the public information might suggest ... I see synergy.</td> </tr> <tr> <td>mradamjohn</td> <td>Steve, Office Directory.. help me understand that? I get what it is IRL but not having seen a reference in these projects if there is one not sure what you mean. Highest level as a directory use case? Yes I see that.</td> </tr> <tr> <td>Steve Ayers</td> <td>People have talked to me about a Directory in a corporate sense. These employees are in this office/region. (edited)</td> </tr> <tr> <td>mradamjohn</td> <td>Reading that as be=me and corerate=corporate ... If I'm understanding that correctly then yes I think there's a strong use case here that is well worth prioritizing.</td> </tr> <tr> <td>svendecabooter</td> <td>re. the initial topic: I have added some issues into the CRM membership queue that I had added to the README.md earlier. Not all might be relevant for a first release.&nbsp; Might pick up a few of those if I find some time</td> </tr> <tr> <td>jdleonard</td> <td>Suggest we move discussion of directories over to the Member profile and directory thread 4&#65039;&#8419; (edited)</td> </tr> <tr> <td>mradamjohn</td> <td>There is already a different conversation there on directories JD, that might confuse things. It fits natively here until at least Steve says I can't put some basic MPMD stuff in this module...</td> </tr> <tr> <td>mradamjohn</td> <td>:grin:</td> </tr> <tr> <td>jdleonard</td> <td>I'll defer</td> </tr> <tr> <td>jdleonard</td> <td>Office directory is an interesting use case that I had not encountered before in this context. It's clearly not required for Member Platform, but I could see it building on top of a relevant CRM relationship type in an analogous way. That is to say, perhaps there are some common requirements for office directory and member directory.</td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>:eyes:</td> </tr> <tr> <td>mradamjohn</td> <td>Bob, if you have any perspective on the thread at all please let me know. I always think it's a good idea to think about things from a variety of perspectives when afforded the opportunity. :grin:</td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>Generally I think the directory listing should be able to serve both Office directory and Member directory.</td> </tr> <tr> <td>Steve Ayers</td> <td>From a code perspective, what in the directory?a Views plugin, display plugin I think?a controller that returns markup?</td> </tr> </table> <h2>4&#65039;&#8419; Member profile and directory</h2> <table> <tr> <td>mradamjohn</td> <td>Great, folks! There's a post or two earlier in this thread and an update on the <a href="http://drupal.org">drupal.org</a> issue. I'll pull things together in a bit, but between them there are open questions to kick around if anyone has input, and some decisions that are being finalized to help us move forward.</td> </tr> <tr> <td>Nico Grienauer</td> <td>should/could we think of this as a recipe, so also e.g. <a href="https://www.drupal.org/project/la_eu">https://www.drupal.org/project/la_eu</a> can use it?</td> </tr> <tr> <td>Nico Grienauer</td> <td>for local drupal association websites we would need profile page, and a taxonomy with e.g. member 2023, member 2024 etc is avalable, to mark the members and their member status (like badges)</td> </tr> <tr> <td>Nico Grienauer</td> <td>e.g. our member profiles and listing: <a href="https://www.drupal-austria.at/community/benutzer">https://www.drupal-austria.at/community/benutzer</a></td> </tr> <tr> <td>jdleonard</td> <td>@Nico Grienauer Would love to meet la_eu's needs as part of this. Can you elaborate on why that would need a recipe (as opposed to a module)?</td> </tr> <tr> <td></td> <td>My neighborhood association (NA) currently similarly tracks each person's annual membership status using a tag e.g. "Member 2026" (not in Drupal). The CRM Membership module will offer a more robust mechanism for tracking memberships and I'd plan on adopting that for my NA. I see member directory functionality being built on top of CRM Membership's representation of memberships.</td> </tr> <tr> <td>mradamjohn</td> <td>@Nico Grienauer, I love how you're thinking about this from several angles. I'm interested in your answer to JDs question and would add that I need time to digest what you posted but I'm loving the opportunity to move forward smartly. (edited)</td> </tr> <tr> <td>mradamjohn</td> <td>@jdleonard I agree that ultimately there's a module here that depends on crm_membership ... Just not sure it should be on its own yet.</td> </tr> <tr> <td>Nico Grienauer</td> <td>I am not sure if it should be a module or recipe.has pros and cons.I am not here to decide this&hellip; but I can hlep in identifying what features woudl be great to have.I will put taht on the table for our next la_eu meeting.</td> </tr> <tr> <td>mradamjohn</td> <td>When is the next meeting, Nico? I might entertain attending if it's virtual and fits my schedule.</td> </tr> <tr> <td>svendecabooter</td> <td>I had already pitched using crm &amp; crm_membership for the la_eu project... but it's difficult to get alignment on the specs that each local association wants in their shared codebase. Also it felt a bit too early to adapt the CRM modules. Maybe in a month or 2 that could be different</td> </tr> <tr> <td>svendecabooter</td> <td>13 march 14h Brussels time</td> </tr> <tr> <td>mradamjohn</td> <td>Can we circle up on the construction of the organization at some point @svendecabooter? I need to dig into this as well, as it will help figure out an "on ramp" if it's time for this to start happening with those groups.</td> </tr> <tr> <td>jdleonard</td> <td>IMO it would be great for both CRM and the various camps for la_eu to contribute to this effort and to help shape the projects to meet la_eu's needs.</td> </tr> <tr> <td>mradamjohn</td> <td>I'm willing to help explore that with Sven and whomever else JD :wink:</td> </tr> <tr> <td>svendecabooter</td> <td>You can join #la_eu and / or ping @Esmeralda who is product owner of the initiative</td> </tr> <tr> <td>svendecabooter</td> <td>You can ping me as well obviously since I'm involved a bit here and with la_eu for <a href="http://Drupal.be">Drupal.be</a> site</td> </tr> <tr> <td>Nico Grienauer</td> <td>therefore I think a recipe is a good approach, as it is then a first shot and can be edited easily&hellip; module is more fixed set in my opinion. recipe more sitebuilder -&gt; go for it.</td> </tr> <tr> <td>James Shields</td> <td>Love the Drupal Austria member directory! Is that a view? Am I the only one who finds it slightly annoying that 25 and 26 are out of order. I'm guessing there's no ordering on the years lookup.</td> </tr> <tr> <td>Nico Grienauer</td> <td>yes. it is a view. and yes it needs more love and it annoyed me also yesterday, when looking on it. but I don't want to spend time here and replace this site ASAP &#128578;</td> </tr> <tr> <td></td> <td>also all the buttons are too much and shold be consolidated</td> </tr> </table> <h2>5&#65039;&#8419; Event management / event registration</h2> <table> <tr> <td>jdleonard</td> <td>@richgerdes[#3502148]#comment-16497788</td> </tr> <tr> <td>richgerdes</td> <td>Hey, let's find a time to catch up on mp stuff. I've had a conflict with the weekly meeting time the last few weeks, so i haven't been able to chat much</td> </tr> <tr> <td>jdleonard</td> <td>@richgerdes (and others interested) How's Tuesday 3pm CT? (edited)</td> </tr> <tr> <td>richgerdes</td> <td>I have a meeting then, might be able to get out of it if that's the best time</td> </tr> <tr> <td>jdleonard</td> <td>Tuesday 11am CT?</td> </tr> <tr> <td>richgerdes</td> <td>Also not great. Its a meeting with the same team, so i can probably skip that one</td> </tr> <tr> <td>jdleonard</td> <td>How about sometime Wednesday 10:30-3:30 CT?</td> </tr> <tr> <td>jdleonard</td> <td>@richgerdes</td> </tr> <tr> <td>richgerdes</td> <td>Sorry yeah, was a crazy weekend. I can do 12:30 ET/11:30 CT, if that works for you</td> </tr> <tr> <td>jdleonard</td> <td>Sounds good! Meeting tomorrow, March 11, for those interested in events in CRM and Member Platform! 11:30am CDT. Send me a DM for a meeting invite or just join at the right time: <a href="https://us06web.zoom.us/j/87913019124?pwd=CY5ewkEaaNBjJlBz29AJxH83AoEzym.1&amp;jst=2">https://us06web.zoom.us/j/87913019124?pwd=CY5ewkEaaNBjJlBz29AJxH83AoEzym.1&amp;jst=2</a></td> </tr> <tr> <td>richgerdes</td> <td>Great! I should also be able to join this weeks weekly, but it will be good to chat about events directly outside of that</td> </tr> <tr> <td>Scott Wolpow</td> <td>Are we not meeting on Thursday?</td> </tr> <tr> <td>jdleonard</td> <td>Yes we are. This is an additional focused meeting.</td> </tr> <tr> <td>Scott Wolpow</td> <td>is this for people who are onboarding</td> </tr> <tr> <td>jdleonard</td> <td>Today's is for anyone with an interest in contributing to the events track.</td> </tr> <tr> <td>Scott Wolpow</td> <td>Nothing new for me to contribute</td> </tr> </table> <h2>6&#65039;&#8419; Composing/sending emails to members</h2> <table> <tr> <td>Steve Ayers</td> <td>I think CRM can send one off emails relying on the mail handle configured for the site.I have concerns about sending bulk emails. I am not sure where to start.</td> </tr> <tr> <td>Steve Ayers</td> <td>For bulk emails, there a few requirements.Bounce processing.Global block list for bounced and other reasonsUnsubscribe processing</td> </tr> </table> <h2>7&#65039;&#8419; Wireframes / mockups</h2> <table> </table> <h2>8&#65039;&#8419; Documentation</h2> <table> <tr> <td>Steve Ayers</td> <td><a href="https://www.drupal.org/docs/extending-drupal/contributed-modules/contributed-module-documentation/crm-contact-relationship-management">https://www.drupal.org/docs/extending-drupal/contributed-modules/contributed-module-documentation/crm-contact-relationship-management</a></td> </tr> </table> <h2>9&#65039;&#8419; CRM (generally)</h2> <table> <tr> <td>bsnodgrass (he/him)</td> <td>@Steve Ayers successfully tested an import using his module for OnePageCRM import into CRM while at FLDrupalCamp</td> </tr> <tr> <td>jdleonard</td> <td>Had a brief discussion with Steve about translatability of Contacts and Relationships. Currently Contact and Relationship entities are not translatable. While most use cases would have no need to translate Contact or Relationship data, it's conceivable that someone might add a "Biography" field or similar to a Contact and want to translate it. Does anyone here have such a use case? Default posture is to not make Contacts and Relationships translatable until there is demand.</td> </tr> <tr> <td>jdleonard</td> <td>Also notable:<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-8"><a href="https://www.drupal.org/project/crm/issues/3577342" title="Status: Needs review">#3577342: Contact Profile (crm_contact_profile)</a></span></td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>I do have a project with translations and a proposed addition to add CRM to intake people and organizations from a Woo Commerce subscription. It&rsquo;s a little too early in the process for details, they are still determining their scope. when we get closer, I&rsquo;ll be pinging @Steve Ayers</td> </tr> <tr> <td>Bluegeek9</td> <td>I think for the next couple of weeks my focus will be on migrations. It is good to have migration paths, but more importantly I am discovering bugs, and missing features.</td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>Re: Translations - I have a project that translations for the user interface. I don&rsquo;t believe those are currently translatable, is that correct?</td> </tr> <tr> <td>Steve Ayers</td> <td>The interfaces should be translatable, but the content is not translatable.</td> </tr> </table>