Please report any problems to the Shared Tools Team at st-help@doit.wisc.edu    Broken Links? Missing Macros? WIKI Retiring Plugins
Child pages
  • POD Meeting 2010-09-30
Skip to end of metadata
Go to start of metadata

Previous Meeting | Next Meeting

Use of Personally Owned Devices for University Business (POD)

Thursday, September 30th, 11:00-1200, Memorial Union (See TITU)

Agenda

  1. Agenda review

  2. Mobile Apps Initiative (Guest: Hideko Mills)

    1. Background

      See also, Mobile Apps Links below

      From Hideko's comments:

      • Hideko began coordinating the Mobile Apps Team in March, (after Rhonda Thompson left to become CIO of VetMed.)
      • The team has looked at how mobile apps have been handled at other institutions, for example: MIT, Duke, Iowa, (including the notable "Laundry App" at Iowa that lets students know when washing machines are available!)
      • The team has worked on version 1 of an official UW-Madison app that includes a number of sub-apps such as: person directory, campus map, safety, news, events, athletics and video. It pulls public data from current production systems. Currently being developed on iPod, iPad and iPhone. Current version is alpha 1. Alpha 2 to be released soon. Target general release in November. Target porting to Android by end of December.
      • The app is owned by UW Communications. Version 1.0 development was funded by DoIT. Because of that, there has so far been no need for governance. However, beyond version 1.0, identifying governance and ongoing funding will be critical. There will be a meeting on Oct 18 to discuss this.
      • More below...

    2. Applications development for the mobile devices
      Some questions: (From POD Meeting 2010-09-02)

      From the discussion:

      • Current focus of apps development?
        • See above.

      • How can (should) decisions regarding apps development be made?
        • See notes on governance above.

      • What about apps developed by individuals and made available to the campus community?
        • The apps team has considered the question of how this effort relates to other applications developed by students or departments. This is a question for the "governance" to address. POD members talked about the importance of including other developers, and perhaps grading the apps, for example: (A) official, (B) supported in some manner and suitable for general use, (C) OK now, but not likey to be supported long-term, (D) use at own risk.

      • What about infrastructure and web site support for various types of mobile devices with limited graphics capability or small screen size?
        • TBD. (We didn't discuss this at the meeting.)

      • Should we (who?) recommend specific devices. How to determine what devices to recommend?
        • See notes on governance above.

    3. Managing mobile device applications
      Some questions: (From POD Meeting 2010-09-02)

      From the discussion:

      • What are the support obligations (if any) if it is an official app of the Univ. or dept?
        • Goal is for "official" apps to be supported, but it depends upon identifying funding for support.

      • Regarding support, does it matter who owns the app? If so, what are the differences? (Note some "official" apps could still be "owned" by the individual.)
        • Yes, it will probably depend on who "owns" the app. Details are another "governance" question.

      • Regarding support, does it matter who owns the data? If so, what are the diffferences?
        • TBD. (We didn't discuss this at the meeting.) The POD team talked about the team's earlier recommendation.

      • Regarding support, does it matter who owns the device? What if it is a recommended vs. unrecommended device? If these distinctions matter, what are the differences?
        • TBD. (We didn't discuss this at the meeting.) The POD team talked about the team's earlier recommendation.

  3. Other?

    • POD team would be glad to assist on "policy" issues (which could take form of guideline, principles, procedures, etc., rather than policy.

Outstanding action items

  • Outstanding action items re: non-UW-Madison apps and services

    • Publish an additional version of the guidelines for "administration", since this is an important issue for them as well. From POD Meeting 2010-08-05.
      Status: Drafted, but we're considering consolidating all three into one document.

    • Recommend that the university create a process for contracting for non-uw apps and services. From POD Meeting 2010-08-05.
      Status: Pending.

    • Recommend there be a brief list of major or most commonly sought apps and services. (Link to this from guidelines, and elsewhere.) From POD Meeting 2010-08-05.
      Status: (Very rough) draft of this is started at: CommonServices.

  • Outstanding action items re: POD Recommendations

    • Clarify what is meant by an application or a service. (This issue was identified early in 2010.)
      Status: Incoporate as we revise recommendations. See: http://en.wikipedia.org/wiki/Cloud_computing.

    • Check to confirm that it is already UW-Madison "policy" that individuals who possess UW-Madison-owned devices or software licensed via UW-Madison, are responsible for compliance with the license terms and applicable laws, (for example: export restrictions.) (From POD Meeting 2010-09-02)
      Status: Pending.

    • Recommend that decisions regarding purchase and support of devices and apps be left the individual units, (to the extent that UW-Madison has the option.) (From POD Meeting 2010-09-02)
      Status: Incoporate as we revise recommendations.

Future Meetings:

Attachments

No files shared here yet.

Contact

  • No labels