Membermatters: Difference between revisions

 
(16 intermediate revisions by the same user not shown)
Line 15: Line 15:
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we also need to edit frontend/src/i18n/en-AU/index.ts to change "mobile number" to "Phone Number (or X)" (it builds to /usr/src/app/frontend/dist/spa/assets/index.*.js )
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* we are working on mounting the docker image with git on the server, so we can make changes to production and try them
* RechnerFox setup a staging instance for us!
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork
* we should set up a schedule for rebasing in changes from upstream, then shoving our changes back on top. then we can deploy to docker directly from our github fork


Line 41: Line 42:
# 'echo "MM_ENV=Development" > ./docker/.env`  - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# 'echo "MM_ENV=Development" > ./docker/.env`  - I am not sure if this needs to go into the docker directory, or just exist? .env files are .gitignored anyway, but it looks like this is used by docker to set some environment vars in the docker-compose.yml
# `cd ./docker`
# `cd ./docker`
# `docker pull` (this make take a while)
# `docker compose pull` (this make take a while)
# `docker compose up -d` to start your docker image
# `docker compose up -d` to start your docker image
# `docker ps` will list your running containers processes that are created by the docker yaml file
# `docker ps` will list your running containers processes that are created by the docker yaml file
Line 65: Line 66:
Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.
Site Logo worked! Martin and Nicholas poked around more with it, and the favicon doesn't seem to be used anywhere except emails? But doing a rectangular image for the logo works! It's one of the logos from the wiki - possible we should switch it to a WP upload for speed, not sure how much that matters.


== Currently ( 2026-02-07 ) ==
== Currently ( 2026-06-04 ) ==
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps
Martin added two payment plans and tested one and put in his card and it worked! Got an email and got to next steps
Ivan signed up, paid, and got to the post-signup page
Julio signed up, paid, and go to the post-signup page
= Membership Plan Setup =
= Membership Plan Setup =
== Adding a Membership Payment Plan ==
== Adding a Membership Payment Plan ==
Line 93: Line 99:
* Inactive / Active -> Supporter
* Inactive / Active -> Supporter
* Inactive / Inactive -> Former Member
* Inactive / Inactive -> Former Member
=== Membermatters-related workflow ===
# User submits Intent to join form
# User creates an account / signs up on member matters. They land on a 'Contact Us' page for next steps - Membership Status: noob. Subscription Status: inactive
# User adds payment info to member matters and selects a payment plan - Membership Status: noob. Subscription Status: active
# User gets 3 endorsements achieved. Membership Status: noob. Subscription Status: active
# Current members have next member meeting, check for new forms, review Taiga.
6. For any members that meet all reqs, to make them a member:
* [[add them to members mailing list]]
* reply to their request form email that they have met reqs and are a member (this lets existing members know)
* on MM in the frontend, go to Admin Tools >Signup Progress > click on SomeUser. (Can also see via Admin Tools > Members, Filter - All > click on SomeUser) Click the Make Member button. This sets their Membership Status in MM to active, and sends the Welcome Email.
* [[get them door access]]
7. User is a member!


=== I want to become a member!! Onboarding Steps ===
=== I want to become a member!! Onboarding Steps ===
Line 110: Line 135:


=== Need to Setup, Immediate Actions ===
=== Need to Setup, Immediate Actions ===
# Set up membership tiers
# Set up membership tiers - done? we only have one
# Set up payment plans
# Set up payment plans - also done, mirroring the ones on sudohumans


=== Pain points: We need to fix these issues ... later ===
=== Pain points: We need to fix these issues ... later ===
Line 118: Line 143:
# ''members can see each others activities on member matters''
# ''members can see each others activities on member matters''
# ''update welcome and alert emails''
# ''update welcome and alert emails''
# ''updating the amount someone is paying requires an admin to change it in django, there's no way for a user to do that, and also no corresponding vue card in the frontend''


= TODO =
= TODO =
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Contact Info (Constance Config) - some of that is still membermatters / defaults (notably the email!)
# '' Where's the place to change the Membership Plan Tier? Martin tried to do this and didn't find an easy way to do it
# '' Seems like some timedate setting is still configured to be DD/MM/YYYY somehow?
# '' Seems like some timedate setting is still configured to be DD/MM/YYY somehow?
# '' UX: The ending page takes someone to Contact Us page, kinda unclear what the actual steps are
# '' UX: Welcome email sent from MM says "here are some next steps" but it's empty, ha.
# '' see also maybe [https://github.com/sudoroom/MemberMatters/issues the github issues page]