> > Obviously reading leak MS/DR-DOS source code is bad, but I want to
> > make sure.
> >
> Those are of course off-limits. (Well, a bit questionable in case of
> DR-DOS, I don't know what exactly the license said when it was briefly
> available as OpenDOS)
>
>
Yes, these are off-limits.
If you download and study the MS-DOS source code, you should not contribute
code to FreeDOS afterwards. We want to avoid any suggestion that FreeDOS
has been "tainted" by this proprietary code. Note that Microsoft released
the source code to an early MS-DOS (version 1, I think?) in March, 2014.
But we have consistently asked that FreeDOS developers should not download
this.
Also, DR-DOS was released as OpenDOS at one point, as Ralf says. OpenDOS
used a very strange license that basically said "you may look, but do not
touch." You were allowed to study the source code to OpenDOS, but could not
use it in other projects, and could not modify the source code to fix bugs
or make it do something else. For this reason, OpenDOS is not really "open
source software," and I ask that FreeDOS developers do not download and
study the OpenDOS source code.
DR-DOS has not released any source code under the name "DR-DOS." So if
anyone finds source code to DR-DOS, you should assume this is illegally
leaked and not look at it.
Jim
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
