ReactOS IP Policy Document

[Jason Filby]

Hi all

Vizzini has spent a lot of time writing a ReactOS IP Policy Document;
he's also had it reviewed by lawyers. I agree what's written here, and
would like to get some feedback from the community before we publish
it as our official policy.

Regards
Jason

[K McI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason Filby wrote:
| Operating System (OS):  A special class of computer software designed to
| provide an environment in which general software can be run.
Operating systems
| interface directly with the hardware of a computer, and provide a
standardized
| set of services that applications can interface with.  Examples include
| Microsoft(R) Windows(TM) XP, GNU/Linux(TM), and Apple(R) Macintosh(TM).

I haven't exhaustively read all of this, but this stuck out. Isn't
"Apple Macintosh" also the name of the entire product line (EG. Hard and
soft, from 1984 to 2005) ? I suggest "and Apple(R) Macintosh(TM) OS
X(Whatever mark appropriate)" since the MS example specifically cites XP
as it's example.

Thanx

~       -uniQ
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFB6XEu7mze81O92HkRAuDSAJ44ITub2V2d6hm7LVqo6KfcGmSgoACgkaws
> ZhIimtpwzHTVsyrpRX1SNCo=
> =/06o
> -----END PGP SIGNATURE-----

[Guido]

Hi, 

To me section "A. ReactOS Copyright" is not clear. I'd rather rewrite to
something like this:

"The ReactOS Project releases almost all of its code under the GNU
General Public License (http://www.gnu.org). Some portions of ReactOS
may be licensed under other licenses, including the GNU Lesser GPL, or
placed into the public domain.  This is generally done only when
necessary for compatibility with other projects.

Each developer maintains his or her copyright in the developed source
code. All code initially developed for use by the ReactOS Project must
be licensed under the GPL."

I could be wrong, but I think this comes closer to what you actually
meant to say. And even if I am wrong, the fact that I interpretted this
section in this way might be something to consider.

- Guido


On Sat, 15 Jan 2005 13:26:07 +0200
Jason Filby <jason.filby(a)gmail.com> wrote:

>   Hi all
>  
>  Vizzini has spent a lot of time writing a ReactOS IP Policy Document;
>  he's also had it reviewed by lawyers. I agree what's written here, and
>  would like to get some feedback from the community before we publish
>  it as our official policy.
>  
>  Regards
>  Jason
>

[Ralph Shumaker]

A few things are amiss in the wording:


Jason Filby wrote:

>  Hi all
>
> Vizzini has spent a lot of time writing a ReactOS IP Policy Document;
> he's also had it reviewed by lawyers. I agree what's written here, and
> would like to get some feedback from the community before we publish
> it as our official policy.
>
> Regards
> Jason
>   
>
> ------------------------------------------------------------------------
>
> REACTOS PROJECT DEVELOPMENT POLICY 
> 12 Decenber 2004
>
> (snip)
>
> I.  INTRODUCTION
>
> Because of the nature of the ReactOS Project, copyright, patent, and other
> legal issues regularly arise in the course of development.  This document
> analyzes each of these areas law and explores implications for ReactOS
> development.
>   
>  
Namely, "... each of these areas law ..." does not make sense.  Perhaps 
it should read "... each of these areas *of* law ..."?


>  Following are the policies of the ReactOS Project as
> they relate to copyright:
>
> 1) Code copying is absolutely never allowed, unless the copied code is in the
>    public domain or is distributed under a Free software license which permits
>    is combination with a GPL program, such as ReactOS (i.e. is GPL Compatible).
>    You should always assume that you do not have a license unless you are
>    explicitly given one.
>   
>  
I think "... which permits is combination ..." should read "... which 
permits its combination ...".


>    2b) Developers are encouraged to NOT attempt to copy
> the coding style
>       of non-free code.  While coding style may not covered by copyright, a
>       similar or identical coding style to a piece of non-free code casts
>       suspicion on the new code.
>   
>  
Perhaps "... may not covered ..." should read "... may not *be* covered 
..."?


>  
> III.  PATENT ISSUES
>
> Software patents have a profound affect on the ReactOS Project.  Currently,
> software patents are legal (i.e. software is statutory matter) in the United
> States.  As a rule, patents are fundamentally incompatible with Free Software,
> and should be carefully avoided in the context of such projects.
>   
>  
"... affect ..." should be "... effect ...".


>  4) Project participants agree that they will not seek
> patent protection for any
>    new developments made in conjunction with ReactOS, or in the alternative,
>    agree in advice to assign ownership of such patents to the ReactOS
>    Foundation, or else to grant a perpetual, irrevocable, transferable,
>    royalty-free license to anyone who wishes to use the patented invention in
>    conjunction with the ReactOS system or in any derivative work of the system
>    (in other words, something like a "patent-left").
>   
>  
Maybe you mean "... agree in advance ..." instead of "... agree in 
advice ...".


>  
> VII.   Other
>
> 1) Trademark and Service Mark Anti-Dilution.  Anti-dilution provisions prevent
>    even the un-related use of a "famous" mark or at trademark that is 
>    confusingly similar to a famous mark.  ReactOS uses only one mark, the 
>    ReactOS mark itself, which does not appear to raise any trademark anti-
>    dilution issues with any other marks.  
>   
>  
I think '... "famous" mark or at trademark ...' should read '... 
"famous" mark or *a* trademark ...'.

[Jason Filby]

Hi all

Thanks to everyone for the feedback regarding the IP Policy. Find the
latest revision attached. Unless there are any more objections I'll
publish this copy.

Thanks
Jason

[Ralph Shumaker]

Jason Filby wrote:

>  Hi all
>
> Thanks to everyone for the feedback regarding the IP Policy. Find the
> latest revision attached. Unless there are any more objections I'll
> publish this copy.
>
> Thanks
> Jason
>   
>
> ------------------------------------------------------------------------
>
> REACTOS PROJECT DEVELOPMENT POLICY
> 2 February 2005
>
>   
>  
>  The "Microsoft" and "Windows" marks
> are property of Microsoft Corp.
>
> I.  INTRODUCTION
>
> Because of the nature of the ReactOS Project, copyright, patent, and other
> legal issues regularly arise in the course of development.  This document
> analyzes each of these areas law and explores implications for ReactOS
> development.
>   
>  
I still think that "areas law" should be "areas of law".


>  C.  Copyrights of Others
>
> The ReactOS Project depends on copyright law for the protection of its code,
> and by the same token, it respects the copyrights of others.
>
> Following are the policies of the ReactOS Project as they relate to copyright:
>
> 1) Code copying is absolutely never allowed, unless the copied code is in the
>    public domain or is distributed under a Free software license which permits
>    is combination with a GPL program, such as ReactOS (i.e. is GPL Compatible).
>    You should always assume that you do not have a license unless you are
>    explicitly given one.
>   
>  
I still say "permits is combination" should be "permits its
combination".

It looks like you got the rest of my suggestions.

[Filip Navara]

Jason Filby wrote:

>    - Microsoft Installable File system Kit (IFS):  A
> special-purpose SDK designed
>     for the development of certain kernel-mode components known as file
>     systems.  This kit is distributed under a restrictive license and for a 
>     fee of around $1000.
>   
>  
should be "...known as file system drivers..." instead of "known as
file 
systems" IMHO.

- Filip