Stephan,
Having been around here for a while I'd be very surprised to find code
contributions simply 'ignored'. If you look at Guacamole's development
history I think you'd see that contributions are welcomed, and where
they address a need and/or fit the project well they are incorporated.
Naturally there would be discussion, and it *may* be that some
contributions are not [immediately] accepted, however they would not be
discarded out of hand for no reason. Perhaps this has been your
experience of other projects but please don't anticipate it here.
Otherwise it's my view (and clearly that of many others) that Guacamole
is not a 'mediocre' product. It has its flaws and no doubt could be
improved, but being derogatory about something is not especially
productive and rarely a good way to effect change.
Thus I wonder if you might spend a little time looking closely at
Guacamole's development and how/why it works the way it does presently?
As an active project with good interaction and hard working developers,
input from experienced coders would be gratefully received. However I
suggest the usual way to go about changing something is first to become
involved, become 'known' by your contributions, to gain better knowledge
of the issues and direction facing the project, and thence be able to
effect positive and cohesive change...
On 22/04/24 08:06, Stephan von Krawczynski wrote:
You may get/see some patch from me to achieve what I want to do with guacamole,
and I expect it to be ignored. I take it as documented then and it may help
further readers along their way.
Often people deny to see how they can make a very good product out of their
mediocre one, unfortunately.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
