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

[John A. Sullivan III]

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





--- Comment #204 from John A. Sullivan III <jsullivan opensourcedevel com>  2010-10-30 17:53:48 ---
On Mon, 2010-10-25 at 11:54 +0200, Simon Bühler wrote:
> https://bugs.kde.org/show_bug.cgi?id=86423
<snip>
Hi, all.  This is becoming a bit complicated because we have two very
distinct needs wrapped up in one project.  As long as we are patient
with each other, I'm sure we can work through it.  Let me state the
issues as I see them and a proposed solution.  It will be a little
complex but I think it will work.

We have the developer of the patch and several key bounty contributors
who need the KDE3 version and are happy to see the KDE4 version but KDE4
is not a requirement.

We have many other bounty contributors (perhaps the majority) for whom
the patch is useless unless it works for KDE4.

In the current offer, because of the needs and environment capabilities
of the developer (to whom I extend great thanks for being willing to do
this), the KDE3 project is a pre-requisite to the KDE4 project.

The danger is KDE4 users contributing to the bounty for the KDE3 project
because it is prerequisite and then there not being enough funds to meet
the second bounty for the KDE4 port.  In which case, they will not have
a usable return on their investment.  So how do we try to please
everyone and, more importantly, keep from accidentally defrauding
anyone? Here's a proposal:

1) We finalize and close the KDE4 spec so we know what the bounty is.  I
think Tim was hesitant to do that because of not really knowing what is
involved until the KDE3 patch is done but I think we'll have to take our
best guess.

2) We set up the KDE3 bounty on chipin and those who need the KDE3 patch
commit their contributions.

3) We do NOT set up the KDE4 bounty on chipin (I'll explain why in a
minute) but those who need the KDE4 patch send their pledge (not their
money) to Tim who will post the results on the Trinity RFE site.

4) Once the KDE4 bounty is hit (I suspect it will be reached before the
KDE3 bounty), remaining KDE4 contributors send their pledges to the KDE3
chipin bounty since the KDE4 patch will not be released without it.
This is why we do not want to put the KDE4 pledges on chipin because
once the amount is reached, the funds are disbursed but we do not want
to release the KDE4 bounty until the KDE3 bounty is also met since we
can't have one without the other.

5) Once the KDE3 bounty is hit, Tim commences work and releases the
KDE3.

6) Now that work can proceed on the KDE4 AND we have sufficient pledges
to fund it, we setup the KDE4 bounty on chipin, collect it, and do the
patch.

I think that will work.  If you followed me, no need to read further.
If I've confused you, let me explain it another way.

We probably have more contributors to the KDE4 bounty than the KDE3
bounty.  The KDE3 bounty is bigger than the KDE4 bounty and is a
prerequisite.  So let's have KDE4 contributors first fill the KDE4
bucket to make sure they're not left without a viable patch for their
money at the end of the project.  Once we've filled the KDE4 bucket,
KDE4 users start filling the KDE3 bucket since it is a prerequisite to
the KDE4 project.  Once we have both buckets full, we can safely begin
work without risk of accidentally defrauding the KDE4 users.

If we happen to fill the KDE3 bucket first, then problem solved (at
least the problem of potentially defrauding the KDE4 users).

Sorry for the complexity but I want to ensure we are all working
together and not accidentally at cross purposes.

Please send your feedback.  If there is no great objection, then we
should proceed with step #1 - finalizing and closing the KDE4 spec.
Thanks - John

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