VirtualBox

Changes between Version 17 and Version 18 of Contributor information


Ignore:
Timestamp:
11/17/2006 08:47:10 AM (13 years ago)
Author:
admin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Contributor information

    v17 v18  
    77On the other hand, if you know how to program C++, you are certainly welcome to '''contribute code''' of all sorts. 
    88 
    9 == Allowing InnoTek to incorporate your contributions == 
     9== Allowing !InnoTek to incorporate your contributions == 
    1010 
    11 Even though VirtualBox' source code is licensed to you under the GPL, it's not enough to submit your patches under the GPL. The [wiki:"Licensing FAQ"] will tell you more about how InnoTek handles VirtualBox licensing. 
     11Even though !VirtualBox' source code is licensed to you under the GPL, it's not enough to submit your patches under the GPL. The [wiki:"Licensing FAQ"] will tell you more about how !InnoTek handles !VirtualBox licensing. 
    1212 
    1313In any event, if you like to contribute anything that is subject to copyright (text, media, or code), InnoTek must be legally certain they can redistribute the code you have contributed to their own customers who have purchased closed-source editions of !VirtualBox. In order to be able to accept your contribution, we must therefore ask you to do one of two things: 
    1414 
    15  1. Fill out the [wiki:"InnoTek Contributor's Agreement"] (ICA) and send it to InnoTek. In the ICA, you give InnoTek permission to use your contribution under licenses other than the main !VirtualBox license. This is a once-in-a-lifetime event: once we have your ICA, we will never again ask you to undergo any bureaucratic procedures, and all future contributions are covered.  
     15 1. Fill out the [wiki:"InnoTek Contributor's Agreement"] (ICA) and send it to !InnoTek. In the ICA, you give !InnoTek permission to use your contribution under licenses other than the main !VirtualBox license. This is a once-in-a-lifetime event: once we have your ICA, we will never again ask you to undergo any bureaucratic procedures, and all future contributions are covered.  
    1616 
    1717 2. If you don't want to sign such an agreement, you can alternatively submit your contribution under the [wiki:"MIT license"]. This is a liberal, wide-spread Open Source license that basically says "do as you wish".  
    1818 
    19 Basically, the main difference between the two options is this: With the ICA, a written statement is necessary, but then ''only'' InnoTek is allowed to relicense your code (unless you give other people the same permission). With the MIT license, you save the paperwork, but everyone else can use your code as well. It's your choice. 
     19Basically, the main difference between the two options is this: With the ICA, a written statement is necessary, but then ''only'' !InnoTek is allowed to relicense your code (unless you give other people the same permission). With the MIT license, you save the paperwork, but everyone else can use your code as well. It's your choice. 
    2020 
    2121== The VirtualBox development model == 

www.oracle.com
ContactPrivacy policyTerms of Use