The Joomla! Community Portal ™

Leadership Blog





Vote for the Version
Written by Ron Severdia   
Saturday, 30 July 2011 21:48

This is a report from the Joomla Leadership Summit now underway in San Jose, CA. Members of the Community Leadership Team (CLT), Production Leadership Team (PLT) and the board of Open Source Matters (OSM) are busy discussing the best foot forward in all areas of the project.

The PLT had our summit in the days leading up to the overall Leadership Summit. We'll share shortly the results of that summit, but we wanted to get some direct feedback from the community on an issue that affects many.

We decided to make a small change to the way Joomla versions are numbered. If you have read about the new development cycle, you know we now have a new Joomla version every six months and one long-term-support (LTS) release every 18 months. Versions 1.6 and 1.7 are six-month releases and the next release in January 2012 will be an LTS release. This way, users have a choice. They can get the latest and greatest version by updating with improvements every six months, or they can have a more stable feature set with updates every 18 months.  Maintenance and security releases will be done as necessary for both LTS and STS releases during their support periods.

To try to make this as clear as possible to users, we have decided that the long-term releases will always be labeled as x.5 releases. For example, 3.0 and 3.1 will be regular, short-term six-month releases. The following version would be 3.5, indicating that it is a LTS release. Version 3.5 will be supported for 18 months. In the meantime, we will release 4.0 and 4.1. The LTS replacement for 3.5 will be 4.5, 18 months later.

We would like to present two options to the community to decide how to proceed with this versioning approach. 

Joomla Version Diagram

Click on the diagram above to view a larger version.

