I would like to contribute but don't know the open source process.
Lets take for instance Chuck's work on XMLSearch() or the bug we
discovered a month back regarding openBD cfhttp not decompressing gzip
content. What would be the steps for building those solutions into JAM
or openBD tag/script library.
You can contribute the code as a patch and we will then review it and
integrate it into the main build if its good enough and doesn't have any
knock-on effects to the rest of the engine. We have had numerous
contributions to the code line from the community.
Alternatively, you are free to build your own version of the engine and
run that particular one. Open source gives you that flexibility. you
never have to wait on the core branch. Everything we release can be
built by yourself, either via Apache Ant, or inside Eclipse.
Supporting ORM would surely demand much more talent than i have.
Interesting though that experts (you guys) could not reach a
conclusion on the benefits of ORM. Puzzling in fact. May be it is too
complex to implement.
LOL @ "too complex to implement" ... aaah no. We are not scared of
complexity, we love hard problems to solve, that is why we are software
engineers. This particular one, isn't a hard one. It all comes down
to time. Where is our time best spent?
--
official tag/function reference: http://openbd.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
