On Tuesday 20 September 2011 22:43:01 Timothy Pearson wrote:

> >> >> As a project with limited resources we do not support applications
> >> that:
> >> >> a.) Are maintained upstream
> >> >> b.) Have standalone replacements that fully include the feature set
> >> of
> >> >> the
> >> >> application in question
> >
> > I would prefer to use an application that is integrated with my desktop.
> 
> What's wrong with Kopete or Konversation?

I don't know, do not use both. Anyway in Kopete I do not like the appearance.

> >> >> c.) Would utilise an unusual amount of Trinity developer resources to
> >> >> maintain, especially applications where there are legal problems or
> >> b.)
> >> >> above applies.
> >> >> d.) Have a very low user base under Trinity.
> >
> > I don't think user base of Trinity is large anyway.
> 
> Well, the population of power users is small compared to regular users in
> most cases anyway.  You know what I meant; out of Trinity users I would
> bet most people never even heard of kde-sim.

I completely agree with you. But if you take power users, or 90% of of the
messengers for KDE3 the picture will not change.

Not only sim, but I bet they did not heard about the following instant messengers:

kmess
psi
licq
kadu

and many others.

> If you want to maintain it that's fine with me. 

Oh now. It is quite enough for me that I maintain them in KDE:KDE3

> I won't consider it for 
> inclusion in the Trinity archives until it supports the Yahoo protocol
> legally again, and even then it would be conditional on your future
> maintenance to handle problems with APIs, etc. 

It is your project, maintain it yourself. I maintain my project,
you maintain yours. I only can point your attention to certain things.

> From where I sit there are 
> plenty of good Trinity-integrated IRC applications available, 

If you are talking about IRC apps, there are even more of them than instant messengers, 
of course. But IRC and IM are something different things.

> and effort 
> should be focused on fixing bugs and upcoming problems such as the
> network-manager 0.9 API switch.

Sure.