[Lazarus] Is there a separate mailing list for Lazarus developers?

Reinier Olislagers reinierolislagers at gmail.com
Sun Jan 5 15:49:56 CET 2014

On 05/01/2014 15:07, vfclists . wrote:
> @Matthias and Bart - I think it helps to open up the more technical
> discussions to outside viewing. There is always smart lurker out there
> who can help with some abstruse issue which escapes you or you don't
> have the time or resources for. Kostas issue is an example of what I am
> taking about. Not that many people would be familiar with that area, be
> involved with it and to recognize that there was a bug there let alone
> have knowledge of the library or API internals to fix it. Bugs for most
> people mean bugs in programming logic not in interfaces to specialized
> libraries.
Nothing wrong with holding that discussion on this list. Go for it, I'd say.
It is *very* telling that Kostas did not ask for or need access to
anything else than he already had (this mailing list, the bug tracker etc).

> @Juha - Perhaps you could follow the example of the older wiser heads
> such as Florian and Matthias who have responded to this thread with
> examples and suggestions because they had a better understanding of why
> I asked this question. Just because someone's manners or style rubs you
> the wrong way doesn't mean they are trolling - which is generally
> understood to be creating drama and controversy for its own sake.
Well, just because somebody's reply rubs you the wrong way doesn't mean
the impression you create is the one you might necessarily want to give.

As said by (I think) everybody, it all starts with code contribution.
Yes, in patches. Yes, on the bugtracker.
If you give excuses about not being able to contribute code but are
willing to correct other people's code (which is what your posts seem to
imply to me)... that's not much use, is it? Because you cannot even test
your own suggestions.

The impression you're giving me is somebody who is used to a set
practice of having well laid-out development goals, central steering
etc, and you are unwilling to just jump in and get started. I may very
well be wrong about it, but we're talking about impressions here.

That said, I hope you'll be able to contribute patches/code - it can
only improve Lazarus.

> A belated Happy New Year to Lazarus Developers and Congratulations for
> what is a good development tool given their resource constraints. <snip>

And best wishes for a good 2014 to you, too.

More information about the Lazarus mailing list