mozilla.org and ports
paul <paul <at> nospam.usa.netscape.com>
2003-05-13 01:48:32 GMT
The following comment was made on Bug#204177:
> BeOS, VMS, and OS2 are not officially supported by mozilla.org (they
> are ports). we try not to bust the ports, but we try even harder not
> the primary platforms. it simply can't be the job of every developer to
> maintain the ports. we can all try, but it can't be our first priority.
> blocker status seems misused if only the ports are busted. moreover,
> development is not hindered... you can add --disable-profilesharing
> mozconfig. so, why don't you help out with the patch (since you are
> testing on BeOS) instead of fussing over the status of this bug?
I understand that BeOS is not officially supported, but, a little
concideration would be nice. The IPC bug is not the first time, that
certain parts of mozilla that are new features, have just been "turned
on", which breaks the ports. I am the primary developer of the BeOS
port, and, was never informed about the fact that this change was going
to be implemented. This is a volunteer project, we do not have paid
developers to work on the port. But, people do somewhat depend on
myself and a couple others, to make sure that the beos port is
maintained, and, improved. I don't mind having to do the work to fix
the BeOS port, even though timeless beat me to it for this one. But I
had started working on it, without knowing of timeless's work. The
thing is, that I had to drop the other work I was doing, to fix this.
If I would have known ahead of time, I could have set time aside, and
started looking into the issue, before it became a problem.