Development Meeting Notes Friday, May 26, 2017

DATE: Friday May 26, 2017 START TIME: 7:00 PM LOCATION: CAW END TIME: 9:00 PM

Attendees

Bruce's work on changes to the save button in the Profile was merged and made the issue ready for testing. #318 has more details.
Bruce's work to confirm potential loss of changes on the Profile was merged and the corresponding issue was made ready for testing. See #349 for details.
The hover text feature was optimized for use with screen readers and tabbing for users who don't use a mouse. #242 is the associated issue.
Bruce did some work that is under review for the password reset/recovery feature, #204.
Areeba pointed out an interesting similar project idea called Ability App. See #355 for the corresponding research issue.
Navroop came back from India and indicated that he wanted to be active on the project again.
Balraj went to Alberta to visit some people.

Bruce on the password reset feature while Jared learned more about the procedure for testing issues.

We discussed the Ability App and Jared thought the employment features of it could be useful.
We discussed meaning of the issue labels. Jared asked for some documentation to review later. Below is a description of how the labels are affected by the issue work process. The labels and process may change but these steps should be current as of May 26, 2017.
We discussed the various stages an issue would go through from:
1. Having a "Help Wanted" and "New" label
2. to getting assigned to someone who will work on it. This is when "Help Wanted" would be removed.
3. to assigned. Can still have a "New" label on it.
4. to the assigned developer "Working on it". "New" should be removed.
5. to it getting in a pull request and having "Working on it" removed.
6. The pull request review step may involve some back and forth between Josh and the assigned developer. The review will look at code quality and double check that requirements were met.
7. to merged, deployed on app.accesslocator.com and marked "Ready for testing". Josh would handle this step after the code review passes.
8. A third person will test the work on app.accesslocator.com. This is basically another set of eyes to verify that the work is ready for the next release to demo.accesslocator.com. When this testing passes, the issue will be closed.

Bruce continued work on #204 and we discussed some of the technical details around how the password token would be remembered in the form. This continued a conversation started in a pull request.