The initial purpose of this list (fpc-devel) was to discuss about the development of FPC. But this has changed, only a little discussion about FPC development is done on this list. So I'll try to change this by posting information about FPC development on this list.

For the curious: a long time ago, when some of the active developers had problems with this list (long delay of message delivery), we created an email alias to coordinate developement but this made FPC development a little bit non-open and it makes it also very hard for new developers to keep up-to-date.

I vote for establishing an FPC-Bugs mailing list.
Fixing problems is different from advancing a concept.

I vote for establishing an FPC-Bugs mailing list. Fixing problems is different from advancing a concept.

You mean something like fpc-bugs where also the notications about bug reports go to?

Alexander Stohr wrote

I vote for establishing an FPC-Bugs mailing list.

For sure I agree with him.

BTW, Alex, did you receive my mail (remember, walking stacks...). Ok, if you did not know, now everything is ok.

Bye.

_________________________________________________________ Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Is there any reason against using this list as bugs mailing list? Development means also fixing bugs. Forwarding the bug reports from the web form to this list would maybe increase the traffic by 4-5 mails a day.

I also was under the impression that that was exactly what this list was for ?

Development means also fixing bugs. Forwarding the bug reports from the web form to this list would maybe increase the traffic by 4-5 mails a day.

If wanted, I can do that, but I don't think this is a good idea; some people may no like that their reports are unadvertedly forwarded to a list.

Michael.

If wanted, I can do that, but I don't think this is a good idea; some people may no like that their reports are unadvertedly forwarded to a list.

But what's the difference? The bug reports are also available to public at the website!

Subject: Re: [fpc-devel]Purpose of this list

for ?

But aren't the reports publicly available anyway ?

Michael.

Regards,
Thomas

Hi,

it's only a question of ethics. It's bad style to use any data in another way than the submitter
expects. But I think this is also the solution: Just mention on the web-page that the report
will also be posted to the developer mailinglist, and you should be fine.

Stefan

To improve privacy the reports can be sent without information about the submitter. This info isn't necessary, maybe we can also remove it from the public section of the web site?

From: Florian Klaempfl

I don't know if it is a significant difference, but mails to the mailing list are placed in an on-line archive (or used to be placed) and can be found by a search engine, i.e. altavista. I didn't succeed in finding the bug reports through altavista.

Vincent Snijders.

Not the ones sent to

Michael.

Date sent: Thu, 28 Sep 2000 15:57:26 +0200
From: Florian Klaempfl
To:
Subject: Re: [fpc-devel]Purpose of this list Send reply to:

I'm sending a copy of this to fpc-other list - we should probably move this discussion there.
I could find a reason for a separate list as well myself. Some people might only be interested in knowing about possible bugs, answers to their own bug reports, workarounds, date of the snapshot, which solves the problem, etc., and not in highly specialized discussions about compiler development (it's a waste of bandwith for most users, I guess). I wouldn't try to introduce people to FPC development by moving the core discussions to the list, where bug reports should be directed. This will only cause people unsubscribing from the list sooner or later, instead of keeping them in touch with the development, IMHO. Most probably they'll start to send reports to fpc-pascal instead - the question is, whether we want this.

Tomas

If the relevant mails about development are few, then 4-5 mails a day become a big number. The optimum is always get what you expect; for example, I am interested in developing in the sense I want to know what is going on, and sometimes would be interesting for me to see at other's bugs. But there is an efficient way to know about bugs (on the fpc web), a full featured database; if I want to see if others have discovered the same bug I have, I can; if I want to help in fixing bugs, I can too.

You are not whole wrong, in effect... but may be only particular bugs would be interesting here, say, biggest ones, or strangest. Unluckily, nearly everyday I read all the messages in this list, but for many of them I don't see really the contents: if I see a boring list of compiler messages, then I skip. This way I can skip important things too, but for me time and energies are important. If there was less bug-reports, I think it would be better.

Even so, it is good, anyway.
Thank you and cheers.

__________________________________________________ Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com