The collaboration within the Joomla! Open-source project is based upon the trust and fun. We want to put as little hierarchy into this team as possible, and, if we actually do Joomla! (all together) this section will be superfluous. But for every team that exists of more than one person, a structure needs to be in place.
This team sometimes also is referred to as core-committers. Some of the members are also core-team members, but the term "core-comitter" refers to team members who have full commit access to the Joomla! code base.
The Development Work group Coordinator has the overall lead on Joomla! development and has the following responsibilities:
A Development working group coordinator his/her main responsibility is to organize everything around Joomla! development. This is actually one of the very few official positions. The Development working group coordinators set direction, organize the team and do general overview for Joomla! development.
A Developer actually performs programming, testing and documentation tasks. A Developer can potentially assign himself to a wide variety of tasks but their individual abilities will likely determine which areas he/she will work on.
The development work group aims at the development of a cutting edge, state of the art Web Content Management application framework. This workgroup is the driving force behind new versions, and building it. Along with the other working groups we try to realize this ambition.
We always seek for new talent. We are very sharp on who we want because the results of this workgroup determines what the quality of Joomla! is. Most of the times we get in touch with you when we see some interesting work around, but if you think you are the talent we seek you also can contact us. If you want to grab our attention, start [Sending in patches] so we actually can see what you do, and how you do. Before you do please bear the following in mind:
Within the development work group, we recognize three membership statuses:
A development team group member is considered active if they are contributing to a communication channel at least once a week and fulfilling a reasonable time commitment to the project. To prevent stagnant teams and blocking out new talent from getting into the development work group some limitations apply to the possible statuses described above:
In all cases it is important that the developers informs the work group coordinator or lead developer of his team that he/she is (planning to go) on leave or being inactive.
It would be naive to assume that a group of people can work together in perfect harmony. There are going to be times when someone feels they have been wronged. In these times the following procedure should apply:
Team members are encouraged to self-mediate all disputes. In all situations, treat 'wounds' appropriately. A prick on the finger just needs a tissue for a couple of seconds. Some grazes and cut just need a Band-Aid to help heal well but will probably heal anyway if left untouched. More serious lacerations need immediate intervention for survival. If a wound is left to attract an infection then the obvious threat of gangrene is present.
Everyone in Joomla! has their season and there are going to be times when someone needs to move on for various reasons. You should always feel comfortable to leave or have a holiday from the project, just inform the work group coordinator or better yet, let the whole team know by posting your absence to the mailing list (email@example.com). If you are going to be unavailable for a period of time, please be considerate and:
A development team member will be removed: