(cut and pasted from the POG board, as Dee posted it there as well)
Woo hoo! Thanks Dee.
Now that the announcement has been made public, I would like to put forth some sort of community effort of adding to/modifying the trinity project. I don't know how many people plan on modifying trinity, but if there are multiple people that do plan on fiddling with it and releasing new trinity plug-ins, we could certainly get into a mess really quick. I imagine 20 versions of trinity that people would have to download and switch between to get minor improvements or features, which would be awful.
I'm not sure what the solution is, but we have time since the source hasn't been released yet, and I figured I would open up discussion on it now that Dee has made the announcement.
I've thought about this for a short while and my the only thing I can think of is to set up some sort of "trinity community," possibly done through a mailing list. Those that wish to modify trinity and release the modifications as an updated version of the trinity plug-in would correspond with the others working on the project, and if no one else was currently working on it they would download the most current source code, do their modifications, and then upload the plugin and the modified source code. Then the next person who wished to modify it would download the modified source code, add their changes, and upload the new source + the new plugin. This way everyone's modifications would be included in a comprehensive plug-in, as opposed to having 50 different "trinity plugins" which would be chaotic.
There would also need to be some rules to this, such as timeliness(as no one would want to wait while someone dinked with the code for 4 months), and documentation(if you change/add/remove something, it should be noted so all developers realize it and don't have to "find" it). I would also like to think that the trinity source would be used only to "fix" existing problems(like shapeshifting bugs, spelling errors, etc) and to allow for compatibility with other plug-ins(I plan on adding a global variable to trinity to make it compatible with a plug-in I am writing). Major changes that affect the flow of the plug-in, or adding things like new classes, etc, should be discouraged as they would be better suited in a seperate plug-in.
Anyhow, these are my thoughts on the subject. Anyone else who is interested in developing with the Trinity source, please post your thoughts.
Also, those here on the CS board who may have ideas on how to facillitate an open source coding project please chime in as I'd love to hear them.
Thanks.
------------------
This may not be your favorite song, but it's got a lot of the same notes.
- KGGO Des Moines in the front?