Auto-Invite to Location Based Channels on Join

[hollomancer]

Relative Priority: MEDIUM

As a user, I want to autojoin a Slack channel corresponding to my location when I join, so I know there is a local community associated with Operation Code that I can interact with.

Product Requirements

• (MVP) Users on signup who have zipcodes associated with the DC area autojoin #dc.
• (Users on signup who have zipcodes associated with the NYC area autojoin #nyc.

  Technical Requirements

• Associate groupings of zipcodes with specific slack channels.
  • Ex. #dc - 20001, 20002, 20003, 20004, 20005, 20006, 20007, 20008, 20009, 20010, 20011, 20012, 20015, 20016, 20017, 20018, 20019, 20020, 20024, 20032, 20036, 20037, 20045, 20052, 20053, 20057, 20064, 20202, 20204, 20228, 20230, 20240, 20245, 20260, 20307, 20317, 20319, 20373, 20390, 20405, 20418, 20427, 20506, 20510, 20520, 20535, 20540, 20551, 20553, 20560, 20565, 20566, 20593.
• Use geolocation based on the different areas and have each of those leaders determine how many miles is close enough.

[aaron-junot]

Let's be very specific about which city or location is the first channel

[JudsonStevens]

I think a good first step here would be to have an inventory of the currently open regional channels. From a quick scan of public channels, this is what I have:

• Austin-TX
• Boston
• Chicago
• ClevelandOhioVets
• Colorado
• Columbus_Ohio
• DC
• Deleware
• Denver
• DFW
• Florida
• Georgia
• Hartford_Western_MA
• Indiana
• Kansas_City
• Kentucky
• Los-Angeles
• Louisiana
• Maine
• Michigan
• Nashville
• Nebraska
• Nevada
• New-York
• North-Carolina
• NorthCarolina
• NYC
• OC-Midwest
• OC-Northeast
• OC-South
• OC-West
• Ohio
• Orlando
• Palo-Alto
• Pennsylvania
• Philly
• Phoenix-AZ
• Portland
• Raleigh
• Reno-Tahoe
• Sacramento
• San-Antonio
• San-Diego
• San-Francisco
• SanDiego
• Seattle
• Texas
• Utah
• Vegas

Now I don't believe this excludes archived channels, so some of them could be archived. I think we should have Alex take a look at these and see which ones are relatively active - maybe at least 5 messages in 3 months? That will give us an idea as to what we already have and where to funnel folks.

For current users, I think we could have the bot send a direct message to anyone not already in their regional channel - so essentially get the zip codes from our DB, parse them for all current users, and then send DMs for users not in those channels.

For future users, I think having an Airtable table set up to have regions and associated zip codes will allow us to place them where needed.