clarification on git, central repositories and commit access lists

Cláudio da Silveira Pinheiro taupter at
Wed Aug 22 19:19:47 BST 2007

Em Qua 22 Ago 2007, Aaron J. Seigo escreveu:
> On Wednesday 22 August 2007, you wrote:
> it would be nice to have at least one release cycle where we can stop
> fetishizing over our tools and actually write some software, something we
> haven't really be able to do for a couple of years now thanks to the
> various changes (svn, cmake, qt4..). moving to git will also likely impact
> negatively the productivity of that given cycle and we will innevitably
> lose some contributors who can't be bothered to follow us on that
> transition.

Agreed completely.
I'm not really a very active developer last months, and even less with so much 
workflow, API, build-system, and VCS changes to absorb, while real life 
issues claim my attention everytime. Sometimes it just feels a search for a 
holy grail of an environment that we'll not really attain, and the multiple 
transitions will take suck a hassle and be so painful that less commited 
contributors (like me, not because of lack of interest, but because of lack 
of time/resources) will not stay up-to-date to the last trend.
CVS to SVN, automake to unsermake to cmake were completely justifiable for 
performance/flexibility issues, but I really don't know what real benefit 
would git bring to the average KDE developer. Really.
Call me dumb, call me names, say I'm not representative of the majority of the 
KDE development community, but in my humble opinion, we should settle with 
the current (good enough) environment for at least one or two years to get 
things done. We're already doing a big push with big changes for KDE4, and a 
period without so much turbulence for the less gifted contributors might be 
Please let's not look for a solution to a problem that doesn't exist.

More information about the kde-core-devel mailing list