Skip to content

XAware Community

Get the Flash Player to see this player.
Flash Image Rotator Module by Joomlashack.
XAware 5.6
Need Help
Webinars and Events
Advanced Tutorials
Webinars and Events

You are here: Home arrow Getting Started arrow How To Contribute
How To Contribute

If you think working with Joomla! is fun, wait until you start working on it. We're passionate about helping Joomla! users make the jump to becoming contributing members of the community, so there are many ways you can help Joomla's development:

  • Submit news about Joomla!. We syndicate all Joomla! related news on our news portal. If you have some Joomla! news that you would like to share with the community, please submit your short story, article, announcement or review here.
  • Report bugs and request features in our trackers. Please read Reporting bugs, below, for details on how we like our bug reports served up
  • Submit patches for new and/or fixed behavior. Please read Submitting patches, below, for details on how to submit a patch.
  • Join the developer forums and share your ideas for how to improve Joomla!. We're always open to suggestions, although we're likely to be skeptical of large-scale suggestions without some code to back it up.
  • Join any of the community working groups and bring your personal expertise to the Joomla! community. More info about the different working groups can be found here.

That's all you need to know if you'd like to join the Joomla! development community. The rest of this document describes the details of how our community works and how it handles bugs, mailing lists, and all the other minutiae of Joomla! development.

Reporting bugs

Well-written bug reports are incredibly helpful. However, there's a certain amount of overhead involved in working with any bug tracking system, so your help in keeping our ticket tracker as useful as possible is appreciated. In particular:

  • Do read the FAQ to see if your issue might be a well-known question.
  • Do search the tracker to see if your issue has already been filed.
  • Do ask on testing forums first if you're not sure if what you're seeing is a bug.
  • Do write complete, reproducible, specific bug reports. Include as much information as you possibly can, complete with code snippets, test cases, etc. A minimal example that illustrates the bug in a nice small test case is the best possible bug report.
  • Don't use the tracker system to ask support questions. Use the joomla forums, or the #joomla IRC channel on freenode for that.
  • Don't use the trackers to make large-scale feature requests. We like to discuss any big changes to Joomla's core on the developers forums before actually working on them.
  • Don't reopen issues that have been marked "not a bug". This mark means that the decision has been made that we can't or won't fix this particular issue. If you're not sure why, please ask on developer forums.
  • Don't use the tracker for lengthy discussions, because they're likely to get lost. If a particular artifcact is controversial, please move discussion to developer forums.

Reporting security issues

Report security issues to security [at] joomla [dot] org. This is a private list only open to long-time, highly trusted Joomla developers, and its archives are not publicly readable.

In the event of a confirmed vulnerability in Joomla itself, we will take the following actions:

  • Acknowledge to the reporter that we've received the report and that a fix is forthcoming. We'll give a rough timeline and ask the reporter to keep the issue confidential until we announce it.
  • Halt all other development as long as is needed to develop a fix, including patches against the current and two previous releases.
  • Determine a go-public date for announcing the vulnerability and the fix. To try to mitigate a possible "arms race" between those applying the patch and those trying to exploit the hole, we will not announce security problems immediately.
  • Publicly announce the vulnerability and the fix on the pre-determined go-public date. This will probably mean a new release of Joomla! but in some cases it may simply be patches against current releases.

Submitting patches

We're always grateful for patches to Joomla's code. Indeed, bug reports with associated patches will get fixed far more quickly than those without patches.

Patch style

  • Make sure your code matches our coding style.
  • Submit patches in the format returned by the svn diff command. An exception is for code changes that are described more clearly in plain English than in code. Indentation is the most common example; it's hard to read patches when the only difference in code is that it's indented.
  • Attach patches to a artefact in the trackers, using the "attach file" button. Please don't put the patch in the artefact description or comment unless it's a single line patch.
  • Name the patch file with a .diff extension
  • Put the prefix "[patch] " before the title of your artifact. This will make it obvious that the artefact includes a patch.
 

Community Login

Get the Flash Player to see this player.
Flash Image Rotator Module by Joomlashack.
Commercial
Free Training
QuickStart Packages
Image 4 Title
Image 5 Title

Polls

Which data source and BizComponent combinations do you most frequently use?
 

Visit XAware.com