Dec. 4, 2015 at 3pm ET
Attending: KeithH, EmilyE, HelenP, AnnW
(Keith is stand-in chair)
Nick, Paul and Tom traveling
Action Items
AI (Keith) contribute TIER Readiness Tip for TIER December 2015 Newsletter
Older Action Items
[AI] (Emily) put TIER Roadmap on agenda for when SteveZ is on the call
[AI] (SteveZ) draft charter for TIER Instrumentation/Measurement working group; Jacob will also work on it
[AI] (Tom, Ann, DavidW, MikeZ) meet to move forward on the Doc Stewardship doc Update: call scheduled for Friday, Dec. 18 at noon ET
Discussion
Welcome Helen Patton, OSU, to this Ad Hoc Advisory Group
Helen has agreed to chair the TIER Security and Audit WG
TIER Working Groups - Brief updates
See TIER Working Group wiki page for links
Packaging: JimJ
Data Structures and APIs: KeithH
Group Management APIs and Resources subgroup underway
Identity Registry APIs and Data Structures subgroup launched
Security and Audit HelenP
Call for participation end of Dec target
hope for monthly meetings in 2016
Possibly some charter scoping work early on. To align Security and Audit WG name with apparent patch/vulnerability focus
Need to come up w Standards and Best Practices
what is software development life cycle and project delivery life cycle?
To be discussed on the next Ad hoc advisory call…
Helen asks: right now for product development, things are silo-ed, but we hope they we will be in the future one operational entity…. or , things will stay separate in the future? what will it look like when it’s up and running?
Keith: hope things will be linked together and will be linkable to existing campus systems …
there are already some connections between Grouper and Shib and COmanage, but the intent is more connection. However campuses should still be able to deploy just one tool (ie just Shib, but not Grouper)
Helen: security should not be tail to wag dog of operations…
Helen: should she visit Ann Arbor and ask lots of question about how things work now?
Keith: SteveZ and the component architects group would be more directly involved Helen will reach out to SteveZ to talk about how to assure that security and audit are not the afterthought that they often are. Perhaps an intensive meeting of component architecture WG members plus others.
Helen has some names of people to invite the working group (from TomB)
Logistical framing for CAPE Charter
how do we move it along toward approved status? (discuss on future call)
TIER Person Registry Decision
Set direction on the criteria for the person registry in TIER Release 1 and possibly which of the volunteered person registries we need to align with.
This arose from the Component Architects call of Nov. 23, 2015 See the section “Nature of "Person Registry" and "IdP" in the context of Release 2
Person Registry issue is important to decide -- but can’t decide without more people on the call
Use COmanage person registry?
commit?
CPR?
Open Registry at Rutgers is stalled in terms of open source, community effort
This registry issue ties into updating the TIER long term roadmap
This Ad Hoc Advisory group can set a strategy for choosing a registry
We may eventually need a working group to focus on the person registry
The API group is not a prerequisite for the person registry work
Ann: TIER hopes to run concurrent working groups that watch what each other is doing. So API work starts out and person registry work can be concurrent.
Keith: A good thing is that Jimmy, a developer of CPR version in Commit, did develop restful web services based on CIFER API work.
Ann: CPR is going in the direction of using spring framework (but that is not in current version of commit)
Keith: Shib is also using spring
- What should be in the TIER Readiness Tip section in the Dec 2015 TIER Newsletter ?
- AI: Keith to draft something about getting ready for a campus Grouper installation by Monday
- how to select campuses for a TIER contributions/volunteer spotlight?
- by nomination of WG chair?
-by outreach over mailing lists asking for volunteers to be spotlighted?
Helen: nomination of WG chairs makes sense.
Keith nominates Univ of FL- Warren Curry for a volunteer spotlight ; Keith will contact Warren & connect him with MikeZ
case study of use to the API work
What should the categories be for the TIER Community Forum? (If SteveZ is on the Call) - Discuss on a future call.
The Component Architects have proposed this list.
Affiliate Membership in Linux Foundation to participate in Open API Initiative? Discuss on a future call.
TIER Roadmap (next time SteveZ is able to attend)
Creation of TIER Person Registry WG - discuss at next call
Next Call: Friday, Dec. 18 at 3pm ET (90 minutes)