Page History

Found the functionality adequate for the current tasks required.

Future:

• Copy/Paste meeting info (or a duplicate function)
• Schedule multiple dates at same venue
• Abitily to store comment data:
  • meeting minutes
  • information links
  • graphics/images

It worked as expected. I created the mobile group, added meetings etc.

Some areas need some refinement:

• was able to enter incorrect email addresses, e.g. 0@1 was accepted.
• long (150 digits) numbers were valid entries for first name and last name
• Adding venue - Mobile Hangout - can only list Busy Body as contact. Cannot unselect.
• meeting - need to create venue first, just document venue needs to be created first.

Good work by all involved; sufficiently implemented and functional to release and start using.

• Change the title element of the initial frontend page to something more meaningful than "TssgDbApp"
• All frontend page titles should, perhaps, be something other than, for example, "TSSG Home", as that's not really the actual TSSG home page that people will see when they go to http://tssg.tech
• Very long table values (such as the first and last name fields in the users' list) make it almost impossible for a user to scroll all the way to the right to use the Edit or Del buttons on the correct entry.  (Perhaps move the buttons to the far left on all tables, make the long fields/columns individually horizontally scrollable, or limit the length of data)
• Move the descriptive text for the list pages (e.g., "A list of all venues currently in the database.") to the top of the page, perhaps between the page title and the table headers
• We probably shouldn't allow whitespace in a username
• Usernames are case-sensitive during login, this is non-standard IMHO
• Home page (after user successfully logs in) should show username (either in addition to or instead of user's first and last names)
• Add copyright in footer
• On the "List Team Schedule" page, the on-page title shouldn't be "Select Team Name"
• On the "List Team Schedule" page, move "(select one)" hint into the dropdown box as its hint
• Add the capability for a user to see which teams they belong to (perhaps just dump it out on the "Current User" page, but it might also be useful for an admin to see all the teams each user is a member of
• Add tips for when the user hovers over (with a mouse or whatever) a field name in all pages
• Sometimes, when I'm adding data and click Add, I see the pink flash of an error message, but it's gone so fast, I can't capture it
• When creating a new team, the specified team lead should be considered to be added as a member so as to not get the "At least one member is required" and/or "One or more team members are required." error

Go

•  Pushpa did a PoC for SonarQube; a static code analyzer.
• We deployed SonarQube to sq.technologynursery.org.  The tool initially found over 300 potential vulnerabilities and bugs.  These included WCAG2 issues.
•  Paul has fixed all bugs and potential vulnerabilities found by SonarQube.

Norm Heckman

Alan Rawsthorne

Scheduledb Feedback

1. Suggestion for recurrent events.
2. Suggestion for automatic Zoom invite sent at meeting creation allowing invitees to add zoom meeting for example to their google calendar(or other calendar). 
3. Suggestion for single login i.e. using Fakebook or Google accounts to login.
4. Suggestion to display the time zone the meeting times are using.
5. Suggestion to further define and improve on the phone number entry.