[Kde-games-devel] Re: Move to git

[Inge Wallin]

On Tuesday, February 01, 2011 18:25:35 Aaron J. Seigo wrote:
> On Tuesday, February 1, 2011, Frederik Schwarzer wrote:
> > With split repos it will be way easier to include new games to the
> > module or to move games from the repo to extragear or playground
> > without messing with history.
> 
> and much harder to build. unless everyone moves to tools like kdesrc-build
> and lets that automate it for them, you can very much expect the # of
> people testing the various games from master to drop as the effort needed
> to keep all those separate repositories and builds up to date goes up.

I would like to add:  Also much harder to browse.

I remember when I was a new KDE developer, I used kdegames as a relatively 
simple way to enter the world of Qt and KDE applications.  I understood the 
games quite easily and soon found a place where I could start hacking: 
KReversi.  I also looked at the other games and added some code and 
improvements here and there: kpat, kpoker (RIP) and a few others.

I think kdegames is a nice portal into KDE and I have heard several people say 
the same as I do above.  This means that I think we should continue to have 
just one repository instead of n of them.


> some things are absolutely simpler and more straightforward by creating 37
> app repoes and then another for the libraries. building the games and
> keeping up with what gaes are available is not one of them.
> 
> if you all decide to go the split route, please, please, please ensure you
> have a sensible build strategy in place otherwise you will lose a large
> portion of your testing and casual contributor base.
> 
> as one non-representative data point: i doubt many (if any) of the patches
> i have contributed to kdegames over the years would have happened if i had
> to track 38 repositories instead of 1. those patches may not be large in
> number or value at the end of the day; you need to decide if casual "drive
> by" contributions are important to you. you should consider the ease of
> people getting involved with dev for the first time.

Indeed.  As far as I'm concerned, this is the biggest reason for 1 repository.

	-Inge