This page contains information about hacking and contributing to the GNOME Commander project. We encourage anyone to contribute with code, translations, bugreporting, new useful ideas, or just give some quality feedback that also is quite important.
If you would like to get involved and don't know where to start, have a look especially into the TODO file. This file gives a hint on what we are working on, or like to work on, and maybe appreciate some community efforts on. You are also welcome to sign up on our mailing lists and take part in discussions and development. If you are keen on fixing open bugs, have a look at our gitlab project page.
The team behind GCMD is currently working on switching from obsolete libraries, e.g. from gnome-vfs to gvfs/GIO. This is a major task and, thus, will take some time.
In the future, the team behind GCMD are will further enhance python plugin support. Plugins should be dropped in the ~/.gnome-commander/plugins directory. The work on supporting meta-data also continues. The plan is to add this functionality to the searchtool, custom columns and the internal viewer.
The official Git repository of GNOME Commander is registered on gitlab.gnome.org.
GNOME Commander is being developed in several branches:
The version numbers (major, minor and micro) follow the standard of odd and even
versioning. Even numbers are stable versions, that are intended for all-day use.
Odd versions are development versions. The version number is stored as git-tags in the
git repository. To see all of them, just type
git tag. The current one is
also stored in the first line of
To check out the GCMD repository to your local hard disc, enter the following commands:
The instable master branch:
git clone https://gitlab.gnome.org/GNOME/gnome-commander.git
The current stable branch:
git clone -b gcmd-1-8 https://gitlab.gnome.org/GNOME/gnome-commander.git
If you already cloned the repository, run
pull inside the gnome-commander directory to get the
latest code revision. To switch between the branches, run
make checkbefore every commit? Nothing easier than that: Just type the following command when you are in the top directory of the GCMD repository:
ln -s ../../pre-commit.sh .git/hooks/pre-commit
git commit. When you only have a small commit to be made, where no check is necessary, you can avoid it with the command
git commit --no-verify.
First, check out the source code as described in the previous section. The next step is the usual
./autogen.sh && make && sudo -i make install procedure,
which should work like a charm. If you are building the code from an unpacked tar archive use
./configure instead of
When you install Gnome Commander manually the first time and you discover some errors like
/configure: line 4721: GLIB_GSETTINGS: command not found or
something similar you have to install some dependencies.
If you want to contribute, send in patches, having some useful idea or just some feedback then you are welcome to contact us or you can make a pull request on GitLab against the GCMD repository.
Here is a quick guide how to do contribute via GitLab after creating an account there and creating a fork of the origin repository in GitLab:
git clone https://gitlab.gnome.org/$USER/gnome-commander && cd gnome-commander
git remote add upstream https://gitlab.gnome.org/GNOME/gnome-commander.git
git checkout -b $BRANCH_NAME
git commit -m "$DESCRIPTION"
git commit -m "...; Closes: #26".
git fetch upstream master && git rebase upstream/master
git push origin HEAD
If you want to submit a patch via email:
diff -Naur old_file new_file
The current status of all project translations can be found at GNOME's Damned Lies. For adding a new translation simply download the initial potfile of the master branch and start translating by renaming the file to LL.po (replace "LL" with your language code, see the complete list of language codes). Or take an already existing po file from the list on the page given above.
Here you will find the recipe on how to contribute with your new or updated translation:
podirectory and run
You may find translation compedia to be quite handy as a reference. You can download some
from other projects and create
such a compedium by:
msgcat -o compendium-LL.po *.po.
Have a look at l10n.gnome.org if you want to start translating for more projects than just GCMD.
From time to time check strings marked for translation. Therefore, create updated
Then search for incorrect translations:
podebug --format='[i18n]' --input po/de.po > output.po.
Now in the output file all found strings for translation are marked with a
[i18n] tag. Then you have to start GCMD with this created po-file.
appstream-util validate data/org.gnome.gnome-commander.appdata.xml.in.
make distcheckmove ebuild file from
--without-exiv2 --without-taglib --without-libchm --without-libgsf --without-poppler, python, etc).
repoman -dx fullor
pkgcheck scan gnome-commander-1.12.1.ebuildand finally
repoman committo prepare a commit to your repo.
gnome-extra/gnome-commander/and create a commit with signing off by doing (
git add -p && pkgdev commit), similar to this one.
If you want to contribute to the Gnome Commander homepage you can simply fork its source code repository and create a pull request with your updates.
The page itself consists of simple html pages like the index.html or doc.html. But you will also notice that the blog posts which are shown on the index.html file are actually markdown posts in the "_posts" subdirectory. When pushing new blog posts in that folder, they are automatically processed by the Jekyll tool on GitHub. No manuall work has to be done in that case. Just create a new markdown file, create a merge request, and when it is accepted, the new post will show up quickly on the Gnome Commander homepage.
Before opening a pull request you may test the look of a new blog post by installing Jekyll locally on your machine and running "jekyll serve" in the main folder of the homepage repository. That will start a local webserver and you can visit the homepage in your browser on page http://localhost:4000.