This list should contain all the words that are important to PBFde with attached explanations or translations. We would like to explain common PBF terms in a short, concise and precise manner.

Bugs

Errors in code are called bugs, because in the past no software errors caused problems but bugs/beetles. Computers used to be a lot bigger than today and so there was enough space for beetles in the computers. These nested in the computers and the relays within were damaged or disturbed.

Committers

When a pull request (patch) has been successfully tested twice, then a committer or a product owner merge the patch into the Joomla! core. A committer has the write permission for the source code of Joomla!.

Core

At PBF, you'll hear the word "Core" more often. This refers to the Joomla! Kernel, the source code of Joomla! so to speak.

GitHub

Github is an online service that allows developer to manage software projects via "Git". Git enables versioning of software code and makes it very easy to collaborate on software development. (more information).
You can also find all Joomla! pull requests on GitHub. For information about GitHub authentication, see this tutorial.

Glip

Glip is a free online service, an English-language project management tool that lets you chat with a team. More information

Issue Status

Shows the current status of an issue. Normally, on the PBF event we test patches when they have the status "new" or "pending". More information

JDocs

The Joomla! Documentation (JDocs) is the official guide and the project documentation : here you can find out how to become a translator.

JUG

A Joomla! User Group (JUG) is a regular gathering of Joomla! people nearby to support you with any questions, is open to suggestions, and invites you to get and give tips and tricks. More information

Issue Tracker

The Issue Tracker is a kind of ticket system that manages and handles a bug from confirmation to troubleshooting. Using the Issue Tracker (http://issues.joomla.org) you can read the error description, for example. (Instruction)

Local installation

Before you can test patches, you need to set up a Joomla installation locally or online. Local installation requires XAMPP, the latest version of Joomla (For PBF, we use Joomla! 4 Nightlybuild), the Joomla extension a Patch Tester and a GitHub Account for patch tester authentication.

Nightlybuild

The Nightly Build is the latest Joomla! Version being worked on. This is generated automatically and contains the current developer status of the current code. The Nightlybuild is not stable and may have security vulnerabilities, so the Nightlybuild should not be used for productive sites. more information

Online PBF Environment

For those who do not have a local installation at the PBF event, we have prepared an online Joomla installation specifically for the PBF. (more information). GitHub allows only a certain number of people who can access the interface anonymous, so it's required that each additional person must enter his GitHub user name and GitHub password in the options of the Joomla! extension "Patchtester".

Patch

A patch is a few lines of code that correct a bug or contain new features. Patches can be merged in the code of the current Joomla installation. In the Joomla environment, patches are provided in Github as pull requests.

Test Patch

What you should be aware of when testing the patch, you can find here: Tutorial patch testing . There is a very helpful Joomla extension, the "Patchtester".

Patchtester

The Patchtester is a Joomla component that is very helpful in testing the patches. The Patchtester makes it possible to use Knopflick patches in Joomla! Here is the step by step guide: Patchtester

Pull Request (= error correction / function suggestion)

A pull request is a request to apply a patch to the code. In our case, a developer has the code of Joomla! working and fixed a bug and dropped a pull request. Now the PBF team can test the new code, discuss it if necessary, or give the developer feedback to modify the patch. At the end of the day a commiter can merge the code into the Joomla! core.

Product Owner

If the pull request (patch) has been successfully tested twice then a product owner will integrate the patch in the Joomla! core. A product owner has the write permission for the source code of Joomla!.

PBF

The event "Pizza Bugs & Fun" is a "Joomla! make it happen day". You get to know the community, learn how to test patches or even write yourself, how to become a translator or how to write Joomla!. Everyone and anyone is heartily welcome. We are happy about anyone who already uses Joomla!, works with Joomla!. It's best to write us an email This email address is being protected from spambots. You need JavaScript enabled to view it., if you wish to be invited or want to connect with a local JUG in your area.

Translation Sandbox

Translators need an environment to test, found here: Translation Sandbox ; Find here out, how to become a translator.

XAMPP

XAMPP is a completely free, easy to install software that contains all the necessary programs for setting up and maintaining a web server. More information