Offering to co-maintain Translation template extractor

Created on 28 February 2023, almost 2 years ago
Updated 14 March 2023, almost 2 years ago

Problem/Motivation

potx does not have a stable release for Drupal 8 yet and we are on Drupal 10. Of course, believe me, I totally understand how that can come to be.

It also has no releases since 2020. On the project page, these things does not look great.

The module however it working great, and we are relying heavily on it for basically all our projects. Which is why I would like to propose help with co-maintaining the module, hopefully getting it to a stable release at some point, or at least create _some_ release?

Personally I don't have any contributions to this particular project, but we have been using an early fork from before the drupal.org d8 version (https://github.com/kgaut/drupal-potx) where I have contributed several fixes, so I am familiar-ish with at least that codebase

Let me know if that is of interest ✌️Otherwise, also totally fine, and we all appreciate all of your hard work maintaining this module. Keep up the good work!

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Active

Version

1.0

Component

Miscellaneous

Created by

🇳🇴Norway eiriksm Norway

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @eiriksm
  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • 🇭🇺Hungary Gábor Hojtsy Hungary

    I worked with Lendude and others to make the project Drupal 10 compatible and released the 8.x-1.0 version. I still that satisfies the original goal of this issue but it would still be great to have active maintenance. The particular delicacy of this project is how its used behind localize.drupal.org -- specifically the Drupal 7 version. Fixes need to be made to the Drupal 7 version to be effectively happen there until the site is ported to Drupal 10 (work is underway to do that, see #localize channel on Drupal Slack). And those fixes should be kept in sync with the 8/9/10 version so that when the site is ported, the behaviour is consistent. Because the two needs to be kept in sync, we backed off from modernizing the codebase or do any significant Drupal 8/9/10-ification of the coebase, because that would make ensuring consitent behaviour harder and backports more costly.

    What do you think about this all?

  • 🇳🇴Norway eiriksm Norway

    I worked with Lendude and others to make the project Drupal 10 compatible and released the 8.x-1.0 version. I still that satisfies the original goal of this issue

    Absolutely, great work, thanks so much ❤️

    but it would still be great to have active maintenance. The particular delicacy of this project is how its used behind localize.drupal.org -- specifically the Drupal 7 version.

    I see, that's delicate indeed. I am comfortable trying to manage this delicacy, maintaining legacy things are a thing one has done 🤓

    That being said. It's just an offer to help. If you want help, I am glad to try to do just that. I am happy there is a 1.0 version, and appreciate the effort made for that 🙏

Production build 0.71.5 2024