Joomla! Documentation™

JBS Portal Page · Bug Squad · Tracker Team · Coding Team · Automated Testing Team

Joomla! Bug Squad-Portal

Purpose, Function and Roles

Purpose

The purpose of the Joomla! Bug Squad (JBS) is to reduce the number of bugs in Joomla.

This is valid not only for the CMS, but for every Joomla (sub-)project.

Read more about Function and Roles of the Bug Squad

Bug Squad beitreten

Become a Contributor

All you need to start contributing is a GitHub account.

A good starting point is testing pull requests (PRs), as we always need at least 2 successful tests for each PR before it can be merged. Detailed instructions for testing Joomla! patches are found on the documentation site.

If you are comfortable with coding, you can create PRs for open issues as well.

Wir verwenden Mattermost für die Teamkommunikation, daher sollte dort ein Konto eingerichtet werden, falls dies noch nicht geschehen ist. Der Kanal "PD Bug Squad" ist für Bug-Squad-Mitwirkende. Wenn Ihr nicht in diesen Kanal kommt, schreibt eine Mail an Bug Squad. Ihr werdet dann manuell hinzugefügt.

Joomla! uses GitHub as its code repository and the Joomla! Issue Tracker for reporting bugs. You will need your GitHub user account to

• report issues on the CMS Issue tracker.
• submit patches (PRs) against the Joomla code repository for bug fixes.
• test patches using the Joomla! Patch Tester.

Become a Member

As a member of the Bug Squad, you are expected to mentor contributors, scan the various communication channels for potential issues, and to support the developers to prevent and fix bugs.

If you accept the challenge, send an email request to the Bug Squad with a short description of your expertise to request membership.

See Bug Squad Team

Communication

The Joomla! Bug Squad uses Glip for team communication, so you are encouraged to create an account there, if you have not yet. The "Bug Squad Public Discussion" channel is for Bug Squad contributors. Drop a mail to the Bug Squad, if you can't get into that channel. You will be added manually then. Additionally, you might want to subscribe to the Joomla! CMS Development Mailing list.

Joomla! uses GitHub as its code repository and the Joomla! Issue Tracker for reporting bugs.

Useful Information

• Bugs & Fun @Home
• Pizza, Bugs & Fun
• Bug Tracking Process
• Filing bugs and issues
• Issue Priorities
• Testing Checklists
• Testing Joomla! patches
• Joomla! Patch Tester
• Joomla CodeSniffer
• Coding style and standards

For more articles and information:

Manuals

Joomla! API · PHP · MySQL · jQuery · Mootools

Setting Up Resources

• Setting Up your Workstation
• Tortoise Git Client for Windows
• XAMPP
• Wampserver
• MAMP