Changes between Version 28 and Version 29 of Contributor information

Timestamp:

Dec 15, 2006 1:29:05 PM (17 years ago)

Author:

jose

Comment:

--

Contributor information

@@ -21 +21 @@
 == The !VirtualBox development model ==
 
-The source code of !VirtualBox resides in a public subversion repository which is hosted on this site. Currently, only !InnoTek employees have write access to ensure that only reviewed and tested patches find their way to the repository. However, over time, we would like to extend the group of people with write access.
+The source code of !VirtualBox resides in a [http://www.virtualbox.org/browser public Subversion repository which is hosted on this site]. Currently, only !InnoTek employees have write access to ensure that only reviewed and tested patches find their way to the repository. However, over time, we would like to extend the group of people with write access.
 
-Patches are always first applied to an !InnoTek internal subversion repository and then automatically synchronized to the public repository. A large test laboratory at !InnoTek's facilities and a dedicated test team in 24/7 operation ensures that the code quality remains excellent: dozens of test machines perform automated tests to spot regressions and monitor performance.
+Patches are always first applied to an internal !InnoTek repository and then automatically synchronized to the public repository. A large test laboratory at !InnoTek's facilities and a dedicated test team in 24/7 operation ensure that the code quality remains excellent: dozens of test machines perform automated tests to spot regressions and monitor performance.
 
 Automated build servers for all supported platforms create ready-to-run !VirtualBox installers every time changes are made to the !VirtualBox source code. These development builds provide end users with the latest features but may not necessarily be well tested or stable.
@@ -31 +31 @@
 == How to submit your contributions ==
 
-If you have developed a patch for !VirtualBox which you think could be useful for others and fits within the product's architecture, then you should submit it for inclusion. As a first step, you should execute the [wiki:"InnoTek Contributor's Agreement"] which is a very straightforward and risk-free process. Then you should submit your patch to the '''vbox-dev''' [wiki:"Mailing lists" mailing list] along with a description of what it does. In case you have not signed the ICA, please explicitly state that you license the patch to us under the premises of the [wiki:"MIT license"].
+If you have developed a patch for !VirtualBox which you think could be useful for others and fits within the product's architecture, then you should submit it for inclusion. As a first step, you should execute the [wiki:"InnoTek Contributor's Agreement"] as described above, which is a very straightforward and risk-free process. Then you should submit your patch to the '''vbox-dev''' mailing list (see the "[wiki:"Community"]" page) along with a description of what it does. In case you have not signed the ICA, please explicitly state that you are licensing the patch under the [wiki:"MIT license"].
 
 Please keep in mind that it might take some time to review your patch and integrate it. Also, please expect feedback from other developers on how to improve your patch and address potential issues. We can only incorporate your patch if it does not harm the product stability.