Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

 

Attendees

Goals

  • Updates on continuing development
  • Review, organize and add to work items

...

Focus points for this meeting

Discussion items

TimeItemWhoNotes
Welcome
  • Greetings and salutations

General Info
  • Collaboratory is not available anymore on Fridays
  • Will meet 10-11:30 on Thursdays

HerokuDiana Antova
  • Account created with api-team@developer.ucsb.edu
  • Kevin setup a team account with the credit card
  • Kevin passed around password to team members
  • Account is with the free access. Once we want the paid access we will have to set it up with the CC.

  • Email GroupsSteven Maglio

    Student Developed Applications - Meet with Professors
    • When should we meet with Professors?
      • Phil Conrad
      • Tobias Hollerer
      • Tim Sherwood (Steven wants to talk with this guy)
    • What should be on the agenda?
      • Capstone project idea, a year long project idea
      • Security review
      • Continuity
      • Use of graduate students to oversee student developers
    • When - in February

    Legal / Policy Statements for Student DevelopmentDiana Antova
    • Working with Sam Horowitz and Jennifer Lowfthus on policy statement for students to sign.

    GoGaucho
    • Met with campus representatives to discuss the student app development
    support on 
    • support 
    • 2018-12-06 Student Application Development Support 
      • Branding
        • Were okay with the name GoGaucho for now. But, Nancy Hamill will need to double check this.
        • In general, we don't need to worry about branding until an application has the notice of the campus
      • Legal documents to sign
        • Sam Horowitz and Jennifer Lowfthus will figure out what documents need to be signed and get back to us
      • Who is responsible if something happens - a data breach
        • It can't be on the students completely. Sam Horowitz and Jennifer Lowfthus will determine how this can pan out and come up with the documents.
      • Can we create a badge that the app is approved by UCSB?
      • API team has the authority to do the security code review, in addition to the technical support representative for the data being requested
      • Adding language to the app to let students know that this is not an official UCSB app?
        • Yes. At the time of login. And also it should be the first line in the description within the store(s).
      • What role the Student Code of Conduct play?
    • Steven Maglio to follow up on resolving the issues that we have identified, including removing the server use from China
    • Add documentation on the website about security reviews, guidance on how to use securely APIs (similar to Oregon State U.), include guidance on where to store the key if they are a student, or don't have a solution in place
    • We need to develop student app development guidelines

    Mobile Applications That We Should Reach Out ToSteven Maglio
    • iOS
      • GoGaucho 
      • Gaucho Life
      • UC Santa Barbara Guides
      • UC Santa Barbara Events
      • UCSB - UC Santa Barbara (Involvio LLC)
    • Android
      • UC Santa Barbara Guides
      • UC Santa Barbara Events

    Workflow - Application Approval RequestDiana Antova

    Workflow - Publish a New APIDiana Antova
    Ian Lessing (Unlicensed)
    page

    @apibot - Powershell Conversion & HostingKevin Wu
    • Working on Kevin's Computer (node 8.9.X) (APIGEE-105 & APIGEE-101)
    • Heroku for deployment
    • Kevin will deploy to Heroku

    Action Items From Previous Meeting



    API Access Expected UsageSteven Maglio
    • Expected Usage Text and Legal-ize (Terms of Service) - page
    • on App create send the legal text to the developer
    • on API access request - 
      • email on auto-approve for API expected usage, send them the form to fill with a check-box to agree on API usage terms
      • email on requesting that they fill out  the form for any non-auto approval- add same check-box
    •  Do we have this documented? Has this been turned into an Apigee Ticket?
    API Versioning

    Steven Maglio

    • Drop Minor Versions as a requirement
    • Write standard approach for departments that want to use Minor versions; using the approach is also optional.
    •  Do we have this documented? Has this been turned into an Apigee Ticket?
     Reinard
    • Create security guidelines
    •  Will review in the context of student development guidelines, maybe create them for everyone

    Developer Portal Front Page Updates
    • In About Section
      •  Diana Antova - Add page about winning the Sautter Award
      •  Diana Antova - If Diana thinks its a good idea to add it to the main page, then she will work with Denise to do so

    CSF notificationDiana Antova

    API Health check/MonitoringDiana Antova
    • will
    check out ZabbixCan we ask campus if we can
    • use
    one of the existing monitoring systems?will use
    • uptime robot
    •  Ian Lessing (Unlicensed)Steven Maglio write requirements - use health check end point
    •  uptime is separate - checks for an api proxy being there, steven is ready to deploy it to uptime robot
    • Steven Maglio create a page with how to setup uptime robot for newly published APIs

    API DictionaryDiana Antova
    • API dictionary and data governance - define field meaning, naming conventions (Bruce Miller)

    Improved DocumentationDiana Antova
    • More documentation, need testers that will help us define the optimal set. Can we have a link to a documentation page?
    dedicate
    • Dedicate a meeting to documentation
    once a month
    •  

    API Selection pageIan Lessing (Unlicensed)
    • API select page - fix layout (Denise)

    Accounts for separated employees/student

     Steven Maglio


    • What do we do with separated employees
    • periodic verification (quarterly, yearly)

    Google Analyticschristian.montecino (Unlicensed)

    Migration of developer.ucsb.edu to the UCSB account Steven Maglio

    Action items

    •