Computer Data Recovery

The Community Leadership Team has created a relief system for the backlog of Joomla User Group (JUG) submissions and correspondence. We would like your help to make this work though.

As of right now, if you are on the waiting list of people who have not heard back about a JUG submission, We have a new form that we ask you to fill out at your earliest convenience.

Resubmit your application using  JUG Submission Form

We know you are tired of forms!  So are we.  For now though this is only a stop gap solution while we work on something more permanent and efficient for all.  We feel this new form can be processed on our end much faster than the current system.

We would appreciate any feedback you have to offer in the JUGs People.Joomla group.

Thank you for your patience! Joomla User Groups make up a valuable component of our community. We appreciate your continued efforts and we look forward to working with you as we resolve this issue as quickly and effectively as possible.

On behalf of the Community Leadership Team, I would like to take this opportunity to welcome Sandra Warren and Matt Lipscomb as our newest members.

Sandra has been instrumental in organizing a brand new team to help with the beta launch of People Site.  As co-admin, her efforts have helped steer our community into new territory here on joomla.org and she's done a tremendous job of it.  Sandra and her team are now hard at work getting the People Site ready for its upcoming Official Launch.

Matt currently works on various Community Workgroup teams including the Site Showcase, Support Forums, JCM and the JRD.  He does an outstanding job in all.  Some of Matt?s more recent contributions include a discussion with the community to find ways to make JRD inclusion easier and the Joomla! Weekly Challenge which encourages people to contribute in various ways to the project and global community.

We think Sandra and Matt will be excellent additions to our team and we thank them for taking on this added role to their current positions in the project.

Sandra, Matt... Welcome!

I'm pleased to announce that the OSM Board has new leaders filling critical roles in our organization.

During the past few months, I've spearheaded a project inside Open Source Matters (OSM) to delineate clear roles and responsibilities for a few important positions within our organization.  The goal of this project was to enable our team to more effectively match board members' talents with positions that set them up for success and provided clear objectives and responsibilities.  By putting this project into action, Board members are able to clearly understand what is expected of them within each position, as well as measure their success more objectively with metrics developed by them and their fellow teammates.

This project also provides the Board an opportunity to have a written understanding of the scope these positions.  In the professionalizing of our Board, I strongly believe that actually writing down these positions roles and responsibilities are key to us achieving our goals, and keeping our sanity.  I've even gone as far as to tell candidates for Board positions that one of their key goals should be to find ways to make themselves "obsolete", or in other words, ensure that when it's time for them to hand over their leadership position to another colleague, the new leader can focus on innovation rather than needing to rebuild systems from scratch.

You probably didn't notice, but recently we have republished the "Support Joomla!" page. We also have a new "Support Joomla!" module for anyone to use. This is exciting because for the past several years we have not been able to ask the Joomla! Community for financial support. What happened?

As I mentioned back in February, at the advice of our attorneys, and with a lot of reflection, the board of Open Source Matters (OSM)  had been exploring the possibility of "correcting" its corporate charter. Those corrections have now been made, and this post will explain what that means. The specific changes could not be discussed previously because they were legal advice, but now we can do so. There are complicated legal and financial reasons for making these changes which I am going to try to explain in this post.   It will be a little heavy going, so before I start let me stress the two main points:

• OSM will always remain a not for profit organization.
• This change will allow OSM to ask for money for support of the Joomla! Project.

  
  

  
  
  
  
• Mooing Forward With Joomla! 1.5
  

  Since the release of Mootools 1.2, we have found ourselves facing a rather difficult question - what do you do with the 1.5 core?  Unfortunately, the changes that came in Mootools 1.2 were significant enough that backwards compatibility with Mootools 1.1 was a difficult task.  I like to compare it to the difference between Joomla! 1.0 and Joomla! 1.5.  We did a lot of house cleaning and made our framework much smoother and much cleaner.

  Such is the case for Mootools 1.1 and Mootools 1.2.  The new Mootools represents a significant step forward.

  As a result, Joomla! developers have found themselves in a difficult position. Do you use the outdated version of Mootools, thereby reducing compatibility issues and making life easier for users, or do you use the new version and attempt one of a variety methods of overriding the core framework.

  We hope to change all of that in the near future.

  As has been previously mentioned, it is our plan to give Joomla! 1.5 an upgrade to Mootools 1.2.  This will allow developers to take advantage of the improvements that this new version offers and to write code that will endure into the future.

  We have set a target release date of July 15, 2010 for Joomla! 1.5 with Mootools 1.2.

  The Gory Details

  I previously released an upgrade plugin for people to test out which replaced the core JHtmlBehavior class. This plugin implemented the JHtmlBehavior::framework method that has been added in trunk. The Mootools upgrade that will be included with Joomla! 1.5 will follow along in this direction.

  After the 1.5 update is uploaded, the plugin will be installed the first time an administrator logs into the administrator panel.  They will also be presented with a message asking them if they would like to enable the plugin. Once the plugin is enabled the site will then be using Mootools 1.2.

  When the plugin is enabled whenever the framework Mootools library is loaded Mootools 1.2 will be loaded with the compatibility layer.

  The hope is that even with the upgrade activated, there will be no negative impact on sites. However, in the event that the upgrade does cause problems, it will be easy for administrators to disable the plugin and restore their site to the previous state.

  We're excited about this development and are grateful to the folks at Mootools who have worked with us to provide a compatibility layer that could make this possible.

  The code is a work in progress. If you would like to check it out you are free to check it out from http://joomlacode.org/svn/joomla/development/branches/mt12.