8/6/2019 NASA Open Source Summit Proceedings
1/85
0
8/6/2019 NASA Open Source Summit Proceedings
2/85
1
Contents
Introduction.................................................................................................................................................3
Overviewofevent........................................................................................................................................4
Analysisofinputcollected...........................................................................................................................5
MajorIssuesandRecommendations...........................................................................................................6
Issue#1:CommunicationandPublicizingNASAsOpenSourceEfforts..................................................6
Issue#2:Licensing...................................................................................................................................6
Issue#3:BarrierstoInvolvementfromtheOpenSourceCommunity....................................................8
Issue#4:BarrierstoDevelopmentModelsandOngoingSupport..........................................................9
Issue#5:GovernmentRestrictions..........................................................................................................9
Issue#6:LimitationsonContributingtoExternalOpenSourceProjects..............................................10
Issue#7:HowdoesOpenSourcegovernancelookwithinNASA?........................................................10 Issue#8:HowshouldOpenSourceEffortsBeSupported?...................................................................11
Issue#9:HowdoesNASAopensource*everything?*..........................................................................12
Issue#10:Howtoclosethefeedbackloopbetweenpolicymakers,developersandendusers?........13
Issue#11:Howtoencourageculturalchangeinhiringpractices?........................................................14
Issue#12:HowtoPackageOpenSourceSoftwaretobeMoreAccessible...........................................14
Issue#13:CombiningopensourcesoftwaredevelopmentstandardswithOfficeoftheChiefEngineer
Policies...................................................................................................................................................15
UnansweredIssues:...............................................................................................................................15
Appendix....................................................................................................................................................16
ParticipantList.......................................................................................................................................16
In-PersonAttendees..........................................................................................................................16
RemoteAttendees.............................................................................................................................21
Press...................................................................................................................................................43
Staff....................................................................................................................................................43
AgendaandSchedule............................................................................................................................45
Day1March29,2011.....................................................................................................................45
Day2March30,2011.....................................................................................................................46
KeynotePresentations...........................................................................................................................47
ExcerptsfromUstreamChat..................................................................................................................48
Tuesday..............................................................................................................................................48
8/6/2019 NASA Open Source Summit Proceedings
3/85
2
Wednesday........................................................................................................................................52
UserVoiceSubmissions..........................................................................................................................55
Communication/PressSummary...........................................................................................................83
8/6/2019 NASA Open Source Summit Proceedings
4/85
3
Introduction
OnMarch29&30,NASAhosteditsfirstOpenSourceSummitatAmesResearchCenterinMountain
View,California.TheeventbroughtengineersandpolicymakersfromacrossNASAtogetherwithwell-
respectedmembersoftheopensourcecommunitytogethertodiscusscurrentchallengeswithNASAs
opensourcepolicyframework,andproposemodificationsthatwouldmakeiteasierforNASAto
develop,release,anduseopensourcesoftware.
OpensourcebringsnumerousbenefitstoNASAsoftwareprojects,includingincreasedsoftwarequality,
reduceddevelopmentcosts,fasterdevelopmentcycles,andreducedbarrierstopublic-private
collaborationthroughnewopportunitiestocommercializeNASAtechnology.Thisinherently
transparent,participatory,andcollaborativeapproachisrevolutionizingthewaysoftwareiscreated,
improved,andused.
AlthoughopensourcereleasehasalreadyprovidedsomeofthepotentialbenefitstoNASA,thefull
benefitsofopensourcecanonlyberealizedifNASAisabletoestablishtheprocesses,policies,and
cultureneededtoencourageandsupportopensourcedevelopment.Thiswillrequireexpandingopensourceactivitiesbeyondreleasingsoftwareonlyaftercompletionandfindingnewwaystosupporttwo-
waycollaborationwithanopendevelopmentcommunitythroughouttheentiresoftwarelifecycle.
ThisdocumentprovidesasnapshotoftheactivitiesduringtheOpenSourceSummitandsummarizesthe
majorissuesandrecommendationsreceivednotonlyfromthein-personattendees,butalsothrough
thevariousonlinevenuesutilizedduringtheevent.
8/6/2019 NASA Open Source Summit Proceedings
5/85
4
Overviewofevent
TheOpenSourceSummitwasmodeledafterthepopularOpenGovCommunitySummitsthatwereco-
hostedbytheDOT,USDA,NASA,Treasury,EPA,andGSAthroughout2010.CalledaFocusForum,the
formatoftheOSSwasgearedtowardinnovatingnewthinkingandcapturingsolutionsonaspecific
topic.Attendeeswereencouragedtoengageinconversationandshareideasaswellasparticipate
digitallyinvariousonlinevenues.
AttendeesheardfromavarietyofstakeholdersintheOpenSourcecommunity,includingtheDoD-
affiliatedInstituteforDefenseAnalysesDavidWheeler,IBMsBobSutor,GooglesChrisDiBona,and
GitHubsChrisWanstrath.Additionally,anumberofleadersofNASAsopensourceeffortspresented
theirprojectsandsharedtheirexperiencesworkingwithinthecurrentsoftwaredevelopment
constraintsattheagency.Targetedbreakoutsessionsoccurredbetweenspeakerpresentationsthat
addressedanumberofcriticalissuesandgatheredideasforpotentialsolutions.
Abreakdownoftheeventsagendaandbreakoutsessiontopicsmaybefoundintheappendix.
8/6/2019 NASA Open Source Summit Proceedings
6/85
5
Analysisofinputcollected
IdeasandinputwerecollectedattheOpenSourceSummitthroughavarietyofmethodsthatincluded
participationfrombothparticipantsphysicallyattheeventandremoteparticipantsviaonlineplatforms.
Fivecommunicationvehiclesfordiscussionwereused:GoogleDocs,Ustream,UserVoice,Twitter,and
Maestro(avirtualteleconferenceplatform).Eachplatformservedadifferentpurposeandaudience,
withmanyparticipantsusingmultipleservicessimultaneously.
GoogleDocs
GoogleDocswasprimarilyusedbyparticipantsasatooltotakenotesandwritedownproposed
solutionstotheissuesraisedattheeventandservesasthemostsubstantialdocumentationofthe
event.Twenty-threedifferentdocumentswerecreatedandsharedwiththepublic,eachcoveringa
separatetopic.Fromthesetopics,66proposedsolutionswereoffered,afulllistingofwhichisofferedin
theMajorIssuesandRecommendationssection.
Ustream
Ustreamwasusedbyremoteparticipantstowatchlivevideoofkeynotespeakersduringtheevent.Additionally,anextensivechatroomwasformedwhereparticipantsdiscussedmanyaspectsofthe
event(seeUstreamChatintheAppendix).Therewereacombinedtotalof2,315viewsonUstream
throughouttheevent.
UserVoice
UserVoice,anideationtool,wasusedtorecordandvoteonspecificactionsorideasduringtheevent.
Forty-sevenuniqueideaswerepostedonUserVoiceandattractedatotalof638votesand125
comments.AfullrecordofUserVoiceactivityislocatedinthe UserVoiceSubmissionssectioninthe
Appendix.
Twitterwasalsousedextensivelybyparticipantstocommunicateusingthehashtag#NASAOSS.Over
1,250tweetswererecordedoriginatingfromtheevent,reachingover3millionpeople.
Maestro
Maestrowasusedasateleconferencetoolforremoteparticipantswhowishedtotakepartinvarious
breakoutsessions.SixtyparticipantsusedMaestroattheeventforatotalof2,578minutesofcalltime.
Asynthesisoftheinputcollectedthroughalltheabovetoolsislocatedinthe MajorIssuesand
Recommendationssection.
8/6/2019 NASA Open Source Summit Proceedings
7/85
6
MajorIssuesandRecommendations
Issue#1:CommunicationandPublicizingNASAsOpenSourceEfforts
InorderforanOpenSourcepolicytobesuccessful,NASAmustmakeanefforttoencourageboth
internalandexternalpartiestoparticipateinopensourcedevelopment.Whatdoestheagencyneedto
doinordertomakeNASAsopensourceeffortswellknown?
Proposedsolutions:
1. PortalpageforNASAworkerstolocateagencyOpenSourceprojectsCreateanonlineportalwithhistoricalandexistingopensourceprojectswithintheagency.The
portalshouldhavewiki-styletoolsforprojectstoassistwithcollaborationandpublicity.Perhaps
expandingthistobeanentireforgerepository,similartoForge.mil.Thiscouldbeaplatform
tobaseanentirefederal-widecoderepositoryon.
2. MoreContestsUtilizecodingconteststodrawpeopleintoworkonopensourceprojects,similartoGoogles
SummerofCode.Rewardscouldincludecashprizes,publicity,orsimplytheprospectof
adoption.
3. EncourageContractorParticipationNASAwouldbenefitfromincreasedcontractorparticipationinopensourceactivities,perhaps
byrequiringsoftwaredevelopedundergovernmentcontracttobereleasedasopensource
softwarebydefaultunlessrestrictedbyexportregulationsorothersecurityrestriction.
4.
DefinemainusercategoriesNASAopensourcedevelopers,generalpublic,worldwideopensourcedevelopercommunity,
sciencecommunity.
5. AttendadditionalOpenSourceconferencesOSCONwasdiscussedasavenueforNASApresentationsorparticipation.
6. CreatemonthlymeetupgroupsMonthlylocalmeetups(perhapswithbi-monthlynation-widephonetagups)wouldgalvanize
communityinterest.
7. CreateaCommunityManagerposition
Someonetoensurethecommunityishealthy,researchnewinitiatives,runtopcoder
competitions,unconferences,andcode-a-thons.
Issue#2:Licensing
TheNASAOpenSourceAgreementlicense(NOSA)wasoriginallydevelopedin2003toenableNASAto
providesoftwareinsourcecodeformtothepublic,butsoftwaremustalreadybeconsideredcomplete
8/6/2019 NASA Open Source Summit Proceedings
8/85
7
priortopublicrelease.Thisprecludestheabilitytodevelopsoftwareiterativelywithotheragenciesand
thepublic.Inordertoparticipateintheopensourcedevelopercommunity,NASAneedstobeinvolved
inthedevelopmentprocessfromthebeginning.
Therearetwoissuesthatneedtobeaddressed:
HowdoesNASAlicensethecodeitdevelopsinternally?ShouldituseNOSAordropit?Whydoessuchcodeneedtobelicensedatall?Shouldntitbepublicdomain?
Whatlicensesareconducivetogovernmentagenciesusingnon-governmentcode?Forthosethatarentconducive,thegovernmentneedsamodelforusingthoselicensesinawaythat
makeslawyershappy.
Proposedsolutions:
1. DropNOSAinfavorofexistingmainstreamopensourcelicensesAlthoughinnovativewhenfirstdevelopedoversevenyearsago,NOSAisnotawell-received
licenseintheOpenSourcecommunityandthepurposeforitsdevelopmentnolongerexists.
NASAsoftwareshouldbereleasedunderwhatevermainstreamopensourcelicensemakes
sensewithinthedevelopmentenvironmentitisbeingreleasedwithin.Further,re-license
softwarethatwaspreviouslyreleasedunderNOSAusingoneofthemainstreamopensource
licenses.
2. Createapolicyandlicensingforunfinishedorin-progressdevelopmentTheNOSAwascreatedforreleasingsoftwarethatiscomplete.NASAneedsapolicythat
addresseslicensingoptionsforiterativesoftwaredevelopmentwithacommunitythatincludes
non-NASAworkforce.
3. Beawareoflicensedsoftwarewithinotheropensourcesoftwarecoveredbyadifferentopensourcelicense
Anopensourcesoftwarepackageoftenwilllistonlytheprimarylicensebutmayinclude
modulesfromothersourcesinitsdistributionthatarecoveredunderadifferentlicense.Source
codefilesmayrevealadditionallicenses,aswellasoriginalcopyrightholders.
4. ApproveasubsetofOSI-approvedlicensesforNASAuseReviewandapproveasetofmainstreamopensourcelicenses(BSD,MIT,GPL,Apache,etc.)that
canbeusedtolicensepublicly-releasedNASAsoftwaresothatsuchareviewdoesnothaveto
beperformedforeachreleaseofNASAsoftware.
5. ProvideaonestopshopforNASAguidancewithregardstolicensingopensourcesoftwareProvideacomprehensivesourceofthecurrentregulationsandrestrictions.CreateaFAQthat
canbeusedtoexplainhowdifferentlicensesmayimpactthereleasesoftware.
8/6/2019 NASA Open Source Summit Proceedings
9/85
8
6. DefineNASArequirementsforContributorLicenseAgreements(CLAs).Currently,inordertoacceptandusethird-partycontributions,aCLAisrequired.Yahoo!Is
currentlyusingHarmonyCLAswhicharebroadlyaccepted.OthersincludeFedoraCLA,GNU
Contributoragreement,andDARPAF6.
Issue#3:BarrierstoInvolvementfromtheOpenSourceCommunityAsagovernmentagencyboundbysignificantregulationandbureaucracy,whatarethelimitsof
communitycontribution?Forexample,couldaNASA-originatedcodebaseeverbehandedovertoa
non-NASAcommunitymemberforlong-termsupportandmaintenance?Isthislegal?Ifitwerelegal,
woulditbepractical?
Thingstoconsider:
OpenSourcedevelopersshouldnotbeconsideredfreelabor. Youneedtohaveamutualbenefitinorderforpeopletohavemotivationtocontribute. Project/missionneedsmustbebalancedwithcommunityneeds. Licensecompatibilityissuesareabarriertoopencontributionanddistributionofcode. IfNASAhastheNOSA,butprojectcontributorstakepatchesfromthecommunitywithout
requiringcopyrightassignmentpaperwork,itshort-circuitstheintentionoftheNOSA.People
aregoingtoroutearoundtheproblemofoverlyrestrictivelicensesinpractice.
Peopleneedtolearnaboutthecodebasebeforetheycancontribute. Openingthingsupearlyandacceptingcontributionswouldbebetterthantryingtoopenthings
uplater.
NASAasanagencyhastocometotermswithlettinggoofaprojectandturningitovertothecommunityinorderforthecommunitytothrive.
NASAhasaslewofexcitingprojects,butisladenwithbureaucraticprocessesanddelays.
PotentialSolutions:
1. HaveNASAengageopenlywiththeOSScommunityUsingandfindingengagementinOSScommunitiesisagreatwayofdrivingexpertiseinward.
NASAteamsarealreadyusingDrupal,Django,Plone,Zope,PostgreSQL,Apache,memcache,
Trac,SVNandmanyothers.However,thereisaneedtoincentivize(oratleastexplicitly
encourage)involvementwithopensourcecommunities.HowdoesNASAcontributewithout
implyingendorsementofatechnologyorproduct?
2. UseexistingopensourcedevelopmenttoolsUsingproprietaryorinternaltoolsinthedevelopmentofopensourcesoftwarecanlimitthe
numberofdeveloperswhocanparticipate.Softwaretoolsneedtoencourageopensource
participation.Forexample,usingSubversiontomanagesourcecontrolisabarriertoentry
becauseanopensourcedevelopercannotcommittoaSubversionrepositorywithouthaving
commitaccess.Usingadistributedversioncontrolsystem(DVCS)suchasGit,Bazaar,or
Mercurialallowsdeveloperstofreelycommittohisorherowncopyofanopensourceproject
8/6/2019 NASA Open Source Summit Proceedings
10/85
9
andallowsforNASAtomoreeasilyselectwhichcommitsitwantstointegrateintoaversion
specializedformissionuse.
3. MakemailinglistsandinternalcommunicationpublicAlargepartofthedevelopmentofopensourcesoftwareishavingaccesstocommunication
relatedtoitsdevelopment.Useseparate,publicmailinglistsforeachopensourceprojectat
NASA.SetupWikisanddocumentrepositoriestohostdesigndocuments,requirementanalyses.
Orbetter,hostNASAopensourceprojectsonpublicrepositoriessuchasSourceForgeand
GitHub.
4. Describehowdeveloperscancontribute(andfollowthrough)Eachprojectshouldcreateapublicfacingwebpagethatdescribestheprocessofcontributing
changestoopensourceprojects.Activelyworkwithdeveloperstogettheircontributions
committedtothemainrepositoryandrespondpromptlytoquestionsonmailinglists.
Issue#4:BarrierstoDevelopmentModelsandOngoingSupport
Howdoweensurethatopen-nessdoesnotconflictwithrigor?Hownarrowshouldthedefinitionof
developmentteambe?
ProposedSolutions:
1. Getfolkswithpassionforaprojectinvolved,eveniftheyrenotformallyassignedtothatproject
Thosemotivatedbypassiontendtodofantasticwork.Openforumsforsuggestionstendtoget
greatideas.Attimes,itmakessensetoborroworlendteammemberstocontributetoother
projectstheTEAMwinsintheend.
2. BugBountyprogramSomeorganizationspaydeveloperstofixbugsinopensourcesoftware,particularlybugsrelated
tosecurity.NASAcouldhaveasimilarprogramtoencouragedeveloperstoworkonissuesthat
areimportanttoNASA.
Issue#5:GovernmentRestrictions
Howtowemeshopensourcesoftwarewithdecidedlyun-openpoliciessuchasITAR?
ProposedSolutions:
1. ClearlydescribeapplicablelegalitiesToassistthepublicwithunderstandingapplicablegovernmentregulationsand/orcontractual
obligations,eachprojectcanwriteadocumentthatoutlinesthelegalissuesthataffectthe
8/6/2019 NASA Open Source Summit Proceedings
11/85
10
project.
2. SpecifywhoownswhatTrademarks,intellectualresources,copyrights,patentsWhichorganizationorpersonowns
which?
Issue#6:LimitationsonContributingtoExternalOpenSourceProjects
Whatarethedifferencesbetweencontributingminimal,incrementalimprovementsorbugfixesand
newfeatures(asperNPR2210.01)?And,whomakesthisdecision?Whatlessonslearned/best
practicescanbedrawnfromcurrentNASAopensourcedevelopmentpathfinderprojects(andcan
thesebeappliedgenerally)?WhatshouldbethepolicyofNASApersonnelcontributingintheiroff-
hours?Howdoyouhandle/treatsituationswherepeopleworkoff-hoursonthingsthatderivedirectly,
orareinspired,bywhattheyworkedonduringdutyhours?
ProposedSolutions:
1. Clarifyexistingpolicyand/orrestrictionsoncontributingtoopensourceprojectsGiventheissuesstatedinthedescriptionandageneralsenseofconfusion,andaprevailing
attitudeofaskingforgivenessiseasierthanaskingpermission,NASAneedstoclarifywhatthe
existingpolicymeansforsoftwaredeveloperswhowanttocontributetoopensourcesoftware
projectsthatmayormaynotalsobeusedwithinNASA.Publishthisinformationprominently
onlineandmakeitwidelyavailable.Simple,unambiguouslanguagewithoutalotofcaveatsis
critical.
2. Agency-wideblanketauthorizationcoveringcontributionstoexternalOpenSourceSoftwareTheagencycouldcreateablanketagreementpermittingcontributionstoopensourceprojects.
Thiswouldbegreatlypreferabletohavingone-offcontributoragreementsforindividual
projects/contributions.Thismayrequireanincrementalimplementationgivencurrentcontract
language,contractoragreements,etc.
Issue#7:HowdoesOpenSourcegovernancelookwithinNASA?
Therecurrentlyisalackofinformationandawarenesstowardslicensing,legalissues,andactivityintheopensourcesoftwarecommunityatNASA.Howdoesonereceiveguidanceonopensource
contributions?Whatdoestheprocesslooklike?
ProposedSolutions:
1. Createasinglepointofcontactforopensourceinformation/governanceThereshouldexistonecentralpointofcontactandprocesstoinitiateanopensourceprojectat
8/6/2019 NASA Open Source Summit Proceedings
12/85
11
NASA.Shouldbesimilarto508orITARreps.Theprocessshouldbeshort,non-legalese,and
makesense.
2. CreateanOpenSourceReviewBoard(communityofpractice)Createagroupofsubjectmatterexpertswhoarenotresponsibleforreviewingeverylineof
code,butwhocanactasresourcesforansweringquestions,recommendingpolicyguidelines,
etc.Shouldhavetechnical,legal,andpolicyknowledge(IBMuses1/3attorneys,1/3technical,
1/3management).
3. Limitapprovaltimeto1week(onaverage)Developanewstructuretorunwith5pilotprojectstowalkthroughthenewprocessandtryit
out.Itdoesnthavetobeperfect.
Issue#8:HowshouldOpenSourceEffortsBeSupported?NASAneedstodevelopcooperativesupportintoprojectstructure
ProjectLevel-permittingcodedeemedoutsidethepurviewofITAR/EARtobeopensource BudgetLevel-allowingforhiringoffloatingtalentastemporarystaffaugmentation OrganizationLevel-designingorganizationtosupporthabitsandpracticesofopensource
development
ProposedSolutions:
1. AssistwithwaystogetfinancialsupportProvidedirectoryofpossibleresources,including:
a. Consortium/Forummembershipb. Standardsgroupsc. Identifyingsponsors
2. OfferNon-FinancialResourcesProvidevarioussupportmechanisms,including:
a. Unittestingb. Documentationc. Bugfixesd. Securityvalidation
3. Conveneconversationswithorganizationexpertsontheappropriatemanagementandorgstructuresforsupportingopensourceapproaches
Tosustainopensourcepolicyandpracticesoverthelongrun,weneedtothinkthroughthe
organizationalandinstitutionalstructuresthatsupportthistypeofcooperativeinteractions.
Materialexistsonhowtorunasuccessfulopensourceprojectandwearegenerallydiscussing
8/6/2019 NASA Open Source Summit Proceedings
13/85
12
opensourcepolicy.Butprojectsandpolicyexistwithinanorganizationalframeworkandopen
sourceprojectswithingovernmentmusthappenwithintheagencyslegacyorganizational
structures.
Issue#9:HowdoesNASAopensource*everything?*
ProposedSolutions:
1. ImplementaDefaultOpenSourcedurationoncodeThereisagrowingincentivetoopensourceeverything.Isthistherightpathtotake?Howdoes
thisfitintoITARissues? Movingtodata-drivenapproachesallowsthesoftwaretobegeneric
andexportable,andthequalityofthedataloadedintoitdetermineswhetheritisITAR.Open
sourceprojectsareonlyusefulwherecodecanbegeneralizedtosolvemanyproblemsformany
people.
Small-but-usefultoolsnotdevelopedinaccordancetoNPR7150.2Aareprobablynotavailable
foranykindofpublicrelease.Shouldthesebeconsideredaswell?
2. NASAOpenSourceSoftwareRepositoriesNASAcouldmakeuseoftwoagency-widesource-coderepositories(GitHuborsomething
similar).AllowtheNASA-wideopensourcingofprojects,includingpotentialITAR/EARones,
tobesharedonthisrepository.Theexternal(publiclyaccessible)repositorywouldbeahome
forthoseprojectsthatcontainnoITAR/EARissues.InconjunctionwithProposedSolution#1,
nonITAR/EARNASAsoftwarecouldgraduatetothislocationafteritsOpenSourceDurationis
reached.
3. EstablishrequirementspriortostartofprojectProposedsoftwareprojectsshoulddescribetheproposedfunctionalityandrequirementsso
thatapreliminaryITARreviewcanoccur.ITARissuescanbeforeseenbasedonproposed
functionality.
4. NewprojectsshoulddeclaretheirlicenseandgetcontributoragreementssignedWhenanewprojectstarts,itshouldbedeclaredsomethingthatcan(orcannot)beshared
openly;ifnot,properjustificationforclosingshouldbeprovidedanddocumented,ideallywith
waysofhowtomaketheprojectopen-able(e.g.,componentizeintoopenandclosedportions)
5. Acceptanceofnon-licensedcommunitycodeMuchsoftwareisopenlydevelopedandfreelysharedbythescientificcommunity.Unfortunatelythissoftwareisoftennotreleasedunderanylicense.ThisrequiresNASAto
obtaincopyrightreleasesfromeveryoneinvolvedinitsdevelopmentinordertoredistributeit
aspartofaNASAprojectrelease.Determiningwhohastouchedthiscommunitycodeisoften
verydifficult. Ifthecommunityisfreelydistributingcodewithoutregardforcopyright and
licensingissues,thenNASAshouldbeallowedtofollowsuit.
8/6/2019 NASA Open Source Summit Proceedings
14/85
13
Issue#10:Howtoclosethefeedbackloopbetweenpolicymakers,developers
andendusers?
Howdoweensurethatdraftpolicieshaveenougheyesonthem,particularlyfromthepeoplewhomay
bemostaffectedorwhohavethemostdetailedknowledgeofthoseareas,andwhocanthusbest
understandtheimplications?Policiesshouldnotputanyoneinthepositionofperformingthemission
byviolatingthepolicy,oradheringtothepolicyandtherebyreducingtheeffectivenessorinducingthe
failureofthemission.Manytimes,ourpoliciesderive(oraresimplycopied)fromFederallaw,
regulation,guidanceor,morecommonly,fromthepoliciesofotheragencies.Effectivefeedback
providesopportunitiestomodifyoradjustpolicybasedonpractical,realisticfeedback.Arewetaking
advantageoftheseflexibilities?
PotentialSolutions:
1. ExperimentwithopenpolicyreviewsonlineInsteadofperformingrelativelyclosedreviewsofdraftpolicy,placedraftpoliciesonlinewhere
eachindividualparagraphofthedraftpolicycanbecommentedonbyanyonewithinNASA,and
perhapsthoseoutsideofNASA.Thosecommentscanthenberespondedtoonlineand
explanationsgivenforwhyaparticularcommentwasaccepted,rejectedorre-written.This
wouldallowthoseforwhomapolicywillaffecttoprovideaccurate,morerelevantanduseful
feedbackonimplicationsandissueswitheachportionofadraftpolicybeforeitbecomescastin
stone.
2. ReversethepolicydevelopmentprocessPolicywrittenattheagencylevelmayoftenbewrittenbythosewithlittleornodirect
experienceintheareaswherethenewpolicywillapply.Wherepossible,havecommunitiesthat
willbeaffecteddevelopthepolicy,andhavetheAgencyorganizationsthatwouldnormally
writethepolicyserveasreviewersofit.Thismaynotworkforallpolicies,butforsomewouldit
bepossibletoprovidethepurposeofanewpolicy,thelawsandregulationsthatconstrainthescopeorreachofthenewpolicy,andallowthecommunitytodevelopthenewpolicytomeet
thoserequirements?Doingsowouldlikelyreducebadpoliciesthatcreateunnecessary
obstaclesandwastetimeandresourcesinworkingaroundthem.Thingswewouldneedto
determinefirst:
WhowritescurrentpolicieswithinNASAforITandotherareas? Whatistheprocessforreviewingdraftpoliciesbeforetheyareimplemented? Whoreviewsdraftpolicies,andaretheyversedintheareathepolicyappliesto? Howdoessomeonegetaccesstothecommentsthatarefedbackduringthereview
process?
Howdoweknowthatdraftpoliciesarereceivingthoroughreviewsgiventhateveryoneseemsoversubscribedalready?
IsthereamechanismforanyonewithinNASAtoprovidefeedbacktodraftpolicies? Howdoessomeonewhoprovidesfeedbackknowthatthefeedbackisbeinglookedat? Aretheirculturalbarrierstoprovidingfeedback? Whataretheorganizationalbarrierstoprovidingfeedback? Howtotrackthateachsectionhasbeenreviewedbyappropriatestakeholders?
8/6/2019 NASA Open Source Summit Proceedings
15/85
14
Howoftenarepoliciesupdated?Whatconstitutestheneedtoupdateapolicy(whatisthepolicyforupdatingapolicy)?
Issue#11:Howtoencourageculturalchangeinhiringpractices?
HowcanNASAattractmoreopensource-savvypeopleinaworldwherecompanieslikeRedHat&
Googleoffercareersthatencouragesuchparticipation?NASAiscompetingagainstthesecompaniesforthesameskills.
PotentialSolutions:
1. HighlightNASAsOngoingopensourceparticipationDoabetterjobofmarketingNASAscurrentOSSparticipation
MakeHeroesandRockstarsoutofNASApersonnelworkinginOSS GetthesepeopleoutonOSSspeakingcircuits(evangelists)
2. StreamlinetheProcesstoParticipateinExternalOSScommunitiesAllowa20%timeforindividualstocontributeto/participateinOSScommunitiesonNASAsbehalf
3. ProposedSolution#3:Allowforremote/distributedworkDontlimityoursearchforOSStalenttojustlocations/centersthatNASAhasaphysical
presencein.Tapintouniversityprogramsandotheracademicinstitutions,etc.
Issue#12:HowtoPackageOpenSourceSoftwaretobeMoreAccessible
Collaborationonopensourcesoftwareisdependentonotherswhofindthesoftwareuseful.Thebarrier
foradoptionofOSSmustbekeptlow.Thisalsopreventstheprojectdyingonthevine.Isthereawaywe
canpackageOSStomakeiteasyforotherstotryandadapttotheirneeds?
ProposedSolutions:
1. DevelopgenericAPIs
2. Marketthesoftwaresuchthatitaddressesageneralneed.Forexample,commodityservices-awiki,anemailsystem,acontentmanagementsystem
MarketingoftheOSSshouldnotbestrictlythroughtheperspectiveofthespecificapplication.
Presentscenariosforwiderapplication.Maywanttolookatdividingupexistingsoftware
packagesintousefultools.E.g.breakdownsomethinglikeWorldWindintoitsmodulesand
thencombinemodulesintologicallyseparateprojects.Encouragereuseandvisibilityby
catalogingexistingprojectssuchas http://ti.arc.NASA.gov/opensource/projects/ .
3. LeveragecloudcomputingandVMimagesCreateturnkeysystemsthatdemoOSSinawaythatwillspeaktolargercommunityneeds.
IncludeextrasupportmaterialtargetedtoneedsoftheFederalGovernmentsuchassecurity
documentationforFISMAconformance.Addsecurityfeaturesthatwouldmaketheseworkboth
insideandoutsidetheNASAenvironment.
8/6/2019 NASA Open Source Summit Proceedings
16/85
15
4. Packagesosoftwarecanbedistributedbya3rdpartythathasareputationStandardizationimprovestrustintheproduct.Providingpackagingspecification(suchasRPM
specfiles)wouldalsohelp.
5. DistributesoftwarebinaryexecutablescompatiblewithaspecificsoftwarestackPackagingbinariescompatiblewithaspecificsoftwarestackcouldincreasesadoption,howeverstillhavingareliablepathtobuildfromsourcecodeinarepeatableprocessisneeded.
6. Providesimple,accessibledocumentationonthesoftwareanditsuseGoodopensourcesoftwaresystemshaveacommonsetofbasicdocumentationthatincludes
somefeatures:
systemrequirementsandconstraints installationinstructions tutorialintroduction awaytodownloadthesourcecode
Issue#13:Combiningopensourcesoftwaredevelopmentstandardswith
OfficeoftheChiefEngineerPolicies
NPR7150.2AappliestoallsoftwaredevelopmentbyandforNASA.Inmanycases,themappingofNPR
7150.2Arequirementtotheopensourcedevelopmentprocessesisapparent.Howeverthemappingis
notalwaysobvious.
ProposedSolutions:
1. EnsurethereisadialogbetweenOpenSourceCommunityandOCEregardingmappingNPR7150.2Atoopensourcedevelopmentprocess.
UnansweredIssues:
ThefollowingquestionsweretopicsconsideredattheOpenSourceSummitthatdidnotreceive
meaningfuldiscussionorresponses:
1. Howdoweofferprojectmanagersguidanceregardingthebestopensourcemodelsfortheirprojects?
2. WhataretheobstaclestoTwo-WaySharingofInformation?3. Howtountanglelicensingregulations?4. Differentapplicationsofopensourcelicensing(i.e.researchvs.ops)?5. Opendata:howtoreleasemoredataandmakeitpartofhowwedobusiness
8/6/2019 NASA Open Source Summit Proceedings
17/85
16
Appendix
RegisteredParticipantList
RegisteredIn-PersonAttendees
Name Title Organization
Arash Aghevli
Avinash Agrawal Director,OpenInnovation SetiInstitute
Andrew Aitken Gm&Svp OllianceGroup,ABlackDuckCompany
Jesse Andrews NASAAmes-Dell
Javier Barreiro SoftwareEngineer NASAAmes-SgtInc.
Greg Barrett GeospatialSpecialist IndependentConsultant
David BellDirector,UsraResearchInstituteFor
AdvancedComNASAAmes-SgtInc.
Genesis Berlanga NlsiIntern NASAAmesResearchCenter
Ross Beyeer ResearchScientistSaganCenter(SETI)AndNASAAmes
ResearchCenter
Zaheda Bhorat
Gary BordaAgencyCounselForIntellectual
Property,OgcNASAHQ
Chris Boshuizen SpaceMissionArchitect NASAAmes
Fred Bourgeois TeamFrednet
Deborah Bryant PublicSectorCommunitiesManager OregonStateUniversityOpenSourceLab
Richard Bullington-McGuire Director,Technology ThreePillarGlobal,Inc.
Bob Burbach Founder,OpenSourceDeveloper CriticalJuncture,LLC
Heather Burke ProgramManagerSpaceAndNavalWarfareSystemsCenter
Atlantic(SscLant)
Matthew Burton TechnicalArchitect ConsumerFinancialProtectionBureau
Steven Carmine FederalAccountRep. RedHat
Edward Chan TaskAreaManager,NASASocNASAAmes|DellServices,Federal
Government
Soo Choi NASAAmes-Dell/AnsoLabs,LLC
8/6/2019 NASA Open Source Summit Proceedings
18/85
17
Op Choudhary President OpalSoft
Cyrus Chow
Kim Chrestenson AmesSoftwareReleaseCoordinator Deltha/Critique
Bob Ciotti SupercomputingSystemsLead NASAAmesTne
Yvonne Clearwater NewMediaInnovationLeader NASA/Ames/Nmit
Keith Cowing SpacerefInteractive
Diana Cox PatentAttorney NASAAmes
Jason Crusan NASAHQ
Linda Cureton ChiefInformationOfficer NASA
Joshua DavisManager,OpenTechnology&
OutreachGeorgiaTechResearchInstitute
Martha DelAlto SoftwareRelease NASA
Bosco Dias SoftwareEngineer SAIC
Christopher Dibona OpenSourceProgramsManager Google
Estelle Dodson NASAAmes-Lm
Aaron Duley NASA
Casey Dunn CzwxLLC
Greg Elin FederalCommunicationsCommission
Stuart Engelhardt SoftwareDeveloper NASAJSC-Tietronix
James Farmer Director SigmaSystemsInc.
Pascal Finette DirectorOfMozillaLabs MozillaCorporation
Jane Finette DirectorOfGlobalUserEngagement MozillaCorporation
Elizabeth Foughty ItProjectCoordinator MCTInc,NASAArc
Jennifer Fung PrincipalSe Sgi
Nicolas GarciaBelmonte SeniorSoftwareArchitect SenchaLabs
Bryan Geurts ChiefPatentCounsel NASAGSFC
Richard Golding NASAAmes-Ktsi
Lester Gong
8/6/2019 NASA Open Source Summit Proceedings
19/85
18
Lon Gowen AssociateDirectorForInnovation NASAGSFC
Justin Gray AerospaceEngineer NASAGlennResearchCenter
Saugata Guha SeniorSoftwareEngineer Uarc/NASA
Guru Guruswamy Sr.Scientist NASAAdvancedSupercomputingDivision
Matthew HancherSeniorSoftwareEngineer,Special
ProjectsGoogle
Gunnar HelleksonChiefTechnologyStrategistForUs
PublicSectorGRedHat
Sarah Hobart Dep.MissionSystemsManager NASA
Patrick Hogan WorldWindProjectManager NASAAmes
Julie Holland PartnershipDevelopmentManager DrydenIppOffice
Jamie Hoover Yummly/NinjaUi
Paula Hunter ExecutiveDirector OutercurveFoundation
Phillip Hyett COO GitHub
Jeetendra Jagasia Architect MicrosoftCorporation
Jean-Marie Jean-Pierre Code750End-UserServicesManager NASAGSFC
John KellyOce,ProgramExecutiveForSoftware
EngineeringNASAHQ
Jim Kerevala Coo Ubm
Taemin Kim NASAPostdoctoralFellow NASAAmesResearchCenter
Hyeongwoo Kim VisitingResearcher NASAAmesResearchCenter
Christopher Koenig SoftwareEngineer MicrosoftCorp.
Amanda KoenigAttorney-Advisor,CommercialAndIP
LawNASAHQ
Paul KolanoSoftwareEngineer,Advanced
SupercomputingDivisio
NASAAmes-ComputerSciences
Corporation
Eric Kutner Consultant Erdg
Rick Kwan ComputerScientist AmericanAcademyOfAeronautics
Tsengdar Lee (Acting)CTOforIT NASA
David Lees SeniorProjectScientist NASAAmes/CmuSiliconValley
8/6/2019 NASA Open Source Summit Proceedings
20/85
19
Creon Levit
Martin Levy Director,Ipv6Strategy HurricaneElectric
Brian Lewis NASAAmes
Aaron Lippold
Ali Llewellyn NASAOpenGovernmentInitiative NASAJSC-Valador
Remy Loubradou StudentComputerScience Supinfo
Mike Lundy NASAAmes-SgtInc.
Mike Lundy
Rachel LunsfordSpecialAssistantToTheChief
TechnologyOfficerDepartmentOfVeteransAffairs
Jeff Luszcz Founder Palamida,Inc.
Will Marshall NASAAmes-Affiliate
Guy Martin CommunityManagerAtForge.Mil Collabnet,Inc.
Chris Mattmann NASAJPL-Affiliate
Paul Mcmillan Cto ZeroCoordinate
Alfred Mecum TechnologyManager GSFCIppo
Cristina Milesi ResearchScientist Csumb/NASAAmes
Eugene Miya NASAAmes
Patrick MoranComputerScientist,Advanced
SupercomputingDivisiNASAAmes
Scott Murman CodeTnf NASAAmes
Gwyn Murray FounderAndPrincipal MatauLegalGroup
James Neushul AmphibiousCommunicationOfficer UsThirdFleet
Ray O'Brien CTOforIT NASAAmes
Ryan Ozimek President Joomla(OpenSourceMatters)
Muni P TechnicalArchitect OpalSoft
RobPadilla Padilla ChiefPatentCounsel NASAAmes
Steve ParkerV.P.TechnologyResearchAnd
Projects
EnergySectorSecurityConsortium,Inc.
(Energysec)
8/6/2019 NASA Open Source Summit Proceedings
21/85
20
Tiago Pereira Post-DoctoralFellow NASAARC
Ab Periasamy CTO Gluster
Tom Preston-Werner CTO GitHub
Margarita Quihuis Director,PeaceInnovationLab Stanford
Jon Richards SoftwareEngineer TheSetiInstitute
Peter Robinson ComputerScientist NASA
Enidia Santiago TechnologyManager GSFCIppo
Edward Scharff ResearchEngineer Sgt
Robbie Schingler NASA
Andrea Schneider Director OpengovInAction
John ScottMil-OssFounder/OpenTechnology
Lead/Sr.SysteRadiantblueTechnologies,Inc.
Sharad SharmaDirector,Operations&Business
DevelopmentOpalsoft,Inc.
Sandeep Shetye InformationArchitect NASA
Michael Sims NASAAmes
Amalie Sinclair Administrator SpaceForProgress
Ryan Singer Researcher StanfordPeaceInnovationLab
James Snow SoftwareEngineer NASA
Harlan Steen ProjectDirector NetworkTimeProtocol
Brian StevensCtoAndVicePresident,Worldwide
EngineeringRedHat
Martin Still NASAAmes-Baeri
Ian StrukenDeputyManager/ServiceOffice
IntegrationLead,OcNASAAmes
Sunny Sundstrom ProductManager Sgi
Bob SutorVicePresident,OpenSystems
StrategyIBM
Andy Tainter SeniorConsultant U.S.DepartmentOfState
Joshua To Director Soup
8/6/2019 NASA Open Source Summit Proceedings
22/85
21
J.J. Toothman NASAAmes-Dell
Tom Trainer Gluster
Philip Tsao
Christopher Tucker InformationTechnologyDirector Laane
Bill VanDalsemSystems&SoftwareLeadDiscipline
Engineer,AmesNASAAmes
Alexander VanDijkWebLeadFlightOpportunities
ProgramMCT@NASAAmesResearchCenter
Alonso VeraChief(Acting),HumanSystems
IntegrationDivisionNASAAmes-SgtInc.
Eric Wahl
Jeffrey Walpole Ceo Phase2Technology,LLC
Chris Wanstrath CEO GitHub
Tony WassermanProfessorOfSoftwareManagement
PracticeAndExecCarnegieMellonSiliconValley
Phil Webster ChiefCisto NASAGSFC
Heather Wellington Gluster
David Wheeler InstituteForDefenseAnalysis
James Williams CIO NASAAmes
Michael Williams
Patti Yamakido AccountExec Sgi
Sara Yap DevelopmentConsultant Soup,Inc./Mozilla
Sara Yap
Gil Yehuda DirectorOfOpenSource Yahoo!Inc.
Alana Zimmer NewMediaIntern NASA/Ames/Nmit
Robert Zimmerman SymbiotekSystems
RegisteredRemoteAttendees
Name Title Organization
Avinash Agrawal Director,OpenInnovation SetiInstitute
8/6/2019 NASA Open Source Summit Proceedings
23/85
22
Ahmed Akour Student JordanOpenSourceAssociation
Nouf Aljalaud ComputerEngineeringStudent PrinceMohammadBinFahdUniversity
Stuart Anderson President Netsweng,Llc
Emma Antunes WebManager NASA
John Archdeacon ProjectLeadEngineer Th
Michael Arida Sr.Programmer/Analyst Adnet
Chad Armond SoftwareEngineer DbConsulting
Jesse Ash SoftwareEngineer SynapseInformationResources
Sohail Aslam SoftwareDeveloper Consultant,NASAHQ
Ditjon Baboci Architect StudioAa
Ben Bac SystemAdministrator Benbac
Darrell Bailey TechnicalAssistant NASA/Msfc/Es50
Uri Barkan
WilliamChiquito Barreto Barreto Ica2InnovacinYTecnologa
Merlin Barschke
Jean-Francois Barthe SystemsEngineer SanMateoCounty
Marco Battistoni Architect UnisysBelgium
Mary Bauer CustomerServiceRep ContactCentersOfAmerica
Guy Bedette KennedySpaceCenter NASA
James Bee
Reid Beels OpenSourceBridge
Steve Belvin Honeywell
Alfredo Bencomo Tl Sgt
Andrew Benson SeniorResearchFellow Caltech
Bachir Benyami SystemAdministrator Benbac
Sarah Berman Sociologist Unt
Csar Bernal Esa
8/6/2019 NASA Open Source Summit Proceedings
24/85
23
Steve Berrick EarthScienceDataSystems NASA-Hq
Stephen Berrick
Thomas Berry SoftwareEngineer NASAJPL
Nancy Bertolino Counsel&President SmlProfessionalServicesLlc
ErnaGiles Beverly EnterpriseApplicationsService
Executive
NASAHQ
Colin Bidwell AerospaceEngineer NASAGlenn/IcingBranch
Conrad Bielski Researcher JointResearchCentreOfTheEuropean
Commission
Ralph Bischof IpamEngineer SAIC/Unites
Nicole Bishop Analyst NASA
Brian Black RoboticsAllianceProject NASA
Steven Bliss HumanResourcesInformation
Systems
NASASharedServicesCenter
Scott Blomquist SystemsAdministrator N/A
Andrew Bodker ItSpecialist ChicagoPublicMedia
Randy Bolanos NisnCsr Unites
Artus Bolzanni
Carolyne Borel
David Bovill Director OpnTechnologiesLlp
Meagan Brant
William Brantley HrSpecialist(It) Opm
Martin Braun
THall Brehme
Marty Brenner AerospaceEngineer NASADrydenFrc
Linda Brewster BranchChief NASA/MsfcEs53
Bill Brodt ExperimentalFacDevEngr NASAHQ
Oscar Brooks Chief,SystemSoftwareEngineering NASA,Ksc
Lee Brotzman ImsArchitect NASASoc
8/6/2019 NASA Open Source Summit Proceedings
25/85
24
Pam Broviak CityEngineer/AsstDpw CityOfGeneva
Christopher Brown StructuresAnalysisLead NASA
Gregory Brown ItSpecialist NASA
Darline Brown TechnicalItSecurityManager NASA/HqItcd
Robert Bruchs ConsultingSoftwareEngineer A.I.Solutions(NASAKscEsc)
Stephen Buckley CIO U.S.Transparency
Lori Budin Gluster
Phillip Bui SeniorSoftwareEngineer Usa
Lori Burke SoftwareDeveloper A.I.Solutions,Inc.
Alexander Burke
Matt Burkhardt Owner ImpariSystems,Inc.
Paul Burr SeniorTechnologySystems
Developer
WashoeCountyTechnicalServices
Chris Burroughs NASA/SOMD
Roland Burton
Johnny Busby
Michelle Cadieux SpaceEducator CreativeCommunications/
David Caldern
Ricky Cambpell AerospaceEngineer NASAMarshallSpaceFlightCenter
Louis Cancino InformationArchitect JohnsonSpaceCenter
Guillermo
Rodrguez
Cano
Chuxiao Cao
William Carlin ComputerSpecialist WashoeCountyLibrarySystem
Christopher Carmichael SscDeputyCto NASA
Bruce Caron ExecutiveDirector TheNewMediaStudio
Cory Casazza ChiefInformationManagement
Officer
WashoeCountyTechnicalServices
Sarah Caufield
8/6/2019 NASA Open Source Summit Proceedings
26/85
25
Peter Cauwels EsbLobManager NASA/Apexio
Ravi Chandra Sv HoneywellTechnologySolutionsLtd.
Jessica Charlesworth Designer Self-Employed
Beau Charvet ItSpecialist NASA
Op Choudhary President OpalSoft
Cyrus Chow
Trisha Christensen Web&MarketingConsultant DharmaCreative
Emmanuel Christophe
Bob Ciotti SupercomputingSystemsLead NASAAmesTne
Matthew Clark HoneywellAerospace
Brian Claywell GraduateResearchAssistant CenterForGeospatialIntelligence,
UniversityOfMissouri-Columbia
Tom Clune SeniorComputational Scientist NASA- GSFC
James Cochran FormsDesigner DbConsultingGroup
Tom Cochrane
Michael Cohen SoftwareLead NASAAmes(JacobsAsgContractor)
Doug Coleman Dougcoleman
James Comstock AerospaceTechnologist NASALangleyResCtr
Casey Conaghan Consultant OpsInternational
Max Connelly ComputerTechnician WashoeCountyLibrarySystem
Alberto Conti ArchiveScientist SpaceTelescopeScienceInstitute
Christopher Cook ItSystemsAndSecurityDirector InuteqLlc
Shawnee Cook Principal Zentu,Llc
David Cox SeniorResearchEngineer NASALangley/D316
Wayne Crane
John Crockett LibraryAssistantIi WashoeCountyLibrarySystem
Alan Cudmore ComputerEngineer NASA/GoddardSpaceFlightCenter
Angela Czupta Secretary InnovativeHealthApplications
8/6/2019 NASA Open Source Summit Proceedings
27/85
26
Mike Dalal ComputerScientist Sgt,Inc.AtNASAAmes
Mat Dalgleish UniversityOfWolverhampton
Saurabh Das
Arun Datta Director,TechnologyR&D(Nucri) NationalUniversity
David Davis RiskManager DyneticsTechnicalServices/MSFCMits
Jerry Davis DeputyAssistantSecretary,InfoSec UsDepartmentOfVeteransAffairs
Galen Debord Coordinator MissouriUbuntuLocoTeam
Martha Del SoftwareRelease NASA
Tishampati Dhar SoftwareEngineer CsiroCmar
Kimberly Diorio SeniorAerospaceEngineer SAIC
Portia Dischinger ItProjectManager NASAMsfc
Ridley Disiena EmergingTechnologyIntegration
Engineer
NASA/Etads/IcamEngineering/Db
Consulting
Kevin Divico Entrepreneur
John Dockendorf HarrisCorp
Visal Doeuk CorePlanningEngineer CamgsmCompanyLimited
Jessie Dotson Astrophysicist NASAAmesResearchCenter/Ssa
Faith Dow
Bob Downing EngineeringManager ArcataAssociates
Prateek Dubey TechnicalSpecialist ZensarTechnologiesInc
Brian Duggan ScientificProgrammer AdnetSystems
Leslie Dugger I.T.Associate Laane
Casey Dunn CzwxLlc
Robin Edwards
PriscillaChang Eines WebAdministrator MagnetMediaNorway
William Eisenhauer NationalDirectorOfVeterans
EngineeringResource
DepartmentOfVeteransAfffairs-Vha
Sheri Elgin ItsdTechnician JrSimplotCo
8/6/2019 NASA Open Source Summit Proceedings
28/85
27
Ehab Elhanafy FreelanceTranslator ElhanfyLimited
Drew Elliott
Michael Enescu CtoOpenSource CiscoSystems
David Engelbrecht SystemsEngineer DellFederalServices/NASAAmesCodeI
Betsy Ensley MarketingManager Phase2Technology
Josh Ermentrout
Hassan Eslami DeputyDir.TechAreaMgr Uarc
Jeff Estefan DivisionTechnologist JetPropulsionLaboratory
John Evans GlobalScience&Technology,Inc.
Dave Eveland ManagingLibrarian WashoeCountyLibrarySystem
Matt Everingham AerospaceEngineer Nlsi
Mark Faine SoftwareEngineer Dts
Rob Falck AerospaceEngineer NASAGlennResearchCenter
James Farmer Researcher InstructionalMedia+MagicInc.
Brandon Farmer Programmer/Analyst Mssu
John Ferrell Principal ClearlyMedia
Marcus Fisher GSFC/Iv&V
James Flanagan
Cecelia Fletcher ManagementAndProgramAnalyst NASALangleyResearchCenter
Karl Fogel OpenCivicsDevelopmentSpecialist O'ReillyMedia,Inc.
Richard Fong Govdelivery
James Francis SoftwareEngineer AuroraFlightSciences
Robin Friedrich ProjectEngineer UnitedSpaceAlliance
Todd Fries FreeDaemonConsulting,Llc
Thomas Gaeng ItManager AdnetSystems
David Galiel ExecutiveDirector BeyondWar
Manuel Gamelas
8/6/2019 NASA Open Source Summit Proceedings
29/85
28
Victor Gandarillas
Gary Gapinski SeniorSystemEngineer NASAGlennResearchCenterDb
ConsultingGroup,Inc.
Sumedha Garud Marketing/Outreach SimlabsAtNASAAmes
Richard Gaskin FourthWorld
Mark Gayler OpenSoftwareEvangelist Microsoft
David Gaylor
James Geiger
Stephan Gerard
Jeffrey Gilbert SoftwareLead DbConsulting/NASA
Sean Gill
Sebastian Gillen EquipmentTechnician JacobBurnsFilmCenter
Kim Gillies SoftwareArchitect ThirtyMeterTelescopeCorporation
Mark Gisi Sr.IPManager WindRiverSystems
Jeremy Glassenberg
Todd Goatley ComputerTechnician WashoeCountyLibrarySystem
Viktor Godard SrLinuxEngineer
Stephane Goldstein Student
Daniel Golombek ChiefOfStrategicCommunications SpaceTelescopeScienceInstitute
Lester Gong LeadAssociate BoozAllenHamilton
Lester Gong
JoseManuel Gonzalez SystemsAdministrator
Kathleen Gordon SystemsEngineer SAIC/Is40
Aman Goyal SoftwareDeveloper ReflexisSystems
Tracy Graham SystemsAdministrator Tbe/MsfcPoif
Patrick Grayson
Scott Gries
Tony Grimshaw InformationSecurityArchitect
8/6/2019 NASA Open Source Summit Proceedings
30/85
29
Manuel Grizonnet FrenchSpaceAgency(Cnes
Rebs Guarina SystemsDeveloper N/A
Sreedhar Gudur SoftwareEngineer ZensarTechnologiesLtd
Arthur Guest
Saugata Guha SeniorSoftwareEngineer Uarc/NASA
Piyush Gupta Programmer Accenture
Aman Gupta
Guru Guruswamy Sr.Scientist NASAAdvancedSupercomputingDivision
David Guterrez SolutionArchitect Centauri
Sandy Gutheinz ProjectManager JPL
Valerie Gwaltney SeniorSystemAdministrator Ssai
Therese Haar Sgt NASA/Goes-R
Jon Hamkins Supervisor JPL
Marc Handelman InformationSecurity
Officer/Research
Infosecurity.Us
Andy Harb
Brian Hargrave SystemsAnalyst Mits
Kazuo Hayashida ElectronicsEngineer NASA/Msfc
April Hayman
Phillip Hebert Lead,SoftwareEngineering NASA/Ssc
Richard Hecker
Ryan Heggem HopperCosmic&Company
Timothy Hemphill GlideDeveloper Asrc
Joel Henry Engineer NASA
Sam Henry ItSecurityAnalyst NASA/Jsc
Jim Henze
Tom Higgins
Evelyn Hill SoftwareReleaseAuthority NASA/Msfc
8/6/2019 NASA Open Source Summit Proceedings
31/85
30
Trudy Hill
Nancy Hine Projects/PayloadCoordinator Ukseds/Mypocketqub
Randall Hirsch Attorney/Physician
Akira Hiyama
Alex Hocking Student OpenUniversity
Terry Hodgson SrSoftwareEngineer Meit/NASA
Erich Hohman TechnologyNetworkEngineerIi WashoeCountyTechnicalServices
Vera Holman ManagingPrincipal V_LanTechnologies
Corbin Holtz SystemsEngineer LockheedMartin/Jsc/Mod
David Hoppe SolutionArchitect Oh4
Mack Houston
James Howard SeniorResearchSystemsAnalyst BoardOfGovernorsOfTheFederalReserve
System
Carrie Howard ItManager WashoeCountyTechnicalServices
Chunyih Hsu
Sara Hunter OfficeManager MetisTechnologySolutions,Inc
Paul Hunter CtoForIt NASA-GSFC
Paul Hunter Cto NASAGoddardSfc
Alan Hylton SoftwareEngineer NASAGlenn/CommunicationTechnology
Dennis Iannicca SoftwareEngineer NASAGlenn/CommunicationTechnology
Luis Ibanez TechnicalLeader KitwareInc.
Chaudhry Ibrahim IcsNett
Daniel Ihonvbere Ceo TechPrognosis
Joseph Isach SoftwareEngineer NASAGlenn/CommunicationTechnology
Mashru Islam MscStudent(Dept.OfEee) KhulnaUniversityOfEngineering
Technology
Marin Ivan Researcher IsGeo
Will Ivancic SeniorResearchEngineer NASAGlenn/CommunicationTechnology
8/6/2019 NASA Open Source Summit Proceedings
32/85
31
Carlos Ize Sr.Engineer AmericanAirlines
Sheila Jackson HumanResourcesDevelopment
Specialist
NASA
Bruce Jackson SeniorResearchEngineer NASALangleyResearchCenter
Andrew Jalics FlightSoftwareEngineer NASAGrcQinetiqNorthAmerica
Contractor
Mark James SoftwareReleaseAuthority NASA/JPL
Jinyoung Jang Ceo Uenginesolutions
Erik Johnson ResearchAssociate MovesInstitute,NavalPostgraduateSchool
Kirk Johnson InformationAssuranceDelivery
Manager
SAIC/NeaccMsfc
Michael Johnson
Jeff Johnstone Retired OpenSourceSpaceCa
Ellen Jones SoftwareEngineer Dtsi
Patricia Jones DeputyDirector,ExplTechnology NASAAmesResearchCenter
Brian Jones
Jim Justen AssocEditor
Elia Kabanov Founder Metkere.Com
Sharmin Kamal TechnologySystemsDeveloperI WashoeCountyTechnicalServices
Amy Kaminski
Nancy Keener Systems&ServicesAccessLibrarian WashoeCountyLibrarySystem
Paul Keller ResearchEngineer NASAAmes
Keith Keller AssociateChief,Strategy&Planning
It
NASAGoddardSpaceFlightCenter
Megan Kelly Gscnc
Sean Kelly Technologist JPL
Brian Kennedy
Jim Keravala
Ellen Keulemans Escg-MeiTechnologies/JSC-Ev
8/6/2019 NASA Open Source Summit Proceedings
33/85
32
Alvin Khaled
Robert Kilker DirectorOfFederalOperations Talend
Stephen King EsmdIcePdm/PlmServiceManager DkiConsulting/EsmdIce
Roy King TechnologySystemsAdministrator
IiorI
WashoeCountyTechnicalServices
Morgan King CipAuditor Wecc
Jon Kocen ItProfessional Ares/Oh4
Joe Kochocki PrincipleMemberTechStaff DraperLaboratory
Christopher Koenig SoftwareEngineer MicrosoftCorp.
Markus Korn
Stefanos Koutsoutos
Aleksandar Kracun
Kevin Kreitman SeniorEngineeringSpecialist AerospaceCorporation/ComputersAnd
SoftwareDivision
Bhagwat Kshirsagar Professor Mit
Iwanka Kultschyckyj
Kieran Kunhya Ceo OpenBroadcastSystems
Eric Kutner
Jose Lagares PrincipalSoftwareEngineer A.I.Solutions(NASAKscEsc)
Amit Lakhanpal
Chatwin Lansdowne ElectronicsEngineer NASA-JSC-Ev611
Joe Latone Ibm
Carsten Lawrenz ApplicationEngineer Ptc
Anh Le
Mike Ledbetter PrincipalInvestigator/Manager MSFCEs61/DavidsonTechnologies,Inc.
Clarissa Lee GraduateStudent/Graduate
Instructor
DukeUniversity
Henry Lee GovernmentOfBritishColumbia
Rebecca Lee GrantThorntonLlp
8/6/2019 NASA Open Source Summit Proceedings
34/85
33
Lucia Lee SeniorComputerScientist Ssai/NASALarc
Brett Lewinski TechnicalAreaExpert Indyne/NASA
Edward Lewinson
Tristan Li
Roger Liang SoftwareReleaseAuthority NASAKennedySpaceCenter
Teresa Liao
Evan Lim ConsultingEngineer SAIC
Greg Lind Govhub
Van Lindberg
Dennis Linders PhdStudent UniversityOfMaryland
Francis Lindsay Esdis
Jeff Lohrmann Director,SalesAndMarketing AdvancedComputerConsulting
Chris Long SeniorTechnologyNetworkEngineer WashoeCountyTechnicalServices
Remy Loubradou Student Supinfo
Filipe Loureno
Greta Lowe ItProjectManager NASA
Roberto Lozano AstronomerAndScientificDifusser AstronomicalObservatoryGiefa
Mark Luboski SoftwareAssuranceEngineer AresCorporation
Chris Lucas
Franklin Lue GroupLeader DrdcToronto
James Lux TaskManager JetPropulsionLaboratory
Mark Lyon AdvSwGroupLeader DraperLaboratory
Cosimo Macafore SoftwareDeveloper Saitech/Nssc
Jeffrey Macdonald It Ksc-Lx
Gail Macdonald SrSystemSupportEngineer QinetiqNa
AnaLigia Machado Advertising Tam
Bob Mader VpLinux Citigroup/PlatformEngineering
8/6/2019 NASA Open Source Summit Proceedings
35/85
34
Dhruv Mahajan Student
Issa Mahasneh President JordanOpenSourceAssociation
Kevin Mahoney SeniorDeveloper Toolhouse
Richard Mains SeniorScientist MainsAssociates
Saurabh Mallik MarketingManager Pushtotest
Joseph Mangan Ceo CoandaAerospaceLlcU.S.A./Coanda
AerospaceSoftwareGmbhAustriaEurope
James Mantovani Physicist NASAKennedySpaceCenter
Jane Maples ItSpecialist NASA/Neacc
Lawrence Markosian ComputerScientist Sgt,Inc.
Jason Maron AssociateHealthFellow NewEnglandVeteransAffairsResource
Center
Jane Marquart ComputerSpecialist NASA/GSFC
James Marshall SeniorStaffScientist Innovim/NASAGoddardSpaceFlight
Center
Sam Martin I360Technologies,Inc.
VictorHugo Martn Planning Davi
Wayne Matthews Escg/Estl
Chris Matthews E-GovernmentInformationOfficer WashoeCounty
Mary Matthews Director/Producer
Arnie Maurins DirectorWashoeCountyLibrary
System
WashoeCountyLibrarySystem
Tom McBride PatentAttorney NASALarc
Neal McBurnett Founder/Developer ElectionauditsOpenSourceProject
David McComas GpmFlightSoftwareProductLead NASAGoddardSpaceFlightCenter
Perry McDowell ExecutiveDirector Delta3D
James McGroary ChiefPatentCounsel MSFCNASA
Dawn McIntosh Darpa/NASAAmes
Edward McLarney ChiefTechnologyOfficer NASALarcOcio
8/6/2019 NASA Open Source Summit Proceedings
36/85
35
Fred McMullen Web2.0PlatformsTeadLead NASAMits
Erin Means SoftwareSystemsEngineer JPLOcio
Luis Mederos
Simon Mehalek GoldStreetLabs
Cade Metz UsEditor TheRegister
Kenneth Meyer SoftwareEngineer JPL
Joel Miller NASAAmes-Dell
Sheena Miller Sr.SoftwareSystemsEngineer NASAJSC(Barrios)/Er6
Chase Million ApplicationsDeveloper CaliforniaInstituteOfTechnology
Robbo Mills HunkyDoreyEntertainment
Bill Monroe GlobalAccountManager AT&T
Bruce Montgomery ChiefTechnologyOfficer TechnologyAccessTelevision
Tristan Moody GraduateResearchAssistant UniversityOfKansas
Kenneth Moore SeniorAnalyst2 DbConsulting/NASAGRC
Neal Most ProjectManager Innovim
Catalina Movileanu
Troy Moyers Engineer Mits/Is70
Erik Mullinix ManagingPartner Rainworks
Stuart Murray
Syed Nadeeb SoftwareEngineer
Theodore Nathanson AerospaceEngineer Consultant
Robert Navarre SystemAdminstrator LockheedMartinEs&S
Diego Naya Ceo Plugtree
Michael Needler Sr.SoftwareEngineer Tietronix/Mod/JSC/NASA
Ara Nefian SeniorScientist NASA
Brent Newhall SoftwareReleaseAssistant,Goddard
IppOffice
NASA-GSFC
David Newton SystemAdmin Dts/MSFC
8/6/2019 NASA Open Source Summit Proceedings
37/85
36
William Neyer Hhs/Fda
Beth Nguyen Arts
Ben Nickell IdahoStateUniversity
Rolando Nieves SoftwareArchitect NASA
Jeffrey Norris SectionManager,PlanningAnd
ExecutionSystems
NASAJetPropulsionLaboratory
Stefan Novak
Daniel Oldham ComputerEngineer NASAGrc
Bonita Oliver ComputerScientist NASA
Robin Orans TechnologyPartnershipManager NASAAmesResearchCenter
Roger Orellana
Jeffrey Osier-Mixon CommunityManager,YoctoProject IntelCorporation/OpenSource
TechnologyCenter
Edward Ost TechnicalDirector Talend
Billy Otrs
Pete Overstreet ItManager BarriosTechnology,Space/LifeSciences,Jsc
Steve Padgett ItManager Arts
Rabi Palikonda Sr.ResearchScientist ScienceSystems&ApplicationsInc.
Aravind Parchuri
Joel Parker FlightDynamicsEngineer NASAGoddardSpaceFlightCenter
Pilar Passmore Librarian
Tripp Pearson Engineer NASA
Tiago Pereira Post-DoctoralFellow NASAArc
Jennifer Perez SoftwareEngineeringLead E301
Ab Perisamy Gluster
Nick Peters Pm Iv
Kenneth Peters AdvancedTechnologyR&D;Software JPL
Kristina Petrosyan SecurityAnalyst ProvinceOfBC
8/6/2019 NASA Open Source Summit Proceedings
38/85
37
Long Pham ComputerEngineer NASA-GoddardSpaceFlightCenter
Shawn Pierce SoftwareEngineer LockheedMartin
Nick Pink SecurityIntern NASAAmes
Alex Pline ItProjectManager NASAHeadquarters
Chris Preimesberger Eweek
Dave Proffer
Dan Proper TechnologySystemsAdministratorI WashoeCountyTechnicalServices
Jessica Prue MastersStudent MaxwellSchool,SyracuseUniversity
David Pruett GeocontrolSystemsInc.
Greg Pryzby SolutionsArchitect RedHat
Martha Przysucha GsaOfficeOfGovernmentwidePolicy
Siegfried-Angel Pujals FreeSoftwareDeveloper
Cuong Quach ResearchEngineer
Garry Qualls SystemsEngineer NASA/Oct
Mark Radcliffe Partner DlaPiper
Frankie Ramos IHA
Thomas Rando OpenSourceTeamLead Indyne,Inc/NASAHQ
Lee Razo Director DatasphereSystems
Michael Redmon ProgramManager Sgt,Inc.
David Reese MobileComputing/EmcsTechnician JacobsTechnologyMaf-G
Chris Regan AerospaceEngineer NASADryden
Scott Reinhart SoftwareEngineer,Staff LockheedMartinSpaceSystemsCompany
David Retherford Retherford ErcInc.
Jon Richards SeniorSoftwareEngineer TheSetiInstitute
Gary Richmond WebServiceDeveloper JetPropulsionLaboratory
Norm Ritchie NewProgrammes InternetSystemsConsortium
Luis Rivas ItManager Ls
8/6/2019 NASA Open Source Summit Proceedings
39/85
38
Marco Rivers Student MiamiDadeCollege
Michael Roberts ProcessEngineeringConsultant Qna/KscEpg
Erin Robinson FoundationForEarthScience
Peter Robinson ComputerScientist NASA
Conrad Roche
Paul Rodgers Londonbikecompany
Jacob Rodriguez TierIiLeadSoftwareSupport
Engineer
Irdeto
Ginny Rogers WebDesigner/Development SimplyBridgesGroup,Inc.
Bryon Rollins ProgramManager UltraElectronics,Prologic,Inc.
Lyford Rome NASA/JPLSolarSystemAmbassador
AlfredoJimenez Ronssin
Ellis Rubio EllisEngineeringSolutionsLtd.
Lamont Ruley SupervisoryComputerEngineer NASA/GSFC
Kyle Ryan ElectricalEngineer OrbitalSciences/NsrocIi
Stephen Ryan
Padma S
Alvaro Salamanca SalesRep NexsysLatinoamerica
John Samson HoneywellAerospace,Defense&Space
Anthony Santopietro SoftwareIntegrationTeamLead ChugachFederalSolutions,Inc/NASACASI
Virat Sarin
Kayla Sather EnvironmentalIntern Jq
Godfrey Sauti ResearchScientist NationalInstituteOfAerospace
Craig Sayler Sr.Unix-Linux,HighPerformance
ClusterEngineer
DfrcNASADrydenFligthResearchCenter
Edward Scharff ResearchEngineer Sgt
John Schipper PrincipleSystemsEngineer L-3-NASAIvvFacility
Weston Schmidt Software/HardwareArchitect OpenRoadster
8/6/2019 NASA Open Source Summit Proceedings
40/85
39
Otto Schnarr EmbeddedSystemsDeveloper NASADryden
John Schnase SeniorComputerScientist NASAGoddardSpaceFlightCenter
Bruce Schubert Emxsys
Kathryn Scoggin NASA
Peter Scott Analyst JPL
Dave Scott ComputerEngineer MSFC/Eo50-HoscGroundSystems
Development&Integration
Anthony Sellers
Chad Sells I.T.SystemAnalyst Laane
Timothy Sesow ChiefTechnicalOfficer OpenSourceStorage,Inc.
Aarshey Shah Student CeptUniversity
Ehsan Shahrokhi IT
Warren Shearer SeniorNetworkAdministrator Dfrc
Salman Sheikh Ee NASA/GSFC
Jack Sheldon Sr.SystemsEngineer ArcataAssociates
Chris Shenton Consultant,AgentProvocateur NASAHQ
Sandeep Shetye InformationArchitect NASA
Fu-Tai Shih SoftwareEngineer Sgt/Ti
David Siedband CEO Zentraal,Inc.
Jacob Silvia SoftwareConfigurationManagement J&PTechnologies
Luca Simoncelli
M. Simos
Amalie Sinclair Organiser SpaceForProgress
Jerome Slangen
Laura Sleasman ProjectManager DellInc.
Ifan Slv
Michael Smith Consultant BoozAllenHamilton
Joe Smith EnterpriseArchitect InformationDynamics
8/6/2019 NASA Open Source Summit Proceedings
41/85
40
Tristan Smith ProgramLead MissionCriticalTechnologies,Inc.
Jeffrey Smith OpticalEngineer NASAGoddardSpaceFlightCtr.
Dan Smith SoftwareDivision-NewBusiness
Lead
NASA/GSFC
Kelly Smith AerospaceEngineer NASA/Jsc
Ernest Smith ProjectIntegrationManager Usra/Ames/Ti
Kraig Smith ItManager WashoeCountyTechnicalServices
Chaise Smith
Paul Snow RulesManagementChiefArchitect Sourcepulse
Sunil Soprey Ceo/Developer/Geek DerigoTechnologyInc
Jared Sperli Co-Founder Itsoftware
John Sprague EndUserServicesExec NASA\OCIO
Amy Stapleton NeaccManagement-ItSupv NASA/Msfc
Gerald Steeman ItSpecialistForCm NASAStiProgramOffice
Sheila Steffenson Esri
Haley Stephenson Writer Valador/NASAAppel
Joseph Steurer Student MissouriUniversityOfScienceAnd
Technology
Martin Still KeplerGuestObserverOffice
Director
NASAAmes
Ted Stodgell Engineer NASA
Kim Stroeger ScrumMaster Nokia
Lynnette Stroeger Developer Trm
Bala Sundarraj ChiefConsultant PodhigaiOpenSourceServices
Patrick Svenburg Director,PlatformStrategy Microsoft
Thomas Swanson ServerAdministrator AbacusTechnology
Keith Swanson ComputerScientist NASAAmesResearchCenter
Eric Sweigard ProgramManager InnovativeDefenseTechnologies(Idt)
Alasdair Swenson DigitalCreative ThePrototypeCommittee
8/6/2019 NASA Open Source Summit Proceedings
42/85
41
Brian Takemoto SeniorTechnologySystems
Developer
WashoeCountyTechnicalServices
Eric Tatara SoftwareEngineer ArgonneNationalLab
Graeme Taylor UndergraduateStudent UniversityOfSouthampton
Harbles Theskepticalcat
Peter Thompson SeniorSystemsEngineer SgtInc/NASANPPMsi&T
GraceB Thomson Owner/Ceo OrganicSoftware&Computers
Ed Thomson SoftwareEngineer Pratt&WhitneyRocketdyne
Marc Tiar LibrarianIi WashoeCountyLibrarySystem
Beth Todd TechnologySystemsDeveloperIi WashoeCountyTechnicalServices
Igor Toledo
Mark Tomizawa Humankindx(AnMtvForDemocracy
WhereTheAudienceIsTheStar;InBeta)
Carlos Torrez BussinessManager NASA
Joel Tosi
Tom Trainer Gluster
Daniel Trebbien
Shui-Ay Tseng DatabaseEngineerLead ComputerScienceCorp.
Tina Tsui ComputerEngineer NASA/GSFC
Christopher Tucker I.T.Director Laane
Nathan Uitenbroek OrionSwArchitect L3/NASA
Luigi Usai Hacker
Andreea Vaculisteanu EventCoordinator UnaweRomania
Clementine Valayer SeniorConsultant TrasysSa(OnAContractForEsa)
Michele Vallisneri ResearchScientist JPL
Anoop Valluthadam Student Vmkv
Michael VanChau DirectorOfCyberStrategy&
Development
MeiTechnologies,Inc.
Alexander VanDijk WebLeadFlightOpportunities Mct@NASAAmesResearchCenter
8/6/2019 NASA Open Source Summit Proceedings
43/85
42
Program
Jaap VanDoorn Consultant CapgeminiNederland
Jay Vasa Cto Applios,Inc.
Rishi Verma SoftwareEngineer NASAJetPropulsionLab
Jon Verville EngineeringCollaborationLead NASAGSFC
Huy Vo Engineer LMSSC@Maf
Stephen Voels Sr.Engineer SAIC
Mary Volz-Peacock ProgramManagerOpenGovernment Opm
Jerry Wagner ISSTrajectoryOperationsOfficer UnitedSpaceAlliance
Eric Wahl
Jeff Walter DeputyProjectManager-Technical NASAGSFC
David Walters SSCCTO
Andrea Warmbier PatentAttorney NASALangley
Keith Watson ResearchEngineer Cerias,PurdueUniversity
Phil Webster Chief NASAGSFCCisto
Lee Wedgeworth Engineer Wyle/Sd24
Jon Welch ItConsultant AeWoodAndAssociates
Heather Wellington Gluster
R Wertenberg
Jason Wickard Manager,SoftwareDevelopment
Michael Williams
Samuel Wong
Michael Worsham SystemsSupportCoordinator Src/Spawar
Michael Wright DeputyBranchChief NASA/Msfc/Es12
Aaron Wright G.I.S.Student SanAntonioCollege
Lawrence Wu
Patti Yamakido AccountExec Sgi
8/6/2019 NASA Open Source Summit Proceedings
44/85
43
Masaki Yamaya Consultant JustSkill,Inc.
Gil Yehuda DirectorOfOpenSource Yahoo!Inc.
KuChung Ying ComputerMaintenanceEngineer
Hans Zaunere ManagingMember NewYorkPhp
William Ziebell SeniorSoftwareEngineer Mct
Angela Ziegenhorn
Press
Name Title Organization
Luke Fretwell Founder,MediaCorrespondent Govfresh
Debbie Gage Reporter DowJonesVenturewire
Sarah Granger Founder CenterForTechnology,Media&Society
Alex Howard Government2.0Washington
Correspondent
O'ReillyMedia,Inc.
Cade Metz
Chris Preimesberger SeniorWriter Eweek
Mike Wall Reporter Space.Com
Staff
Name Title Organization
Wayne Burke ExecutiveDirector OpenForumFoundation
Lucas Cioffi OnlinetownhallsInc.
Jessica Culler PublicAffairsOfficer NASAAmes|Deltha-Critique
Gretchen Curtis CTO-ITCommunicationsManager NASAAmes|DellFederalServices
Pat Elson NASAAmes|DellFederalServices
William Eshagh
Terry Fong Director,IntelligentRoboticsGroup NASAAmes
Rita Galan NASAAmes|DellFederalServices
8/6/2019 NASA Open Source Summit Proceedings
45/85
44
Chris Gerty OpenGovernmentAnalyst NASAHQ
Scott Goodwin CIOForSpaceOperations NASAHQ
Gabriel Hurley-Ramstad SeniorWebDeveloper NASAAmes|DellFederalServices
Cristina LeClerc CTO-ITProjectCoordinator NASAAmes|DellFederalServices
Kim Lembo TechnologyPartnershipManager NASAAmes|LockheedMartin
Nick Skytland Director,OpenGovernmentInitiative NASAHQ
8/6/2019 NASA Open Source Summit Proceedings
46/85
45
AgendaandSchedule
Day1March29,2011
8:00am RegistrationOpens
MainRoom BreakoutRooms
9:00am Dr.TsengdarLee,NASAIntroductionandFraming
9:15am WayneBurke,OpenForum
Foundation
Overview,Goals,andFormatofthe
Summit
9:30am DavidWheeler,InstituteforDefense
Analysis/DoD
Whatispossible?Keydifferences
betweenopensourcedevelopment
insideandoutsidefederal
government
BreakoutSession#1
10:00am TerryFong,NASAARC
OpenSourceatNASA
BreakoutSession#2
10:30am PatrickHogan,NASA
WorldWind,ImplementinganOpen
SourceProjectatNASA
BreakoutSession#3
11:00am BreakoutSession#4
12:00pm Lunch
1:15pm WayneBurke,OpenForum
Foundation
Welcomeback,afternoongoals.
1:30pm RichardBullington-McGuire&Guy
Martin
DoD'sforge.mil:Collaboratingon
SoftwareDevelopmentwithinDoD
BreakoutSession#1
Developsolutionsto
Communicationand
publicizingNASA'sopen
sourceefforts
2:00pm BreakoutSession#2
Licensing
2:30pm BreakoutSession#3
Howdeeplycanthe
communitybeinvolved?
3:00pm BobSutor,IBM
TheValueofOpenSource
BreakoutSession#1
Developmentmodels&
ongoingsupport3:30pm ChrisMattmann,NASAJPL
OpenSourceatNASA
BreakoutSession#2
Governmentrestrictions,
e.g.ITAR
4:00pm BreakoutSession#3
Limitationsoncontributing
toexternalopensource
projects
8/6/2019 NASA Open Source Summit Proceedings
47/85
46
4:35pm WayneBurke,OpenForumFoundation
SummaryofDay1,OverviewofDay2
4:40pm RayOBrien,NASA
MovingForward
Day2March30,2011
MainRoom BreakoutRooms
9:00am JamesWilliams,NASA
WelcometoDayTwo
9:15am WayneBurke,OpenForum
Foundation
Overview,Goals,andFormatofthe
Summit
9:30am GroupDiscussion
ReviewtheIssueList,whats
missing?
10:00am ChrisWanstrath,GitHub
GitHub
10:30am ChrisDiBona,Google
Google,NASA,andOpenSource
11:00am BreakoutSession#1
12:00pm Lunch
1:15pm WayneBurke,OpenForum
Foundation
Welcomeback,afternoongoals.
1:30pm BrianStevens,RedHat
2:00pm BreakoutSession#2
Opendiscussionsthatmayrevisitanytopicfromthe
restoftheeventorcover
entirelynewtopicsthat
havebeenmissedthusfar.
3:00pm PascalFinette
TheMozillaexample:Whats
happeningwithopensourcein
industry?
3:30pm LindaCureton,NASA
Thankyou,Wrapup
3:40pm BreakoutSession#3
4:30pm WayneBurke,OpenForumFoundation
Conclusion
8/6/2019 NASA Open Source Summit Proceedings
48/85
8/6/2019 NASA Open Source Summit Proceedings
49/85
48
ExcerptsfromUstreamChat
ThefollowisanexcerptoftheUstreamchatfromtheSummit.Relevantsectionsofconversationhave
beenincluded,whileunrelatedorlogisticalconversationhasbeenremoved.
Tuesday
Time Username Comment11:51 user16 Doesthephrase"worksforhire"notapplytocontractorsmaking
softwareforthegovernment?
11:51 User10 Correct,doesNOTapply.
11:52 user17 Sothecontractorfirm'owns'thesoftwaretheGovispayingfor?
11:52 user30 Ifonlygnuhadtakenthatadvicepriortounleashinggpl3
11:52 user24 dependsonthecontractingagreement
11:52 user24 Theycangoeitherway
11:53 user16 Notonlyislicenseproliferationaproblem,butsatisfyingallofthe
requirementsofsubcomponents.
11:54 user24 Yeah.thelicenseisprettyhorrible.Thelawyerswhowroteitclearlydidn't
spendanytimestudyingothersimilartypesoflicenses
11:54 user30 wow,that'sreallybad
11:54 User10 Thegovernment's"unlimitedrights"specificallydoNOTallowdistribution
tothepublic.Yes,thecontractorgenerallycancontrolthesoftware.
11:54 user23 Nicelicencetablehere:
http://fedoraproject.org/wiki/Licensing:Main#GPL_Compatibility_Matrix
11:55 User10 Forthecontractortonotcontrolthesoftware,wegenerallyneeda
deviationtotheFAR.
11:55 user30 @User10:soacontractorcouldbethe"leader"ofanOSSproject,thereby
absolbingNASAofitscrazyNOSAandliabilityrequirements
11:55 User10 No.
11:55 user30 *absolving
11:55 user16 Shouldthatchange?IfIworkasanindependentcontractor,thenI
automaticallyassignmyrightstosoftwarethatIproducetothecompany.
11:56 user16 Actually,whenIworkasabonifiedemployeeaswell.
11:56 user24 user16itdependsonyourstate,andyouremploymentagreement.
Usually.
11:56 User12 bonafide?
11:57 user16 *bonafide.Yessorry.
11:57 user30 Ifyouwanttoretainownershipofyourowncode,orwriteOSSonthe
clock,makesureitisinyourcontract.
11:57 user24 NASAdoesn'teffectivelymonetizeit'spatents
11:57 user24 sothatargumentisbunk
11:57 User12 bonifiedemployeesmightbepeoplewhoretired(anddied)inplace.:-}
11:58 user22 hehe
11:58 user16 DoesNASAholdpatents?
11:58 User10 ThedefaultisUSGeneralReleasesothattaxpayersdohaveaccessto
NASAsoftware,butforeignpersonsdoNITgetbenefitpaidforbyUS
taxpayersexceptincertainsituations.
8/6/2019 NASA Open Source Summit Proceedings
50/85
49
11:58 user24 he'sabsolutelyrightaboutallthis.Ihopeitisn'tnewstomsotofthe
peopleinthisroom
11:58 user16 Iknowthatotherbranchesdo.
11:58 user17 NASAcanmakemoneyoffpatents?Ithoughwewerenotallowedby
CongresstotakeinfundsnotallocatedbyCongress??
11:58 user24 well,ifacontractorproducessomethingpatentable,thatpatentprobablygoestoNASA
11:59 user24 (makesnotsensetodoanythingelse)
11:59 User10 BASAdoesgetpatentroyaltiesandthedeveloperscanalsogetasplitof
thefunds.Thepatentgoestothecontractor.
11:59 User4 @user17,yes,ourgrouphasnumerouspatents.Theindividualdoesn't
makemoney,oreventhegroupthough.
11:59 user17 Thatisprobablytruebutwecannottakemoneyforit,Ithink?
11:59 user24 butthenthatpatentisusedasanexcusenottoreleasepatent
encumberedsoftware
11:59 user26 Ibelievepatent-ableproductssharethepatentbetweenNASAandthe
contractor(ifappl)
12:00 User10 Sharedroylatiesiscorrect.
12:00 User10 ThereareveryfewNASAcodesthathaveeverbeenpatentedsoitisNOT
usedatooltopreventreleasetoothers.
12:01 user24 Butifthecontractorhasthepatent,it'shardforNASAtoreleasethecode
12:01 User10 Correct,ifothersholdthepatentNASAcanonlyreleaseforgovernment
purposes.
12:02 user24 whichiswhypatentsrelatedtosoftwaredevelopedforNASAshould
reverttoNASAownership
12:02 user26 ifNASAandacontractor"share"apatent,canNASA"buyout"the
contractorsinterest?
12:03 user24 you'dneverbeabletojustifythefunding12:03 user17 CouldheclarifyhowNASAcanmakemoneyortakeinfundsforNASA
patents?
12:03 user22 User1:What'sthebestwayforOpenSourceprojectstocommunicate
withGovernmentagencies?
12:03 user16 https://secure.wikimedia.org/wikipedia/en/wiki/Copyright_status_of_wo
rk_by_the_U.S._government
12:04 User10 PublicDomainisalegaltermandgovernmentworks,whilenot
copyrightable,arepatentablesotheyareNOTautomaticallypublic
domain.
12:05 User11 everythinghementionedisinteresting-butwadingthroughitrequiresa
lawyer.NASAneedsaano-nonsenseandeasy-to-comprehendpolicy
thatinvitesdeveloperstomakethedecisioneasy
12:05 user17 goodidea!
12:05 user21 greatquestion
12:05 user24 User11:hopefullythat'swhatwillcomeoutofthis
12:05 user17 herehereUser11!
12:05 User11 excellent
12:06 user16 Yes.It'susefulwhenOSSlicenseshaveFAQpages.
8/6/2019 NASA Open Source Summit Proceedings
51/85
50
12:06 user16 AsimilarFAQcanbecreatedforthelegalissuesinvolvedwithOSSat
NASA.
12:07 User8 Developmentgroupsshouldnothavetobecomelegalexpertstogetthe
benefitsofcollaborationandmoreeyesonthecode.
12:08 user24 I'dlovetoseesoftwarecontractedforNASAreleasedbydefaultunder
BSDorGPLunlessotherwisenecessary
12:08 user24 makeitpartoftheagreement
12:08 User8 @user24:+1
12:08 User10 Theydon'tneedtobecomelawyers.EveryCenterhasaSoftwareRelease
Authoritythatansweranyquestionsaboutthissubject.
12:09 user30-1 manthatwouldbewonderful.it'ssofrustratingtomanageaproprietary
SWprojectwithmultiplecontractors...everybodyhastosignNDA'setc
12:09 user24 yeah.Hell,havearequirementthatitbereleasedasit'sdeveloped.Solve
that"neverdone"problemhewastalkingabout
12:10 user24 alsoactuallygetaneyeonwhat'sreallybeingdone,ascomparedtowhat
thecontractorwantsyoutothinkisdone
12:10 user30-1 thenyouhavetheproblemofacontractorclaimingcopyrightoversome
trivialpieceofsoftware,andthentheyturnaroundandselltheir"secret"
modificationtothegovernmentatridiculousprices
12:10 User6 Andavoidthepossibilitythatasoftwarevendorcanuseittomilkthe
contract.
12:10 user24 woot!continiousreleaseprocess!
12:10 user24 that'swhatNASAneedsasdefault
12:11 user24 ted:I'msureNASAscleverlawyerscouldfigureouthowtodiscourage
that.
12:11 user21 thatsverytrue!
12:13 user24 Thisisneatsoftware.I'llneedtocheckitout
12:13 user24 butdiditstartasanOSSproject?
12:13 user24 oraNASAproject?
12:14 user20 ThisistheSoftwareReleasesiteforNASAGoddard:
http://ipp.gsfc.NASA.gov/SRA/Release-process.htm
12:14 User11 putitonapps.gov
12:15 user30-1 speakingofsoftwarereleasesites...doesanyoneknowwhathappenedto
CosmosCode?
12:15 User10 DoyoumeanCOSMIC?
12:15 user24 sawthecommentaboutthatintheuservoicestuff.
12:15 user24 I'mcuriousaswell
12:15 user30-1 itwasanARCproject.partoftheirCo-Lab
12:15 user30-1 sortofNASA'sversionofsourceforge12:16 User10 ThesoftwarewastransferredtotheNationalTechnologyTransferCenter
inWestVirginia.Thecodesareavailable.
12:16 user30-1 umm,theywereusingsvnanddrupal,etc.nothingrealearthshattering
12:16 User3 @User10:canweuseLGPLinsteadofNOSA?
12:16 user24 Thecodesaren'treallyrelevant.It'sthepeopleworkingtomakeit
happen
12:16 user30-1 theinterestingpartwasthatitwasaNASAhostedservice
8/6/2019 NASA Open Source Summit Proceedings
52/85
8/6/2019 NASA Open Source Summit Proceedings
53/85
52
throughonetrivialapprovalprocess,once,ever.
12:28 User6 Andeverythingwouldbeaderivedworkofthatset.
12:29 User1 QuestionsforFong?
12:30 user29 TheyshoulddoaLeanSixSigmaeventtolookattheopensourceprocess
togetthesoftwareapprovedmorequickly.
12:31 user19 Peopleneedtorecallthatcrowdsourcing!==opensource...thedifferencesaresubtle,butimportant
12:33 user26 @User1:CanwebdevelopersuseopenAPIs(e.g.,GoogleMapsAPI,etc.)
simplyundertheSpaceActAgreement,orisadditionalapproval
required?
12:34 user30-1 @user26:whywouldtheyberestrictedinthefirstplace?aredevelopers
restrictedfromusingotheropenstandards?
12:34 user26 @User1:notsure,hencethequestion.
Wednesday
Time Username Comment11:41 user16 Opensourcebydefault.That'saninterestingidea.
11:41 User2 IsthereanyNASAlawyerattendingorparticipatinginthisevent?
11:44 user15 Wetriedtohaveeveryaffectedgrouprepresented,andyes,thelaw
componentwillbecriticalinanysolutionsweimplement-soweneed
theminvolvedinthediscussionfromthebeginning.
11:44 User2 EncouragingNASAscientistsandengineers,andLAWYERStoparticipate
inOSSdevelopment
11:49 user18 andwebmasters
11:50 user22 User5:areyouinterestedinusingopensourceforyourwork?
11:51 User5 @user22...unfortunately,that'sadiscussionthathastohappenatamuch
higherlevelthanwhereIsit.11:52 User5 Weareconstrainedwiththetools,gear,manpowerandtaskinggivento
us.
11:52 User2 cuteanswer
11:52 User5 Atthistime,thetoolswearegivenworkandaresimilaracrossthe
Agency.
11:53 User5 OpenSourcewouldbeavaluabletool,butonequestionishowto
distributeacrosstheAgency,spanning11Centers...andacountry!
11:58 user22 BasicallyIamworkingtogetopensourceintobroadcastingwith2major
networksintheUSandlotsinEurope
12:00 user22 what'squiteinterestingisthattheyareinterestedinreplacingmission
criticalpartsoftheirbroadcastinfrastructurewithopensource,notjustthebackofficestuff
12:19 user16 MaybeChriscantalkaboutwhetheropensourceprojectsshoulduse
centralVCS(likeSubversion)oradistributedVCS(likegit,Bazaar,
Mercurial,...)
12:21 User11 needsomebodytotranslatewhatwassaidonday1(legalstuff)w/how
NASAcanuseGitHub.excitingstuff
12:21 user28 @User11+1.I'dlovetohearNASALegalmakeapronouncementonour
8/6/2019 NASA Open Source Summit Proceedings
54/85
8/6/2019 NASA Open Source Summit Proceedings
55/85
54
1:01 User1 askedApache&ITARquestion.thankyou
1:03 user13 haveyoulookedathowlongunmodifiedcodecansurvive-sincelicenses
mayimpactscontributions/updates
1:04 user13 rateofcoderot,howlongbeforethat2Blinesofcodebecomesuselessor
stopsworking1:05 user16 Thatwasagreatquestionfromtheaudience.
1:06 user16 WhichopensourcelicensedoesGoogleprefer?
1:06 user14 Apache2
1:07 user14 IhadthisquestionthatIdidn'tgetoutintime:Can
"useless/rotting/unattended"codebeturnedintoopen-source,by
default?SomethingliketheFOIAafteracertaintime?
1:13 user13 Thatsagoodquestionforthelawyers.Codeisreallyalivingthing,ifits
sitsaroundtoolong,itbecomesuselessorisreplacedwithsomething
else.
1:15 user13 Anyvaluethatthecodehadisoftenlost-andthatisabadthing,because
thevaluereturnedtothetaxpayerisdiminshed.1:16 User10 Howdoesthatdiminishvaluetotaxpayers?
1:17 User10 ThedefaultreleaselevelforallNASAcodewithoutexport/programmatic
restrictioniscurrentlyUSGeneralreleasewhichallowstaxpayersto
requestthecodes.
1:21 user13 Theassertionisthatlicensetypeimpactscommunityparticipation,and
communityparticipationdetermineshowlongandhowmuchvalue
certaincodemayhave(notall).
1:22 user13 theremayalsobecodethatsneverofficiallyreleasedbecauseofthelevel
ofefforttodoso.
1:23 User10 Bob,Idounderstandthosepoints.
1:24 User10 However,widelydisseminatedcodeswhenadaptedbyAirbusorEmbraer
alsoservetodiminishtaxpayervaluebecausetheyaidforeign
competetion.
1:27 user13 ITARisanimportantbutorthogonalissue.
1:32 user13 Clearly-wedon'twanttorunafoulofITARorsensitiveengineeringdata.
Butthereisalargeclassofcodethatcanandshouldbepushedtoanyone
thatcanuseit.
1:33 User10 ThereistruthinthatBob.Agenypolicylimitsustoreleasingcodethatis
forhealth,humansafety,qualityoflifeatthispoint.
3:43 user13 FYI:TheinitialworkforlargeSSIwasdoneatNASAAmes.Wecurrently
havea2048CPULINUXsystem.
3:44 User9
8/6/2019 NASA Open Source Summit Proceedings
56/85
55
3:54 user13 question:clearlyRHhasbenifitedfromOSS.HowdoesRHview
debrandedderivativeslikecentosororacle?positive/negative/neutral.
3:54 User1 thanks,Bob.
3:55 user25 Greatanswer.
3:56 user16 WhatopensourcelicensesdoesRedHatrecommendfornewprojects?
5:22 User1 Interestingtoseethenewparts,comparingtoLilly'spresofrom3yearsagohttp://www.slideshare.net/johnolilly/7-lessons-from-mozilla-
presentation
5:23 user16 SomequestionsforPascal:
5:23 user16 InwhatwaysdoesMozillaneedtoimprove,toincreasetheeffectiveness
ofitsopensourcedevelopmentefforts?
5:23 user16 DoyoubelievethatMozilla'sfocusonwebtechnologyhelpsMozilla's
effortstomaintainactiveopensourceprojects?
5:23 user16 Doyouthinkthatasingleorganizationcanmaintainactivecommunities
ofdevelopersofsoftwarethatcoverawiderrangeofpurposes?
5:24 user16 https://github.com/mozilla
5:26 User1 thx.asked5:27 user16 Beingableto*build*apieceofsoftwareiscrucial.That'sagoodanswer.
UserVoiceSubmissions
85Votes
Licensing
Thismayincludemanyissues,includingthefactthatNOSA(NASAOpenSourceAgreement)detersoutsidersfromusingNASAproducedsoftware.
Comments:
March28,2011
1:45PM
Lotofvoteshere,andthisisthekeytopic.ButI'mcuriouswhatdetailsofthe
NASAOpenSourceAgreement,
http://www.opensource.org/licenses/NASA1.3dooutsidersfindlimiting?
March28,2011
1:59PM
Agreed.theNOSAlicenseisunnecessarilycomplicated.NASAdoesn'teven
needitsownvanitylicensewhentherearesomanyappropriatechoices
already.PertheNationalAeronauticsandSpaceActof1958,anythingother
thanpublicdomainisquestionable.Where"fancy"licensescomeinhandyaretwofold:1)ForrespectingtheIPcreatedthroughjointprojectsbetweenNASA
anditsprivatecontractors.2)ForprotectingtheUSGovernment'sown
authorshipandcopyrightwhereappropriate,e.g.througha2clauseBSDstyle
licenseinsteadofplainoldpublicdomain.
March28,2011
AlsocanhavecaseswhereNASA/centerlegalstaffdecidenottorelease
softwarebasedonexternalopensource,iftheyhavetroubledeciding
8/6/2019 NASA Open Source Summit Proceedings
57/85
56
8:07PM whethertheexternallicensesaresatisfied.
March29,2011
1:03AM
Iwouldagreewithhimhere.Ifyouhaveanewproductwhichisaderivative
workwithcomponentsfromavarietyofdifferentopensourcelicenses,the
legalreviewburdenissubstantial,andunfunded.Sothecost-effectiveoption
is"don'treleasethework"sinceexternalreleaseisrarelyarequirementforthefundingproject.
March29,2011
1:30PM
IamlookingcloselyatNOSA1.3forthefirsttime,andfromtheperspectiveof
Recipient.Themostworrisomeparttomeisclause3.J."...Recipientishereby
putonnoticethatexportofanygoodsortechnicaldatafromtheUnited
StatesmayrequiresomeformofexportlicensefromtheU.S.Government.
Failuretoobtainnecessaryexportlicensesmayresultincriminalliabilityunder
U.S.laws.."ThisisnotcompatiblewiththeInternetasitexiststoday,andputs
alegalburdenthatmanygrass-rootsopensourceprojectscannothandle.
Theseandperhapsmanyacademicinstitutionswouldbewaryofbasingtheir
opensourceeffortsontopofit.HavingthisclauseintheNOSAwouldverynearlydoomacodebasetobeingthesameasclosedsource,i.e.,thepeople
whouseopensourceandrespectUSlawwillstayawayforfearofcriminal
prosecution.
March29,2011
1:57PM
Hehasavalidconcern,butIdon'tknowthatthereisanywaytogetaround
thefactthatNASAdoesstuffinspaceandtechnology,andit'sinjustsuch
areasthatexportcontrolsoftenapply.However,lotsofacademicandgrass
rootseffortsmanagetoworkwithintheexportcontrolrules.Sure,it'snotthe
totalcarefreeworldofpublishwhatyouwill.
March29,2011
3:04PM
Unlesstheappropriatepartofthesourcecodeisspecificallymarkedasexportcontrolled,thenhowisanyonesupposedtomeetthislicense?Ifsomethingis
notclearlymarkedasexportcontrolled,thenitshouldbefairgame.
March29,2011
3:22PM
Ourproject,OpenMDAOiscurrentlyreleasedunderNOSA.Wehavelotsof
outsideinterestfromAcademiaandIndustry.Noonehasyetexpressed
concernoverthelicense.Thatbeingsaid,Iseethattherearesomegotchasin
thelicense.Itwouldbenicetohaveotheroptions,butinourcaseitwas