| Changes in the bug squad and development team |
| Coordinator Blog | |||
| Written by Wilco Jansen | |||
|
Over the past three years, Joomla! development has evolved. During the split from the Mambo project the Joomla! Core Team was fully responsible for overall development. As the project grew, the Core Team realized that additional structures where required to organize everything around the Joomla! project. Mid-2006, the Joomla! Core Team changed from a "developers only" team into a team that had coordinators for several focused areas. One of the roles was the role of "Development Coordinator." I was the first Development Coordinator within the Joomla! project and we only had general ideas on how this role should be fulfilled. The role has changed over time, and is still changing as the project evolves. In August 2007, we drafted a plan to work on a final version of Joomla! 1.5. Being able to work on maintenance releases was key for releasing a stable version of Joomla! 1.5. After the split the development team worked on maintenance versions for Joomla! 1.0 and a full refactoring for Joomla! 1.5, but until then we never had released a new major version. The development team was simply too small, and with the focus on creating new logic we decided to create a new team with maintenance as their main responsibility. The Bug Squad has also evolved from a relative small and unstructured team, into a large group of active people that is very well organized (see the Joomla! maintenance procedures if you are interested how things work in the Bug Squad). Bug SquadWithin the Bug Squad we also have implemented some changes. We abandoned the position of team leader and created a new position of Joomla! Bug Squad Team Coordinator. We asked Ian MacLennan and Mark Dexter to fill that role, and we are glad they accepted. Within this role, they take care of the day to day operation of the Joomla! Bug Squad and help new members to find their way into this team. Andrew Eddie, Anthony Ferrara and Samuel Moffatt represent the core team, and along with me, the four of us support Ian and Mark working on the overall coordination (in the role as Development Team Coordinators) working hard on moving forward. Development teamLet's start with the Google Summer of Code. As you could have read in the September edition of the magazine we had a very successful version of this great event. As a result, we had ten successful projects. We invited Chantal Bisson, Dahn Le Phuoc and Ercan Özkaya to join the Development Working Group. We are very happy to announce that they each accepted our invitation, strengthening the Development Working Group. We expect to see them accomplish more great work.
|





Monday, 24 November 2008
Thank you for your massive contribution.
Wednesday, 19 November 2008
Monday, 17 November 2008
Thursday, 13 November 2008
Keep it coming and good luck!
Monday, 10 November 2008
Thanks.
Monday, 03 November 2008
thanks
Wednesday, 22 October 2008
Monday, 29 September 2008
I do quiet a lot of Joomla Testing when new versions come out would love to help you guys in being one of the testers but then again everyone who uses Joomla is really a tester until a final version is released.
I cant wait for 1.6 been dreaming about the functionality in it
Let me know if you guys need any business development help I would be more than happy to extend any help possible specially if it involves the Middle East Region.
Saturday, 27 September 2008
Saturday, 27 September 2008
Saturday, 27 September 2008
Friday, 26 September 2008
Friday, 26 September 2008
As you probably know I am a former Quality & Testing team member and I know all the hard work and first of all the time needed to be dedicated to the project. It's a good and exciting experience!
The splitting idea is a good one. In addition to that I'd like to share with you an idea of mine, that is to foresee a sort of special team, only another one for a particular, specific work, maybe the team could be named as the improvement team. An example, if you need to code all the lines from php4 to php5, well, an improvement team should be more strategical and less time consuming than an improvement one...
Bye
Ezio
Thursday, 25 September 2008
Wednesday, 24 September 2008
Thats not quite right as probably half of the original "core team" were not developers.