As a free software project, phpMyAdmin is very open to your contributions. You don't need developer skills to help, there are several non-coding ways to get involved in a project (code is welcome too, of course!).
Ways in which you can contribute:
As you can see, everyone can help.
phpMyAdmin is (as the name says) written in PHP and uses MySQL. Besides this, we also need people skilled in HTML, JavaScript and CSS, as these are parts which make our user interface. You don't have to be expert in all these areas - even knowing only one of them, you can still provide substantial help in creating or debugging some features.
For storing our code we use Git. If you don't know it, you can get some basic facts in Wikipedia or reference in the comprehensive book Pro Git.
Once you have coded an improvement and you are ready to submit it to us, please use our patch tracker, where developers will pick up your contributions or guide you through improving the patch.
If you are looking for some simple task where you can start, check out our wiki page with junior jobs where you can find some tips where to look.
Git repositories are located at
git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/REPONAME and you
can browse them online using Git web.
You want to start with the phpmyadmin repository.
Full list of repositories include:
Examples of how to checkout phpMyAdmin code:
# Latest development version: git clone git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin
Several statistics about the repository are available:
Standards should be obeyed in all cases when possible. Generated content should be valid XHTML 1.0 and CSS. PHP code should match PEAR Coding Standards and documented using phpDocumentator.
More documentation can be found in the following places:
For localization, phpMyAdmin uses its own simple localization system - each translation has its own PHP file with all texts. All these files are encoded in UTF-8 (if you see another encoding, you're using an old version). To translate, you have to follow steps described in FAQ 7.2.
Documentation is being translated using po4a and gettext (see documentation for existing
translations). To start, checkout localized_docs/po from Git, or
just go to translation
server and translate it online. If your language is missing, just contact
Michal Čihař, he will add it. If you
prefer to translate directly the po files, please put updated ones into our translation
tracker.