Community Supported Requests For Enhancement [RFE]

The following RFEs are currently open and available for editing
No work has started. Pending approval of developer(s) sponsoring the RFE.

Title Description Specification Bounty Sponsoring Developer(s) Comments Status
KMail HTML Add basic HTML editing and inline image support to Trinity KMail Locked
[Click for Software Details]
Timothy Pearson
Trinity Project Lead Developer
Pledged: $300.00
Collected: $0.00
KDE4 Port
Port KMail HTML support to KDE4
Depends on "KMail HTML" RFE completion
Timothy Pearson
Trinity Project Lead Developer
Pledged: $0.00
Collected: $0.00
The following RFEs have been finalized
Implementation is in progress or has been completed. No further changes to the specification are permitted.

Title Description Specification Bounty Sponsoring Developer(s) Comments Status

Frequently Asked Questions

Why do I have to pay for new features? Isn't the Trinity Desktop Environment free software?
As most Free Open Source Software projects are built and maintained in software developer(s) free time, only those features that are of interest to the developer(s) are generally implemented when the developer(s) are left to themselves. You do not need pay for a new feature. If you would like, you may try to implement it yourself by modifying the source code that comprises the Trinity Desktop Environment.

If you are unable to implement the feature yourself for any reason, and the Trinity development team is not actively working on the feature, you have an alternative. By offering monetary support to a sponsoring developer, you allow that developer to allocate more time to work on the Trinity project, specifically on the feature that you would like to see implemented.

As hiring a software engineer can be expensive, the Trinity project has decided to allow many individuals to contribute small amounts towards the feature(s) they would like to see implemented. At first, no payment is required, only a pledge that you would pay a certain amount if others will also contribute. When enough pledges are received for a certain feature, we ask that all interested individuals pay their pledge amounts to a third party. At this point, the sponsoring developer(s) begin working on the feature, and when the feature is complete to the users' satisfaction the payment is released by the third party. If for any reason the sponsoring developer(s) are unable to complete the feature, all contributors will be reimbursed for their original payment amounts.

* The payment system works somewhat differently for precompleted/ready-to-release software. In this case, the developer can place the software up for bounty for a limited time; if the bounty has not been met by the expiration date the software can be removed without release. You would NOT receive a refund in this case, so you may wish to handle pledges and funds collection/delivery in collaboration with your business, local Linux user's group, or similar third party.

How will I receive the software once the bounty has been paid?
All software available through the TDE RFE system will be released under a Free and Open Source Software (FOSS) license once the bounty has been paid for that particular software. For those projects requiring development, you will need to wait for the developer to finish the software before you will be able to download it. Predeveloped/ready-for-release software will generally be released within a few business days after the bounty has been met. In all cases a link to the software will be placed on this page when it is available for download.

How can I contribute?
Please contact Timothy Pearson at with the name of the feature you wish to sponsor, your name, and the amount you are willing to contribute.

** The editable specifications are locked for new Wiki users as an anti-spam measure. Please contact Timothy Pearson at with your registered Wiki name to receive write access to all editable specifications.