Skip to content

Team Meeting Agendas and Notes for 2019

Ashley Engelund edited this page Feb 12, 2020 · 1 revision

Agendas (and some notes) for SHF 2019 Team Meetings


Agenda for 2 December, 2019

Next client meeting scheduled: ..?..

  1. Users Acknowledge ("sign") the list of Ethical Guidelines
  2. Supporting Memberships
  3. Managing Membership Status
  4. Approving new (additional) categories for a Member
  5. Proof of Membership for Individuals and Companies

1. Scrum

2. Parking lot items

  • Ashley: I went ahead and merged some chores without waiting for reviews. They were 'clean up' type chores. (The PT stories have been marked as finished.)
    • have been waiting for reviews

3. PT Stories

3 a. Current Sprint Work: Review current stories/chores/bugs being worked on

Mark as "Accept" (feature), "Deliver" (bug), or "Finished" (chore) if team agrees

3 b. Backlog: priorities and order ok? points assigned?

3 c. Icebox:

  • review any newly added items: person that added them should give a brief explanation and answer questions

Any BLOCKERs?

Any pair programming that would be helpful?

4. Code Quality: Reviewing, Refactoring, technical debt

Review the most recent RubyCritic report of the develop branch and of the deployed code

  • What needs to be specifically reviewed and refactored?

  • Status of current refactoring work

5. Upcoming or Needed Client Discussions

  • 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:

6. Other items


Agenda for 16 September, 2019

Next client meeting scheduled: ..?..

  1. Supporting Memberships
  2. Managing Membership Status
  3. Approving new (additional) categories for a Member
  4. Proof of Membership for Individuals and Companies

1. Scrum

2. Parking lot items

  • [Ashley] Cucumber tests: This is a whole topic with a definite learning curve (cucumber DSL, our specific steps, regular expressions, etc.). For devs unfamiliar with them, would it sometimes be faster/better to pair with someone that is familiar with cucumber to get tests written? At least have that be a choice.

3. PT Stories

3 a. Current Sprint Work: Review current stories/chores/bugs being worked on

Mark as "Accept" (feature), "Deliver" (bug), or "Finished" (chore) if team agrees

3 b. Backlog: priorities and order ok? points assigned?

3 c. Icebox:

  • review any newly added items: person that added them should give a brief explanation and answer questions

Any BLOCKERs?

Any pair programming that would be helpful?

4. Code Quality: Reviewing, Refactoring, technical debt

Review the most recent RubyCritic report of the develop branch and of the deployed code

  • What needs to be specifically reviewed and refactored?

  • Status of current refactoring work

5. Upcoming or Needed Client Discussions

  • Susanna: have a meeting with top 10 active users about the member dashboard

  • 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:

6. Other items


Agenda for 5 September, 2019 (sprint nn)

Basil, Herman, Patrick, Susanna, Ashley

Next client meeting scheduled: today at 18:00 UTC

  • Will meet with SHF Board member Jenny. Main agenda topic = Subcategories

Top Priorities:

  • Subcategories
  • Analytics information (SEO)

1. Scrum

2. Parking lot items

  • [Ashley] I'd like to do a slight revision of Github PR template: make the sections bold and a little larger. I've been doing this manually with my PRs. Can we try it and then adjust based on feedback?

  • [Ashley] Need to clean up and revamp our PT stories. Set another time to discuss? See the new PT story: Improve our PT stories

3. PT Stories

3 a. Current Sprint Work: Review current stories/chores/bugs being worked on

Mark as "Accept" (feature), "Deliver" (bug), or "Finished" (chore) if team agrees

  • H-markt/Proof of membership context menu

    • Need to have 3 actions as buttons and context menu: download, copy url, view

    • style suggestion

    • Patrick's note about extraneous text in the generated (download) image

    • some discussion of when to generate the image (discussion for later PR)

3 b. Backlog: priorities and order ok? points assigned?

3 c. Icebox:

  • review any newly added items: person that added them should give a brief explanation and answer questions

Any BLOCKERs?

Any pair programming that would be helpful?

4. Code Quality: Reviewing, Refactoring, technical debt

