Submitting code to OpenSim - Revision history

Diva at 20:17, 21 August 2015

2015-08-21T20:17:22Z

Orenh at 06:36, 26 July 2015

2015-07-26T06:36:15Z

Justincc at 18:14, 22 October 2013

2013-10-22T18:14:06Z

Justincc at 18:13, 22 October 2013

2013-10-22T18:13:16Z

Justincc at 04:00, 8 November 2012

2012-11-08T04:00:07Z

Justincc at 03:57, 8 November 2012

2012-11-08T03:57:39Z

Justincc at 03:55, 8 November 2012

2012-11-08T03:55:00Z

Justincc at 03:54, 8 November 2012

2012-11-08T03:54:24Z

Justincc at 03:54, 8 November 2012

2012-11-08T03:54:08Z

MakoBot: Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

2012-03-04T07:00:30Z

Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

@@ Line 11: / Line 11: @@
 Please review the [[Coding standards]] and stick to them in your patch. The only exception should be if the surrounding code does not conform to these guidelines, in which cases its okay to be consistent with the code already in the file.  If a patch does not follow the guidelines we will ask for it to be changed.
-Please put only one logical change in a patch at a time. Patches that contain more than one logical change tend to be larger, more complex and hence take more time to be applied. At worse, developers will tend not to look at them because it's hard to disentangle all the possible effects.
+Please put only one logical change in a patch at a time. Patches that contain more than one logical change tend to be larger, more complex and hence take more time to be applied. At worse, developers will tend not to look at them because it's hard to disentangle all the possible effects. Multiple logical changes can be in a patch if they only affect a single feature (like, for example, the feature the patch enables).
 == Test ==

@@ Line 3: / Line 3: @@
 <br />
