After three long days at the Joomla Leadership Summit, a team of eleven Open Source Matters members from four continents met in San Jose, California for our annual summit. Yes, much pizza was eaten. No, we didn’t spend too much time swimming in the hotel pool. Instead, we worked hard through seven sessions to pack as much Joomla goodness into two days as possible. We recognized that we couldn’t solve all our challenges in this short period, so we created small groups and focused on action items to help build momentum and progress.
Your OSM team, from left-to-right: Akarawuth Tamrareang, Thomas Hampton, Marijke Stuivenberg, Ryan Ozimek, Altansukh Tumenjargal, Robert Deutz, Alice Grevet, Jacques Rentzke, Sandy Ordonez, Paul Orwig, Dianne Henning
Now, for your viewing pleasure, here’s our report-back to the community.
CLT: Peter Martin, Paul Orwig, Wendy Robinson, Sandra Warren OSM: Robert Deutz, Alice Grevet, Dianne Henning, Sandy Ordonez, Paul Orwig, Ryan Ozimek, Jacques Rentzke, Marijke Stuivenberg, Akarawuth Tamrareang, Altansukh Tumenjargal PLT: Chris Davenport, Mark Dexter, Louis Landry, Sam Moffatt, Omar Ramos, Ron Severdia, Jean-Marie Simmonet, Andrea Tarr
Where we came from:
Topics Covered and Action Items (where applicable) Created
The following is a brief summary of the topics discussed. Detailed reports will be published as they are produced.
Removal of the AGPL license from the Joomla Contributor Agreement (JCA)
It was unanimously voted to discontinue the AGPL license. This lessens restrictions and will open up the project to more contributors.
The Joomla Leadership, including the Open Source Matters board, Community Leadership Team, and Production Leadership team, recognize that our current leadership structure could be more effective. Communication between our teams and the community needs improvement, and oversight needs rethinking. As a team, we strive to be more effective leaders for the community. To achieve this, we have begun extensive discussions about the project’s leadership structure. This discussion is early and on-going. As we consider important changes to continue on a path towards more effectiveness, we intend to request community input and feedback to help us in this important effort.
Communications - External
The communications breakout discussion was one of the most lengthy. Audiences and current communications channels were identified - there are many! A review was made of the document produced by the current communications team this past spring, defining what is communications. Roles and responsibilities for the communications team moving forward were listed. Action items include: condensing the 12 newly defined roles into a more manageable list and begin identifying potential owners for these roles. Candidates must have a passion for communications and experience in the specific area (marketing, branding, graphics, etc).
A working group will be started to bridge the gap when communication needs a boost between the community and the JUGs, the JED, events, merchandise and trademark. A comprehensive leadership directory wiki will be created for a better flow of leadership communication and troubleshooting. The communications team volunteers to disburse intra team communications, and facilitate intra team conflict resolution, including the creation of a FAQ list within the wiki for that purpose.
While English is the common language in the software world, the majority of the world population does not speak English. To increase Joomla’s presence in a proactive way and recruit more non-English-speaking volunteers, the following action items will be implemented: concentrating our efforts in the different regions of the world by identifying one or two community coordinators / contact persons in each region; compiling a list of currently active local communities and JUGs and see if there are any groups which have not yet been accounted for; identifying their needs, the nature of their communities, and recruiting translation help to update the Joomla info pages.
Roadmap and Goals
This discussion first explored the benefits of creating a public unified roadmap that encompasses the entire scope of the Joomla! project. After that, the discussion continued to define a process for creating a public unified roadmap that also includes periodic public progress updates from leadership.
The process for creating a public unified roadmap involves: Leadership defines and publishes an overall mission statement for the project. This is high level and conceptual.
Each leadership team defines and publishes their team’s mission statement, which should support the project’s overall mission. Each leadership team’s mission statement may need to be revised to insure that they all tie in well with the overall project mission statement. Each leadership team defines and publishes their annual goals which support their team’s mission statement. For each leadership team’s goals, the following supporting details will be added and published: milestones (achievement and target completion date); action items (each task required to progress toward achieving the milestone; resource(s): volunteer or paid workers, financial (specify the purpose and budget line item); features (if applicable), action items (if applicable), resources (if applicable). Each leadership team publishes periodic updates during the course of the year regarding their progress on each of their goals.
Volunteer Recruitment and Rentention
The PLT discussed forming a Joomla Outreach Project (JOP), where a "bucket" of tasks is created by teams, using the wiki. Community members would be invited to join these teams, and they would work in alignment with development goals, under the guidance of the PLT. Incentives (such as T-shirts) would be awarded upon the completion of each set of tasks.
Volunteer Now is a plan for recruiting new team members, because teams should be created to manage recurring, long-term tasks that require deeper knowledge. A volunteer engagement page will be created on the wiki, and a Volunteer Now button will link to it from the joomla.org home page. In the wiki a future volunteer will find documentation on how and why we build teams, and contacts for the projects major teams and assets.
A concept will be drafted listing outreach ideas for engaging university students.
Regarding processes and messages in correspondence (for example, in areas of trademark, the JED and events), we often need more differentiation and adapted responses to specific situations.
Action items include: reviewing our texts to verify if we are using a friendly approach aimed at optimizing communication; listing and identifying situations and creating responses adapted to them; simplifying language.
Review Developer Sponsorship Program
We talked about the state of the Developer Sponsorship Program and how we handle the involvement of sponsored development time from companies and guide this process more effectively in the future. One Idea was to move from pre to post recognition and use a to-do list and let people pick from the “cookie jar” list to sponsor development time.
Action items include: speaking with the existing sponsors about their experience and writing a report; deciding if a money only approach or money and development time approach is best, finding a volunteer to manage the cookie jar.
A 1 - 2 plan of certification ideas and how to approach them will be drafted. Feedback from each leadership team will be gathered. The plan will include creating levels for web masters, designers and instructors of joomla, creating a curriculum and courses template for trainers, financial and licensing fees to create more revenue, a test database infrastructure.
Improving Recruitment of New Developers
A story we want to help tell is that Joomla can provide students with CS degrees experience on a global team that goes far beyond just a curriculum. Action items include creating a spreadsheet where we can determine which events developers are attending, and writing a one page messaging document outlining persuasive reasons why the Joomla Platform and CMS are useful for developers, and target university students.
Long Term Roadmap
We talked about the process for establishing goals and milestones for the Joomla project long term releases. Once every 6 months the PLT and developers will meet just before or after an existing event such as a Joomla Day or JandBeyond. We are hoping to do the first one this fall where milestones and goals for the July 2013 long term release will be discussed.
The entire leadership would like to thank eBay for the use of its offices for our summit, and Louis and Ron for coordinating with them. Thanks to Rochen we had tasty lunches, ordered with care by Wendy. And Gunner, our Summit Facilitator Extraordinaire kept us on target and on time!
This is a report from the Joomla Leadership Summit now underway in San Jose, CA. Members of the Community Leadership Team (CLT), Production Leadership Team (PLT) and the board of Open Source Matters (OSM) are busy discussing the best foot forward in all areas of the project.
The PLT had our summit in the days leading up to the overall Leadership Summit. We'll share shortly the results of that summit, but we wanted to get some direct feedback from the community on an issue that affects many.
We decided to make a small change to the way Joomla versions are numbered. If you have read about the new development cycle, you know we now have a new Joomla version every six months and one long-term-support (LTS) release every 18 months. Versions 1.6 and 1.7 are six-month releases and the next release in January 2012 will be an LTS release. This way, users have a choice. They can get the latest and greatest version by updating with improvements every six months, or they can have a more stable feature set with updates every 18 months. Maintenance and security releases will be done as necessary for both LTS and STS releases during their support periods.
To try to make this as clear as possible to users, we have decided that the long-term releases will always be labeled as x.5 releases. For example, 3.0 and 3.1 will be regular, short-term six-month releases. The following version would be 3.5, indicating that it is a LTS release. Version 3.5 will be supported for 18 months. In the meantime, we will release 4.0 and 4.1. The LTS replacement for 3.5 will be 4.5, 18 months later.
We would like to present two options to the community to decide how to proceed with this versioning approach.
Click on the diagram above to view a larger version.
The first option (Option #1) in the diagram is to call the January 2012 release (long-term release) 1.8. The subsequent short -term releases would be 2.0 and 2.1 (e.g. maintenance releases would be 2.0.1 or 2.1.1, etc.) and the following release would be 2.5 (using the x.5 number to identify it as a long-term release). This would be an anomaly in the versioning strategy because it would be the only version to not follow the x.5 numbering, but this version number would naturally follow 1.6 and 1.7.
The second option (Option #2) in the diagram is to call the January 2012 release (long-term release) 2.5. The subsequent short -term releases would be 3.0 and 3.1 (e.g. maintenance releases would be 3.0.1 or 3.1.1, etc.) and the following release would be 3.5 (using the x.5 number to identify it as a long-term release). This would be an anomaly in the versioning strategy because there would be no version numbers between 1.7 and 2.5, but this version number would follow the future versioning strategy (also there would be backwards compatibility with Joomla 1.5).
Vote for the option that makes the best sense here:
Since the start of the Joomla! Project we have had an Events Team. This team created the Joomla!Day Charter and helped create the first of many Joomla!Days. Over time, the Joomla!Day organizers became more professional and the help of the Events Team was not as necessary.
Without a clear description of responsibilities or concept as to what this team should or can do, activities have reached a very low level: near zero, if we try to paraphrase it a little bit.
On the other hand, we have a lot of things in terms of events to do and to optimise. With this request for help I’ll try to fill the gaps.
In March 2011 the JED hit 7000 listings. Now, half way to 8000, we are announcing a major change and improvement to the JED. It's my pleasure to introduce the JED Support System. With over a quarter million registered users in the JED, providing support is the primary use of volunteer time. In the latest blog, we outlined a few areas of improvements that we would be working on over the coming months. One of these areas was a new ticket support system. After nearly two years going back and forth between what we wanted for the teams, end users and management, we have come up with a solution that goes far beyond standard ticket support and includes a Knowledge Base, Announcement Panel, Download and Sample Repository, task calendaring, integration with Mosets Tree and ArtofUser and more!