5. What is uPortal-start?
● The way to adopt uPortal 5
● “Fork” this repo; not the main uPortal repo
● Contains the things that make uPortal your portal…
○ Configuration
○ Skin
○ Data
● Includes CLI tools to manage these items, also packaging & deployment
● You build uPortal-start (lightning fast!); Apereo builds uPortal
8. Reasons why using uPortal-start is better
1. You don’t need Apache Ant
2. You don’t need Apache Maven
3. uPortal-start installs & configures Tomcat for you
4.build.properties is not required
5. Run any task on a single submodule, e.g.
$ ./gradlew overlays:CalendarPortlet:tomcatDeploy
6. Data is in the data directory, not uportal-war/src/main/data
7. All data is in the same place (incl. portlet data)
11. Open Apereo 2017 | Workshops (June 4)
● My UW for You: Workshop Edition
● Getting Started with uPortal 5 (Thanks Drew!!)
● Developing Soffits for uPortal 5
12. Open Apereo 2017 | Sessions
1. BOF Devops in Higher Ed (Tim Vertein)
2. Portals? uPortal!? What is this Béchamel? (Christian Cousquer)
3. BOF Apereo Security Incident Response (Andrew Petro)
4. State of the uPortal 2017 (Jim Helwig, Drew Wills)
5. BOF uPortal Roadmap (Jim Helwig)
6. BOF Accessibility Across Apereo (Matt Clare)
7. Speeding up uPortal with ReactJS (Brandon Powell)
8. Apereo Portlet Showcase 2017 (Benito Gonzalez)
9. MyUW and You: Progress in [uPortal Home] and How You Can Too (Andrew Petro)
13. Open Apereo 2017 | Shared Slides
1. Two Hard Problems, in Vignettes
○ Andrew Petro - University of Wisconsin - Madison
○ https://www.icloud.com/keynote/0vEJysMgblVjGUv0ystx1xWrA#two-hard-problems
2. Speeding Up uPortal with ReactJS
○ Brandon Powell, KaJuan Johnson, Aaron Goodfellow - Oakland University
○ https://www.slideshare.net/bpowell29a/speeding-up-uportal-with-reactjs
3. Portal?! uPortal! What is this Béchamel
○ Christian Cousquer - UPMC
○ https://cousquer.github.io/apereo2017/
14. Open Apereo 2017 | uPortal Roadmap
● https://goo.gl/wZ7VTC
● 12 Items of interest
● 21 attendees!
● Items of interest highlight
○ Release uPortal 5
○ Alternative layout manager
○ Better web service API documentation (documentation all around)
○ Dockerizing
15. Open Apereo 2017 | uPortal Collaboration Days
● https://goo.gl/HYVe88
● Wednesday and Thursday, post-conference
● Google Hangout for those not at the conference to participate
● Several hours to deep-dive into topics from the BoF
● Respectful discussion even with countering views on approaches
● About a dozen attendees
● Topics
○ Release uPortal 5
17. Message from uPortal Steering Cmte Chair
Consider becoming a uPortal Supporting Subscriber
https://www.apereo.org/projects/uportal/uportal-community
● Our primary use is in support of securing a uPortal Community Liaison and
Release Lead. This person would focus on:
○ Coordination and engineering of releases and pull requests
○ Testing
○ Bug fixing
○ Engaging the uPortal community
18. Interest in uPortal Developer Conference?
● We are examining if there is enough interest for one
● Timeframe is mid-October
● UW Madison has offered to host
● 2-3 day event
● If interested, please let us know on the mailing list
○ uportal-dev@apereo.org
○ uportal-user@apereo.org
20. uPortal 5 High-Level Status Update (Q1)
https://wiki.jasig.org/display/UPC/uPortal+5+Project+Overhaul
1. Implement a Gradle-based build
2. Process open pull requests
3. Remove @Deprecated, unreachable, and/or unused sources
Legacy DLM | Legacy PAGS | Tab Groups | Opt-in DLM fragments
4. Decompose uPortal sources into tightly-scoped jars built with Gradle
5. Move everything that doesn’t go into a vanilla uPortal war file to
uPortal-start
Done
Done
In Progress
TODO
TODO
TODO
21. Done
Done
https://wiki.jasig.org/display/UPC/uPortal+5+Project+Overhaul
1. Implement a Gradle-based build
2. Process open pull requests
3. Remove @Deprecated, unreachable, and/or unused sources
○ Legacy DLM | Legacy PAGS | Tab Groups | Opt-in DLM fragments
4. Decompose uPortal sources into tightly-scoped jars built with Gradle
5. Move everything that doesn’t go into a vanilla uPortal war file to
uPortal-start
uPortal 5 High-Level Status Update (Q2)
Done
Done
Done
In Progress
22. Overview of Work
Stories Authors Commits Pull Requests
Refactoring
Packages
UP-4830 Drew 71
(incl carryover)
6
Splitting out
uPortal Start
UP-4858 Drew, Christian 5 3
Gradle transition 6 Drew, Seema,
Christian
32 9
Testing
Improvements
UP-4870 + 6,
UP-4745 + 2
Seema,
Christian
31 8
Documentation 3 5 39 12
26. Highlight: Documentation Improved
Contributor Chris Beach, Welcome!
Documentation for F5, Committers, IDE Integration
Port of Confluence pages into uPortal manual (Thanks Andrew Petro!)
Getting Started Guide
New
New
Improved
Improved
29. Marissa Warner-Wu, Edinburgh
Goal: transform the way that students were experiencing our portal
“I can cope with MyEd [uPortal], but it took me a while to get used to it.”
– student, from Headscape: Transforming Student Digital Lives
30. Marissa Warner-Wu, Edinburgh
Business problems with our current portal:
● Structure around services, not user tasks - burden is put on user to find what
they need
● Little support for user preferences (mobile, offline, low bandwidth)
● Information presented in a way that isn’t easily understandable (use of
acronyms, specialist vocabulary)
● Information is often generic - e.g. “You may need to do this”
31. Marissa Warner-Wu, Edinburgh
Proposed solutions:
● Restructure around student tasks and journeys
○ Highlight “To Do” items
● Allow users to interact how and when they want
● Use language that students understand
● Personalise what is being shown to the current user
36. Look for the Slides on the
Unicon Blog
https://www.unicon.net/about/blogs
Notes de l'éditeur
Intro (Stephen) 2 minutes
Record this! 📷
General Housekeeping Items
Team Intro
Benito is an Apereo Fellow! 🌠Recognized for the decade of contributions he has made the foundation.
Add questions to chat during the presentation, questions will be answered
uPortal-start Overview (Drew) 10-12 minutes
What is uPortal-start
Gradle technology
Setup -> Live Demo
Open Apereo 2017 Recap (Benito) 10 minutes
How it went
Common themes
uPortal start
uPortal home
Front-end technologies
Roadmap 2017-2018
Sustaining Engineering Recap (Christian) 10 minutes
Overview
Testing Highlights
Documentation Highlights
Community Spotlight (Marissa) 10 minutes
Q&A (All) 1-10 minutes
Drew: Possible live demo?
Was a great conference at a great location in Philly. Very high level view of what I go out of the conference.
Discuss the topics and how attending a workshop provides real value. Even some topics that seem like a review can bring up some surprising new details
Mention something about each presentation that someone would not get form the slidedeck -- presenter personalities
Talk about the mood, how full the room was, new voices. This was an opportunity for those that could not stay for collaboration days
In the past we have used this time for ad hoc discussion on topics of interest, hashing out the road map, working together on mutual problems, etc. Good discussions. Really felt a connection with others -- passionate about uPortal.
It’s really about face-to-face time, sharing what we are passionate about and re-invigorating our community!
While we are talking about Apereo and the uPortal community, the uPSC chair wanted to me to raise awareness about the Apereo uPortal Supporting Subscription
Looking for support to have a dev conference. Not sure the minimum we need, but should be more than me visiting UW Madison, Jim said ;)
Submitting Requests
Subscribers will sometimes discover bugs they would like to have fixed in the supported software, or have ideas for minor features or other enhancements they would like to see implemented. When these arise, the subscriber contact should submit an “S5 – Request” support case and provide full details on the issue they would like to have addressed.
When a subscriber contact submits a development request, the receiving engineer will first review it to ensure it is sufficiently descriptive. If further information is required, the engineer may perform some independent research or engage in further discussion with the submitter in order to fully understand and document the issue. The engineer will then provide an initial estimate for the level-of-effort required to resolve this development request.
If the subscriber would like to have this issue addressed immediately, they can use Consulting Assistance time to proceed directly to getting an engineer engaged on the development work quickly. Otherwise, the team will submit the issue to the tracking system of the open source project itself (without identifying the subscriber in any way).