Welcome to Joomla Blog

PBF 2013

http://developer.joomla.org/pbf-2013.html

Pizza, Pizza! Bugs, Bugs! and Fun Fun! Fun!

July 12th, 2013 is our next PBF event and we'd love for you to be a part of it.

  • The key goal is to fix as many Joomla 3 and Joomla 2.5 bugs as possible.
  • The event is an all-day global event for virtual participants, with local venues wherever they are organized.
  • The event is open to both businesses and individuals.

More information is available below.

Training Sessions

more

Optional webinar training session: 11 July, 2013, at 15:00 UTC.

Optional Q&A/getting-started: 11 July, 2013, from 17:00-18:00 UTC.

Event Info

more

Date: Friday, 12 July 2013b

Location: Online globally

Who's invited: everyone

Docs

more

How to test bug fixes

How to submit bug fixes

How to report a bug

Participation

We've dubbed the event as a Business PBF, since it's our first PBF on a weekday (Friday) and we'd like to get more businesses involved. We've created badges that you can use on your sites to spread awareness of the event and get recognition for your participation.

Furthermore, we'd like to give you more recognition and highlight your pledge of participation by placing your logo and a link to your site on this landing page. To be listed on this landing page, please submit this form.

There are four participations levels: Epic, Platinum, Gold, and Bug Squasher.

Epic
is for 100 hours or more pledged to the event
Platinum
is for 10 hours or more pledged to the event
Gold
is for 5 hours or more pledged to the event
Bug Squasher
is for individuals that have pledged to participate

So, for example, if Company ABC had five of their developers for two hours, then they could use the Platinum badge and have their logo (and link) in the platinum area on the landing page.

The hours you choose to pledge towards the event is totally up to you as an individual or business. As a bonus, if you write a blog post about the event, you can count it as 30 minutes towards your pledge. So if you pledged 5 hours and write a blog post, you'd be helping at the event for 4.5 hours.

Finally, on the day of the event, come and go as you'd like and fulfill your pledged hours. You can help with testing bug fixes, reporting bugs, coding bug fixes, etc. Most of all, enjoy every minute! Have fun, enjoy the fellowship, learn, and make Joomla better for you, your business, your clients, and your friends.

Credits and special thanks to

Host
Joomla! Bug Squad (JBS)
Organizer
Nick Savov
Designer for landing page
CloudAccess
Developer for landing page
Janich Rasmussen
Designer for badges
Helvecio "Elvis" da Silva

Announcement en-GB User Interface Text Working Group

http://developer.joomla.org/news/600-announcement-en-gb-user-interface-text-working-group.html

I am pleased to announce the following with Brian Teeman leading this overdue and needed core en-GB standardisation.

The PLT have accepted the proposal to review and standardise all the en-GB language strings in the core of Joomla based on the style guide that you can see here (until it gets a permanent home).

Abstract

Joomla Extension Developers, what resources do you need for the final release of 2.5

http://developer.joomla.org/news/599-joomla-extension-developers-what-resources-do-you-need-for-the-final-release-of-2-5.html

Dear Joomla Extension Developers

We need your to help spread the word!

We are currently planning the Joomla 2.5 marketing campaign. Joomla 2.5.28 is scheduled to be released on December 10th. As part of our campaign, we are asking extension developers to write a blog (of any length) that explains 2.5.28 will be the final release of the 2.5 series. Additionally, it would be helpful for your users if you provide documentation on how to upgrade your extension within your blog post.

Here is documentation by Jennifer Gress, Tom Hutchison, and Connie Lippert to help people plan for upgrading http://docs.joomla.org/Why_Migrate. The marketing team is preparing an information pack that explains 2.5.28.

Our goal for this campaign is to work together to help the community find the resources they need for successful upgrade planning. If you have suggestions on how else we can assist in this transition, please post here. 

Call for Production Leadership Team Nominations

http://developer.joomla.org/news/598-call-for-production-leadership-team-nominations.html

The Joomla! Production Leadership Team (PLT) is responsible for leading and coordinating the development of the Joomla CMS and Framework. This includes releasing new versions, fixing bugs, adding new features, and creating documentation and translations.

We are looking for your nominations for new PLT members. We acknowledge that the greater worldwide Joomla community can help us a lot in this election process, and make us aware of potential candidates we might otherwise overlook.

Although the nomination form is available permanently to continuously gather suggestions, a number of PLT members are stepping down this month and we are additionally looking to fill some gaps in our skills base.  Consequently we are blogging this reminder that we need your nominations because we are actively looking to recruit new PLT members soon.

You can nominate yourself or someone else at any time. If you nominate someone else, please ask them first if they are interested and have the time available.

Release Postmortem

http://developer.joomla.org/news/597-release-postmortem.html

While we strive to be as efficient as possible, there are times when things don't go smoothly, causing stress and headaches for our user base and the community members who test and prepare our releases. This last week has been an example of some rough times for our releases, and though no single person or group is to blame for any of the issues that we've experienced with these last releases, they do highlight areas where our teams and workflows can improve.

Easing the contribution process

http://developer.joomla.org/news/591-easing-the-contribution-process.html

The Joomla PLT is happy to announce that contributions to the CMS will no longer require a JoomlaCode tracker item. We’re now ready to start using our brand new issue tracker issues.joomla.org.

New bug reports and feature requests should be created either at issues.joomla.org or directly on GitHub. Code contributions made via Github will automatically create the issue for you (no more duplication required). All outstanding JoomlaCode items will require a corresponding Github issue.

Due to technical limitations of the JoomlaCode software, we cannot disable the JoomlaCode tracker for just the Joomla CMS project. We ask that contributors stop using it immediately to create new issues or comment on existing issues. We will make all the necessary process changes to reinforce that.

NOTE: This change will not have any impact on other projects using JoomlaCode.org.

An Update on Joomla 3.4

http://developer.joomla.org/news/589-joomla-3-4-update.html

Ok, so there’s been some questions about Joomla 3.4, the next big release for Joomla. I’m quite excited to be able to be a part of this release and we have some great things planned. Timelines are always the first thing people want to know; followed closely with what features will be available. In this particular release there are some additional new terms being used which may be helpful to define. Three quick topics, let’s discuss each in order.