Event: Free & Open Source Software in Government

[jthalls]

Free & Open Source Software in Government

Date: Tuesday, May 8, 2018 Summary (one sentence) — text goes here

Description (min ~200 words) — 

Join the Code.mil team for a discussion on open source in government and a look at the important work they've been doing on Code.mil to enable greater adoption of open source at the DoD.

They will cover:

• What is open source and why is it so important?
• How can open source code reduce risk, cost and time to delivery?
• A look at common myths of open source in government

The Code.mil team will give an overview of the recent refresh of Code.mil where it’s possible to contribute code and see it go live almost immediately! This refresh empowers the DoD to accelerate open source participation across government and improve open source guidance.

About Code.mil

In February 2017 the Defense Digital Service (DDS) started a conversation with the Free and Open Source Software (F/OSS) community on how the DoD could better open source code. That dialogue produced a lot of guidance on how the DoD can open source projects, but the information was all on GitHub and not very accessible.

Proposed Topics

• Define the free & open source software movement.
• What is the goal of Code.mil? How does it tie into the larger view of open source software in government?
• Why should government employees be concerned about moving their code to the public domain? Who cares?
• Isn't it a lot of "busy work" to open source software? How will this help govies do their work better?
• What about security? Doesn't releasing our source code to the world open up critical US infrastructure to malicious attacks?

Speakers

• Ari Chivukula: Policy wrangler working with the US Digital Service team at Department of Defense in cloud security, cyber warfare, and open source.
• Jordan Kasper: Evangelist, developer, community organizer, open sourcer (and he's been called worse). Currently improving tech at the US Digital Service.

---

• [x] 30min meeting w/ presenters
• [x] Send calendar invite once event date has been determined
• [x] Request video title card
• [x] Create event in Eventbrite
• [x] Create event in YouTube live https://www.youtube.com/watch?v=4ulaWNBDPgk
• [x] Post event page on DigitalGov https://digital.gov/event/2018/06/05/free-open-source-software-in-government-with-codemil/
• [x] Schedule emails through Eventbrite
• [x] Schedule real time captioning through FedRelay http://www.fedrcc.us//Enter.aspx?EventID=3661193&CustomerID=321
• [x] Identify moderator for live chat/online questions and send moderator script
• [x] Schedule tech check with presenters to review online platform and logistics of event
• [x] Work with DG team to promote via Social Media platforms
• [x] Track registration and provide event partner weekly registration updates
• [x] Set up evaluation in Google Forms and share with POC
• [x] Update metrics spreadsheet
• [x] Schedule post event/training retro
• [x] Add title card immediately following event
• [x] Send post-event email with link to video, evaluation, and any additional resources
• [x] Share evaluation results with event partner and presenters
• [x] Conduct retro

[cygov]

Revised Questions for Open Source @ Digital Gov

Anticipated date of filming

• May 8, 2018 2pm

  Participants

  Code.mil @ DDS:

• Ari Chivukula (Policy Wrangler)
• Jordan Kasper (Digital Services Expert)

  Code.gov @ GSA

• Alvin Salahey (Director, Code.gov)

  Questions

  When was the initial launch? What's happened since Code.mil launched? In February 2017 the Defense Digital Service (DDS) started a conversation with the Free and Open Source Software (F/OSS) community on how the DoD could better open source code. That dialogue produced a lot of guidance on how the DoD can open source projects, but the information was all on GitHub and not very accessible.

This relaunch of Code.mil provides an easy-to-navigate website with clear guidance through checklists and links dynamically fitted to the needs of a given project. DDS was motivated by the volume of emails and calls received on a weekly basis from the outstanding military and civilian DoD personnel who were developing code and sought to participate in the F/OSS community. They wanted to use open source tools and to share what they’ve worked on: within the DoD, across the federal government, and to the broader developer community.

Code.mil is also working to inventory custom developed code across the Department, a requirement of OMB policy (M-16-21), in conjunction with the Code.gov team.

What has your team learned about open source at the DoD this past year? We’ve learned a lot by talking to service members, program offices, and contractors across the DoD excited about participating in the F/OSS community. The main problems they run into are the shortage of practical guidance on how to open source code and the lack of visibility around existing open source projects.

What's next for Code.mil? DDS will continue to field questions from programs across the DoD and improve guidance on how to open source code. We’re also working on refining source code policies within the DoD in conjunction with the CIO’s office.

Does DDS open source any code? DDS maintains the U.S. Dept Of Defense GitHub organization, which we use to share our work as well as some other DoD projects looking for help getting their code online.

Is this an agile development? If so, what's the next iteration and timeline? Absolutely! We’re firm believers in agile development as it enables rapid reaction to the changing needs of our community. Everyone is encouraged to check out Code.mil and join the conversation on GitHub to help shape our direction. It’s also possible to contribute code and, after review, see it go live almost immediately! This refresh empowers the DoD to accelerate open source participation improve open source guidance.

How does this help DOD meet the latest open source requirements included in the 2018 NDAA? The Open Source Pilot Program established by OMB policy (M-16-21) is directly referenced in the 2018 NDAA. The NDAA instructs DoD to begin implementation of this pilot program. Code.mil is working closely with the DoD CIO and Code.gov, the OMB team that facilitates compliance, in inventorying DoD’s open source projects and refining DoD source code policies.

Next steps:

• Talking points, build out into different buckets - @cygov, @arichiv-usds, @jordangov
• Support contacting Alvin & Code.gov team @ GSA - @jeremyzilar
• If unable to participate, consider which Listserv(s) would be best suited to find a stand-in - @AndreaSigz
• Set a time on 4/19 or 4/20 for Jeremy, Andrea, and @jthalls to meet Ari & Jordan

[cygov]

Notes (4/20/18):

• high-level "myths" about open source which we can address early on in the conversation.
• goal is to produce a video we feel comfortable embedding as a tool to sell our audience on open source in government.
• aim for 30 minutes.
• DDS to sync about key messages to highlight around Code.mil.
• consider Code.gov perspective, makes more sense for them to be looped into an ongoing conversation on this topic (perhaps second segment as a follow-on).

[cygov]

DDS Presentation

May 8, 2018 - GSA - 1400

@arichiv-usds & @jordangov Presentation (15 minutes)

• What is Code.mil?
• The value of open source software in government
• -Reusability
• -Security
• Success stories
• -ANET
• -SE Linux

Audience Q&A: Moderated by DigitalGov (10 minutes)

Potential topics to highlight in absence of strong audience participation (@jeremyzilar, @AndreaSigz, @jthalls):

• Advice for those within DoD who want to open source their code, but are receiving pushback?
• How can we better arm our allies within DoD with the guidance and policies they need to push through the bureaucracy and open source their code?

@reinastaley, DDS Chief-of-Staff, for awareness.

[SoncerrayBolling]

@jeremyzilar Did you reach out to schedule a retro for this, or would you like me to? If not, we can close the issue.

[thisisdano]