Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By smartsystems160 on
I think it would be a nice addition to ask developers to indicate if they plan to port their modules to the next version of drupal, maybe a mandatory check button or textfield where they can indicate so. The importance of this is that users get to know the implications of using certain modules which may hamper their chances of easily migrating to the next version of drupal (lets say drupal 6.x to 7.x). Also, developers get to know ahead of time if they can start developing for the next version of drupal, for modules which will not be ported.
Here are some insights on this:
1. Some users pay developers to build custom modules for them, then port to the community. In this case, the developer may not have interest in further developing this module except they are paid to do so
2. Some developers also develop modules for their personal projects, with no plans on further development. It would be fair to users to know that the module in question "does not have upgrade plans, so please use at your own decision"
3. Some website managers are stuck with unsupported or near unsupported versions of drupal core because they are probably running low budget websites and simply cant replicate functionality if they upgrade their websites, due to unsupported modules
Comments
_
honestly, I don't see this as a value add at all. Most every module developer has the best of intentions and will likely check the box. That in no way will influence whether or not the module will actually be upgraded in a timely manner. As with any purely volunteer effort, things get in the way. That's just a fact of life.
imo it's far more valuable to judge a module's viability with facts as opposed to good intentions. How many reported downloads are there? How much reported site usage? How active is/are the maintainer(s)? How active is the issue queue? What is the commit history like? These are all things that can be judged for oneself right from the project page and far more indicative of a good viable module.
I know I'd check the box, but
I know I'd check the box, but it may take me a year or more to actually get to upgrading all my modules. I'm trying to catch up my modules that I have already just to bring them more in line with Drupal 7 APIs, as I've learned a lot since I first upgraded them to Drupal 7. I've started with the most well-used ones, and am trying to work my way through the list.