Thanks David. Your points are helpful. We will add a definitions section
and include a definition for free software. With regard to the model code
for Article 2, we would like to amplify the meaning of source code in a
practical sense rather than a conceptual sense. In doing so, it might be
3.4 Licensor reserves the right at any time to cease
public release of
the Licensed Software or, if released, to change fees
and prices,
features, specifications, capabilities, functions,
licensing terms,
release dates, general availability or other
characteristics of the
release. Title,
On Thursday 23 May 2002 4:03 am, Rod Dixon wrote:
Please take a moment or two to download a draft of the framework for our
work on the OSD. We have only posted Article 1. We would like to hear
your thoughts on the framework. It is our view that a model code is the
most helpful framework for
Good point! Thank you.
Rod
On Thu, 23 May 2002, phil hunt wrote:
On Thursday 23 May 2002 4:03 am, Rod Dixon wrote:
Please take a moment or two to download a draft of the framework for our
work on the OSD. We have only posted Article 1. We would like to hear
your thoughts on the
--- phil hunt [EMAIL PROTECTED] wrote:
This is very similar to the GPL. Why not just use
that?
The big issue is that the GPL allows companies that do
not distribute modifications outside their company to
sue consultants/employees/contractors that distribute
changes that have been made to
Rod Dixon wrote:
...what I am unsure of is whether we should be satisfied
with the status quo or whether we should amplify Article 2 with something
more than just saying the source code should not be deliberately
obfuscated. Poorly expressed source code need not be deliberately
obfuscated to
6 matches
Mail list logo
