There are some pretty exciting changes coming with regard to how we work on Joomla!.  In the near future we are going to be allowing developers to register accounts via our Joomla! Developer Network site and be given access to commit code to our subversion repositories with those accounts.  We will be keeping the trunk and release sections of our repository secured for trusted maintainers, but anyone will be able to create and work in branches so that more people can be working collaboratively on making Joomla! better.

While these changes are a fantastic step towards facilitating access to the core software, they also potentially expose the project to some problems.  Historically, gaining commit access to the core repository has come with earning the trust and favor of the existing committers.  This has kept the group relatively small, and given us all good assurances that the people who are committing code understand the ramifications, both legal and social, of having that privilege.  By opening up to self-registration we are losing some of that assurance, so we felt it was important to formalize the terms under which we accept contributions to our project repositories.  

I?ve spent quite a bit of time working with OSM, the Production Leadership Team, and obviously OSM?s attorneys to come up with what we believe to be a great solution to these challenges: the Joomla! Contributor Agreement (JCA).  The JCA is based on the Sun Contributor Agreement, version 1.5, by Sun Microsystems, but obviously reworked for our purposes.  My hope is that it will make expectations for both the contributor and the Joomla! project more clear as we move into the future.  What I am presenting here today are three draft documents, and I am asking for your feedback.

The Joomla Community Leadership Team is proud to announce the addition of two new members.

Wendy Robinson is currently on the OSM board. She will be leaving OSM when her term is up in February.

Ole Ottosen was already on the Production Leadership Team, but found that most of the work he was doing was for the community side of the project. Ole's move from the Production Leadership Team to the Community Leadership Team is effective immediately.

With a new year upon us, we welcome both Wendy and Ole to the team.

This is just a short note to say that we've asked the Forum Admins to archive the White Papers forum while the Production Leadership Team works on a replacement in conjunction with the rebooting of developer.joomla.org and the commencement of new development initiatives this year.  The content will be kept for some time as there is good material in there to work off.  More information about a replacement process will be forthcoming as soon as we can make it available to you.

The Joomla! Production Leadership Team is pleased to welcome two new members, Christophe Demko and Jean-Marie Simonet.

They have both demonstrated remarkable and continued contributions for joomla 1.5 and the upcoming joomla 1.6, and their combined insight and devotion for i18n/l10n and translation matters, will be of great importance for further improvements of this part of the joomla software.

We see them as the best people for this particular job currently, and therefore are very pleased that they both accepted the invitation to join the team.

One of the great things about the recent Joomla! Developers Conference in New York was that, with Andrew, Ian, Louis, Ron, Sam, and myself, we had all four Development Coordinators plus a majority of the Production Work Group all in one place for the very first time. This gave us the chance to talk in depth about an important issue that is critical to the future of the project -- the release cycle.

As many of you know, version 1.5 was released in January of 2007, almost 2 years ago. That means that it will be over 2 years between versions 1.5 and 1.6. I think most of us would agree that this is too long between versions. But just saying we should release more often doesn't address the underlying issues and challenges.

Fortunately, Louis had given this a lot of thought, and he led a discussion of how we can get to a more dynamic release cycle while preserving the stability and reliability that our users have come to expect. I wrote up a short proposal based on that discussion and just posted it to the General Development list here.

As I stress in that post, although we are excited about this idea, it is only a proposal at this point. We want to hear your feedback before we make any decisions. So, if this is a subject that you care about, please read, consider, and then let us know your thoughts. Thanks!