On 02.03.10 14:00:36, Thomas Zander wrote: > On Tuesday 2. March 2010 12.52.12 Andreas Pakulat wrote: > > > The actual uploading of the git repo is something that I hope we can > > > postpone till the rest of KDE moves too. > [] > > Also as far as the plan goes, playground-code should be moved by the > > respective maintainers and there's no indication that this playground-code > > should wait for the core-modules to be done. So I really don't understand > > why kdevelop-pg-qt cannot move when its ready? > > Its about the splitting of the community, best explained in the blog by Aaron. > http://aseigo.blogspot.com/2010/02/keeping-it-our-source-code-together.html
I read part of that and while that might be true for the core modules and even extragear apps, this clearly doesn't apply to kdevelop-pg-qt. As far as we know there's not a single user of the codebase out there thats not also part of the kdevelop team. There hasn't ever been a public release of this utility. Nobody uses a parser generator "just for fun". Hence I still fail to see the reason for not moving it. > In short, by moving this one thing you loose occasional contributors, testers > and essentially mind share. Not because its hard, but because its different > from the rest. I wonder how these "occasional contributors and testers" will work when KDE is split over 30 different repositories on gitorious. (And no, I'm not in favour of 1 git repository for all of KDE, thats just insane). Anyway, don't want to start a lengthy discussion on that. Andreas -- You love your home and want it to be beautiful. _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
