Portal

Difference between revisions of "Bug Squad"

From Joomla! Documentation

m (update)
(Marked this version for translation)
 
(28 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<!-- This portal was created using subst:box portal skeleton  -->
+
<noinclude><languages /></noinclude>
{{browsebar|bugsquad}}__NOTOC__
+
{{browsebar|bugsquad}}
<div style="clear:both; width:100%">
+
{{Top portal heading|color=white-bkgd|icon=bug|icon-color=#5091cd|size=5x|text-color=#333|title=<translate><!--T:4-->
 +
Joomla! Bug Squad Portal</translate>}}
 +
{{section portal heading|icon=info|title=<translate><!--T:20--> Purpose, Function and Roles</translate>}}
 +
<translate>
 +
== Purpose == <!--T:21-->
 +
</translate>  
  
{{:{{FULLPAGENAME}}/box-header|<big>This is the Joomla! Bug Squad Portal</big>|{{FULLPAGENAME}}/Intro|}}
+
'''<translate><!--T:22--> The purpose of the Joomla! Bug Squad (JBS) is to reduce the number of bugs in Joomla.</translate>'''
{{{{FULLPAGENAME}}/Intro}}
+
 
{{:{{FULLPAGENAME}}/box-footer|Please make sure you read about the [[Bug Squad|Bug Squad]]}}
+
<translate><!--T:23--> This is valid not only for the CMS, but for every Joomla (sub-)project.</translate>
</div>
+
 
<div class="portal-column-left">
+
<div class="large-6 columns">{{Basic button|S:MyLanguage/Portal:Bug_Squad/Intro|<translate><!--T:24--> Read more about Function and Roles of the Bug Squad</translate>|class=expand success}}</div>
{{:{{FULLPAGENAME}}/box-header|Join the Bug Squad|{{FULLPAGENAME}}/Join the Bug Squad|}}
+
 
{{{{FULLPAGENAME}}/Join the Bug Squad}}
+
{{-}}
{{:{{FULLPAGENAME}}/box-footer|}}
+
 
</div>
+
 
<div class="portal-column-right"> <!-- Switch to one column on narrow screens -->
+
{{section portal heading|icon=user|title=<translate><!--T:7-->
{{:{{FULLPAGENAME}}/box-header|Joomla! Bug Squad Communication|{{FULLPAGENAME}}/Communication|}}
+
Join the Bug Squad</translate>}}{{Portal:Bug_Squad/Join_the_Bug_Squad/<translate><!--T:8-->
{{{{FULLPAGENAME}}/Communication}}
+
en</translate>}}
{{:{{FULLPAGENAME}}/box-footer|}}
+
 
</div>
+
{{section portal heading|icon=sort|title=<translate><!--T:9-->
<div style="clear:both; width:100%"></div>
+
Communication</translate>}}{{Portal:Bug_Squad/Communication/<translate><!--T:19-->
<div class="portal-column-right">
+
en</translate>}}
{{:{{FULLPAGENAME}}/box-header|Manuals|{{FULLPAGENAME}}/Manuals|}}
 
{{{{FULLPAGENAME}}/Manuals}}
 
{{:{{FULLPAGENAME}}/box-footer|}}
 
  
{{:{{FULLPAGENAME}}/box-header|Setting Up Resources|{{FULLPAGENAME}}/Setting Up Resources|}}
+
{{-}}
{{{{FULLPAGENAME}}/Setting Up Resources}}
+
<div class="large-6 column">
{{:{{FULLPAGENAME}}/box-footer|}}
+
{{section portal heading|icon=thumbs-up|title=<translate><!--T:11-->
 +
Useful Information</translate>}}{{Portal:Bug_Squad/Useful Information/<translate><!--T:12-->
 +
en</translate>}}{{tip|<translate><!--T:13-->
 +
See the [[S:MyLanguage/Category:Bug_Squad|Bug Squad references]].</translate>|title=<translate><!--T:14-->
 +
For more articles and information:</translate>}}  
 
</div>
 
</div>
<div class="portal-column-left">
+
<div class="large-6 column">
{{:{{FULLPAGENAME}}/box-header|Useful Information|{{FULLPAGENAME}}/Useful Information|}}
+
{{section portal heading|icon=book|title=<translate><!--T:15-->
{{{{FULLPAGENAME}}/Useful Information}}{{:{{FULLPAGENAME}}/box-footer|<small>''...more [[:Category:Bug Squad|Bug Squad References]]''</small>}}
+
Manuals</translate>}}{{Portal:Bug_Squad/Manuals/<translate><!--T:16-->
 +
en</translate>}}
 
</div>
 
</div>
 
+
<div class="large-6 column">
<div class="portal-column-left"> <!-- Switch to one column on narrow screens -->
+
{{section portal heading|icon=gears|title=<translate><!--T:17-->
{{:{{FULLPAGENAME}}/box-header|Teams|{{FULLPAGENAME}}/Teams|}}
+
Setting Up Resources</translate>}}{{Portal:Bug_Squad/Setting Up Resources/<translate><!--T:18-->
{{{{FULLPAGENAME}}/Teams}}
+
en</translate>}}
{{:{{FULLPAGENAME}}/box-footer|}}
 
 
</div>
 
</div>
  
<div class="portal-column-right"> <!-- Switch to one column on narrow screens -->
+
__NOTOC__
{{:{{FULLPAGENAME}}/box-header|Tricks and Tips|{{FULLPAGENAME}}/Tricks and Tips|}}
+
<noinclude>
{{{{FULLPAGENAME}}/Tricks and Tips}}
+
[[Category:Bug Squad{{#translation:}}]]
{{:{{FULLPAGENAME}}/box-footer|}}
+
[[Category:Development{{#translation:}}]]
</div>
+
[[Category:Production Department{{#translation:}}]]
<div style="clear:both; width:100%">
+
[[Category:Active Working Groups{{#translation:}}]]
{{purgepage}}</div>
+
[[Category:Working Groups{{#translation:}}]]
__NOTOC__ __NOEDITSECTION__
+
</noinclude>
[[Category:Bug Squad|Bug Squad]][[Category:Development]]
 

Latest revision as of 03:08, 24 October 2018

Other languages:
Bahasa Indonesia • ‎Deutsch • ‎English • ‎Nederlands • ‎Türkçe • ‎español • ‎français • ‎italiano • ‎português • ‎беларуская • ‎русский • ‎中文(台灣)‎

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

Joomla! Bug Squad Portal

Purpose, Function and Roles

Purpose[edit]

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.


Join the Bug Squad

Become a Contributor[edit]

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 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.

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

Become a Member[edit]

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.


Manuals

Joomla! API · PHP · MySQL · jQuery · Mootools