Mon 24 Feb - Wed 26 Feb
Location Seattle, WA
What information would you like to present users on the front page of
the system when they first log in or when they arrive "home" by clicking
the logo in the UI?
Several things come to mind at the moment:
Bedework
Calendar user stories
Hosting - the wave of the future
OpenApereo side meeting?
COmanage Future on Sep 1 2014
See the OpenConext wiki for more info on the platform
Do we prioritize doing anything more with this this year?
This was originally the plan for the MFA Cohortium. There are a number of "Phase 4" thing that should be cleared first that won't have another funding source. If we have more hours available in the MFA contract, then we can apply that to an OpenConext deployment. We should have an MFA/SCG meeting to talk about this further.
Note we do need to have a meeting at TNC 2014 to meet the requirements for funding Benn's travel there. Where do they stand with the hosted COmanage/OpenConext service?
From the Registry point of view, the Registry contains the people known to the VO, and apps pull info from the Registry. We are also looking at TERENA CORE as a possible service to integrate with COmanage. What would it mean to integrate Bedework? What are we pitching as the benefits? How would this happen? COmanage could handle the provisioning from a full enrollment work flow or a just in time event.
Bedework is a calendar system and it integrates with calendars; it is not just a web service. The big parts are the personal calendaring, public calendaring, scheduling. Bedework needs a self-registration component. If you have public events of interest coming from an organization, having direct subscription to those public events and self-sign in component so people could register for an account and be provisioned into a system. You have to have an account to authN to for the calendar entries to sync.
AI: Write up some user stories and then bring in Mike Douglas as chief Bedework architect and start the discussion as to what's possible
There are one or two MFA use cases we can start with:
Note that platform admins can delete CO, and they can delete people when the people are in the system, but they cannot approve petitions. Should a platform admin be able to run your enrollment process?
Priorities:
Comments in the ticket are sufficient (CO-755)
see Technical Roadmap
questions being asked in Jira: Is this needed for I2GS? MyLIGO?
Note: needs more discussion
When are we targeting a release? May would be great; will be doing a more detailed gap analysis today since the overall framework, incl notifications, is ready. The gap analysis is comparing the current functionality of MyLIGO 2 with what we currently have. No functionality may be lost.
We have to have something called "Directory" available; verify if what we have now will suffice.