Occasionally, it is worthwhile expending effort highlighting that there are
other resources to draw on. Resources which may help resolve problems more
quickly than mailing the lists. And that one contribution everyone can make
is to add their experiences and knowledge gained to the Wiki. The more
people do this, the more valuable a resource the Wiki becomes.
Of course. But I think that in this case, it would be more effective to do the quick fix, since as we have seen about every month somebody tries to build the head, runs into the trouble, asks the mailing list...
Take into account that James is quite overwhelming to start with. Unfortunately the site is not as clear as it could be and is not immediately obvious how to find valuable information in Wikis and mailing list archives...
I'm sorry if you read anything I wrote as a complaint. This was a personal
observation about how things are and a suggestion as to how everyone in the
community can better help each other.
I didn't mean your post in particular... the thing is that it happens frequently that a new James user enthousiastically tries to accomplish something, runs into issues which he posts, still happy to contribute to the project, and then the replies are, ehm, not very thankful. After that, the new happy user suddenly doesn't post that often anymore.
I think that it is very valuable for the James project to keep new enthousiastic users on board and enthousiastic... My point is that if it happens frequently that someone downloads the wrong branch, make it easier for them to download the right branch, in stead of telling them they were wrong...
This extends of course to installing and usability issues.
All valid ideas, as would be someone with practical James experience contributing to the Wiki "How To Develop From James Source".
Point taken :-)
But I wish I'd gotten so far as to build from a CVS checkout... :-/
My Wiki would be "Download the source package and try to build that first".
I will try to see if I can get some useful information up there in the coming days.
But Wiki is not the only thing, there is also the web site. I would also wnat to help out and updte the documentation. I have tried to suggest some improvements through the mailing lists and through JIRA, but have had no response... I'm afraid that is rather discouraging. For example, the mailet documentation on the site is out of date, and I am willing to help updating is. But if noone reacts to the observation, I am not taking the trouble of preparing revised documentation, while taking the risk that that will not be picked up either...
Cheers,
Hes.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
