2. Frameworks To get on the same page word wise To suggest some useful analytic approaches To identify opportunities for integration

3. Some Basic Distinctions Origin Generalizing a campus effort (Kerberos, Signet, Sakai) New, shared development effort (Shib, Globus, Apache, etc.) Commercial to open source (Java, …) Control versus cost Arguments exist on both sides of “open source costs less” Control issues are seen as favoring open source Intra-realm versus inter-realm issues Integration and manageability cut across each piece of software

4. Technical Stack Core Enterprise And Interrealm Plumbing Identity management – Authentication/Authorization and Directories –Kerberos, LDAP Interrealm interactions – SAML and Shib, PKI Data repository – Fedora, DSpace, etc. Platform Layer Operating Systems – Linux, MS, etc Application Environment – Java, Apache, etc Applications Community centric – CMS, listproc’s, Innovative apps - mozilla, Chandler, croquet

5. Policy Issues Licensing Varieties of open source motivation lead to differences Within a motivation, language variations lead to differences Project Management Scoping and functional specs Development model Opportunities for funding and their implications Federal Foundations Commercial sponsors

6. Development Cycle Originators An investment/specification group Early Adopters/Deployers An open source community for maintenance and ongoing work How organized? How supported? Depends, in part, on technical stack issues.

7. Can higher ed capture economies of scale in software creation and maintenance? The $100 Million question… Lifecycle System Costs/ Effectiveness Number Participating Solo Functional Partnership Dysfunctional Partnership ? Capturing Industry Leverage: Learning how to partner Synchronizing institutional investments IT architecture discipline Creating effective consortia Common licensing