Logistics

Mon 24 Feb - Wed 26 Feb
Location Seattle, WA

Agenda - Monday

1. OpenConext (recent queries to the list)
2. Bedework integration / Foodle integration
3. UI-2 planning
   1. Dashboard (see note below)
   2. Goals for I2GS
   3. Directory (over dinner)
4. Dealing with deprecation of Sanitize library (HTMLPurifier, strip_tags(), htmlentities(), etc)
5. Self-Service Updates Are Broken (CO-755)

Dashboard

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:

• Recent notifications
• List of COs they can select
• If platform admin, a full expansion of the platform menu (for quick
  access)
• List of applications (CO-101)

Agenda - Tuesday

1. Milestone Planning
2. Triage all issues for 0.9.1/1.0/Future
3. MyLIGO 3 status and planning
   1. Where do notifications need to be added? (CO-788)
   2. Prioritization and handling of deleting vs expiring (CO-149 and CO-766)
4. COmanage for HPC
   1. Backlog for HTCondor, etc
5. MFA CMP status and planning

Tuesday dinner

Bedework
Calendar user stories
Hosting - the wave of the future
OpenApereo side meeting?
COmanage Future on Sep 1 2014

Agenda - Wednesday

1. I2GS session planning (and dev meeting planning)
   1. Slides due 3/24!
2. Terena travel planning
3. Should mailing lists be objects in COmanage, perhaps tied to groups?
   1. This would allow for additional attributes to be managed explicitly (such as mapping groups to mailing list names, lists of moderators, whether the list should be archived, etc) that can then be passed to plugins such as the SympaProvisioner (CO-674)
4. git branching / management strategy

Notes - Monday

OpenConext

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?

Bedework Integration

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:

• ongoing meetings that are read-only or read-mostly
• point to point scheduling
  Try to spend the time between now and the Global Summit to figure out the use cases, have those conference calls and develop a strategy. After the Global Summit, start coding.
  Also add this to dinner discussion Tuesday night.

UI Planning - Dashboard

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:

1. Get the CO Person page better
2. Get the collaborations menu finished off
3. Sidebar changes (CO-416, CO-822)
4. Simple Search (CO-209)
5. Dashboard (though this won't be done by I2GS)
   1. Note that Filter needs to be differentiated from Search (CO-821)
6. Advanced Search (CO-820)
   1. Cross controller search (backend) (CO-819)
      If we make Dashboard a plug-in driven entity, what plug ins will it need? Need a dashboard controller (CO-823).
7. user info (CO-824)
8. notifications (CO-826)
9. apps (CO-825)

Self-service bugs

Comments in the ticket are sufficient (CO-755)

Milestone planning

see Technical Roadmap
questions being asked in Jira: Is this needed for I2GS? MyLIGO?

• 0.9 (target release by I2GS)
  • Notifications
  • UI
• 0.9.1 (pre-release for MyLIGO, then functionality freeze)
  • Search
  • Expirations
  • Terena CORE
• 1.0 (the MyLIGO release)
  • Scalability
  • Stabilization
  • Directory 0.2
• 1.1
  • Audit
  • Dashboard
  • Reporting
  • Credential Management
  • Directory 0.3
• Future
  • Directory 0.4

Note: needs more discussion

• CO-801
• Notifications (some will need an ack, some will not, some will not right away; some req an action)
• Release strategy that accommodates the need for something other than 100 issues per release
• What can a CMP admin do?

MyLIGO

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.