The Joomla! Community Portal ™

Leadership Blog





Summary of the Community Leadership Team Summit
Written by Wendy Robinson   
Saturday, 06 August 2011 23:20

Community Leadership Team Summit - 28th July and August 1st,  2011

Participants: Peter Martin, Wendy Robinson, Sandra Warren, Paul Orwig (Day 1)

Video participants: Matt Lipscomb, Brad Baker

CLT Team members during our 2011 summit

The following is a summary of the topics discussed in the Community Leadership Team (CLT) Summit:

A. All current websites that are under overview of the CLT:

1. now has about 30 internationalized pages that are used to redirect non-English people to local Joomla community resources. However because of the new Joomla 1.7 banner, the localized link is currently unavailable.

  • Action item 1: reinsert the link to localized “Joomla Information Pages”.
  • Action item 2: get the “info pages” translated in more languages.

2. The site seems to have a less important role then it used to have. Probably because of the success of the Magazine and People sub-websites.

  • Action item 3: we should communicate that *all* working group members should be able to post blog posts regarding related matters.

3. The new ticket support system for the Joomla Extension Directory (JED) is working very well. Other teams might use the system for their own process communication as well. The “premium listings” idea is moving forward, but we’ll have to wait on a new design for the JED site before it can be implemented.

  • Action item 4: evaluate new design for JED.

Furthermore we’ll have to make a decision about the Joomla version compatibility buttons.

  • Action item 5: wait for a decision on the new Joomla version numbering, and create buttons for Long Time Support (LTS) versions.

Finally we’ll need input for the “standards” information: what evaluation items for extensions should be included.

  • Action item 6: ask PLT / 3rd party extension developers for feedback on best practices for extensions.

4. There haven’t been any major changes regarding the Joomla Resources Directory (JRD) besides one new featured hosting provider in the hosting provider section. It has been decided to honor Rochen as a featured hosting provider listing (Brad and Wendy were excluded from this discussion).

5. The forum, which is used for technical Joomla support, has been experiencing a great influx of spam the last year. Last May a new forum protection mechanism has been put in place. It decreased the amount of spammers drastically. The downside is that some people with dynamic IP addresses have problems reaching the forum because spammer’s IP addresses get automatically banned for some period. This resulted in three complaints from (non-spamming ;-) people over the last three months.

  • Action item 7: create a contact form for issues like these, and link from the forum.

The new Joomla versioning system will increase the maintenance of main boards and international subboards because those have to be created. It has been decided to only create boards for Long Time Support (LTS) versions.

  • Action Item 8: To ensure that we have enough forum coverage to support our users, we need to check in with any inactive moderators to see if their interest is still in being members of the Moderator team

6. The People website lacks some moderation features.

  • Action item 9: define the needed moderation features and write a Request For Proposals (RFP) to get the features developed.

7. JUGs
* 1st official Joomla book (from Person) was meant to be spread around all JUGs, but this did not work out as planned. There is an idea to try using coupons that people can use to order copies of the books
Sandra + Liam will arrange it for the next books that are released in the series
* be more proactive: identify areas / countries where no JUGs are active (or where they are inactive) and try to reactivate / support people in those areas to organize JUGs.

8. Currently does not have a credits page to acknowledge current as well as all previous contributors to the sites and infrastructure areas (software/design/support services donated to the project for use). This is something that can be worked in with the site redesign which is currently in progress *link to people site redesign group.

B. New candidates for CLT:

The current CLT members have selected people from the nominations that were submitted by the community. Invitations have been sent out to these folks and once confirmation has been received from them, we will announce this and welcome them to the CLT publicly.

C. Ways to improve processes to become more proactive

Currently a lot of teams are functioning in a reactive way, in the sense that a lot of actions will be taken when people from the (international) community ask for help. E.g. a community from some country may ask for help regarding organizing a Joomladay. This behavior might result in some countries and areas that are not covered. Action item 10: We should come up with ways to be more proactive. E.g. find uncovered countries and motivate local communities to organize events.

D. Version labeling for JED and Forums

We need to request clarification from the PLT regarding the version numbering as this affects some areas such as the JED compatibility labeling and the categorizing of support forums. (note: discussed by PLT and put forth since for community feedback)

E. and its community are very English orientated.

While English is the common language in the software world, the majority of the world population don't speak English. For Joomla! to be successful in the non Anglo-Saxon world, we must invest more (time) in local foreign language communities. We would like to increase Joomla use as well as recruit more volunteers from the non-Anglo-Saxon world. We realize that there are communication issues and barriers for participation that need to be addressed.

F. Combined Summit Notes Discussed during the CLT meeting Day 2:

During the combined summit the following communication issues have been identified:

1. Language barriers. Sometimes our communication is too difficult (e.g. difficult English words and sentences too long) and too much fragmented over different communication channels. And has too much information to translate all to local languages.

