Required reading for TB-Core members IMO

Bron Gondwana brong at
Fri Oct 31 04:46:53 UTC 2014

On Thu, Oct 30, 2014, at 07:23 PM, JoeS wrote:
> Hey, I understand there are always "Edge Case" TB
      users, whose wants can be pretty much dismissed.
      But more and more, especially in this age of social media,
      communications are expected to be web-like.
      We have done little to address this trend.
      I urge you all (as painful as it may be) to read through the
      following bugs completely:
>  * 250539[1]
>  * 590640[2] And as you read, ask yourself how we could ask
      these users to contribute to TB

Totally unrelated (or maybe not), FastMail open-sourced our HTML5 editor
a while ago. It is pretty much entirely designed for generating nice
HTML emails.

It works very nicely in Firefox (that's what I'm doing now), and it
doesn't come with any UI of its own, just good APIs for hooking up
your own UI.


Back on topic - yes, those bugs - ouch. This isn't a rare problem in
open source either - look on any project. But then check this out: Bug
ID 18777415: Use RFC6186 for auto discovery of mail server settings

Apple Developer Bug Reporting

Oct 29 (23 hours ago) to appledev

Hello Marian,

Engineering has determined that your bug report (18777415) is a
duplicate of another issue (7685458) and will be closed.

The open or closed status of the original bug report your issue was
duplicated to appears in the yellow "Duplicate of XXXXXXXX" section of
the bug reporter user interface. This section appears near the top of
the right column's bug detail view just under the bug number, title,
state, product and rank.

An example of the duplicate section from the bug reporter user interface
with your bug and the duplicate bug info is included below:

18777415 Use RFC6186 for auto discovery of mail server settings

State: Closed Product: Rank: No Value
Duplicate of 7685458 (Open/Closed)

If you have any questions or concerns, please update your report
directly here:


You don't have a monopoly on shitty responses to bug reports. This is us
reporting that autodiscovery in Apple's mail client is
broken - with an RFC they bloody well wrote themselves. We will get no
more information on this bug, only the original reporter will.

And we're paying them for the privilege of a developer account, and
every one of the users who is being affected by this bug paid them for
their software.

So don't be too hard on yourselves as you read this bug. Certainly
resolve to be nicer to bug reporters, and make things not crap - but
don't be too ashamed to ask for money so that you _can_ dedicate
resources to fixing their issues. I bet a few of those reporters and
their big companies would have been willing to pay for a fix if you'd
been able to phrase it the right way to the right person. They pay
licence fees to other companies for the illusion of being listened to.


Bron Gondwana brong at


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the tb-planning mailing list