From Bil.Kleb at NASA.gov Fri Jan 4 15:08:52 2008 From: Bil.Kleb at NASA.gov (Bil Kleb) Date: Fri, 04 Jan 2008 15:08:52 -0500 Subject: [NASArb-developers] summary of ARC ad-hoc open-source working group approach In-Reply-To: <477E7F52.8040302@nasa.gov> References: <477E7F52.8040302@nasa.gov> Message-ID: <477E9254.1000109@NASA.gov> Terry Fong wrote: > Chris & James, > > Let me try to briefly summarize where the ARC ad-hoc open-source working > group was at when it last met (6/20/2007). If anyone else has additions, > or corrections, please chime in... This is interesting, thanks for sharing with the list. I didn't even realize that the NOSA hinders contributions from the community. We recently received some enhancements to http://rubyforge.org/projects/nasarb/ from a third party. Sigh, I guess I'll have to go read the NOSA again... > * - need to create a NASA contributor agreement (POC: Matt Hancher) > * - need a "continuous open-source release" process so that do not have to > wait 3 months to release new features (POC: Terry Fong) FWIW, we have a "Continuous Integration Agreement" that our external FUN3D developers sign upfront so that "by committing code to the repository, you agree that NASA can release it, etc." Regards, -- Bil Kleb 757.812.1805 http://fun3d.larc.nasa.gov From Bil.Kleb at NASA.gov Fri Jan 4 15:47:01 2008 From: Bil.Kleb at NASA.gov (Bil Kleb) Date: Fri, 04 Jan 2008 15:47:01 -0500 Subject: [NASArb-developers] summary of ARC ad-hoc open-source working group approach In-Reply-To: <90DC0F1BB0C6414E8677784E71D74B61297DEE@NDMSEVS34B.ndc.nasa.gov> References: <477E7F52.8040302@nasa.gov> <477E9254.1000109@NASA.gov> <90DC0F1BB0C6414E8677784E71D74B61297DEE@NDMSEVS34B.ndc.nasa.gov> Message-ID: <477E9B45.7040605@NASA.gov> Padilla, Robert M. (ARC-DL) wrote: > Hi Bill, Hi. > Let me try to clarify things a little regarding contributions. It isn't > that the NOSA really "hinders" contributions, it's that without some > sort of contribution agreement, clear rights aren't adequately defined > in contributions. But I thought that was one of the intents of an OSI license? I.e., to spell out how contributions are treated. > We've learned that most companies have contributors > sign a contribution agreement before they will accept contributions into > their open source software. What do the unwashed masses do? I've never heard of a "contribution agreement" in the wild... > It sounds like you are already using a > contributor agreement of sorts for the FUN3D development. We are, but it is not released under NOSA because it is export restricted software. My concern is the NOSA software we have at http://rubyforge.org/projects/nasarb/ I didn't realize that contributions were not somehow addressed via NOSA, and I'm surprised that it isn't a requirement of the OSI stamp of approval. > Have a good weekend. Likewise, -- Bil Kleb 757.812.1805 http://nasarb.rubyforge.org From hmk at ipp.mpg.de Wed Jan 9 05:36:40 2008 From: hmk at ipp.mpg.de (Hans-Joachim Klingshirn TOK) Date: Wed, 09 Jan 2008 11:36:40 +0100 Subject: [NASArb-developers] funit+fortran extensions Message-ID: <4784A3B8.3080909@ipp.mpg.de> Hello all, I've been signed up to this project for some time now, but only recently came back to using it. I am using funit in a makefile-based build system for a largish Fortran code to introduce unit testing for new code that gets added in the course of my work. For this, I want to implement in the following features: -USEing of of additional modules in .fun files For more complicated test setups I want to be able to use additional modules in the test code, which are not used by the tested module itself. This requires a little extension of testsuite.rb -command line switch for funit.rb to only expand the tests, without compiling and running them. In the environment here, not all systems I want to run the tests on have ruby installed, so I want to separate creation of the test code from compiling+running it. -I want to use the fortran dependencies code to generate makefile dependency lines for compilers supporting inlining code from other fortran files. This basically some refactoring in fortran.rb and a little frontend to use it. Bil, before I get started on this, another question: I saw on the commit mailing list that on Dec 27 you commited the patches by Diego Virasoro in revision 395. Unfortunately, when I check out the current trunk revision 395, the patches are not included - am I missing something here? Cheers! Hajo -- http://www.ipp.mpg.de/~hmk/ From hmk at ipp.mpg.de Wed Jan 9 06:55:34 2008 From: hmk at ipp.mpg.de (Hans-Joachim Klingshirn TOK) Date: Wed, 09 Jan 2008 12:55:34 +0100 Subject: [NASArb-developers] funit+fortran extensions In-Reply-To: <4784A3B8.3080909@ipp.mpg.de> References: <4784A3B8.3080909@ipp.mpg.de> Message-ID: <4784B636.4090700@ipp.mpg.de> Hans-Joachim Klingshirn TOK wrote: > Bil, before I get started on this, another question: I saw on the commit > mailing list that on Dec 27 you commited the patches by Diego Virasoro > in revision 395. Unfortunately, when I check out the current trunk > revision 395, the patches are not included - am I missing something here? Ah, never mind this question - I assumed the patches are already applied to the trunk. Cheers! Hajo -- http://www.ipp.mpg.de/~hmk/