[Namaste-dev] Re: Weekly Plan June 2 - June 6
w5nyv at yahoo.com
Thu Jun 5 10:44:35 PDT 2008
To me, an engineering effort is a compound phrase formed of effort, which is the expenditure of energy to get a particular goal accomplished, and engineering, which is the act, in part or in whole, of maneuvering or managing scientific knowledge for practical purposes.
Yes, I'm referring to software in any form, as well as hardware, and design documents, requirements, analysis, and any other supporting engineering documentation along the way.
I am very interested in providing a community resource and community property here with respect to designing satellite ground stations, both in our particular case and in general, through the production of verification and summary documents that are products of later phases.
I'd like to identify a policy or license that will serve us for the entire process, serving for the engineering effort as well as the final product. Are there any well-known problems or drawbacks with GPL that we should consider?
----- Original Message ----
From: Eric Blossom <eb at comsec.com>
To: Michelle <w5nyv at yahoo.com>
Cc: Bruce Perens <bruce at perens.com>; namaste-dev <namaste-dev at amsat.org>
Sent: Thursday, June 5, 2008 9:49:22 AM
Subject: Re: [Namaste-dev] Re: Weekly Plan June 2 - June 6
On Thu, Jun 05, 2008 at 06:44:15AM -0700, Michelle wrote:
> What do you all think of using Creative Commons licensing for the engineering effort?
What do you mean by "engineering effort" ?
If you're referring to s/w in any of its forms, I think we should
stick with one of the well known and understood free / open source
FWIW, I'm a fan of the GPL since it strongly encourages the ongoing
creation of a community resource -- a commons if you will.
More information about the Namaste-dev