NASA Open Source Summit

Solutions to Issue #1: Communication and Publicizing NASA’s Open Source Efforts

Solutions to Issue #1/DAY 2: HOW DOES NASA  OPEN SOURCE EVERYTHING?

Instructions

  • This is the place for all summit participants to propose and discuss solutions to the one issue listed above.
  • Feel free to build on rather than delete what others are saying.
  • Format for Breakout Sessions:
  • Introduce each other with quick, 1-sentence bios
  • Describe the issue to get everyone on the same page
  • Brainstorm solutions
  • Go in-depth with one solution at a time
  • Record notes or your discussions will not impact policy

Notes

  • The full list of issues is here.
  • If you opened this in Edit mode and it’s now Read Only, there are probably too many editors right now (max is 50). In that case, use this supplemental page to capture your solutions to this issue.Notes from all supplemental pages will be moved to the main page for that issue after the summit.

Description of the Issue

[Communication and Publicizing NASA’s Open Source Efforts]

Proposed Solution #1: Portal Page for NASA workers to locate agency Open Source projects

- locate historical and existing OSS communication efforts/projects within the agency

- see what can be re-used or brought into a collaboration

- create a portal page as a “meeting place”

- create wiki-style tools for projects using or creating OSS to fly their flags

Proposed Solution #2: More Contests

More coding contests can provide publicity by demonstrating interesting things that can be done with this model

Proposed Solution #3: Encourage Contractors to follow suit

The contractors are developing and using much of the software involved, and it would benefit NASA’s goals to encourage these groups to participate in their open-source efforts.

Proposed Solution #4: Use nasa.gov/open/source as an entry point

Provide an easy to remember URL as entry point to catalog of NASA OSS projects

Proposed Solution #5: Address the needs of the three main user categories: (1) NASA OSS developers/users (2) General Public interested in NASA and OSS (3) The worldwide OSS developer community

[Description of Proposed Solution]

Proposed Solution #6: Attend conference like OSCON and have OSS from NASA present/participate as a group

[Description of Proposed Solution]

Proposed Solution #7: Be the testbed for/initiator of a federal-wide code repository

Proposed Solution #8: Meetup Group - hosted once every other or third month

Local Meetup groups have a great ability to galvanize community interest

Proposed Solution #9: [Title]

[Description of Proposed Solution]

Proposed Solution #10: [Title]

[Description of Proposed Solution]


Description of the Issue

[Anyone can add to the description of the issue here.]

Proposed Solution #1: [Title]

[Description of Proposed Solution]

Proposed Solution #2: [Title]

[Description of Proposed Solution]

Proposed Solution #3: [Title]

[Description of Proposed Solution]

Proposed Solution #4: [Title]

[Description of Proposed Solution]

Proposed Solution #5: [Title]

[Description of Proposed Solution]

Proposed Solution #6: [Title]

[Description of Proposed Solution]

Proposed Solution #7: [Title]

[Description of Proposed Solution]

Proposed Solution #8: [Title]

[Description of Proposed Solution]

Proposed Solution #9: [Title]

[Description of Proposed Solution]

Proposed Solution #10: [Title]

[Description of Proposed Solution]

HOW DOES NASA  OPEN SOURCE EVERYTHING?

(30 March 2011 @ 1100)

NASA Perspective

Half of the culture is supportive of open sourcing software...the thought is that it is a cultural thing

Q&A

Question -  Has any government entity made the default open source?

Answer - perhaps DOE has an policy of sort that pushes this way.  Sounds like they worked on stuff in the past that they “published” to start the culture.  A gu

Question - Does NASA have the leadership?

Answer - Is yes.  R

Question -

Next Steps

Idea

Curation and then eventual conversion of NASA SW to be considered for OSS release

Develop stuff externally...

Orical...provide the decisoin trip...checklists for ITAR...GSA do that

Recommended Policy

Establish default state that all software will be considered for open source assuming

is open source, you have to justify, you have to recommend a license, and start it down the process of open sourcing - recommended license...include the license

include license, default open source, include a waver.....technology transfer

software requirements specification is key...to convey...a formal..informal ...also include ITAR checklists that engineers provide with software requirements for submission of the concept....

the culture started out sourcing the development and using the results

help explain the software lifecycle for NASA and what it might look for an open source project

<I’LL BE BACK SHORTLY...GOING TO CHOW...WILL CLEAN UP AFTERWARDS>