KDE Games/Git Conversion Progress

From KDE Community Wiki

Template:Being Edited

This page is used to keep track of progress in KDEGames's conversion from SVN to Git.

How to Fill Out the Table

Rule Writers

The progress table uses a Mediawiki template with named parameters, to make it easier to edit than the raw table markup.

  • When you start writing rules for a particular game, add your initials in a rulesby= parameter, and set inprogress=1; for example rulesby=NA|inprogress=1. This will indicate that the rules are in progress so that efforts aren't duplicated.
  • Once you've written the rules and feel they're complete, push them to the kdegames directory of the kde-ruleset repository and remove inprogress=1 from the table. The "Rules" column will automatically turn into a link pointing to the rules file.
  • Once you've generated a repository from the rules and verified its correctness, push it some place public, preferably a personal scratch repo. Add a scratch= param with the scratch repository path, and a scratchby= param with your initials; for example scratch=scratch/nalvarez/kdegames-foo.git|scratchby=NA.

Repository Checkers

  • It is assumed that the rule writer has already verified the correctness of the repository, so don't bother adding yourself to the table.
  • Checkout the repository, poke around a bit and then perform each of the following checks, adding your initials in each column. Ideally, more than one person should check each repo, in which case, separate each set of initials with a comma.

The Checks

Completeness
The complete history is present. The first commit should be the initial import into KDE's CVS or SVN. All transitions from playground, kdereview, extragear, KDE3, etc. should be present.
Docs
The user documentation is in a subdirectory named "doc". The history of the doc folder should match that of the "kdegames/doc/<game>" folder.
Heads
The repository has only one head. (git branch -r) Two heads mean a broken master branch.
Stable branches
All relevant stable branches are present. If a game entered the kdegames module for the 4.3 release, it should have a stable branch "KDE/4.x" for each x >= 3 and none for x < 3.
Tags
All relevant release tags are present. If a game entered the kdegames module for the 4.3 release, it should have tags "KDE/4.x.y" for each x >= 3 and none for x < 3.
Branches
If the game has a non-linear history (i.e. work branches were created and later merged back in to trunk) that should be recreated in the Git history. This is by far the most difficult check. Use git gui to visualise branches and merges, but you have to know what you're looking for. Fortunately, this isn't required for games that have a simple playground -> kdereview -> kdegames history. To determine where an application has been throughout its history, enter its name into this page, which will return all known SVN change paths containing the name. (Pay no attention to the l10n and www stuff.)


Contributor Initials

MK
Mathias Kraus
NA
Nicolás Alvarez
PC
Parker Coates
WR
Wolfgang Rohdewald
FS
Frederik Schwarzer
CK
Christian Krippendorf
SM
Stefan Majewsky
NH
Ni Hui

The Table

Rules Repo Main history Version branches/tags Local work branches Global work branches Parent map Other notes
Bomber PC PC
Bovo PC PC
Granatier MK MK
Kajongg WR WR
Kapman PC PC MK MK MK MK MK MK
Katomic
KBlackBox
KBlocks PC PC
KBounce
KBreakout PC PC
KDiamond SM SM
KFourInLine
KGoldrunner FS% [1]
Kigo PC PC
Killbots PC PC
Kiriki PC% PC
KJumpingCube
Klickety NH%
KLines
KMahjongg WR% WR
KMines
KNavalBattle
KNetWalk PC
Kolf
Kollision PC PC
Konquest
KPatience NA%
KReversi
KShisen FS%
KSirk
KSnakeDuel
KSpaceDuel
KSquares PC PC
KSudoku PC PC
KTuberling NA%
Kubrick PC PC
libkdegames SM%
libkmahjongg WR WR CK CK CK CK
Lieutenant Skat WR%
Palapeli SM%