Re: Announcing the VM/370 and VM/380 "SixPack" version 1.2 release candidate 1!

--- In [email protected], "Rocky" <rocsystems@...> wrote:
>
> Harold
> 
> As promised -
> 
> No License and definitely open source

Note that code is copyright by default these days,
and needs an explicit statement to say that it is
being released to the public domain, which is how
I interpret "no license".

> I don't want to put the source on the  SixPack-Release 
> just yet, Just for Source version Control purposes, 
> as I have no control over updating that.

The whole point of open source is that others
can update it. It is harmless if others update
it. That doesn't magically cause your official
version to change!

Also note that if it is genuinely public domain,
you can't stop people from including source in
the sixpack should they choose. Or for updating
their own version.

So if you wish to exercise control over it, you'll
need to keep it copyrighted, and have an explicit
licence as to what people can or can't do.

In addition, if your problem is with people making
code changes and then it being difficult to merge
them into the official version, then that's what
"diff3" (included on the sixpack) will do for you.
It is a 3-way diff, one of the greatest achievements
in computer science.

So would it be possible for you to:

1. Put a copyright notice and licence on the code
so that people know where they stand, or else
explicitly release it to the public domain.

2. Have a zip file with ASCII source and put it in
the files area here, with an explicit version
number of the product (even if that is 0.03 or
whatever).

Thanks.  Paul.