Funder and hunter personas in user profile, sync personas to individual mailchimp lists

[danlipert]

Description

This PR adds two additional boolean values to user profiles, whether a user is a bounty hunter, and/or a bounty funder. In addition, a migration is added that sets these flags for each user. The SQL query is used directly to maintain compatibility between the query used here and the query used on Metabase created by @frankchen07 . Also, two endpoints are created to export these lists easily for mailing list purposes. The hunter and funder flags are set daily via cronjob for all users.

The hunter and funder flags are only set to true for a given user if the SQL query lists the user as active.

The different personas are then synced to 3 new mailchimp audiences on the new mailchimp account: one for funders, one for hunters, and one for everyone.

Refers/Fixes

#4415

Testing

Tested persona assignment locally by applying migration manually and checking the export endpoints. Mailchimp integration tested via unit test.

[codecov]

Codecov Report

Merging #4481 into master will decrease coverage by 0.01%.
The diff coverage is 25%.

@@            Coverage Diff             @@
##           master    #4481      +/-   ##
==========================================
- Coverage   30.08%   30.07%   -0.02%     
==========================================
  Files         209      211       +2     
  Lines       16850    16873      +23     
  Branches     2267     2270       +3     
==========================================
+ Hits         5070     5075       +5     
- Misses      11582    11600      +18     
  Partials      198      198

Impacted Files	Coverage Δ
...dashboard/management/commands/set_user_personas.py	0% <0%> (ø)
app/dashboard/sql/persona.py	100% <100%> (ø)
app/dashboard/models.py	56.29% <31.25%> (-0.28%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d59ae5c...ba33bbc. Read the comment docs.

[codecov]

Codecov Report

Merging #4481 into master will increase coverage by 0.13%.
The diff coverage is 50.94%.

@@            Coverage Diff             @@
##           master    #4481      +/-   ##
==========================================
+ Coverage    30.3%   30.44%   +0.13%     
==========================================
  Files         214      216       +2     
  Lines       17142    17442     +300     
  Branches     2319     2362      +43     
==========================================
+ Hits         5195     5310     +115     
- Misses      11740    11926     +186     
+ Partials      207      206       -1

Impacted Files	Coverage Δ
app/app/urls.py	89.36% <ø> (ø)	⬆️
...dashboard/management/commands/set_user_personas.py	0% <0%> (ø)
app/app/settings.py	78.81% <100%> (+0.15%)	⬆️
app/dashboard/sql/persona.py	100% <100%> (ø)
app/dashboard/models.py	56.39% <26.31%> (+0.13%)	⬆️
app/dashboard/views.py	14.43% <33.33%> (+0.11%)	⬆️
app/marketing/management/commands/sync_mail.py	29.16% <94.44%> (+29.16%)	⬆️
app/grants/templatetags/grants_extra.py	71.42% <0%> (-28.58%)	⬇️
app/grants/models.py	49.67% <0%> (-8.89%)	⬇️
app/economy/models.py	56.34% <0%> (-2.07%)	⬇️
... and 7 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0955aff...4263b6c. Read the comment docs.

[frankchen07]

Thanks for the hard work on this @danlipert.

1. This is the statement that I would revise: The hunter and funder flags are only set to true for a given user if the SQL query lists the user as active.

I would modify this with the flags are set to true if a funder has ever funded an issue / performed a funder action, and a bounty hunter has ever done work on an issue / performed a bounty hunter action. If we set them to true only if they're active, we miss out on emailing bounty hunters and/or funders who have done something but not in the last 3 months. I'm assuming with how it stands now, "not active funder/bounty hunters" are labeled as users?

I've coded up that broader definition of designation here: https://metabase.gitcoin.co/question/423

2. Because this runs on a cron job, I'm seeing the possible path that a user can only become bounty hunter or funder, but never can revert back to just "user" (if we use the logic in the metabase question above). That's also a point of contention if we use "active" set to true - that means bounty hunters and funders could potentially become "users" again if they fall inactive, which we don't want.

Lemme know if these make sense, and if you're able to access that Metabase question.

[danlipert]

@frankchen07 Correct, this would only classify you as a given persona if you were active in the last three months. I will change this to use the updated metabase question so that bounty_hunter has persona_is_hunter set to True, and funder has persona_is_funder set to True. Once a given user is marked as a hunter or funder, then they won't later be have these persona flags removed.

[frankchen07]

@danlipert - also, Alisa made a good point to make sure that the github handles are also in mailchimp, since when we send it out, we'll be using their handle to address them. I'm not sure if it's already in there, but the updated SQL query also has a handle listed.

[frankchen07]

@danlipert - sorry caught one small change on metabase yesterday: https://metabase.gitcoin.co/question/423

line 120 - changed to db.web3_created created_on, instead of db.created_on,

[thelostone-mc]

codewise lgtm but could you shed some info on the query ?
might be worth to document it in the file itself ?

[danlipert]

@danlipert - also, Alisa made a good point to make sure that the github handles are also in mailchimp, since when we send it out, we'll be using their handle to address them. I'm not sure if it's already in there, but the updated SQL query also has a handle listed.

Isn't the github handle out of scope for this ticket? It can be added at some point (as a first name, or something else) but I want to make sure this change is in sync with the other related tickets, such as @octavioamu 's. We haven't been capturing this previously in mailchimp. @PixelantDesign @frankchen07

[octavioamu]

Tested locally working fine!!

will get this in as separate PR if needed