Em Quarta 19 Abril 2006 12:55, Matt Rogers escreveu: > If we move Kopete to trunk/KDE/kopete, then a and b are not issues, because > we would still be a core KDE module. e becomes very easy for packagers and > other folks to do. c is a weak point because i'm not talking about having > our own release schedules all the time. In fact, I think it makes lots of > sense to still release with the KDE releases. Kopete 0.12 was a special > case, since KDE 4 is going to be a long way away.
0.12 being a special case or not, in fact we can release as often as we want. Some distros (like Kubuntu) package Kopete as an app by itself, showing no ties to kdenetwork at all besides its dependencies. It can even point to a possible migration to our own module if distros already handle it this way, but the point is we do not have to be worried about how Kopete will be packaged for a particular distro. Distro maintainers are already paid to do so. We must be concerned about what does make sense from developers' point of view. > i don't want to move extragear. if we don't move to trunk/KDE/kopete, we > might as well just stay in kdenetwork. Instant messaging is not a PIM app, > so kdepim makes no sense, no matter how much addressbook integration we > have. -- > Matt Well, Kopete handles lists of personal contacts and allows us to communicate with them, just like Kmail, but just in a more agile way. So that's why imho it belogs to kdepim. Kdenetwork made more sense before the contact integration, but now we're more PIM than a torrent kioslave. Be it kdenetwork or kdepim, it will not make such a big difference at all, I just think the closer proximity with the kdepim team would help in the long run, but even this would be minimal. Cláudio (taupter) _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