Review the most recent RubyCritic report of the develop branch and of the deployed code

  • What needs to be specifically reviewed and refactored?

  • Status of current refactoring work

5. Upcoming or Needed Client Discussions

  • 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:

6. Other items


Agenda for 22 Aug 2019

Rodrigo, Herman, Susanna, Ashley

1. Scrum

2. Parking lot items

  • [Ashley] We need to regularly view the Google Analytics information for the site as a whole and also for the Company Pages.

    1. Manually view and review the information. (ex: First developer meeting each month?) Susanna would need to get that info from Google Analytics page and share it (print -> pdf or something?)
    2. Next step is to automate it: Get info from Google Analytics to (1) show to the admin, and then (2) use to show value to members. (e.g. showing if their company page is being viewed more/less this [quarter/month] ?) Seems like a possible next path

    Discussion: Rodrigo: be sure to identify the business objectives. Don't get lost in all of the possible numbers and analytics. Insights... rankings.. how do they work within the site page rankings? How does it reflect on individual companies (they may change their pages and have their own impact(s) etc. GTM = Google Tag Manager (more than page views, bounce, etc.) Enhances ability to track an event on a page. (could even have a template for each business page). Allows you to track separate events (our SHF site vs. the objectives of an individual company/business).

3. PT/PR reviews

#164983459 Link categories to categories show #706 - merged! 🎉

[WIP] #164878049 Disable contextmenu on H mark image #707

  • both Herman Lule and Rodrigo had good ideas for improving the UI. Ideas noted in the PR
  • PT story: review how/when H-markt image is generated need to discuss when/how the image is created. (needs to be created as 1 flat image; etc.)

4. Blockers?

(none)


Agenda for 12 Aug 2019

Patrick, Herman Lule, Ashley

1. Scrum

2. Parking lot items

(none)

3. PT/PR reviews

  • Ashley will have more for PR #686 - Capistrano One Time Tasks: How to incorporate the one-time tasks that we have already manually run.

  • Patrick will create a wiki page for Business Categories & Subcategories to capture open questions, especially about the related business processes. (Ex: Review process(es) that might need to happen if/when a member adds a new subcategory to their company.)

    • Subcategory abilities for different roles: admins, members, users, visitors
    • Phase 1 might be very limited abilities; later phases more involved (esp. if SHF business processes need to be defined/changed/approved)
  • Herman will start on Link Categories to Categories Show for the ADMIN. Fits in with the work we (Patrick) are doing to add functionality and value to BusinessCategories (Will also be a good intro to Pundit). Ashley will help.

4. Blockers?


Agenda for 17 June 2019

1. Scrum

2. Parking lot items

  1. AWS credentials [Ashley]

  2. emails

    1. emails:
      • admin@sveriges = system administration (e.g. disk space), technical support (customer questions about how the app works; something is broken, etc.) currently = Susanna

      • info@ = the public email; where the public (including members) can ask questions about SHF (the organization) or anything.
        currently = Jenny

      • medlem@ (membership) = specific questions about membership (for SHF members, applicants)

        • used as the reply_to: email in some emails are sent out currently = Susanna
  3. Backups: How many to keep? [Ashley | Patrick]

    • current.tar is everything under /app which includes both code and data (/public attachments)

      • /docs = our notes, including images, etc. for this (GitHub) wiki. Should only keep 1 copy of this?

      • /spec/fixtures is BIG

      • should review to see if there are other directories that we

    • du -h = disk usage [-h = human readable, to show kB, etc.]

3. PT/PR reviews

4. Blockers?


Agenda for 13 June, 2019

1. Scrum

2. Parking lot items

  • User problem:

    A user said she had uploaded 2 files for her application, but she received an email that said she did not have any uploaded files We checked Mailgun logs - she got an acknowledgement email at 9:51am (her local time)

    Looks like it was a matter of timing when the application was submitted, acknowledgement email sent, and then files uploaded:

    1. she submitted her application with no files uploaded
    2. acknowledgment email sent, and said that no files were uploaded
    3. she uploaded her 2 files
    4. she checked her email

    Need to add text to the acknowledgment email saying something like "if you have uploaded emails since this email was sent, ... nevermind about 'none being uploaded'"

  • business templates:

    Patrick Q: what do we need to do? Susanna: just need to change text to make this work (change text from 'upload meeting minutes')

    Do we have any PDFs to put into there? ("business templates/files")? nope. Hence none of the words have been changed.

    We do need to change the words in the cucumber features:

  • showing recent instaGram activity

    • discussion about what this might look like, how it might work

