!Team Meetings agendas and notes (2020)
Been on kind of a light schedule for working and tracking items since August 2020. (hello pandemic)
Decisions from Susanna and Fredrik (SHF Board Chair)
From PivotalTracker: Renewal Process https://www.pivotaltracker.com/story/show/175802657
Decision:
Reminder sent When their payment runs out - 90 days User fills in membership guidelines (That's checked off) Submits a file ( Submit file checked off) Pays ( Payment checked off) 365 days minus 90 days = Reminder of time to renew.
if a member has paid ahead they just wont need to go through the process until it is time for them to renew.
And like now if they are unpaid/unrenewed they will be invisible. They are allowed to linger unpaid for 3 years before being manually deleted after a manual heads up (phone if possible, otherwise email) and will need to reapply etc.
Next client meeting scheduled: ..?..
- Users Acknowledge ("sign") the list of Ethical Guidelines
- Renewals
- Update Member landing page/dashboard
- Business Subcategories
- Add another Category to your Membership
- SEO information for Members
- Anything that makes it easier for Visitors to search and find Member Company pages
- Supporting Memberships
-
Proof of Membership: The image that is a member's proof of current membership in SHF
- who can access the simple .jpg file that is a member's proof of membership? EVERYONE
- Patrick will create an endpoint (publicly available route) for the .jpg file
Notes:
-
"jpg proof of membership" [endpoint] Anyone should be able to access/download the jpg of a Member's proof of membership.
A member needs to be able to download their proof of membership image so that they can show it to potential customers.
Because some may view the proof of membership image in an iFrame, we cannot check who is accessing the jpg proof of membership, so we must set access so that anyone can access the jpg proof of membership. Some (members, usually) will download this to put into their WordPress blogs, etc.
-
See the image as HTML with helper text (has the text at the bottom about size and short url) should this one have any security?
- used for those accessing it via iFrame
Will this still be needed once (#1 endpoint) is done? Nope. #1 will replace this version. (Susanna will let people know that #1 is available)
- who can access the simple .jpg file that is a member's proof of membership? EVERYONE
Mark as "Accept" (feature), "Deliver" (bug), or "Finished" (chore) if team agrees
- review any newly added items: person that added them should give a brief explanation and answer questions
-
What needs to be specifically reviewed and refactored?
-
Status of current refactoring work
-
Is the next needed discussion scheduled and confirmed with the client?
- agenda / notes ready?
- Ready with client demo(s)?
-
topics that need discussion with the client:
Next client meeting scheduled: ..?..
- Had a meeting on 6 juli with Fredrik, the SHF board chair. Ashley will type up some notes.
- Users Acknowledge ("sign") the list of Ethical Guidelines
- Renewals
- Update Member landing page/dashboard
- Business Subcategories
- Add another Category to your Membership
- SEO information for Members
- Anything that makes it easier for Visitors to search and find Member Company pages
- Supporting Memberships
- Ashley:
- worked with Susanna to figure out why the admin couldn't edit the membership status for a member that did have past payments
- the edit membership status modal isn't being displayed because of the CSS
.fadeclass. PT story (bug) created
- the edit membership status modal isn't being displayed because of the CSS
- deployed to production
- PRs created
- worked with Susanna to figure out why the admin couldn't edit the membership status for a member that did have past payments
-
Deploying: what I'd like to implement [Ashley]
- create a git tag
- some kind of semantic versioning (e.g. version 1.01.01)
- show the current version (and git REVISION info) in a simple
About...modal - automatically create a CHANGELOG.txt file (from the git PRs) this is a lower priority
-
Documenting [Ashley]: this is a task from our meeting with Fredrick
- I created a PT story, but this is likely to be an epic with many smaller stories
- Anyone can help by writing up outlines and basic content and doing screen shots, but the main translation will be in Swedish, so that means work for Susanna. (Just pointing that out)
Mark as "Accept" (feature), "Deliver" (bug), or "Finished" (chore) if team agrees
- review any newly added items: person that added them should give a brief explanation and answer questions
-
What needs to be specifically reviewed and refactored?
-
Status of current refactoring work
-
Is the next needed discussion scheduled and confirmed with the client?
- agenda / notes ready?
- Ready with client demo(s)?
-
topics that need discussion with the client:
Next client meeting scheduled: ..?..
- Users Acknowledge ("sign") the list of Ethical Guidelines
- Update Member landing page/dashboard
- Business Subcategories
- SEO information for Members
- Anything that makes it easier for Visitors to search and find Member Company pages
- Supporting Memberships
-
Active/Inactive Members [Ashley]: review updates to wiki page
-
Production server [Ashley]: (sysadmin work) FYI - I updated packages on the server for security
-
Review Priorities and update as needed
Mark as "Accept" (feature), "Deliver" (bug), or "Finished" (chore) if team agrees
- review any newly added items: person that added them should give a brief explanation and answer questions
-
What needs to be specifically reviewed and refactored?
-
Status of current refactoring work
-
Is the next needed discussion scheduled and confirmed with the client?
- agenda / notes ready?
- Ready with client demo(s)?
-
topics that need discussion with the client:
Next client meeting scheduled: ..?..
- Users Acknowledge ("sign") the list of Ethical Guidelines
- SEO information for Members
- Supporting Memberships
- Managing Membership Status
- Approving new (additional) categories for a Member
- Proof of Membership for Individuals and Companies
-
Active/Inactive Members [Ashley]: Start of discussion (new wiki page)
- We talked about this. Ashley will revise the wiki page with what we discussed.
-
Admin changes the membership status () [Ashley]
- The current business rule is:
app/models/concerns/payment_utility.rb: # This is our current rule: an admin cannot edit the status if there are no payments [2019-12-05] def admin_can_edit_status? has_successful_payments? endAn admin can only change the membership status if a user already has made successful payments.
Do we need to revisit and discuss this? Is this still correct?
Susanna: Yes, this business rule is still correct.
SHF applicants/members should use the SHF system to do payments. This is what SHF want to happen; it's best for the organization if applicants/members use the SHF system (and thus HIPS) to make their payments.If someone does not want to pay through the system, Susanna will manually do a 'payment' for them through HIPS choosing the option that sends an invoice to the applicant. - this will (1) be a successful payment from HIPS and reported back to our system (via the webhooks) This will then be a successful payment in the system.
So the business rule still stands: Members must have at least 1 successful electronic payment done through our system.
Mark as "Accept" (feature), "Deliver" (bug), or "Finished" (chore) if team agrees
- review any newly added items: person that added them should give a brief explanation and answer questions
-
What needs to be specifically reviewed and refactored?
-
Status of current refactoring work
-
Is the next needed discussion scheduled and confirmed with the client?
- agenda / notes ready?
- Ready with client demo(s)?
-
topics that need discussion with the client:
Next client meeting scheduled: ..?..
- Users Acknowledge ("sign") the list of Ethical Guidelines
- SEO information for Members
- Supporting Memberships
- Managing Membership Status
- Approving new (additional) categories for a Member
- Proof of Membership for Individuals and Companies
-
What is the date of the SHF Annual Meeting?
- Will we have "Ethical Guidelines" done by then? (implemented, deployed)
- UI/UX is the most work right now
- reviewing PRs
- Will we have "Ethical Guidelines" done by then? (implemented, deployed)
-
Merge PT 767 (cluster map markers) ?
Mark as "Accept" (feature), "Deliver" (bug), or "Finished" (chore) if team agrees
- review any newly added items: person that added them should give a brief explanation and answer questions
-
What needs to be specifically reviewed and refactored?
-
Status of current refactoring work
-
Is the next needed discussion scheduled and confirmed with the client?
- agenda / notes ready?
- Ready with client demo(s)?
-
topics that need discussion with the client:
Next client meeting scheduled: ..?..
- Users Acknowledge ("sign") the list of Ethical Guidelines
- SEO information for Members
- Supporting Memberships
- Managing Membership Status
- Approving new (additional) categories for a Member
- Proof of Membership for Individuals and Companies
Mark as "Accept" (feature), "Deliver" (bug), or "Finished" (chore) if team agrees
- review any newly added items: person that added them should give a brief explanation and answer questions
-
What needs to be specifically reviewed and refactored?
-
Status of current refactoring work
-
Is the next needed discussion scheduled and confirmed with the client?
- agenda / notes ready?
- Ready with client demo(s)?
-
topics that need discussion with the client:
Next client meeting scheduled: ..?..
- Users Acknowledge ("sign") the list of Ethical Guidelines
- SEO information for Members
- Supporting Memberships
- Managing Membership Status
- Approving new (additional) categories for a Member
- Proof of Membership for Individuals and Companies
- Ashley: Review the rules for changing a Master Checklist: (new wiki page)
Mark as "Accept" (feature), "Deliver" (bug), or "Finished" (chore) if team agrees
- review any newly added items: person that added them should give a brief explanation and answer questions
- What needs to be specifically reviewed and refactored?
- Status of current refactoring work
- Is the next needed discussion scheduled and confirmed with the client?
- agenda / notes ready?
- Ready with client demo(s)?
- topics that need discussion with the client:
