Subscribe to the mailing list for all things CIFER by visiting http://lists.ciferproject.org/listinfo.cgi/community-ciferproject.org
Inaugural CIFER Tech Coordination Call
Friday, May 17, 1:00 pm Eastern, 10:00 am Pacific
Dial-in numbers:
+1-734-615-7474 (English I2, Please use if you do not pay for Long Distance),
+1-866-411-0013 (English I2, toll free US/Canada Only)
Access code: 0140110#
participants: BennO, Dedra, TomB, BillT, BillY, RobC, SteveO, KeithH, ChrisH,
elsewhere: Renee, JimJ, NickR
_____________________
My hope is that we can use this call to start giving real shape to the long-envisioned CIFER cross-work-stream technical coordination work. Over the course of this week I''ve had conversations with each of the current work stream leads and we have a rough first take of a combined feature and capability list (or wish list, if you will).
Preliminary agenda:
1. What would a cross-team tech coordination group work on?
- Shared APIs (shared by OR and CPR, defined in collaboration with the Provisioning and Integration team and the Authentication team where there is overlap)
- Coordinated and rationalized feature lists (and roadmaps)
- Shared modules where appropriate (possible examples: IdMatch, Password management)
- Shared schema, protocols and bindings between them (e.g., Identity Registry schema, SCIM and CIFER schema extensions for SCIM)
- Overall functional model
- Coordinated Requests for resources for projects aimed at delivering specific feature and capability sets
- Review, QA, test coordination and planning; testing cycle; overall development lifecycle
- Dedra: Oversight, prioritization across caretaker organizations running projects;
- BillT: Integration testing across projects
- TomB: Overall functional model/technical architecture would be responsibility of this group; carries some responsibilities re oversight across caretakers and projects;
- Other cross-team activities?
- BillY: Shy away from calling it a tech coordination; Keep as generic as possible;
- Dedra: Sustainability of existing projects: Shib, CAS, Grouper,...
- Chris: Depends on expectations and investments
- TomB: Will need to sort out what's Groupers to do and what's CIFERs to do?;
- BillY: Let's steer away from the resources question until the CIFER Consortium is up and running
- BillT: Sustainability: uPortal & CAS: even though we're a dozen years on the issue is there. the key to sustainability is adoption...
2. Expansion, refinement of CIFER feature and capability list
- Is this list the critical next deliverable? If not, what?
- RobC: How much do we focus on the outward stuff vs. the inward? Two lists.
- BillY: High-level ref arch has been invaluable; CISO types found it useful
- For the more tech folks, they're looking for more details
- TomB: Let's tackle this soon: Start at functional model: For each piece: functional interfaces (enrich the existing slides that show the components);
- See https://spaces.at.internet2.edu/display/cifer/Cross-team+features+and+capabilities+list
- BillT: Some of these things are cross-project; Broken down by workstream; is there another list that flips this around and talks about overall IAM Arch; We don't have an overarching tech ref arch; products are being adopted in a variety of ways; Wiring to other components;
- Overall tech arch would show how all the components would come together to solve a biz use case.
- BillY: The 4 layer version biz arch, info arch, tech, app architecture, explain how you'd solve problems with your choice of technical stacks
- When do we need a shareable draft? What do people need?
- Rob: when is hard to answer. The work streams don't have roadmap with calendars yet;
- JimJ has questions about account and credential functionality that would benefit from speedy resolution...
- Dedra: We would welcome input on priority of Open Registry features: API, provisioning, etc.
3. Scheduling a standing call
- Who should be invited?
- Original proposal was to alternate weeks with CIFER business and governance using the CIFER-StratOrg call slot (Wednesdays at 3:00 pm Eastern, noon Pacific)
- Or Doodle for a new time?
4. Agenda for another ad hoc call
- Project roadmap reviews (CIFER needs; features & releases)
- Shared schema
- Overall functional model