Bug Squad/id: Difference between revisions
From Joomla! Documentation
Updating to match new version of source page |
Updating to match new version of source page |
||
| Line 10: | Line 10: | ||
This is valid not only for the CMS, but for every Joomla (sub-)project. | This is valid not only for the CMS, but for every Joomla (sub-)project. | ||
<div class="large-6 columns">{{Basic button|S:MyLanguage/Portal:Bug_Squad/Intro|Read more about Function and Roles of the Bug | <div class="large-6 columns">{{Basic button|S:MyLanguage/Portal:Bug_Squad/Intro|Read more about Function and Roles of the Bug Squad|class=expand success}}</div> | ||
{{-}} | {{-}} | ||
| Line 32: | Line 32: | ||
__NOTOC__ __NOEDITSECTION__ | __NOTOC__ __NOEDITSECTION__ | ||
<noinclude> | <noinclude> | ||
<div class="mw-translate-fuzzy"> | |||
[[Category:Bug Squad/id|Regu Bug]] | [[Category:Bug Squad/id|Regu Bug]] | ||
[[Category:Development/id|Pengembangan]] | [[Category:Development/id|Pengembangan]] | ||
</div> | |||
</noinclude> | </noinclude> | ||
Revision as of 08:28, 31 August 2018
JBS Portal Page · Bug Squad · Tracker Team · Coding Team · Automated Testing Team
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.
Gabung dengan Regu Bug
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.
We use Mattermost for team communication, so you are encouraged to create an account there, if you have not yet. The "PD Bug Squad" 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.
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
Komunikasi
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.