Joomla! Press - The Official Books of Joomla
Joomla! Press™ is the official imprint of the Joomla! Project, through our publishing partner, Pearson (Addison-Wesley Professional). A portion of each book sale is given to the Joomla! Project. Additionally, Open Source Matters, Inc. is an affiliate of informIT - so each purchase made through affiliate sales produces additional revenue for Joomla and goes directly back to the Joomla! project and community needs.
Purchasing one these books is an excellent way to learn about Joomla while supporting the project and community!
- Joomla! Templates - By Angie Radtke
- Joomla! Programming - By Mark Dexter, Louis Landry
- Joomla! Explained: Your Step-by-Step Guide - By Stephen Burge
- Official Joomla! Book, 2nd Edition - By Jennifer Marriott, Elin Waring
These books (and translations) are also avialable from Amazon
The global leader in education services and technology, Pearson is home to such respected brands as Addison-Wesley Professional, Cisco Press, Exam Cram, IBM Press, Prentice Hall Professional, Que, and Sams Publishing, which have as their online publishing arm, InformIT (www.informit.com) -The Trusted Technology Learning Source.
Joomla! Press Mission Statement
The mission of Joomla! Press is to enhance the Joomla! experience by providing useful, well-written, and engaging publications for all segments of the Joomla! Community from beginning users to framework developers. Titles in Joomla! Press are authored by the leading experts and contributors in the community.
The Joomla Project is comprised of many teams, each with a general areas of responsibility in accordance with our overall project mission/vision. Below is an outline of the teams and their areas of responsibility.
Joomla Leadership Team
The Leadership Team consists of leaders from Production Working Group and Community Working Group.
Responsibilities: Responsible for overall management of project and the community.
Public Discussion Group: http://groups.google.com/group/joomla-leadership
Production Working Group
Create software that is free, secure and of high-quality—encompasses everything that goes into the final product, not just code but also documentation, internationalization and localization efforts of all types.
Leaders: Roland Dalmulder, Chris Davenport, Robert Deutz, Jessica Dunbar, Javier Gomez, Thomas Hunziker, David Hurley, Tom Hutchison, Viktor Vogel, and George Wilson
Public Discussion Group: http://groups.google.com/group/joomla-wg-production
Community Working Group
Provide the structures and community management necessary to create an online community that is enjoyable and rewarding to participate in, nurture and support online communities of users, provide support and information to users, and facilitate communication between users and the Production Working Group.
Leaders:Brad Baker, Isidro Baquero, Guillermo Bravo, Peter Bui, Ruth Cheesley, Alice Grevet, Dianne Hennig, David Jardin, Peter Martin, Olaf Offick and Sander Potjer.
Responsibilities: Joomla Discussion Forums, social networks, communications support, Joomla Extensions Directory, Joomla Community Portal, Joomla Community Showcase, Joomla User Groups, Joomla demo sites.
Public Discussion Group: http://groups.google.com/group/joomla-wg-community
Open Source Matters
Legal, financial and other organizational needs of the Project that fall outside of the two Working Groups.
Board of Directors: Martijn Boomsma, Mike Carson, Ronni Christiansen, Victor Drover, Jorge Lopez-Bachiller Fernandez, Rod Martin, Tessa Mero, Ryan Ozimek, Saurabh Shah, Joe Sonne, Marijke Stuivenberg, Radek Suski, Sarah Watz
More information: http://www.opensourcematters.org
Public Discussion Group: http://groups.google.com/group/open-source-matters-public
Volunteer Code of Conduct
This document outlines the Code of Conduct for all persons volunteering their service to the Joomla Project as a Core or Working Group Member or part of Open Source Matters. It covers your behaviour as a member of the Joomla community, in any forum, mailing list, Wiki, Web site, IRC channel, install-fest, public meeting or private correspondence. If you cannot agree to any of these principles, then volunteering in the Joomla Project is not for you. Accepting the role offered assumes acceptance of these principles:
You are working with others as a team so be considerate of how your actions or contribution affects your colleagues and the community as a whole.
Treat one another and members of the community with respect. Everyone can make a valuable contribution to Joomla. We may not always agree, but disagreement is no excuse for poor behavior or poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect the members of Joomla community to be respectful when dealing with other volunteers as well as with people from outside projects and initiatives and with users. Avoid becoming involved in flame wars, trolling, personal attacks, and repetitive arguments. Take the matters "outside" (off-list, etc) if it helps resolve the situation, and do not use communal methods of communication to be a vehicle for your private "wall of shame."
Joomla is free software and about collaboration and working together. Collaboration reduces redundancy of work done in the free software world, and improves the quality of the software produced regardless of whether you are writing code or performing some other task.
When you disagree, consult others. Disagreements, both political and technical, happen all the time, and Joomla is no exception. Disagreement, debate and constructive criticism is often how progress is made and are a necessary part of doing complex work in a team. The important goal is not to avoid disagreements or differing views but to resolve them constructively. Above all, avoid making conflicts about the work into personal conflicts. Debate should never include reference to someone's nationality, gender, religion or other personal characteristics. You should turn to the community and to the community process to seek advice and to resolve disagreements. There are also Working Group Coordinators and Team Leaders who may be able to help you figure out which direction will be most acceptable.
When you are unsure, ask for help. Nobody knows everything and nobody is expected to be perfect. Asking questions avoids many problems down the road and so questions are encouraged. Those who are asked should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum. Off-topic questions, such as requests for help on a development mailing list, detract from productive discussion.
Step Down Considerately
People on every project come and go, and Joomla is no different. When you leave or disengage from the community, in whole or in part, we ask that you do so in a way that minimizes disruption to the Project. This means you should tell people you are leaving and take the proper steps to ensure that others can pick up where you leave off.
Check your e-mails regularly and answer them promptly—even if it's "I'll get back to you."
Sometimes the hardest thing to say is "no" or admit you've forgotten do something. Be honest with each other and yourself with regards to what you say and what you can realistically commit to.
Follow the Rules
Volunteers are expected to uphold Joomla's licensing and trademark requirements including, but not limited to, compliance on their own or affiliate Web sites and extensions. Make sure you have sought the appropriate approvals for domain name, name and logo usage prior to volunteering and that any extensions you distribute comply with the Joomla license.
All work contributed to the Project, whether code, documentation or other material, must observe the appropriate licenses as set down by the Core Team and Open Source Matters.
Some Workgroup members represent the Joomla Project in specific areas, but you should not speak on behalf of the Project or present yourself as an official representative of the Project unless you are specifically authorized to do so, and you should never state your opinions as the official policies of the Project.
Exercise Discretion and Confidentiality at Appropriate Times
Depending on your role, you will be privy to various levels of information. As a volunteer you are expected to keep site access details (such as logins, FTP details, etc.) secure at all times. Information contained within private forums (for example, about serious security matters, legal cases, or personal details), private mailing lists, chats or other mediums is also to be kept confidential even after you have discontinued your service. Breaches in the area of privacy and confidentiality are taken very seriously by the Project.
Conflict of Interest
When using Project resources or making decisions within your team, workgroup or the concerning Project's policy positions, you must do so based only based on the best interests of the Project and its user community. If you have a situation or affiliation that might constitute or lead to a conflict of interest or might be perceived by a reasonable person in the community to be a conflict of interest, disclose this to your Team Leaders or the team as a whole. If appropriate, after discussing with your team, you should remove yourself from specific decisions or discussions in which you may have a conflict of interest.
The Fine Print
Members of the Community Oversight Committee (Core Team) and the board of Open Source Matters are governed by additional guidelines and requirements and, where a conflict exists, these take precedence over this Code of Conduct.
The Last Bit
This Code of Conduct has changed over time and will continue to develop, but was originally derived, with permission, from the Ubuntu CoC.
Mission, Vision & Values
In 2008, the Joomla Project wrote the following statement to reaffirm its overall mission, vision, and project goals.
Our mission is to provide a flexible platform for digital publishing and collaboration.
(View commentary below)
In our vision, we see:
- People publishing and collaborating in their communities and around the world
- Software that is free, secure, and high-quality
- A community that is enjoyable and rewarding to participate in
- People around the world using their preferred languages
- A project that acts autonomously
- A project that is socially responsible
- A project dedicated to maintaining the trust of its users
To further clarify the items outlined above, the following commentary is provided.
Our mission is to provide a flexible platform for digital publishing and collaboration.
We felt strongly that the mission statement should be short and succinct; the inspiration being the Subversion mission statement: "To create a compelling replacement for CVS."
The word "provide" is used because it can be taken to imply "design," "develop," and "distribute" as well as leaving the possibility of providing "software as a service" capabilities.
The word "platform" is used to emphasise not only that the Joomla CMS can be extended, but also that we will most likely release the Joomla Framework as a separate platform at some point and might develop a non-CMS application on top of it.
The word "digital" is used in preference to words like "Web" or "Internet" because many users run Joomla on an intranet with no Internet connection. A use case we kept in mind was of a school in Africa which has a network of PCs and uses Joomla to disseminate information to students, but which has no Internet connection.
The words "publishing" and "collaboration" were carefully chosen. "Publishing" seems an obvious choice given that Joomla is a CMS, but "collaboration" was chosen to try to express the kind of applications that we might provide on top of the Joomla Framework. With our sites and events we also provide platforms for communication and collaboration so those things are part of carrying out our mission too.
In our vision, we see:
People publishing and collaborating in their communities and around the world;
Notice that we use the word "people" here and not "users." Users might be thought of as those who build and run a Web site, but by deliberately avoiding that term we broaden our vision to include everyone, including site visitors, but perhaps even those members of the community who never come into contact with the software at all but are affected by those who do.
Notice that "publishing and collaborating" is taken directly from our Mission Statement. Our mission is to provide a platform for publishing and collaboration and our vision is that people will be empowered by that platform to publish and collaborate.
The word "communities" is deliberately vague in that it could refer to the community of people who visit the user's Web site, the Joomla community, or indeed other communities too. The plural is used because people invariably belong to multiple overlapping communities.
The words "and around the world" hint at people being able to go beyond their local communities, however we define "local," to reach out around the world. Perhaps they are publishing to a global audience or perhaps they want to invite new collaborators into their community from around the world.
Software that is free, secure and of high-quality;
"Freedom" is one of our key values, but the use of the word "free" here deliberately exploits the ambiguity in the English language between "free as in freedom" and "free as in no charge." Translators of this vision statement will need to be aware that both meanings are intended.
The words "secure" and "high-quality" were added in response to feedback at the Core Team Summit.
A community that is enjoyable and rewarding to participate in;
This statement is not only a recognition that a community is essential for the future of the project, but also that it must be of a certain character, namely "rewarding and enjoyable to participate in."
Participation is important since the entire project hinges on it. Although the community could be thought of as including people who do not participate in any meaningful way, it is those who participate that are key to the success of the project. It follows that the community must be attractive enough for people to want to participate in it. This is a statement of our belief that if we can make the community "rewarding and enjoyable to participate in," then people will be attracted to it and will remain a part of it.
Of course, it doesn't say how to make the community rewarding and enjoyable to participate in because that is not an easy question to answer. It may be different things to different people and it may change over time. The community itself learns how to best reward its members.
People around the world using their preferred languages;
Again, "people" instead of "users."
The word "using" should be thought of as including activities such as installing and maintaining a Web site as well as site visitors actually using the Web site.
The words "around the world" and "preferred languages" are used so that languages are not thought of as being geographically localized. It should be possible for someone to use the software in their preferred languages no matter which country they find themselves in.
The plural "languages" is used here as people might have multiple preferred languages.
Our key value of "equality" makes it clear that just making the English version downloadable anywhere is not sufficient—it must be downloadable anywhere in the user's preferred langauge. Once downloaded and installed, it should also support people working in multiple languages.
A project that acts autonomously;
The word "project" is used here instead of "community" as only the project can make decisions. The exact boundaries of the project are ill-defined but could include Working Group members, for example, as they are often closely involved in decision-making.
That we should remain an organization that can make decisions autonomously is important to allay fears that we might "sell out" the project to some commercial operation.
A project that is socially responsible;
The words "socially responsible" echo Google's mantra "do no evil." Society could mean just "the community," but it could also refer to society in general.
The responsibility can be negative, meaning that there is a responsibility to refrain from acting, or it can be positive, meaning that there is a responsibility to take action.
An example of the project acting in a socially responsible manner is the work done by the forum moderators in ensuring that the forum is "rewarding and enjoyable to participate in." This is achieved through constant vigilance and upholding the forum rules.
A project dedicated to maintaining the trust of its users.
This is a recognition that anyone who is part of the community, even if only as a user of the software, places some degree of trust in the project and that is something that the project should strive to live up to.
One of the most important aspects of that trust is the recognition that project participants can't just think of their own individual interests, or even the interests of a collective, when making decisions.
"Freedom" was chosen as our topmost value for many reasons. We want to give people the freedom to build Web sites with which to publish their ideas. We want to give people the freedom to collaborate with others in their own language. And we want to give people the freedom to use, copy, modify, and distribute the code and protect those freedoms using the GNU/GPL. We also want to provide people with the freedom to be a part of the community and to participate in the future development of the project.
"Equality" was chosen as our second key value for many reasons. Naturally we want to ensure that the community is open to everyone regardless of race, sex, age or religion. We want to ensure that everyone has the opportunity to download the software regardless of their geographical location, which includes being aware of issues such as limited bandwidth. We want people to be able to use it in their preferred language, whatever that may be, so internationalization and localization are important too. We must also consider accessibility, both of our Web sites and of the software we produce.
"Trust" is a necessary foundation for the project. For example, it should be possible for people to trust that the project will deliver on its promises; that people in our Working Groups should be able to trust each other. Indeed, the project and the community exists largely because of a web of trust.
"Community" was chosen as our next key value because we are fundamentally a community project and would be unable to achieve anything without the community. Furthermore, the tools we provide are often used in the context of building communities. A sense of community should pervade everything we do. What we do, we do as a community.
"Collaboration" is another theme running through the project. Joomla lets people collaborate—to say work together on things—which is not necessarily part of community. Also, other things we do, such as in Joomlacode and the documentation wiki, encourage collaboration as do all of our work processes. The GPL in general encourages people to work together and the applications created by the project and even the project's culture encourage this.
"Usability" is a key value because we want everyone to be able to make use of our software, our documentation, our forums, and all our other sites. By making usability a key value, we hope to guide decision-making towards wider use and greater participation.
The Joomla Project has several Working Groups that have been created to utilize the wealth of knowledge our community provides. Each of these groups focuses on a specific aspect of Joomla essential to the project's growth and development.
They are also an opportunity for anyone interested in helping Joomla grow. Those who are interested are encouraged to work with or join a Working Group where your talents are best applied.
In order to make it as easy as possible for people to participate in working groups and for there to be flexible collaboration across team boundaries there are two large working groups.
The focus of the Production Working Group is on creating "Software that is free, secure and of high-quality." Production encompasses everything that goes into the final product, not just code but also documentation, internationalisation and localisation efforts of all types.
As an open source project, community lies at the heart of our very existence. We would not be the major open source project we are today were it not for the time and effort given by so many people who together form the Joomla community. The new Community Working Group is charged with providing the structures and community management necessary to create an online community that is "enjoyable and rewarding to participate in." It will nurture and support online communities of users, provide support and information to users, and facilitate communication between users and the Production Working Group. User communities may be based on language or region, user type (such as administrator, developer, site user, host, and so on), areas of interest or a new classification that emerges organically.
Working Group Leadership
Each Working Group has people who provide direction and leadership for the group. These are the people who keep the working groups functioning and provide continuity for project contributors.
Production Working Group Leadership
You can follow the Joomla Production Working Group Leadership Team on their public mailing list here:
|Subscribe to Joomla! Production Working Group Leadership|
|Visit this group|
Community Working Group Leadership
You can follow the Joomla Community Working Group Leadership Team on their public mailing list here:
|Subscribe to Joomla! Community Working Group Leadership|
|Visit this group|
Membership in a leadership team is not defined by being in a specific role but rather by doing the work of leading and directing the group. Members of the leadership teams will be appointed by the teams themselves and members can be removed by the teams themselves. The number of members of each leadership team is fluid and determined by the needs of the group. The leadership teams will be responsible for organising and managing task groups and other teams as they determine will be most effective.