Ivan Jouikov wrote: > > > Sounds to me like a lot of people are using JAMES... why > don't we all throw > some money together, even $200/person, and donate it to the > developers? > That should give them a good push in the right direction... > And if they can > clean up the site, make some good predictions as to what features/etc > they're planning to introduce, you guys could get your bosses > to cash out...
There are lots of reasons why people contribute their energies to OSS projects like James. In my experience, money is rarely one of them. The major constraint for most experienced James developers is time. I say this with some feeling having just completed yet another 12 hour day on the work that earns me a living. Many people on this thread have expressed the opinion that its a steep learning curve to understand the James architecture and see this as a block to contributing, while others have cited poor documentation as an impediment to getting a useable configuration up and running. One great way to solve the latter problem while learning about the former would be to research and contribute enhanced documentation. Currently, only a subset of the Mailets and Matchers are documented. It would be great if volunteers could fill in the gaps by looking at the Javadocs and source code and documenting their use for humans. The same goes for any other documentation areas people feel are lacking, such as setup and use-case scenarios. -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
