-
Notifications
You must be signed in to change notification settings - Fork 39
Development Meeting Notes Friday, March 24 2017
Kim (author), Zoya, Areeba, Balraj, Sukhamrit, Josh, Dr. Blandine
We got feedback from an application analyst and she was very impressed with what has been accomplished since the hackathon! She was also able to find some bugs, mostly CSS.
Since our team is growing, we really need to follow the processes so that everyone is on the same page. Some of the processes brought up were:
- Updating labels (change from “New” to “Working on it”, set to “Ready for Testing”)
- If you set an issue to “Ready for Testing”, make sure to provide high-level steps for the tester to follow.
- If you set an issue to “Ready for Testing” be sure to un-assign yourself from the issue so we know that someone can be assigned the testing task.
- Dr. Blandine created two new labels (Design and Requirement) for the design and research issues since we will need to keep those issues open for further reference.
- When you finish your testing and the issue passes, comment the word “PASS”, remove the “Ready for Testing” label and close the issue.
- If an issue does not pass the testing, comment why the issue failed, change the label from “ready for testing” to “Failed Testing”, and reassign the issue to the person who worked on the issue.
- In the “New Feature” tab on AccessLocator.com we could add a link in the title which will take the user to the demo.accesslocator.com
- There was also confusion on the main page of AccessLocator.com of whether the monitor logos are buttons or not.
- Before we release the next version, we should have a week of testing before having that demo version go live so we can catch bugs before the public has access to it. We could have the old versions available in case the user wants to compare the versions.
We need to get the development team together with Luke to get started on the video. We also need to start thinking about what we’re going to present at Digifest. The MAC students should also arrange who will be going to Toronto with Dr. Stephanos.
Working hours for February need to be sent tonight at the latest!!! Make sure to send Dr. Blandine your working hours for the month of March by April 7th.
Be sure to read over any directives provided very carefully in order to not miss any details. This will limit small unconscious errors that wastes other people's time.
Not following directives and/or not providing requested information by the deadline impedes on Dr. Blandine work as Project Coordinator.
There was talk about adding multi language features to the application. If there is a demand for different languages and we have a good functioning application, this will be something that we can implement in the future.
We went through the different Discovery findings and clarified some questions. For example, what does "High contrast signage" mean? At the next meeting (next Saturday April 1st) we will spend time reviewing the Discovery activities of Zoya and Baseer.
End of meeting: 9:30 pm