3. Deploy today

We deployed (after getting through a little confusion by Ashley)

Ran the task: shf:one_time:format_city_names to correct city names that had poorly formatted/inconsistent entries.

  • We learned that if you're logged into the production system as a user other than deploy, you are not able to run/execute the same gems, etc -- which will cause an error if you try to run a rake file or even run rails!

Agenda for 25 Mar, 2019

1. Scrum

2. Parking lot items

  1. System admin items:
  • password
  • accounts
  • update packages (requires a reboot)

3. Deploy today


Agenda for 18 Mar, 2019

1. Scrum

2. Parking lot items

  1. Alert bug: PR needs review.

    • we will keep getting the error every day until a fix is deployed. Not a big deal for users (they don't see the errors) except people are not getting reminder emails (alerts) that they need to submit their documentation.
  2. NewLook design (PR # )

    • All tests are passing
    • what "review" needs to be done?
      • Code?
      • UI? What parts are not being displayed correctly? or incomplete? Different platforms?
    • Can we address HoundCI issues in another PR so that we can get this deployed quickly?
  3. "Organization Supporter" - new Wiki page to track design and discussion: Organization-Supporter: a Membership type


Agenda for 25 February, 2019

1. Scrum

2. Parking lot items

  1. [Ashley] Company H-Brand image - what is it supposed to be?

    • the H-Brand image shows up when I am logged in as an admin BUT if try to look at the image for a company, I get an ERROR. Very confusing.

    • Need this for the meta image for the company page

    • the images_utility is not very clear. The functions are fine, but the intent is unclear.

    • this part has not be easy to untangle; have had to refactor some things so I have access to info/methods

  2. Security vulnerability with the paperclip .. provide image Should NEVER provide or expose a path that isn't under the /public directory!


Agenda for 7 February, 2019

1. Scrum

2. Parking lot items

  1. [Ashley] Alert when Company information is not "complete" 2 things that will cause a company to be "incomplete"

    1. company name is blank
    2. an address for a company has a nil Region

    What is the "day 0" date for sending out an alert?

    • when the company is created? (This seems most straightforward.)
    • the earliest membership date for a current member?
  2. [Ashley] Starting the meta-tag story

    • will implement a general mechanism for setting the meta-tags for a page: will get the meta info from the locale file if it exists, else will use sensible defaults
    • should we also implement schema.org tags? (as a separate PT story). Might be helpful to tag each Company and Event to improve the search results for it.

After the client meeting with Jenny, Ashley added a page for recording SEO ideas and info: https://github.com/AgileVentures/shf-project/wiki/SEO


Agenda for 28 January, 2019

1. Scrum

2. Parking lot items

  1. [Pat] UX behavior associated with (application) file delivery method selection (new or update)
  • No files uploaded, no file delivery method selected, application saved without errors:

    • User sees "app saved, but please upload files or select other delivery method"
  • No files uploaded, method "upload now" selected:

    • same message as above
  • No files uploaded, method other than "upload now" selected:

    • User sees "app saved, but please remember to deliver files via selected method"
  • Should add option All required files for my application are now uploaded

  • We will need an admin setting, for the application: Do not show file delivery choices

    • Do we check this automatically upon app acceptance?
    • We would "uncheck" this when app is first created
    • This could be checked (by admin or auto) when annual(?) app review begins
  • Team discussion decisions:

    • Warnings should be yellow
    • Delivery methods selection should be below the "files download" box
    • Make file delivery method required via validation
    • Client-side validation of delivery method selection (before form submit)

Meeting notes and agendas for 2018 are in a separate page to keep this page length manageable.

Meeting notes and agendas for 2017 are in a separate page to keep this page length manageable.

Clone this wiki locally