[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received

John A. Sullivan III jsullivan at opensourcedevel.com
Sun Aug 29 04:45:41 BST 2010


https://bugs.kde.org/show_bug.cgi?id=86423





--- Comment #158 from John A. Sullivan III <jsullivan opensourcedevel com>  2010-08-29 05:45:24 ---
On Sun, 2010-08-29 at 02:03 +0200, Simon Toth wrote:
> https://bugs.kde.org/show_bug.cgi?id=86423

Well we have a bounty amount and a bounty hunter.  Tim Pearson of the
Trinity project (http://trinity.pearsoncomputing.net) has said he would
do the work for $1500 (US).  When I asked if he could review the bug
report and see if the information would help trim the cost, he replied:

"I was already aware of the bug report you linked to, and I consider the
fact that KMail 4 is *still* missing this feature as a rather bad omen.
I am concerned a large rewrite of the editor is in order, and after this
CalDAV/CardDAV project I don't have much confidence in the ease of
extension of any part of kdepim.  Hopefully enough people are still
interested to get the project started!"

I can verify his concerns.  The bounty we posted for Zimbra integration
including CalDAV/CardDAV was originally $300.  We voluntarily increased
that to almost as large as this bounty and I'm sure Tim's time was worth
much more than we paid (and, no, we are not making it up together on
this job - Tim and I have no financial or business connection other than
I paid a large bounty to him for Kontact/Zimbra integration patches).

So now we have a few practical details to make this happen.  First, we
need a rough spec for the work.  Is it as simple as:

"The final patch will enable KMail running in KDE4 and the Trinity
version of KDE3 to reply to HTML email in HTML format including editing
in HTML format by simply choosing to reply when the email which is being
replied to is displayed in HTML mode.  If the email is being displayed
in text, the reply will initially be in text but with an option to edit
and send the reply as HTML.  Patches to KDE4 will be submitted
upstream."

Or do we need something more specific including HTML standards, which
html tags should be supported, something about css support, etc? Would
someone care to write it? I am no HTML expert.

We then need to coordinate the bounty until the pledges (no money sent)
equal at least $1500.  I would be willing to do that.  You can send your
pledge amounts to me at jsullivan (we'll break this up)  at (to thwart
the spammers)  pacifera  (I'm sure you know) dot (what to do)  com.

I've suggested to Tim that payment be in thirds - one third before work
begins, one third when the first patch is delivered, one third on final
sign-off (bugs fixed).  Tim is comfortable with this.  Coming to
consensus on sign-off can be a bit tricky.  I would hope we will all be
civil and fair.

The tricky part is actually transferring the money.  I have a vested
financial interest in this patch as we would like it for our clients. I
have also worked with Tim before so he knows I pay the bills in good
faith and he is comfortable with me functioning as the fund coordinator.
If others are not, I quite understand but someone needs to do it.  Tim
is uncomfortable with people sending money to him directly because he is
concerned about deadbeats not paying the final third.  He also thinks it
unfair for him to collect all they money up front as that is a lot of
trust to place in an unknown entity. That's why he prefers the funds be
escrowed by a third party with a financial interest in the final patch.

We also need to account for those who do not make good on their pledges.
I will pledge $100.  I will also pledge to make up any shortfall for up
to another $100.  I would suggest we pull the trigger when the pledge
amount hits $1600.  If we only collect $1400 of it, I'll make up the
$100 difference.  If we hit $1500, we'll pay that.  If we collect the
full $1600, we'll pay that all to Tim as an extra thank you for his
work.

Thoughts? Comments? Insults? - John

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list