SO 9-23-11 Meeting Agenda and Notes

OSIdM4HE-Strategy&Org. call, 4pm - 5pm (ET) Friday, 9/23/2011

Participants

 
 
AGENDA

1. Convene

2. Agenda Bash

3. AI review

4. Review and revise action plan put forward by Bill Yock in an email to the list (copied below with inline discussion points from the meeting)

5. Decisions and Preparation for the F2F

6. Public Presence; What to say at I2MM

7. Review New Action Items

  [OSIdM4HEteam:Keith] Post Doodle poll for possible intercalary meeting of S&O Tuesday, Wednesday or Thursday Sept. 27, 28, 29.

______________________
Colleagues,

In thinking about next steps I wanted to outline some of my thinking of action items/deliverables and offer it as input to this afternoon's conference call. Hopefully this will guide when and who can tackle these items. In no particular order...

1) Identify a federation operator and socialize the concept with them. Add details to coord agreement regarding expectations of a federation operator and the management support needed for the coordination committee. One of the first things to do is host a web site / page were the concept and materials can be posted. What other management support will be required? I suspect the Caretakers do a majority of heavy lifting within each module work stream. (i.e. bringing on new contributing members, training resources, etc.)

2) Fill out coord agreement vision section that highlights the overall module development and product strategy. We need to put a stake in the ground around what work streams to spawn, what core code/products to start from, and what major gaps / features to build. For example, Registries, use KIM as base, fold in or modify OpenReg concepts/code for this, fold in Penn State concepts/code for that, etc. For Access Management use Grouper as base, fold in or modify KIM for this, etc. We need to do enough of this type of planning to present a comprehensive solution vision. Of course, the vision may change as we engage in the nitty gritty but it is important to take a first stab for marketing purposes.

DedraC: AlbertWu about to roll out accessMgmt. Could we put calls out to do env. scan.

TomB: UCLA have been developing based on Grouper.

RL"Bob" Registries Team will be developing a project proposal.  

TomB: Process to next milestone: make the pitch & be prepared to respond to queries.  How will we prepare ourselves to questions?

HamptonS: There didn't seem to be recommendations coming forth

Dedra: how do we get the work going?   1) coord committee credibility & gravitas will depend on answers to the questions we expect from outside? How is it led? I don't mean top-down.  Needs to be a combination.  Questions last week were largely looking for clarity about authority, membership,....

We have adequately identified gaps, and good plans to address, credibility through momentum.

TomB: It will be a process, building on the cred that ppl associated with the effort brought. Then continue to bootstrap credibility. Pull together those where we have more influence, e.g. KIM & Grouper.  That can help to get 1st round of success.

Hampton: Help flesh out structure (helped by 4); and fill in details. Personally in favor of fleshing out model

RL"Bob"  concrete opportunity in weeks. Having stuff to pitch there would be great.

3) Rough out a high level Standards and Reference Architecture appendix to the coord agreement. I am thinking 2 page maximum and it may initially be high level principle statements primarily, but at least enough content to get CIO's buying in to the cooperative and collaborative approach to making all the pieces eventually fit together easily.

4) Create a marketing and sales deck oriented to target caretakers and their boards. Enhance the ppt deck we presented last week to beef up the problem statement and value proposition sections. Include additional details on expectations around MOU details. I think it makes sense to get preliminary buy-in from the target caretakers that if the federation takes off that they are willing to play the part.

5) Create a public marketing and sales presentation deck. Remove some of the details of the caretaker deck but highlight the overall concept and orient towards drumming up possible contributing members. Socialize the deck at different events, I2, Educause, Kauli Days, etc. Would need a primary point of contact or mechanism to receive comments and track interest and leads on possible contributing members.

6) Form a start-up coordination committee to pull together an initial set of interested contributing members and rough out the MOU's for each work stream module. Help create a launch plan to initiate the overall effort.

7) Once launched sit back and watch the magic happen!

Regards,
Bill