2. For some countries the concept of Joomladays is not always clear. Furthermore there’s too little marketing budget for local foreign language communities to promote Joomla.

3. Documentation about processes in local communities is sometimes lacking. Which makes it difficult for people to take over the organisation of local JUGS when current JUG organiser steps down.

4. Official communication from to foreign non-English communities is too sometimes too difficult, and not helpful with solving the actual problem. Official documents (e.g. trademark rules) have often not been translated into foreign non-English languages.

During the combined summit the following participation issues have been identified:

1. Missing overview of all countries/language entities and local communities

2. How to organize responsibilities and autonomy of local communities in relation with

3. Cultural barriers - in some countries people are not always that outspoken to the international community, only within their own local community.

4. In some cultures/countries the standards of living are not as high as they are in the western world. Which causes that some people have too little time to participate because they need to have multiple jobs to make their living which leaves no time to participate. In that case working as volunteer doesn’t have much incentives / rewards back.

At the combined summit two new problems regarding have been found: The International flags in the main menu are confusing visitors, as when they click on a flag they expect to be taken to a page that contains content and/or language packs respective to each flag. This creates an additional problem in that, by looking at those flags, one might assume that certain languages are missing.

  • Action item 11: find a better way to represent “internationalism” and create an image/button for the website.

Another issue that has been brought forward is that the current site is missing a search box.

  • Action item 12: find out why the search box has not been placed on the homepage, and put it there if needed.

During the combined summit we’ve decided to compile a spreadsheet to take inventory of countries, languages, regions, local communities, nature of those communities, and in what countries communities are missing. [action item solved]. Secondly we’ve divided the world in regions: North-America, South-America, Europe, Africa, Asia+Pacific. Each region gets assigned one or two regional community coordinators / contact persons who will help with making the inventory. After we have such an overview they will get in touch with the local communities to find our their needs (e.g marketing, translation), get information and opinions, and help with updating the Joomla Info Pages project (to redirect international people to the local community sites). A further update will be provided to the community when it is time to put this idea into action and request volunteer help.

In Closing...

we would like to say that we enjoyed our time at the summit so much. Not only together as the CLT but with our friends and fellow team members on the Open Source Matters board and the Production Leadership Team. It was a very productive and positive event and we thank everyone that we were able to attend the summit with, as well as the incredible Joomla Community, whom without, we would not have been able to take part.

Comments and Discussion are welcome in this thread at the Joomla! People site.






Report from the OSM Summit - San Jose 2011
Written by Ryan Ozimek   
Wednesday, 03 August 2011 00:29

After three long days at the Joomla Leadership Summit, a team of eleven Open Source Matters members from four continents met in San Jose, California for our annual summit. Yes, much pizza was eaten. No, we didn’t spend too much time swimming in the hotel pool. Instead, we worked hard through seven sessions to pack as much Joomla goodness into two days as possible. We recognized that we couldn’t solve all our challenges in this short period, so we created small groups and focused on action items to help build momentum and progress.

OSM Board Summit 2011

Your OSM team, from left-to-right: Akarawuth Tamrareang, Thomas Hampton, Marijke Stuivenberg, Ryan Ozimek, Altansukh Tumenjargal, Robert Deutz, Alice Grevet, Jacques Rentzke, Sandy Ordonez, Paul Orwig, Dianne Henning

Now, for your viewing pleasure, here’s our report-back to the community.






Joint Summit Report
Written by Alice Grevet   
Monday, 01 August 2011 21:16

Joint Summit Attendees:

CLT: Peter Martin, Paul Orwig, Wendy Robinson, Sandra Warren
OSM: Robert Deutz, Alice Grevet, Dianne Henning, Sandy Ordonez, Paul Orwig, Ryan Ozimek, Jacques Rentzke, Marijke Stuivenberg, Akarawuth Tamrareang, Altansukh Tumenjargal
PLT: Chris Davenport, Mark Dexter, Louis Landry, Sam Moffatt, Omar Ramos, Ron Severdia, Jean-Marie Simmonet, Andrea Tarr

Where we came from:

The Netherlands
South Africa

Topics Covered and Action Items (where applicable) Created

