Written by Radek Suski
Friday, 07 March 2014 17:39
The Joomla! project is proud to announce the Joomla Event Travel Programme (JET), an initiative created to support active project volunteers and community members who have dedicated time and energy to make Joomla better, and who would like to attend larger Joomla events. The recipients of the first JET Programme recognition will have the cost of admission covered to the upcoming J and Beyond Conference on May 30 – June 1, 2014 in Königstein Germany, and will receive assistance with travel and lodging.
We invite anyone to apply who has actively contributed to Joomla through involvement in the community (by contributing code, participating in a translation team or a JUG, organising local events...) and requires financial assistance to attend the J and Beyond event.
Anyone who has contributed to the Joomla project in any way (www.joomla.org/about-joomla/contribute-to-joomla.html) during the past year is eligible to apply to the JET Programme.
Each application will be evaluated on a case-by-case basis and will be judged on its own merit. Because the number of recognitions, and the amount of money in the JET fund is limited, we will take into account criteria like the current involvement in the Joomla community (either locally or globally), the potential benefit to the Joomla project, or the overall participation in the Joomla! community.
The deadline for applications is Tuesday, April 1, 2014 and all applicants will be notified by Tuesday, April 15, 2014. Applications must be completed by the interested person at http://events.joomla.org/jet-jab-2014.
Important Note: We are seeking volunteers in the Joomla! community to become part of the JET Committee team. The selected volunteers will review the applications for J and Beyond. If you have at least three hours per week to contribute to the Joomla project in the next two months, and you are interested in joining the team, please contact us at
Written by Matthew Baylor
Monday, 03 March 2014 13:48
In August of 2013, the Joomla Extensions Directory (JED) Team put out a Request for Proposals looking for developers interested in designing a new Joomla 3.x component to manage JED listings. The JED Team also released a list of JED 3.x Requirements outlining the required functionality needed for the component.
Nine proposals were submitted and the JED Team narrowed the list down to three submissions based on scope, viability and the timeframe to complete the project. The final three candidates were interviewed by members of the JED Team who determined that Fabrikar had the best solution.
On behalf of The JED Team, we’d like to thank all of the developers who submitted proposals. I’m pleased to announce that the contract between OSM and Fabrikar has been negotiated and signed by both parties.
Development will begin starting today with a target completion date for the second quarter of 2014. After a period of testing we will begin to roll out the new system, provide thorough documentation on how to use the new JED, and replace the existing website.
You can comment on this blog post here.
Written by Tom Hutchison
Monday, 24 February 2014 14:36
I am pleased to announce the launch of our localisation project for Joomla! documentation. Using an extension designed specifically for translation of pages, our documentation can now be translated. In fact, the translation will be close to the original content of a current documentation page. Once translated, a page will be tracked and when needed, it can be updated easily if the content changes.
For a long time, our international community has desired Joomla! documentation in their native language. One of the major hurdles was deciding how and what tools to use for translating our documentation. This not only included how to translate, but how to track documentation changes while keeping the translated pages up-to-date with the original source pages. You can see an example of a translated page in our sandbox.
Besides tracking the original content of the page, if the original content ever changes, the translation can be updated easily. What is radically different from traditional translations, it will be unnecessary to translate the entire page again. Translators will only have to re-translate the section of a page with changes.
As the Documentation Working Group launches this project, please keep in mind we must be organised and use an appropriate workflow. Joomla already translates strings for the language packs available for our CMS's core with a specific workflow. Our translation of documentation will take a similar approach. Our workflow will be mainly set by the extension we are using for translations. Below is a brief summary of our documentation translation workflow.
- Our current documentation is en-GB. The English version of a page will be the source language. Simply, there must be an English version of a page for translation.
- A page must be marked (tagged) for translation. The page will automatically be sectioned into smaller translation units called 'message groups' when the page is saved. The message groups are used to track changes but more importantly, they break a page into smaller sections for translation.
- A marked page must then be approved for translation by a Translation Administrator. The role of a Translation Administrator will be to determine if a page should be translated and verify if the page’s message groups are manageable.
- Once a page is marked and approved, it can be freely translated into any language. A translator will not have to translate the entire page all at once and may work at their own speed translating a few message groups at a time. The fallback language is always the source language.
- Any user with translator permission can help translate pages and any translator will be able to review other translator’s translations. For some languages, the translator and translation reviewer may be one and the same.
- Translations are available for viewing immediately upon a successful translation save completion.
- If the source content of a page is changed, a Translation Administrator marks the changes so the translators know there have been changes. Step 5 will start again with the exception that only the changes to affected message groups need to be translated again. For example, if a page has been sectioned into 15 message groups and the changes only affect 1 message group, then only 1 message group will need to be re-translated.
For a more indepth look, please read about the Life of a Translatable Page on https://www.mediawiki.org.
Tools for Translators
There are tools built into the extension to assist volunteer translators. One of the most useful ones is machine translation to assist in preparing some text for manual translation. Most translators know machine translations are inaccurate because they lack the finite knowledge of a language, but they can be useful in helping build a text block quickly which can be manually improved by an actual human translator. Translators can choose to use this feature or completely ignore it.
Translators may sign up to be notified about new pages which need translation. These notifications can be by email, a user talk page post or both. Settings include instant notifications to a weekly or monthly digest. Translation Administrators will be able to send out these notices for page translations or re-translations to a page.
Another built-in tool allows for exporting a file of translation units or ‘message groups’ in need of translation. The exported file can be for a single page or multiple pages. Translators can then use a local translation tool such as Poedit. Once translations are complete locally, you can then import the file, review the individual changes and commit the changes. Even a partially translated file of message groups can be imported. Only changes to the message groups being imported will be processed.
There are reports to track translated page statistics, such as percentages of completion, and notifications of a page’s base language change. Actually there is a dual purpose for these percentages. A documentation reader will know a page’s percentage of translation when they view it. The viewer will also know if changes to the source language have occurred and the translation they are reading is not in sync with the source content.
A Call for Volunteers
Even though we are in the early stages of the documentation translation project, there are already volunteers interested in Spanish and Dutch translations. I hope everyone is excited and can’t wait to sign up as a translator for your language. The international community has really desired localisation of documentation, but it will take willing volunteers and the dedication of interested community members to make this project a success.
Here are some key pages to help translators understand translation of our documentation.
This is a large project and there will be decisions to make as it progresses. One thing I would like to discuss further, will there be a need to use a channel specifically for translator help and feedback. If so, what should we use? The Documentation Mail List? The #joomla irc channel? I also recently discovered a #joomla-docs irc channel, should we use this instead? Those with an interest should be able to come and go as needed.
Please provide feedback and comments on http://forum.joomla.org/viewtopic.php?f=704&t=836702
This announcement in Dutch, http://www.joomlacommunity.eu/nieuws/joomla-community/942-het-vertalen-van-joomla-documentatie.html
Written by Paul Orwig
Friday, 21 February 2014 02:59
The board of directors of Open Source Matters (OSM) is requesting public feedback from our community members through March 6, 2014, regarding a potential license change for the Joomla! Framework from the GPL to the LGPL. This potential license change would only apply to the Joomla Framework, but not to the Joomla Content Management System (CMS).
Early last year, following a previous public email list discussion, the Joomla Production Leadership Team (PLT) conducted a survey with the Joomla developer community to learn more about how they felt about potentially relicensing the Joomla Framework, but not the Joomla CMS, from GPL v2+ to LGPL v2.1+.
Here are some links to published results of that survey:
Because the survey results indicated strong support from the Joomla developer community for that potential license change, the PLT requested that OSM research legal issues regarding this potential change for the Joomla Framework:
Since that time, OSM has had multiple internal discussions about this request, and has also been in contact with the Software Freedom Law Center to receive guidance about legal issues. Discussions are still ongoing, but at this point it appears feasible from a legal standpoint to make this potential license change for the Joomla Framework.
Summary rationale and additional resources
Changing the license of the Joomla Framework to LGPL would follow the example of many other popular software frameworks, and would remove a potential barrier to increased adoption of the Joomla Framework. But the first "L" in the LGPL license stands for "lesser" (compared to the GPL license), and making this license change would also allow the Joomla Framework (but not the Joomla CMS) to be used in proprietary programs, which is not allowed by the current GPL license.
Here is a Frequently Asked Questions page regarding the GNU family of licenses (covering both the GPL and LGPL licenses):
Here is an article that summarizes some of the reasons both for and against using the LGPL license:
Next step: more community feedback
OSM recognizes that this potential license change for the Joomla Framework is an important issue, and so in addition to previous public discussions, we now want to allow two more weeks for a final period of public feedback from our community members. Please share your questions and comments about this issue through March 6, 2014 in this public forum thread:
Beginning March 7, 2014, OSM will move forward to address any remaining unanswered legal questions, and then there will be a final OSM discussion and vote on this issue. OSM will make a public announcement of the results of that vote.
Written by Victor Drover
Wednesday, 19 February 2014 13:54
Shortly after being selected to serve as Treasurer of Open Source Matters, I presented my vision for managing the financial interests of the Joomla project. This short presentation (PDF) was delivered at the 2013 Leadership Summit in November in Boston.
The main point of the presentation was to solicit feedback from all the leadership teams regarding things that were working well when it came to the project’s accounting practices, and of course things that needed improvement. The main takeaways from this part of the summit were as follows:
- The financial health of the project remains strong
- Financial reporting per leadership team is not currently possible
- The Chart of Accounts is not intuitive
- Financial status reports need simplification
To address these issues, it became clear that a complete restructure of the project’s Chart of Accounts was required. Critically, the new Chart of Accounts would need to be implemented at the same time as the 2014 budget.
This was further complicated by the timing of the Christmas holidays and the busy season that often follows.
Coincidentally, a colleague who has experience in such things recommended the Unified Chart of Accounts (UCOA) for nonprofit organizations.
After some research and conversations with our accountants, I decided this was a good choice for the Joomla project.
However, this did not solve our issues with reporting on a per-team basis.
The Joomla project uses Quickbooks as our accounting software. In addition to supporting a Chart of Accounts to organize transactions into the common financial categories (i.e. income, expenses, payables, receivables, etc…), Quickbooks “Classes” can be used to organize transactions into any categories you want. Importantly, we have full control over what those categories are.
To solve the reporting problem, I decided to use Leadership Teams as classes: CLT, PLT, OSM and INF (for Infrastructure, or expenses shared among the teams), as well as some other common classes like Events.