If I can identify and fix any of the problems that I am having I will
make specific suggestions about how to fix them.
It was not my intention to fix code written by people who are much
better coders than me without some confirmation that the fix makes sense.
I am still trying to learn about the system so I am reluctant to declare
my problems as bugs.
I have made corrections to the Wiki reflecting the things that I learned
about building the system under Eclipse.
What I am looking for in the forum, is confirmation that my problems are
general or that there is a configuration error that I made. It seems to
be counterproductive to file bug reports about configuration errors that
I made.
Ron
Lee Carroll wrote:
Ron,
Gregor j rothfuss wrote
as soon as the bugs are shaken out. if you test 1.4, make sure to
file bugs :)
I think this is a hint that one contribution you can make is to follow
the apache quidelines on filing bugs.
Spending the time to systematically record and descibe the problem in
the appropriate tool. Sounding off
in the mail list is of limited worth. (and I'm sure I've been quilty
of this too)
One approach to open source often quoted is, "If its broke its up to
you to fix it if you can." It's not a choice between
lenya or this or that cms on functionality terms. It should be a
choice between the commitment of communities.
(I can't resist, just to sound off in a mailing list, opencms is
devoid of a varied community and is run pretty much by a single
organization. Of course this my have changed and developed)
Lee C
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
