Logistics

Sun Apr 6 12n - 5pm
Location Denver, CO, Sheraton Plaza Court 5

Agenda

1. Planning for Monday's session
2. Review myLIGO 3.0 Checklist
   1. Notifications via enrollment flows (requirements vs implementation)
3. Niels email re ticking the organizational identities from enrollment flows check box
4. Terena CORE lightning talk
5. Calendaring: Bedework, Foodle, etc
6. UI-2 review and planning
   1. co_people/index
   2. LIGO 60 MOUs

Notes

Planning for Monday's session

see latest info in google docs; using Scott's laptop

UI-2 - co_people

Changing "Compare" to "View"?
Suggest changing shading in lists to be more distinct
Consider removing the buttons and going straight to a CO person? The most important thing is the email associated and displayed with the person, and the edits or acceptance of pending confirmation. Valid-through date would be useful, and the COU itself.
Other suggestions for ExampleCO People - see new ticket CO-

• having the roles is useful, but have it at the bottom of the open view
• valid from/to dates
• provisioning status for multiple provisioners (but that's probably too much information)
• photo should definitely go here, maybe in the drop down, maybe as a hover-over + drop down
• what COU they are associated with

Terena CORE

No update

Niels email re ticking the organizational identities from enrollment flows check box

In order to do something useful with enrollment flows, you have to click the box on "Enable Organization Attributes Via CO Enrollment Flow"; this would get clicked by the admin once per setup

• the early vision was that we would contact an LDAP or have a SAML assertion that would give us all the organizational info we would want. That didn't quite work out, so we need to accept attributes via an enrollment form.
• we need to have the documentation to be more accurate
• Hide "Enable LDAP Attribute Retrieval" and "Enable SAML Attribute Extraction" for now until we have a use case for their use. There is no code behind those items anyway. – See ticket CO-855

Calendaring

We don't know what the requirements or use cases are yet. CMP wants some "foodle" and some "event". LARPP wants to do mostly "foodle" - maybe this is just out of ignorance in terms of what is available?
Note that for bedework, the back end for consensus scheduling is done. UI is the next step, and there is a javascript implementation to start from.
Need to collect requirements, and need to figure out how to bring the bedework developer (Mike) on to a subcontract to get him involved.

Review myLIGO 3.0 Checklist

• Notifications via enrollment flows (requirements vs implementation)
• Concerned that we are not going to get 3.0 fully deployed before the end of the grant
• the list is still accurate for now; nothing to add