1. Open Source Policy Community Call 1:00 PM, Eastern Thursday, March 24, 2016 Seong K. Mun, PhD Don Hewitt Arlington, VA

2. Create a Workgroup –https://www.osehra.org/groups/community-response-omb-open-source-policyhttps://www.osehra.org/groups/community-response-omb-open-source-policy Join the Workgroup –Join OSEHRA as an Associate member (Free)Join OSEHRA –Join the Community Response to OMB Open Source Policy Work GroupJoin the Community Response to OMB Open Source Policy Work Group Create a Workgroup Resources –Co-chairs - Volunteers –Section Leaders - Volunteers –Reference Documents –Draft Response Documents –Members Weekly Call Meetings –March 23, March 30, April 7 –Webex url: https://osehra.webex.com/osehra/onstage/g.php?MTID=e421d9648ed46cb9ffc2c3cd29f 103a6fhttps://osehra.webex.com/osehra/onstage/g.php?MTID=e421d9648ed46cb9ffc2c3cd29f 103a6f –Call-in Number: 1-650-479-3207, Access code: 666 433 175 Workgroup Information 2

3. OSEHRA Ecosystem Make the Code Reusable ANSI OS Certification Effective Repository Product Management Shared Vision and Interests Open Collaboration Promote Business Opportunities Marketing and Advocacy IP Management Transparency Decision Making Authoritative & Neutral

4. Discussion: David Wheeler, PhD, IDA How to Respond? Possible Response Topics Schedule Possible Additional Activity Please note: All calls are recorded and contributed documents are all open. Today’s Agenda 4

5. Overall Impression of the Draft – Strengthens – Weaknesses What are the Policy Gaps for OS Adoption? Need for Implementation Guidelines? Other Items David Wheeler, PhD, IDA 5

6. FAR Changes – Eliminate conflicts – Add provisions Specific Acquisition Language – Template in FAR Acquisition and FAR 6

7. Public Domain Code Open Source Code Licensing and Attribution Attribution Requirements – Code developed by Government Employees (personal identification optional) – Code developed under contract – Open Source code IP and Licensing 7

8. Government release of existing code – Attribution – Mechanism for release (FOIA??) New Code – Deliver code as open source? Redaction issues – Deliver to Government first? – Deliver to Community? Or have Government release subsequent to acceptance? Target Organization - Community Code Release 8

9. OS Usability Certification OSEHRA – ANSI SDO Funding needed to develop consensus standard Code Quality and Certification 9

10. Guidelines for community engagement Sustainment Open Collaboration Market Stimulation – FED Agencies – Private Sector Community for Sustainment 10

11. The Best of Both Worlds Productizes Open Source Unix Innovations from Fedora Project Disciplined Product Management Strategic Accretion Maintainability Maximum continuity Release cycle >2 years Provides Customer Support Productizes Open Source Unix Innovations from Fedora Project Disciplined Product Management Strategic Accretion Maintainability Maximum continuity Release cycle >2 years Provides Customer Support Maximum Innovation Proof of concept 6-Month Release Cycle Community Drives Red Hat Sponsored Maximum Innovation Proof of concept 6-Month Release Cycle Community Drives Red Hat Sponsored Fedora Innovation Sponsorship Fedora: Higher-risk, community-driven open source project as innovation incubator. Red Hat: Product management through integration of best-of- breed Fedora innovations. Red Hat engineers participate in Fedora activities to insert innovations “upstream”. Fedora is open source operation supported by Red Hat. Open Source Global Community

12. Commercial Corporations Commercial Corporations Comparing Red Hat, VA & OSEHRA FEDORA Open Source Community FEDORA Open Source Community Red Hat Enterprise Customers Enterprise Customers OSEHRA Open Source Community OSEHRA Open Source Community VA OI&T VA OI&T VHA Commercial Customers Community Driven Focused on Innovation Features and Functionality Free Community Driven Focused on Innovation Features and Functionality Free Product / Patch Management Disciplined Testing Commitment to Long Term Support Stability vs “Leading Edge” Product / Patch Management Disciplined Testing Commitment to Long Term Support Stability vs “Leading Edge” Deployment Subscription to obtain patches Reliant on long term support from distributor Deployment Subscription to obtain patches Reliant on long term support from distributor GOV/Private

13. Product Management 13 Productization Done – Government – Contractor Not By the OS Community

14. Open Source Policy Training Workshop 14 Target Timeframe: Last week of July 2016

15. 1 pm, Thursday Thursday 31 March Thursday 7 April – Last Call Monday 11 April – Due Date for Comments Future Calls 15

16. Adjournment