Community generated patches

niko · Post by **niko** » Wed Feb 18, 2004 7:08 am

BradB wrote:Well, there is an unused CVS tree here at Irrlicht
Niko would you mind turning over the keys to CVS to someone here?

That's an idea. If you like, saigumi? About wrong mails: No problem, I could simply forward to the right one.

saigumi · Post by **saigumi** » Wed Feb 18, 2004 1:16 pm

Sure.. set me up.

saigumi · Post by **saigumi** » Wed Feb 18, 2004 2:38 pm

Below is a link to the draft of the protocol/howto submit a module document.

Let me know your thoughts.

http://www.saigumi.net/3p-irrlicht-modules.txt

buhatkj · Post by **buhatkj** » Wed Feb 18, 2004 2:56 pm

i cant see anything m8issing from your doc sai, looks like you got it down.

-Ted

keless · Post by **keless** » Wed Feb 18, 2004 3:04 pm

looks good. though you may want to write something in there to keep people cross-platform and cross-compiler aware. Like "it is required to work in blah, blah blah" or "if it does not build in all three compilers/OSs, say so in the conflict area" or add two new catagories "Supported Compilers" and "Supported OS"

BradB · Post by **BradB** » Wed Feb 18, 2004 8:27 pm

Good protocol, I like it. Could I suggest another type "bugfix", where you are fixing a bug in Irrlicht & not submitting new features?

Only thing that is a little lacking is a directory structure, for example (I don't know the layout of the Irrlicht code) what if I make changes to
irrlicht/source/util/someutil.cpp
irrlicht/source/core/list.cpp

Maybe the README file needs to list all changed files & their original location within the Irrlicht directory structure.

Cheers
Brad

saigumi · Post by **saigumi** » Thu Feb 19, 2004 3:37 pm

Document updated: http://www.saigumi.net/3p-irrlicht-modules.txt

Irrlicht Engine

Community generated patches

Should there be a community repositry of patches?

looks great, think you got everything...