Dear maintainer,

The Events Log Track is being used on some 1200 sites at least on Drupal 8.

There are Drupal 9 compatibility issues. You can see them on the following ticket(s):
#3140447: Automated Drupal 9 compatibility fixes
#3139064: Drupal 9 readiness
#3139060: Drupal 9 Deprecated Code Report

If you unable to maintain the module to fix these issues, I'm willing to get maintain it so we release the D9 version ASAP.
If you're able to, it would be great if you can please review the patch provided in the ticket(s).

Note that we're using this module as part of the Varbase distribution. So it's of vital importance to us to get it to Drupal 9. That's why we're willing to maintain the module if you're unable to.

Thanks!

Comments

Mohammed J. Razem created an issue. See original summary.

apaderno’s picture

Title: Maintaining the module - Drupal 9 release » Offering to maintain Events Log Track
stevenlafl’s picture

I have written this entire module to be much much better at logging (with more ways to store them), reporting (the UI actually works properly now), way more comprehensive (including individual field changes, files and other specific logging), and to be able to support the needs of federal organizations. It is either maintain this module (and patch the active security vulnerability) or create a new one at this point. I'm ready to release version 2. Read your emails!!

kumaratulesh’s picture

Hi Steven,

I will release this updated module soon.

Mohammed J. Razem’s picture

@stevenlafl if you’ve already written a better, more secure, and comprehensive version, I highly recommend to create a new module for that.

As this module has not been updated for more 3 years now, and the maintainer’s (kumaratulesh) response was not quite assuring or detailed to address any of the issues raised.

Mohammed J. Razem’s picture

@kumaratulesh can you please update us on when you can look into the issue queue?

Again, I'm offering my help here to review patches help in a stabler module.

kumaratulesh’s picture

@Mohammed J. Razem Thanks for your patience and support.

I have updated the modules after testing will release the new module by today or tomorrow.

@Steven: If you have any code update suggestion then please share with me I will update those also here. Please don't create new module for same it will create confusion for the end user.

I am also working on UI part and will update soon.

Mohammed J. Razem’s picture

@kumaratulesh thanks for the update - however it seems you marked the previous version as unsupported.
And there's still no release for the new version.

This means all the 1200+ websites using the module will receive a security warning of unsupported module version!
Are you planning to release the 2.x version soon?

kumaratulesh’s picture

@Mohammed J. Razem: Thanks for your patience, I have released a new version of this module.

@Steven and @Mohammed J. Razem: I am open for your suggestions.

Mohammed J. Razem’s picture

@kiamlaluno

  • The new release still has no D9 support. I thought a new branch (2.x) would bring in D9 support, hence why this issue to offer maintenance help was opened.
  • The old release (which 1200+ sites are using) is marked as unsupported now which causes a security warning for these sites.
  • None of the issues that you included in the release notes have been updated or reviewed. It makes it hard to track what has been actually fixed here.
kumaratulesh’s picture

@Mohammed J. Razem: In Release notes I have putted all the links of patch which was reviewed by the community. I have also updated the code for D9 support but after testing I will release soon.

apaderno’s picture

@Mohammed J. Razem Issues offering to maintain a project needs to contain the project name and follow the Offering to maintain [project name]. The fact you are offering to maintain the Drupal 9 version can be stated in the IS.

Mohammed J. Razem’s picture

Status: Active » Closed (won't fix)

@kiamlaluno I did offer to maintain the module as a whole (the D8 and D9 versions).

I'm still interested to do so, but @kumaratulesh has already moved forward with the release. Although he did not acknowledge any of our maintainership requests (whether by saying yes or no).

However, I'm now left with no choice but to fork this module where we can maintain a fork but with a clearer roadmap.

This is mainly because:

  1. The approach of the release affected us badly by marking the 8.x-1.x version as unsupported without prior communication. We're now left with some 900 websites built on Varbase (which enabled this module by default) showing a security warning of unsupported module. I'm sure similar feedback would arrive soon from GovCMS8 team.
  2. The release notes of the new version (8.x-2.x) did include what got fixed, but none of the issues were actually updated and/or closed. Patches were manually applied in a single commit! Instead of utilizing Drupal's credit system and standardized commit messages, and responding to the issue creators. This made it hard on us to track what was actually fixed and committed.

Therefore, my highest gratitude and appreciation to the module maintainer @kumaratulesh - I do understand that we're not made of time to maintain these open source components - but we were expecting better communication on the issue queue (and emails sent via the contact form) and the new release of the module.

I will go ahead and create a fork of this module.

apaderno’s picture

@Mohammed J. Razem I am sorry the cooperation tentative didn't work well.

elgandoz’s picture

@Mohammed J. Razem, do you intend to publish your fork?
This module to the day is not compatible with D9 and the lack of communication and collaboration unsettles me. This is one of the few projects that is currently holding the upgrade of our build.
I would be very interested in a new project with improved functionality.
Edit: Found it! Admin audit trail