DRAFT DRAFT DRAFT DRAFT
Incomplete, unpolished, in-flight thoughts.
Title: UW-Madison Division of Information Technology is hiring software developers.
The University of Wisconsin-Madison is accepting applications for several software developer positions in a variety of roles and experience levels, including front-end developers and full-stack developers, and including roles with opportunities to develop applications and integrations for UW-Madison's well-regarded MyUW portal.
The application period for the specific opportunities prompting this newsletter item closes 2017-01-09.
https://it.wisc.edu/about/division-of-information-technology/jobs/
-Andrew Petro
...
This software is distributed under the Apache 2 license, which provides
Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. ...
This is a uPortal project vulnerability disclosure, pursuant to uPortal's Security Incident Response Plan.
This vulnerability is first being privately disclosed to known adopters and then soon after will be publicly disclosed.
With the theme of Leading Through Engagement, the 2016 I+T Leadership Conference is seeking proposals that reflect all aspects of engagement.
Please respond to the following questions to submit a proposal for a 45 minute session. Proposals should connect to the theme and have clear takeaways for the audience. Sessions that engage the audience are encouraged.
Andrew Petro
The exercise here is to move from
BROWSE permission is intended to gate whether users can see the app directory entry for an app, whether in search results, when browsing, or when following a deep link to an app details page.
Andrew Petro will share an introduction to Scrum (an agile method) as practiced by the MyUW Infrastructure team, emphasizing project management and product management (rather than development) aspects.
Attendees will gain context on this ongoing Scrum team, opening opportunities to apply this approach to other projects. This talk is at a “survey” level, that is, enough to whet your appetite for a subsequent conversation.
If you come away knowing about some people using Scrum and knowing some useful artifacts, along with answers on follow up questions, that’s success!
Structure: 30 minutes survey of Scrum; 20 minutes discussion.