NASA Open Source Summit

Solutions to Issue #4: Barriers to Development Models and Ongoing Support

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(s)

How do we ensure that “open-ness” does not conflict with rigor?

How narrow should the definition of “development team” be, and when?

Proposed Solution #1: Get folks with passion for a project involved, even if they’re not formally assigned to that project

Proposed Solution #2: Identify limitations/regulations for collaboration internal and external to an Agency, Center, Organization, Program or Division

[Description of Proposed Solution]

Proposed Solution #3: “Bug Bounty” program

Some organizations pay developers to fix bugs in open source software, particularly bugs related to security. NASA could have a similar program to encourage developers to work on issues that are important to NASA.

Proposed Solution #4: Pay NASA employees to develop open source software that would be useful to NASA; in a way, pay for an open source product by paying employees to develop it.

[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]