The first option (Option #1) in the diagram is to call the January 2012 release (long-term release) 1.8. The subsequent short -term releases would be 2.0 and 2.1 (e.g. maintenance releases would be 2.0.1 or 2.1.1, etc.) and the following release would be 2.5 (using the x.5 number to identify it as a long-term release). This would be an anomaly in the versioning strategy because it would be the only version to not follow the x.5 numbering, but this version number would naturally follow 1.6 and 1.7.

The second option (Option #2) in the diagram is to call the January 2012 release (long-term release) 2.5. The subsequent short -term releases would be 3.0 and 3.1 (e.g. maintenance releases would be 3.0.1 or 3.1.1, etc.) and the following release would be 3.5 (using the x.5 number to identify it as a long-term release). This would be an anomaly in the versioning strategy because there would be no version numbers between 1.7 and 2.5, but this version number would follow the future versioning strategy (also there would be backwards compatibility with Joomla 1.5).





Vote for the option that makes the best sense here:


To comment on this post, visit









Help Wanted for the Joomla! Events Team
Written by Robert Deutz   
Wednesday, 06 July 2011 15:28

Since the start of the Joomla! Project we have had an Events Team.  This team created the Joomla!Day Charter and helped create the first of many Joomla!Days. Over time, the Joomla!Day organizers became more professional and the help of the Events Team was not as necessary.

Without a clear description of responsibilities or concept as to what this team should or can do, activities have reached a very low level: near zero, if we try to paraphrase it a little bit.

On the other hand, we have a lot of things in terms of events to do and to optimise. With this request for help I’ll try to fill the gaps.






JED Announces Support System
Written by Matt Lipscomb   
Monday, 30 May 2011 00:32

 In March 2011 the JED hit 7000 listings.  Now, half way to 8000, we are announcing a major change and improvement to the JED.  It's my pleasure to introduce the JED Support System.  With over a quarter million registered users in the JED, providing support is the primary use of volunteer time.  In the latest blog, we outlined a few areas of improvements that we would be working on over the coming months.  One of these areas was a new ticket support system.  After nearly two years going back and forth between what we wanted for the teams, end users and management, we have come up with a solution that goes far beyond standard ticket support and includes a Knowledge Base, Announcement Panel, Download and Sample Repository, task calendaring, integration with Mosets Tree and ArtofUser and more!






The Joomla! Community Leadership Team is Growing!
Written by Wendy Robinson   
Friday, 27 May 2011 04:45

The Joomla! Community Leadership Team (CLT) is currently seeking new members to join us on our team and we want YOU, our fellow community members, to nominate those you feel would be well suited! (yes, you can nominate yourself as well ;) )

If you’ve been around Joomla for a long time then you’re likely already aware of what the CLT is, what we do and how we fit into the project structure.  If that’s the case, feel free to skip to the bottom for the nomination details.  

For those of you who don’t know or who aren’t 100% sure, we’ve listed some details here to help outline the whole picture.

What is the CLT?

There is a large working group within the project called the Community Workgroup (CWG) under which certain sites/areas fall. Those areas are Joomla User Groups (JUGs), the Joomla Extensions Directory (JED), the Joomla Resources Directory (JRD), the Joomla Community Magazine (JCM), the Joomla People Site, the Joomla Community Forums, the Joomla! Community Portal, the Vulnerable Extensions List (VEL) and main site. Hundreds of volunteers make up the teams that manage those areas.  The Community Leadership Team, CLT, is the leadership arm of the project responsible for the Community Workgroup , CWG as a whole.

What does the CLT do?

Our CLT roles in the Community Workgroup includes recruiting new volunteers, working with the teams on daily tasks, adding necessary features to the various directories and sites, helping the teams roll out new sites when ready, as well as the overall responsibility of ensuring a healthy atmosphere for all contributors.  We also communicate on a regular basis with one another, members of our teams, community members and our fellow teams the leadership group - the Production Leadership Team (PLT) and the Open Source Matters board (OSM).  

In addition to our roles within teams, the CLT is also responsible for the organization and upkeep of the various sites in the family. This includes duties such as software updates, security monitoring, feature updates and overall site management.

There are also a number of administrative and communicative responsibilities where we could use some additional help such as blogging, keeping the community updated and involved in our news and decisions, community outreach and evangelism, scheduled and recorded meetings, publishing of meeting minutes and outcomes, managing our People site group, and utilizing other social media areas such as Twitter, facebook and YouTube.

We also want make a larger effort towards internationalization of the sites and communication between various regional and international communities and

Who is the CLT looking for?

So as you can see, the CLT has a lot on its plate and we could really use some new, fresh faces and ideas and experience to help us with these tasks, reach goals and move the Community Workgroup forward.  

We’re looking for people with the following skills and abilities:

In General:

  • comfortable working with people of different backgrounds - be they cultural, professional or any other
  • Somebody who can work well on their own but also contribute to combined goals as a member of a team
  • Demonstrate problem solving abilities
  • Ability to handle controversial situations
  • Some experience working/volunteering for an open source software project, preferably Joomla, though experience that can be shared from other projects is certainly welcome
  • General conduct of a professional and considerate nature on as well as other sites and media channels
  • Must have a reasonable and consistent amount of time to focus on your leadership responsibilities each week.
  • Must be willing to read and agree to abide by the Joomla Code of Conduct

Some specific skills that would be an asset to the CLT:

  • Good administrative skills - Not necessarily due to professional experience, but if you’re an organizer, planner, get-stuff-done kind of person then let us know
  • Management skills - whether in business or volunteer roles, if you’ve been a leader in the past, we’d love to know more about you
  • International community members with English as a first or second language
  • Writing/blogging/communication skills with a general interest in that area.
  • An interest in, and aptitude for making use of, social media channels of communication: twitter, facebook, youTube, etc

So if you or someone you know fits any combination of the above criteria and would like to be a part of Joomla’s Community Leadership Team, please send us an email with a name, some information about your nominee and why you think they would be a good fit,  and a preferred email address and/or Skype or GTalk details for contact.

We will be welcoming nominations from today through Friday, June 10, 2011. The current members of the CLT will be reviewing and considering all nominations from which we will select and contact those we feel would be the best fit to join. You can send your email to This e-mail address is being protected from spambots. You need JavaScript enabled to view it Please be sure to include “CLT Nomination” in your email title.






Joint Leadership Summit Goals
Written by Alice Grevet   
Thursday, 26 May 2011 23:24

In preparation for the Joint Summit (CLT, PLT, OSM) sheduled for July 29 - 31, 2011, at eBay in San Jose, California, the Joint Summit Committee has compiled a list of proposed goals for discussion at the three day meeting. The list below is shared with the community for feedback before finalizing the meeting agenda.

The goals include planning and discussing the following topics (not presented in any particular order):

  • Who are we building Joomla for? Who is our target audience and thus who should we build new features for?
  • Better collaboration
  • The future of the Project
  • The Joomla Project common goals
  • The Joomla Project strategy
  • Evaluate our project structure
    • The future role, if any, of the Community Oversight Committee
    • Better understand how our teams function
  • Talk about processes (conflict resolution, budget process, ….)
  • How to attract more developers?
  • Review Sponsored Development program
  • Review our Mission, Vision and Values
  • Collaboration strategy with international communities
  • Joomla! World Conference 2012 - Setup a committee, define goals

To comment on this list of goals please visit:


Page 26 of 48