JED Team Meeting - November 29th, 2019
The Joomla! Extensions Directory (JED) team met on November 29th, 2019, at 4 pm GMT, via Glip to discuss our progress of current tasks.
In attendance: Anibal Sanchez, Jaz Parkyn, Mark Lee, and Troy Hall.
Absent: Hugh Douglas-Smith. Around the channel: Dénes Székely, Daniel Dubois and Luca Marzo.
- New Members: Carlos Cámara and Tony Partridge.
Plans for 2019 - 2020
- Joomla 4 Beta is planned to be released soon. We are updating our plans accordingly: New extensions guidelines for J4 and JED Checker CI for Joomla 4 (see below).
- New Ticketing System: the implementation is almost complete. We are operating the new system, improving the implementation, and in the way to deactivate the old system (once all tickets are solved).
- Ticket system usernames: Since the team is answering all tickets without assigning them to a single user, we are changing our usernames to the role: "Team Member" and "Team Leadership".
- Process Reorganization: In the past, we defined that we answered tickets and closed them at once. It was almost impossible to keep a conversation going in the system. Now, in the new Ticketing System, we answer the tickets, and they remain answered waiting for user feedback. Once it is solved, the system auto-closes them after a period of time (7 days). There is also a satisfaction survey.
Now, we could define what tickets deserve a prompt action and what tickets can wait for the developer response. We are creating a new state "Waiting for Developer Answer", to avoid unpublishing extensions while we wait for the developer response (For instance, Broken links).
- Call for Support Specialist, Review Specialist: We'll publish a call to increase our team, ahead of Joomla 4 release.
- Templates on JED: At this time, the topic of publishing Templates on JED has come up again. The aim of the current JED Team is supporting all types of Joomla extensions on the directory. Since the previous effort to create a Template Directory for Joomla (JTD) is inactive (OSM, Inc. - Full Board Meeting - October 18, 2018), and the time of new ideas around Joomla 4 campaign has arrived, we are going to prepare a proposal for the board. Technically speaking, JED already has everything to add a new category for templates (in fact, we process and check template submissions today, and reject them due to not being allowed). We are also going to gather information from the previous JTD experience and checking the idea with other community members. At this time, the licensing of Templates on JED would follow a GPL / Creative Commons license model.
- About Templates on JED - GPL / Creative Commons (CC) licenses: CC Licenses are free of charge to the public. These licenses allow creators to communicate which rights they reserve and which rights they waive for the benefit of recipients or other creators. An easy-to-understand one-page explanation of rights, with associated visual symbols, explains the specifics of each Creative Commons license. Creative Commons licenses do not replace copyright but are based upon it. They replace individual negotiations for specific rights between copyright owner (licensor) and licensee, which are necessary under an "all rights reserved" copyright management, with a "some rights reserved" management employing standardized licenses for re-use cases where no commercial compensation is sought by the copyright owner. The result is an agile, low-overhead and low-cost copyright-management regime, benefiting both copyright owners and licensees. For more info: https://en.wikipedia.org/wiki/Creative_Commons, https://creativecommons.org/, and Comparison of free and open-source software licenses.
- Account / Delete account implementation is pending.
- JED Checker CI Online. This is project scope: https://github.com/joomla/jed-issues/wiki/Extensions-Checker. Based on PHPCS WIP PR 246 / SonarQube.
- JED Design Updates
- Recently Added, Top Rated, Most Viewed modules
- New scrolling widgets (similar to Google Play Store style)
- JED4 (2019 Q4 - 2020)
- GDPR Part2
- We are processing the queue of new extensions and pending tickets within the seven days processing window. In the meeting, we have discussed several severe cases and reports.
- We have delayed tickets on the Review Reports queue. We are taking action to solve the delay.
- Two new members are joining the team: Carlos Cámara and Tony Partridge.
New support for Cloud Services and SaaS extensions
This month, we published a new guideline, we introduced the specific support of Cloud Services and SaaS extensions. For more info: https://extensions.joomla.org/blog/item/new-support-for-cloud-services-and-saas-extensions/
Spam Checks for Reviews
The current system to process Spam Review needs to be revamped. The current implementation has several shortcomings that must be addressed.
In the short term, to clarify the validation output, we are improving the messages shown to the user. Spam Checkup can fail due to the following points:
In the medium term, we are planning to redefine the system and implement a new checkup in the context of the JED4 project. We are updating the progress in the implementation here: https://github.com/joomla/jed-issues/issues/85
JED 4 Project
- JED4 development has been continuing. To contribute to the project: https://extensions.joomla.org/support/knowledgebase/item/contributing-code-to-the-jed/
- The board approved the proposal to make the new JED 4 codebase and project information available publicly.
- The Review Detective and Review Scores will be kept private within the JED team.
- This is the JED 4 Project Scope Summary. To simplify the project coordination, we have the JED - Developer Chat room in Glip for developers to work on JED4. Please, join the JED Dev Chat on Glip to discuss the scope and access the rest of the materials we are working on.
Proposed JED Guidelines for Joomla 4
- Minimum technical requirements: We have been discussing the steps to manage extensions for Joomla 3 and Joomla 4 after Joomla 4 is released, to keep compatibility with minimum technical requirements for Joomla 3 and encourage the usage of PHP latest stable version and security practices.
- Override Everything: All assets should go through HTML helper or web assets. In this way, the assets are overridable, and scripts can be put in the footer and still work. Restrict handwritten script tags in the output (This needs to go through addScriptDeclaration). Include assets ONLY in the layouts, not in the main logic.
General Data Protection Regulation (GDPR)
- We are collaborating with the implementation of the process and coordinating tasks with the Joomla GDPR/Compliance Team.