-* '''Before you begin, please review our [[Contributions Policy]]'''.
+== Overview ==
-* Not all patches will make it into OpenSimulator.  To keep a lid on code complexity, OpenSimulator is not trying to be a 'batteries included' project.  Things that can't be considered core functionality are better implements as an external region module.  If extra hooks/events are needed to make these work then patches for those are very welcome.
+'''Before you begin, please review our [[Contributions Policy]]'''.
-* Please review the [[Coding standards]] and stick to them in your patch. The only exception should be if the surrounding code does not conform to these guidelines, in which cases its okay to be consistent with the code already in the file.  If a patch does not follow the guidelines we will ask for it to be changed.
+Not all patches will make it into OpenSimulator.  To keep a lid on code complexity, OpenSimulator is not trying to be a 'batteries included' project.  Things that can't be considered core functionality are better implements as an external region module.  If extra hooks/events are needed to make these work then patches for those are very welcome.
-Code is submitted to OpenSimulator via patches attached to entries in our [http://opensimulator.org/mantis/my_view_page.php Mantis bug tracker]. One way to generate these is by using the Git command line
+Please review the [[Coding standards]] and stick to them in your patch. The only exception should be if the surrounding code does not conform to these guidelines, in which cases its okay to be consistent with the code already in the file.  If a patch does not follow the guidelines we will ask for it to be changed.
   git format-patch <commit hash>^!
-This will package up all your git commit changes into a nice easily appliable file.
+This will package up all your git commit changes into a nice easily applicable file.
-* Please run the automated tests (via "nant test" on the command line) before submitting your patch. Patches that add new tests (either to test accompanying patch code or to test existing code) are very welcome.
+Alternatively, if you have a specific commit, or range of commits, that you want to include in the patch, then run this command:
-* Please put only one logical change in a patch at a time. Patches that contain more than one logical change tend to be larger, more complex and hence take more time to be applied. At worse, developers will tend not to look at them because it's hard to disentangle all the possible effects.
+ git format-patch -<num> <newest commit hash>
-* In your Mantis, the title line should ideally start with [PATCH]. When you've opened it, change the state to patch included. Once you've put in on a Mantis, you may want to hop on the IRC channels and mention it someone there (though at the moment we're pretty good at getting round to these, since e-mails about newly opened mantis entries are sent to developers automatically).
+For example, if your commit hash is a30f224, and you want the patch to include only this one commit, then you would use this command:
 * Once you've submitted your patch please move the Mantis entry into the '''Patch Included''' state to let us know there's a patch waiting to be reviewed.  It might take a bit longer to see a mantis entry with a patch if it's not in this state (and in unfortunate rare cases it may be missed altogether for a period).
-* General turnaround time for patch review is a week. though, it could be up to two weeks depending on the situation.  If you want to chat about a patch (or remind people that it exists after a week has gone by), please feel free to pop into #opensim-dev on IRC or send an e-mail to the opensim-dev ailing list.
+Once you've put it on a Mantis, you may want to hop on the IRC channels and mention it someone there (though at the moment we're pretty good at getting round to these, since e-mails about newly opened mantis entries are sent to developers automatically).
-* When a patch is reviewed, it will either be applied (in which case, thanks very much!) or the Mantis entry will be changed to the "Patch feedback" state with comments from developers/interested parties.  If you revise the patch in light of the discussion, please then change the state back to "Patch Included".
+== Helping Out ==
-* If you're looking for an initial piece of code to do, the bugs in Mantis are a very good starting point. You may want to see if there's anybody on IRC to discuss the difficulty of a particular bug (they do vary, sometimes in unexpected ways).
+If you're looking for an initial piece of code to do, the bugs in Mantis are a very good starting point. You may want to see if there's anybody on IRC to discuss the difficulty of a particular bug (they do vary, sometimes in unexpected ways).
 [[Category:Development]]

@@ Line 7: / Line 7: @@
 * Not all patches will make it into OpenSimulator.  To keep a lid on code complexity, OpenSimulator is not trying to be a 'batteries included' project.  Things that can't be considered core functionality are better implements as an external region module.  If extra hooks/events are needed to make these work then patches for those are very welcome.
-* Please review the [[Coding standards]] and stick to them in your patch. The only exception should be if the surrounding code does not conform to these guidelines.  If a patch does not follow the guidelines we will ask for it to be changed.
+* Please review the [[Coding standards]] and stick to them in your patch. The only exception should be if the surrounding code does not conform to these guidelines, in which cases its okay to be consistent with the code already in the file.  If a patch does not follow the guidelines we will ask for it to be changed.
 Code is submitted to OpenSimulator via patches attached to entries in our [http://opensimulator.org/mantis/my_view_page.php Mantis bug tracker]. One way to generate these is by using the Git command line

@@ Line 17: / Line 17: @@
 * Please run the automated tests (via "nant test" on the command line) before submitting your patch. Patches that add new tests (either to test accompanying patch code or to test existing code) are very welcome.
-* '''Please''' put only one logical change in a patch at a time. Patches that contain more than one logical change tend to be larger, more complex and hence take more time to be applied. At worse, developers will tend not to look at them because it's hard to disentangle all the possible effects.
+* Please put only one logical change in a patch at a time. Patches that contain more than one logical change tend to be larger, more complex and hence take more time to be applied. At worse, developers will tend not to look at them because it's hard to disentangle all the possible effects.
 * In your Mantis, the title line should ideally start with [PATCH]. When you've opened it, change the state to patch included. Once you've put in on a Mantis, you may want to hop on the IRC channels and mention it someone there (though at the moment we're pretty good at getting round to these, since e-mails about newly opened mantis entries are sent to developers automatically).

@@ Line 21: / Line 21: @@
 * In your Mantis, the title line should ideally start with [PATCH]. When you've opened it, change the state to patch included. Once you've put in on a Mantis, you may want to hop on the IRC channels and mention it someone there (though at the moment we're pretty good at getting round to these, since e-mails about newly opened mantis entries are sent to developers automatically).
-* Once you've submitted your patch please move the Mantis entry into the '''Patch Included''' state to let us know there's a patch waiting to be reviewed.
+* Once you've submitted your patch please move the Mantis entry into the '''Patch Included''' state to let us know there's a patch waiting to be reviewed.  It might take a bit longer to see a mantis entry with a patch if it's not in this state (and in unfortunate rare cases it may be missed altogether for a period).
 * General turnaround time for patch review is a week. though, it could be up to two weeks depending on the situation.  If you want to chat about a patch (or remind people that it exists after a week has gone by), please feel free to pop into #opensim-dev on IRC or send an e-mail to the opensim-dev ailing list.
 * If you're looking for an initial piece of code to do, the bugs in Mantis are a very good starting point. You may want to see if there's anybody on IRC to discuss the difficulty of a particular bug (they do vary, sometimes in unexpected ways).
 [[Category:Development]]