On 4/18/06, Matt Rogers <[EMAIL PROTECTED]> wrote: > Hi, > > In line with the mentioning of moving to kdepim in the topic of #kopete, I'd > like to propose something different: > > Move kopete into its own module.
Dunno if it's the best idea. Moving it to kdepim makes a lot of sense because the contact integration and all (and it's where Kopete really belongs to, and I believe tying it to kdepim would be better in the long run), and at least imho Kopete has to be tied logically to some kde module. > Doing this will allow us to have a lot more flexibility with regard to our > release schedules and our ability to release fixes for issues with closed > protocols when they occur. We already can release whenever we want. We're launching 0.12 out of the "official stable" branch because we have the flexibility to do so. At the same time _not_having_ the "flexibility" allows us to (at least try) to meet kde's deadlines, and imho its a good thing(tm). Fixes to protocols can be commited to -stable anyway. It's among distros' responsibility to update their packages to reflect the changes made by us. We shouldn't be concerned about them at all. > I'm completely against moving kopete anywhere else unless it's to extragear or > its own module. Any other locations at this point are counterproductive, > especially with the possible introduction of kdepimlibs, which we would also > be able to depend on. If we have to move to somewhere, the best place is kdepim. Extragear is just running away from main and losing some perceived "official" status by potential users, and it wouldn't help. Putting Kopete in its own module doesn't make sense because we're in fact tied to kdepim a lot more than we're tied to kdenetwork, and moving to kdepim is the logical step. ymmv Cláudio Pinheiro (taupter) _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
