JED Team Meeting - April 6th, 2018
By Private Profile b2c8cac3 on 2018-04-13 14:56 in Extensions Directory Team
Today the Joomla! Extensions Directory (JED) team met at 2 pm GMT via Glip to discuss our progress of current tasks.
-
In attendance: Jaz Parkyn, Anibal Sanchez, Dénes Székely, Hugh Douglas-Smith, Luca Marzo and Mark Lee.
-
Absent: Aleksander Kuczek, Daniel Dubois, Darek Śnieg (On leave), Markus Bopp, Martin Mueller, Miron Savan, Paul Franklin, Sotiris Katsaniotis and Troy Hall.
Plans for Joomla 4
- Joomla 4 Readiness Survey: We are running a survey on the JED Developers list to know more about the adoption of J4 Alpha 1. As a summary: Most people have installed J4 A1, but they didn't go further beyond the initial installation. Most people don't know that Joomla supports any web framework and that J4 will be accessible. The detailed results can be found here and here.
- A new edition of the survey will be published (for the next J4 Alpha) to the general list of users to gather more feedback and monitor the adoption process.
- As a consequence of the required changes of Joomla 4, the internal reorganization in the current Joomla 3.8 release is causing issues on extensions that rely on class names like JUser, JMail, JUri, etc. For more information about Joomla 4 and Potential backward compatibility issues.
- JED has now the checkbox for J4 compatibility, and a new menu "Compatible with J4 Alpha" has been published to feature J4 extensions.
JED 4 - New System Specification
- JED Full-Text/ Instant Search. Algolia is the new search partner of Joomla. We are already developing and testing the new Instant Search. We plan to publish it as soon as possible. The first step will implement Instant Search to gather community feedback, and the second step will replace the current search engine.
-
JED 4 Specification: JED4 spec is complete. More efforts are necessary to define the 2018 plan. At this time, we are evaluating the available resources and possible technologies for the future implementation. Volunteers will develop the JED4 in a series of sprints. We are evaluating Component Creator as the tool to prototype the next iteration. The first sprint will take place at J and Beyond 2018 (Cologne). The reviews and scoring functionality could remain a closed subject (only available to JED Team Members).
JED Homepage updates
Following the initial phase, we are working on the second stage:
- More SEO Improvements have been applied to the profile area to avoid content duplication at search engines.
- Recently Added, Top Rated, Most Viewed modules are coming, on incremental small/new changes.
- New scrolling widgets (similar to Google Play style).
The Review Checking Process
- The efforts to improve the process are ongoing. We expect further additions in the short term. We are already working on an updated review (IP Detective) checker that Hugh is setting up.
- Hugh has been working on migrating the IP Detective for the reviews over to our server. The work is nearing completion now, just a few bugs to fix. When done, we also have some new rules to put on the checker.
- There are still pending issues (Error 500 source of the problem) that need to be fixed before implementing the new service on the live platform.
Developer Collaboration Process
- Migration to Github: In January 2018, we migrated the central repository to Github.
- Issues reported in Bitbucket will remain on that platform for future reference.
- New JED Dev Collaboration: On Github, we have received two new fixes from developers:
- Fixed calculation of overall scores (#11), by Marco Beierer: It has been merged. Since it updates the scoring algorithm, it requires a full review (Hugh Douglas-Smith).
- Fixed language selector display (#15), Tony Partridge.
- Comment wrong syntax for HTML, Ciaran Walsh.
- Anibal sent several PRs (but I'm not going to detail all of them ;-))
Quality of Developer Support
- We've been discussing several complex cases to define a consistent support strategy and enforce the terms of service.
- JED newsletter: A new edition of the has been sent.
- Mining Extensions: Extensions that promote the use of (unaware) users CPU resources to mine digital coins will be banned. We are also looking closely the general industry trend to ban the whole field of crypto coins, more information, here and here.
- GPDR compliance: We are taking the steps to implement the recommendations of the project organization.