OSIdM4HE-Strategy&Org. call, 5pm - 6pm (ET) Friday, 12/16/2011
Participants
Who |
With |
Present |
|---|---|---|
Tom Barton |
U Chicago |
√ |
Dedra Chamberlin |
Berkeley & UCSF |
√ |
Jacob Farmer |
Indiana U |
|
Keith Hazelton |
UW-Madison / Internet2 |
√ |
RL "Bob" Morgan |
U Dub / Internet2 |
√ |
Benn Oshrin |
Internet2 / Various |
√ |
Hampton Sublett |
UC Davis |
|
Bill Yock |
U Dub/Rice Board |
√ |
AGENDA
1) F2F planning:
- Figuring out how to engage consultants; what does a DIP plan look like?
- Chris Mackie, facilitation, note taking,....
- BillY: Asked John Lewis from Unicon: still comfortable as a volunteer participant representing JASIG
] Dedra: we each write up our ideas & then work on a consensus view given a draft agenda from Bill:
- differing dev. methodologies
- decision-making, roles & responsibiities
- High-level architecture: prod suite vs. api/integration
- Refining the marketecture; Communications strategy
2) Building suites vs. building standards
- RL"Bob": Both. The only possible way. APIs sans code & functionaliity always fail.
- Benn: The extremes between Bill & me: I'd go the path of understanding use cases to validate the approach we're taking;
- BillT: Modular Reference Architecture and reference implementations & particular solutions; anxious for a community of practice around OSIdM4HE.
- Dedra: concerned that ongoing development & support for what we come up with. If we do our own-to the api-we're still stuck supporting our locally developed software stack
- TomB: Fill the gaps: Registries and provisioning; Interoperability of multiple sets; Wiring diagrams on solving real world problems
- BillT: We want folks to know that they have options to put on the evaluation list up against the monolithic suites.
- BillY: we need to come to agreement on the nature of development efforts that are needed. Roughly speaking, what are the levels of resourcing required.
- BillY: Think about a moonshot, too. Could we accomplish something more significant.
- Benn: This is why we need a clearer picture of the gaps. We need to figure out where the funding would go.
- TomB: One severe gap: Guides, Documentation and Training materials; The How-Tos; there are capabilities that are missing--person registries; there is missing knowledge about how to integrate things that are already out there
- Dedra: We also want to be able to tell decision makers that there are commercial vendors/affiliates
- Benn: Before F2F, take a stab at the more concrete gap analysis.
3) Another public statement like our Sept. 16th one.
- Just a heartbeat; updates, PSU code, other developments, UC Davis, UCB/UCSF ptiching in; "we're working on the DIP"
4) Next meeting, Friday, Dec. 30, 2 hours: 4 - 6 pm EST; OSIdM4HE "All Hands" call.; Meanwhile: Use the tools: Email & Wiki to keep up the momentum.