Date
Attendees
Goals
- Updates on continuing development
- Review, organize and add to work items
Focus points for this meeting
General update
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| Welcome |
| ||
| Vacations | Vince - - | ||
| Workflow - API Access Request | Diana Antova |
| |
| Developer Portal Migration to Drupal 8 | Ian Lessing (Unlicensed) | Motes: Drupal 8 Migration Notes Ian and Denise meeting on 4/30 to continue to work on the migration. In the last session they separated the site from the UCSB managed upstream. Will continue to update it thru composer. Denise had to reschedule due to UCTech commitment. Will meet on 5/8. Denise S. & Ian L. had a working session on 5/14 and have another scheduled for 5/17. Got setup with development environments utilizing Lando which utilizes Docker underneath. Ian and Denise met on Tuesday. Next meeting is next week on the 5th. Setup is similar as the UC Tech site where multiple developers are contributing to the development. | |
| Heroku | Kevin Wu |
| |
| CAS 5.3 upgrade | Steven Maglio | Targeting a deadline of August 2019. Ability to do headless authentication, which is what we need for the employee API. Will be able to transition from API keys. It will be a significant work for us. CAS 5.3 Adds
| |
| Reports and alerts | Diana Antova |
| |
| Student Developed Applications |
| ||
| CS 48 |
| ||
| Photos APIs | Diana Antova |
| |
| Accounts for separated employees/student |
| ||
| Documentation | Diana Antova |
|
: The API Access Request form asks for the Application Name, which is generally filled out as a normal human readable name. However this name is usually different than the actual 'application name' that is registered in the API Gateway (for example. Request "CS48 Project" is for Application "cs48test"). Do we want to setup a multiline input box that will ask for the exact name of all applications that are associated with the request? Sometimes requests will need to be split up into multiple apps (for cams).