Gili wrote: > > On Tue, 14 Dec 2004 14:35:16 -0500, Serge Knystautas wrote: > > >Ahmed Mohombe wrote: > >>> a) we're developing on the branch "branch_2_1", not the > MAIN branch. > >> > >> Interesting. Are there other "unusual issues" with JAMES > like the above > >> that a new user should know (before in his desperation > abandons JAMES)? > > > >Know this is open source, and if you want something done, > feel free to > >do so. > > Not to be too cynical here, but this is really bad feedback > coming back from a development team. All the projects I've had the > displeasure of dealing with that have stated: "This is open-source, > what more do you expect?" have ultimately delivered terrible products > because they believed exactly what they were saying. The best > open-source products I've worked with were backed up by an > enthusiastic > development team. > > Just food for thought. > I think that by browsing the mail archives - http://nagoya.apache.org/eyebrowse/SummarizeList?listId=21, http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED] apache.org - you will find that we do provide pretty good feedback when people hit issues. But then as one of the people who answers questions when I can, I am biased.
As an experienced developer in the commercial world, familiar with development processes and source control, I had few problems getting up to speed with James' and its development process. While getting started, I sometimes had to ask and invariably got helpful answers. I see the same happening today just as when I went through this process. For less experienced people delving into source the problem can often be more one of understanding source code management and development process than James per se. I also see happy James users helping each other in the James user group. That is great as eveyone is helping each othet and it can sometimes be that what is obvious to a developer needs interpreting into user more friendly language. But the bottom line is that most developers watch this site and as a James user you will often get support directly from a James developer, that can only be a positive. While specifically NOT aiming this at anyone in this particular thread, and not wishing to appear complacent, I continue to be stunned by the number of people who ask the same questions, when they have not done elementary searches of the mailing lists, read the FAQ or looked at the Wiki to see if the question has been asked and resolved already. Even more stunned by the willingness of others to answer and hugely grateful that they do. "Know this is open source, and if you want something done, feel free to do so." has many avenues. Augment the Wiki installation instructions, submit a patch to the FAQ, enhance the code. In general, if you have learnt something in getting James to work for you that is not documented, give it back so that those who follow can learn from your experience. Enthusiastic? I think we demonstrate that most everyday. Could do better? Of course, contribute! -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
