Home

Important Upcoming Events:

• Next Client review meeting:
  Monday, Feb 26, 19:00 UTC (= 20:00 Stockholm time)

  (Meetings are usually on Tuesdays, but this one is Wednesday because of scheduling conflicts.)

Current Sprint: Sprint 33 (ends 22 Jan)

• Next Team Meeting on our regular schedule of every Monday and Thursday at 16:30 UTC

---

Contents

Developing and Contributing

• Working with Git and Github
  • Developing a Feature (or bug or chore)
  • Resolving Pull Request merge conflicts
• Workflow: Using PivotalTracker - how we use PivotalTracker

Meeting Agendas and Notes

We have a weekly team meeting (scrum & review) every MONDAY and THURSDAY at 17:30 UTC (== 18:30 CET, 12:30 EDT, 9:30 PDT). We review the current state of the project with each other and plan ahead for the upcoming client meeting. (Here is a blank agenda you can copy and paste for each meeting: Team Meeting Agenda template)

We meet with the client every other week. (That's as often as her schedule currently allows.) The meeting date and time varies a bit because of scheduling issues, but it generally is on **Tuesdays around 17:00 UTC [18:00 CET] **. We always list the next client meeting date/time in the Client Meeting notes (below). Be sure to check the Client Meetings doc (below) to see the date and time for the next meeting(s).

• Team Meetings
• Client Meetings

Partners

• HIPS - Payment Processing Services
  • Notes related to payment processing
  • HIPS Example Code - using the "Checkout-API"

SHF Business: Goals, Rules, Decisions, Features

• Major SHF Areas of Functionality

• SHF Business Goals, Rules, and Decisions

• Payment Services Providers - Discussion Topics

• Classes, Events, and Integration with DinKurs.se

• Business rules around payments (membership and H Branding)

Design Considerations - discussions and decisions

• Addresses and Geolocation This takes you to the item in PivotalTracker. There is a discussion there in the 'Activity' section about the considerations, classes, and decisions for handling addresses and geocoding and mapping.

  • Useful site showing valid Swedish addresses

• MembershipApplication State Diagram and Transition Table

• Addresses that SHF needs and defaults for the UI

• Emails Sent When a Membership Application changes

• Business rules for managing membership status and membership fee payment

• Model destroy actions for associated models

Production configuration

• Production server configuration
• Pushing to the development and production servers

Deployment Notes

• Payments deployment

How-tos:

• How to Use I18n to Localize SHF : A guide for using I18n to localize SHF, with an example that walks through localizing a menu
• Notes on looking at DB info on Heroku
• Add JS pagination to a view
• Configure Postgesql DB for correct text sorting by locale
• Manage Heroku environment:
  • Seed the DB on Heroku
  • Configure email for correct URLs
• Add a new member page
• Run webhook(s) in development
• Work-around for Capybara driver visibility to select field option values
• Execute HIPS payment processing in development
• Fix test error "PG::UndefinedTable: ERROR: relation "membership_number_seq" does not exist"
• Dates and Times and Timezones (oh my!) - working with Dates and Times and timezones

Resources:

• Mapping and Geolocating
• Security and User File Uploads and Downloads