Le Mercredi 19 Avril 2006 02:28, Matt Rogers a écrit : > 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. > > 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. > > 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.
Here is my opinion: I don't like being in kdeextragear because: a - Users don't beleive it is a part of the core kde application. b - We don't get translation c - We have to take care about our own schedule. But kdeextragear is nice because d - We can release more often. e - User can upgrade only Kopete without upgrade the whole KDE (at least kdelibs+kdenetwork) Having Kopete in his own module does not have bad side effect of kdeextragear. but doesn't really have the advantage #d. Also I don't think it is justified to have kopete as a "module"
pgpEpaFezes0x.pgp
Description: PGP signature
_______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
