>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3542789. --> Reported by: [jdleonard](https://www.drupal.org/user/80902) >>> <h2>0&#65039;&#8419; Who is here today? Please post your Drupal.org 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>beautifulmind</td> <td>Beautifulmind</td> </tr> <tr> <td>Lee Walker (mr_scumbag)</td> <td>Lee Walker (mr_scumbag)</td> </tr> <tr> <td>jdleonard</td> <td>JD Leonard (jdleonard). Austin DUG</td> </tr> <tr> <td>James Shields</td> <td>James (lostcarpark) from Ireland</td> </tr> <tr> <td>paulmckibben</td> <td>Paul (paulmckibben) - Atlanta DUG</td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>Bob Snodgrass (bsnodgrass) here from St Charles IL US</td> </tr> <tr> <td>estevenson</td> <td>Erica Stevenson (speckles)</td> </tr> <tr> <td>mandclu</td> <td>Martin (mandclu) from :canada:</td> </tr> <tr> <td>jdleonard</td> <td>If anyone wants to try their hand at items to show in mockups, threads await!</td> </tr> <tr> <td>mandclu</td> <td>Do we need one for admin RSVP on behalf of a CRM contact?</td> </tr> <tr> <td>jdleonard</td> <td>That might be covered by "Manage RSVPs flow (for Organizers)"</td> </tr> <tr> <td>Steve Ayers</td> <td>Steve (bluegeek9)</td> </tr> <tr> <td>Nico Grienauer</td> <td>Nico Grienauer (grienauer) Drupal-Austria</td> </tr> </table> <h2>1&#65039;&#8419; Do you have any topics to propose for the meeting today? Open your own thread in the next numeric order or reply to this thread and I'll do it.</h2> <table> <tr> <td>estevenson</td> <td>Would it make sense to touch on unit testing?Since I&rsquo;ve now got a list of things that need testing in my PR, my next goal is to start turning some of them into unit tests.I&rsquo;m not sure if that actually needs discussion though, or just me googling best Drupal practices then submitting something for review</td> </tr> <tr> <td>jdleonard</td> <td>@estevenson Yeah I think you could just submit something for review!</td> </tr> <tr> <td>estevenson</td> <td>Okay, I&rsquo;ll try diving in and ask if I get stuck</td> </tr> </table> <h2>2&#65039;&#8419; Mockups! I'll be opening a thread for each page/flow for which a mockup would be useful to seek feedback on what things should be on each page/flow. This will serve as input for @Bee Low who has volunteered to create mockups for each, similar to those he shared last Thursday. Please use this thread for any high-level discussion on mockups and add feedback on the lists of items for each mockup in the respective threads.&nbsp;(edited)&nbsp;</h2> <table> </table> <h2>3&#65039;&#8419; Mockup: Navigation. Not a page or flow, but presumably some navigation elements are necessary and it would be helpful to know what that might look like.</h2> <table> <tr> <td>jdleonard</td> <td>Links to:Landing PageMember DirectoryEvents page (TBD calendar or list)My profile (Member profile page for current user)Manage group (for Organizers)</td> </tr> <tr> <td>James Shields</td> <td>Is it too early to consider what it will look like for users with different privileges?</td> </tr> <tr> <td>jdleonard</td> <td>Not too early! For this thread I was only considering a Member Platform-specific navigation element. I figure Organizer-oriented navigation might live in the admin menu, but open to ideas!</td> </tr> <tr> <td>James Shields</td> <td>Could we make use of a Drupal CMS style dashboard?</td> </tr> <tr> <td>James Shields</td> <td>Oh, you've got that on landing page!</td> </tr> </table> <h2>4&#65039;&#8419; Mockup: Landing page / homepage / dashboard.</h2> <table> <tr> <td>jdleonard</td> <td>Group nameGroup descriptionGroup photoGroup links (e.g. social links)Button or form to join (if logged out)Button or form to leave (if logged in)List of X upcoming events (cards)Count of upcoming eventsLink to List of Events page (filtered to upcoming)List of X past events (cards)Count of past eventsLink to List of Events page (filtered to past)List of X membersCount of members</td> </tr> <tr> <td>jdleonard</td> <td>On a site with just Member Platform installed, its home page / front page would be this.</td> </tr> <tr> <td>jdleonard</td> <td>For inspiration...</td> </tr> <tr> <td>paulmckibben</td> <td>This list looks good to me. Using meetup as a guide makes sense for this first iteration.</td> </tr> <tr> <td>James Shields</td> <td>Looks good.I think for MVP, we're considering membership for one organisation.Later on me wight support multiple organisations.So it might be not as simple as logged in/out to determine whether Join/Leave are shown.</td> </tr> <tr> <td>jdleonard</td> <td>Sounds like a problem for future us &#128578;</td> </tr> </table> <h2>5&#65039;&#8419; Mockup: Join flow</h2> <table> <tr> <td>jdleonard</td> <td>Starting on landing page.</td> </tr> <tr> <td>jdleonard</td> <td>Only applicable for non-logged in users.</td> </tr> <tr> <td>jdleonard</td> <td>Field: email address (required)Field: name (required)Submit button</td> </tr> <tr> <td>jdleonard</td> <td>The above feels like the bare minimum for 1.0. More flexible would be to let an Organizers choose which fields (beyond email) on the Person Contact Type should be exposed on the join form and whether each should be required or optional. Thoughts?</td> </tr> <tr> <td>paulmckibben</td> <td>I agree - keep it simple for now.</td> </tr> <tr> <td>James Shields</td> <td>Something to consider is do we want to consider user/contact/member as having a 1:1 relationship,Could I be logged in, but not be a member?</td> </tr> <tr> <td>jdleonard</td> <td>For 1.0, we've said that any person registering on the site (joining) is a member and that when they leave, their account is cancelled such that they can't log in any more.</td> </tr> <tr> <td>jdleonard</td> <td>Presumably we need to support non-member admin Users</td> </tr> <tr> <td>jdleonard</td> <td>And we've said we'd support Members who don't have an associated User ("Offline Members"</td> </tr> </table> <h2>6&#65039;&#8419; Mockup: Leave flow</h2> <table> <tr> <td>jdleonard</td> <td>Button on landing page (and perhaps Member Profile Edit Page) triggers a modal window.</td> </tr> <tr> <td>jdleonard</td> <td>"Are you sure" explanatory languageRed "Delete account" button</td> </tr> <tr> <td>James Shields</td> <td>If I leave, what actually gets deleted?I would assume that we want some record that I was a member.Does contact get deleted? What about user?</td> </tr> <tr> <td>James Shields</td> <td>For EU and other countries with GDPR or similar, we probably do want a process to delete all information about a member.</td> </tr> <tr> <td>jdleonard</td> <td>Agreed!</td> </tr> </table> <h2>7&#65039;&#8419; Mockup: Member directory page</h2> <table> <tr> <td>jdleonard</td> <td>View listing members, depending on privacy preferences.</td> </tr> <tr> <td>jdleonard</td> <td>Each item has:Profile picture (could be a default pic)NameJoin dateClicking name or picture navigates to Member Profile Page</td> </tr> <tr> <td>James Shields</td> <td>Sounds good for 1.0.</td> </tr> <tr> <td>James Shields</td> <td>Something that would be nice to have later on would be a way of marking members as "friends".</td> </tr> <tr> <td>James Shields</td> <td>My friends would appear at the top when I view the member directory.</td> </tr> <tr> <td>James Shields</td> <td>Might also have filter criteria for member directory page.</td> </tr> <tr> <td>jdleonard</td> <td>Great ideas!</td> </tr> </table> <h2>8&#65039;&#8419; Mockup: Member profile page</h2> <table> <tr> <td>jdleonard</td> <td>Profile picNameJoin dateTags (that are public)Bio/AboutLink/button to edit profile (for logged in user's profile)Link/button to compose an email (for Organizers)(edited)</td> </tr> <tr> <td>jdleonard</td> <td>How should we handle additional fields added to the Person Contact Type?</td> </tr> </table> <h2>9&#65039;&#8419; Mockup: Member profile edit page</h2> <table> <tr> <td>jdleonard</td> <td>Fields:NameEmail addressBioProfile pic(other fields added to Person Contact Type)</td> </tr> </table> <h2>1&#65039;&#8419;0&#65039;&#8419; Mockup: Calendar of events page</h2> <table> </table> <h2>1&#65039;&#8419;1&#65039;&#8419; Mockup: List of events page</h2> <table> </table> <h2>1&#65039;&#8419;2&#65039;&#8419; Mockup: Event detail page</h2> <table> </table> <h2>1&#65039;&#8419;3&#65039;&#8419; Mockup: RSVP flow (non-member)</h2> <table> </table> <h2>1&#65039;&#8419;4&#65039;&#8419; Mockup: RSVP flow (member)&nbsp;(edited)&nbsp;</h2> <table> </table> <h2>1&#65039;&#8419;5&#65039;&#8419; Mockup: Member add page (for Organizers)</h2> <table> <tr> <td>estevenson</td> <td>I wonder if it&rsquo;s worth looking at how Apple lets people add relationships in their contacts app.Aka: <a href="https://appleinsider.com/inside/ios-16/tips/how-to-add-relationships-to-contacts-in-ios-16">https://appleinsider.com/inside/ios-16/tips/how-to-add-relationships-to-contacts-in-ios-16</a></td> </tr> <tr> <td>jdleonard</td> <td>Probably! For Member Platform 1.0, we haven't identified tracking relationships as in scope. We haven't yet discussed what CRM functionality to expose vs. hide for Member Platform 1.0. There is a desire to keep things simple, but also to offer powerful features. I'm sure relationships would come into scope post 1.0.</td> </tr> <tr> <td>estevenson</td> <td>Yeah, something like automatically creating an Organization for the site, then creating a Member relationship as part of user creation for version 1.0 seems like a good approach to me. An MVP event platform doesn&rsquo;t need to have complicated relationship options.</td> </tr> <tr> <td>jdleonard</td> <td>Agreed.</td> </tr> </table> <h2>1&#65039;&#8419;6&#65039;&#8419; Mockup: Event add/edit page (for Organizers)</h2> <table> </table> <h2>1&#65039;&#8419;7&#65039;&#8419; Mockup: Manage RSVPs flow (for Organizers)</h2> <table> </table> <h2>1&#65039;&#8419;8&#65039;&#8419; Mockup: Manage members page (for Organizers)</h2> <table> </table> <h2>1&#65039;&#8419;9&#65039;&#8419; Mockup: Email members form (for Organizers)</h2> <table> </table> <h2>2&#65039;&#8419;0&#65039;&#8419; Mockup: Email template management (for Organizers)</h2> <table> <tr> <td>jdleonard</td> <td>Two types of templates that Organizers need to be able to customize:Standard templates (e.g. email automatically sent when member joins/leaves/RSVPs/etc.)Custom templates (e.g. to save typing when composing an email to a set of members)Arguably custom templates are not in 1.0 scope.</td> </tr> <tr> <td>mandclu</td> <td>Personally I would recommend looking at the Easy Email ecosystem, including the <a href="https://www.drupal.org/project/easy_email_express">Express recipe</a> that is now part of Drupal CMS</td> </tr> <tr> <td>jdleonard</td> <td>Thanks @mandclu! This has been brought up before and I suspect we might use Easy Email.</td> </tr> </table> <h2>2&#65039;&#8419;1&#65039;&#8419; Event registration. I met with @mandclu last week and he recommended that we analyze the <a href="https://www.drupal.org/project/registration">Entity Registration</a> module for opportunities to extend it so that registration can be of CRM Contacts (not just Users) and open an issue in the queue there with a proposal. Anyone game to dig in?</h2> <table> </table> <h2>2&#65039;&#8419;2&#65039;&#8419; There's some discussion here about theming and how Event Platform and Member Platform might make it easy on an organizer who wants to use both projects. Seeking additional thoughts there please!</h2> <table> <tr> <td>mandclu</td> <td>There is already a <a href="https://www.drupal.org/project/event_horizon/issues/3516915">relevant issue</a> on the Event Horizon issue queue, so please comment on that with any additional input too</td> </tr> </table>