> Hi,
>
> Pardus is a Linux distribution funded and developed by the Turkish
> Government.
> We're planning to release a Corporate version - Pardus Corporate 2 - which
> is
> based on KDE 3.5.
>
> We've been maintaining KDE 3.5 for a very long time so we have a lot of
> bugfix/feature patches in our base packages.
>
> I want to push those patches to trinity after doing a review with trinity
> contributors about their upstreamability.
>
> And then I really want to switch to Trinity KDE in Pardus Corporate 2 as
> this
> will be a long-term supported release which should a have a maintained
> desktop
> environment.
>
> Right now I started to prepare packages for the dependencies.
>
> I'm waiting for your co-operation to make things better.

This sounds like a great idea!  I am not sure how you would like to
slipstream the bugfixes into Trinity, as equivalent patches may have
already been applied.  Suggestions here are welcome.

The main criteria for including patches into the Trinity project is that
a.) No existing user-visible functionality is removed
b.) If new functionality is added or the user interface is altered that
said functionality or UI changes can be deactivated by the end user
through a GUI configuration option
c.) The patches must be maintainable; i.e. clearly understandable by a
third party and adhering to all rules of the programming language in use.

Thanks!

Timothy Pearson
Trinity Desktop Project