The following is a brief summary of the topics discussed. Detailed reports will be published as they are produced.

  1. Removal of the AGPL license from the Joomla Contributor Agreement (JCA)

    It was unanimously voted to discontinue the AGPL license. This lessens restrictions and will open up the project to more contributors.
  2. Restructuring

    The Joomla Leadership, including the Open Source Matters board, Community Leadership Team, and Production Leadership team, recognize that our current leadership structure could be more effective.  Communication between our teams and the community needs improvement, and oversight needs rethinking.  As a team, we strive to be more effective leaders for the community. To achieve this, we have begun extensive discussions about the project’s leadership structure. This discussion is early and on-going.  As we consider important changes to continue on a path towards more effectiveness, we intend to request community input and feedback to help us in this important effort.
  3. Communications - External

    The communications breakout discussion was one of the most lengthy. Audiences and current communications channels were identified - there are many! A review was made of the document produced by the current communications team this past spring, defining what is communications. Roles and responsibilities for the communications team moving forward were listed. Action items include: condensing the 12 newly defined roles into a more manageable list and begin identifying potential owners for these roles. Candidates must have a passion for communications and experience in the specific area (marketing, branding, graphics, etc).
  4. Communications Internal

    A working group will be started to bridge the gap when communication needs a boost between the community and the JUGs, the JED, events, merchandise and trademark. A comprehensive leadership directory wiki will be created for a better flow of leadership communication and troubleshooting. The communications team volunteers to disburse intra team communications, and facilitate intra team conflict resolution, including the creation of a FAQ list within the wiki for that purpose.
  5. Internationalization

    While English is the common language in the software world, the majority of the world population does not speak English. To increase Joomla’s presence in a proactive way and recruit more non-English-speaking volunteers, the following action items will be implemented: concentrating our efforts in the different regions of the world by identifying one or two community coordinators / contact persons in each region; compiling a list of currently active local communities and JUGs and see if there are any groups which have not yet been accounted for; identifying their needs, the nature of their communities, and recruiting translation help to update the Joomla info pages.
  6. Roadmap and Goals

    This discussion first explored the benefits of creating a public unified roadmap that encompasses the entire scope of the Joomla! project. After that, the discussion continued to define a process for creating a public unified roadmap that also includes periodic public progress updates from leadership.

    The process for creating a public unified roadmap involves: Leadership defines and publishes an overall mission statement for the project. This is high level and conceptual.

    Each leadership team defines and publishes their team’s mission statement, which should support the project’s overall mission. Each leadership team’s mission statement may need to be revised to insure that they all tie in well with the overall project mission statement. Each leadership team defines and publishes their annual goals which support their team’s mission statement. For each leadership team’s goals, the following supporting details will be added and published: milestones (achievement and target completion date); action items (each task required to progress toward achieving the milestone; resource(s): volunteer or paid workers, financial (specify the purpose and budget line item); features (if applicable), action items (if applicable), resources (if applicable). Each leadership team publishes periodic updates during the course of the year regarding their progress on each of their goals.
  7. Volunteer Recruitment and Rentention

    The PLT discussed forming a Joomla Outreach Project (JOP), where a "bucket" of tasks is created by teams, using the wiki. Community members would be invited to join these teams, and they would work in alignment with development goals, under the guidance of the PLT. Incentives (such as T-shirts) would be awarded upon the completion of each set of tasks.

    Volunteer Now is a plan for recruiting new team members, because teams should be created to manage recurring, long-term tasks that require deeper knowledge. A volunteer engagement page will be created on the wiki, and a Volunteer Now button will link to it from the home page. In the wiki a future volunteer will find documentation on how and why we build teams, and contacts for the projects major teams and assets.

    A concept will be drafted listing outreach ideas for engaging university students.
  8. Process Improvement

    Regarding processes and messages in correspondence (for example, in areas of trademark, the JED and events), we often need more differentiation and adapted responses to specific situations.

    Action items include: reviewing our texts to verify if we are using a friendly approach aimed at optimizing communication; listing and identifying situations and creating responses adapted to them; simplifying language.
  9. Review Developer Sponsorship Program

    We talked about the state of the Developer Sponsorship Program and how we handle the involvement of sponsored development time from companies and guide this process more effectively in the future. One Idea was to move from pre to post recognition and use a to-do list and let people pick from the “cookie jar” list to sponsor development time.

    Action items include: speaking with the existing sponsors about their experience and writing a report; deciding if a money only approach or money and development time approach is best, finding a volunteer to manage the cookie jar.
  10. Certification

    A 1 - 2 plan of certification ideas and how to approach them will be drafted. Feedback from each leadership team will be gathered. The plan will include creating levels for web masters, designers and instructors of joomla, creating a curriculum and courses template for trainers, financial and licensing fees to create more revenue, a test database infrastructure.
  11. Improving Recruitment of New Developers

    A story we want to help tell is that Joomla can provide students with CS degrees experience on a global team that goes far beyond just a curriculum. Action items include creating a spreadsheet where we can determine which events developers are attending, and writing a one page messaging document outlining persuasive reasons why the Joomla Platform and CMS are useful for developers, and target university students.
  12. Long Term Roadmap

    We talked about the process for establishing goals and milestones for the Joomla project long term releases. Once every 6 months the PLT and developers will meet just before or after an existing event such as a Joomla Day or JandBeyond. We are hoping to do the first one this fall where milestones and goals for the July 2013 long term release will be discussed.

The entire leadership would like to thank eBay for the use of its offices for our summit, and Louis and Ron for coordinating with them. Thanks to Rochen we had tasty lunches, ordered with care by Wendy. And Gunner, our Summit Facilitator Extraordinaire kept us on target and on time!

For comments and feedback click here






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.


Page 26 of 48