search

codeformilwaukee / hack-night-planning

Hack Night Planning Repository
0 stars 1 forks source link

Devise a way for Brigade members to know they are members #124

Open Aycrazy opened 4 years ago

Aycrazy commented 4 years ago

And decide when exactly they can consider themselves a member. What privileges does membership afford for starters, as well

erinmagennis commented 4 years ago

Here's how Chicago does it: https://chihacknight.org/membership/application.html

mitchellhenke commented 4 years ago

Important to note that Chicago is not a Code for America brigade. Would be curious if other brigades have some processes for it or not.

anthonyjesmok commented 4 years ago

I know we had a few ideas come up in the past:

  1. Use a CRM (Constituent Relationship Management) system to track our member base across a variety of platforms (Meetup, Facebook, etc.) and also to track activities, project leadership, attendance, etc.
  2. Issue membership cards to qualified members. I proposed using barcodes on the membership card that are scanned for quick check-in and also could be linked to an automated process to log records in the CRM for attendance.
  3. Have the definition of a full member be someone who is engaged and has shown demonstrable contributions to at least one project. Those simply coming for the talk or not engaging are marked as "Guests" instead.
mitchellhenke commented 4 years ago

I think tracking people’s attendance and activity at that level of detail is deserving of further thought before starting any effort on it.

What are our goals in starting a membership system?

erinmagennis commented 4 years ago

In the meantime for any system, I could use some help with ushering people to get signed in. I think I am at ~80% check in rate (which obviously could be improved), but it's been challenging to try to engage with people when they are signing in and make them feel welcome, meanwhile, trying to flag down the new people coming in.

anthonyjesmok commented 4 years ago

Our goals of a membership system would be to maintain a central database to track who attends our events, no matter what channel they come from (word of mouth, Meetup, Facebook, newspaper, etc.) This would allow us to maintain a central database, beyond a Google Sheet, for marketing purposes. This system could later be used to off-shoot other initiatives or systems, like one for project management.

BarkleyBG commented 4 years ago

@anthonyjesmok do you know of any examples of a database system or toolkit that we could use for this?

Aycrazy commented 4 years ago

@romkedehaan likes airtable :)