Rationales for Open Source Release

Contact the author
ames, legal, opensource No Comments »

recently a colleague sent an email out to an agency discussion group about open source, asking about rationales for open source release. his management didnt see the justification for his request to release his software under the NOSA. it’s interesting that although, as someone in the resulting discussion pointed out, NASA’s own charter states that it shall “provide for the widest practicable and appropriate dissemination of information concerning its activities and the results thereof”, open source software release is, in many instances, still seen as more of special case, than as a natural way to minimize overhead while maximizing the aforementioned dissemination (among other things).

last year i did a series of interviews with a cross section of developers, engineers, managers, and lawyers at Ames about open source. from there, i compiled the rationales they offered as the motivation for their interest in open source. i think it’s worth noting that none of these are unique to NASA per se, but i do consider all of them strong reasons in their own right for open source release and/or development, and certainly together they present a strong argument for encouraging open source release as long as there is no explicit reason not to. Read the rest of this entry »

del.icio.us:Rationales for Open Source Release  digg:Rationales for Open Source Release  spurl:Rationales for Open Source Release  simpy:Rationales for Open Source Release  newsvine:Rationales for Open Source Release  blinklist:Rationales for Open Source Release  furl:Rationales for Open Source Release  reddit:Rationales for Open Source Release  fark:Rationales for Open Source Release  Y!:Rationales for Open Source Release

community content and project hosting

Contact the author
ames, cosmoscode, nasa, opensource 1 Comment »

as most people know we are working on putting together an open source development site for nasa ames. these tools would support active open source development, as opposed to just release, by providing technical tools as well as a collection of written resources and documentation about the institutional, legal, and technical challenges, existing precedence, best practices, and general community support and interaction.

for a long time i’ve thought that we should create one comprehensive open source space community site, with the written resources and community interaction as the overarching element of a site that also hosts numerous individual projects and the respective tools to support this (wikis, issue tracking, subversion, etc.).

Read the rest of this entry »

del.icio.us:community content and project hosting  digg:community content and project hosting  spurl:community content and project hosting  simpy:community content and project hosting  newsvine:community content and project hosting  blinklist:community content and project hosting  furl:community content and project hosting  reddit:community content and project hosting  fark:community content and project hosting  Y!:community content and project hosting