Offering to co-maintain Translate Drupal with GTranslate

Created on 2 November 2023, about 1 year ago
Updated 17 November 2023, about 1 year ago

Problem/Motivation

For the purpose of providing the stable upgrade path from 1.x to 3.x and bug fixes in the Translate Drupal with GTranslate module. I volunteer to be a co-maintainer for this module. I have permissions to opt-in to security coverage. I have experience maintaining several other modules as well. https://www.drupal.org/u/naveenvalecha

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Closed: won't fix

Version

2.0

Component

Co-maintaining offer

Created by

🇮🇳India naveenvalecha New Delhi

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

Comments & Activities

  • Issue created by @naveenvalecha
  • 🇮🇳India naveenvalecha New Delhi

    I have contacted the maintainer edo888 from contact tab from their user profile.

  • Assigned to apaderno
  • Status changed to Postponed about 1 year ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    I contacted edo888 using the following message.

    Hello Edvard,

    I am contacting you because Naveen ( https://www.drupal.org/u/naveenvalecha ) offered to co-maintain Translate Drupal with GTranslate ( https://www.drupal.org/project/gtranslate ), a project for which you are project owner and sole maintainer.

    May you post a comment on https://www.drupal.org/project/projectownership/issues/3398678 about accepting or declining the offer? Without a comment posted in that issue in the next 14 days, Naveen will be probably added as co-maintainer (with all the permissions on the project, except the permission to administer maintainers/co-maintainers).
    None of the current maintainers/co-maintainers will be removed by site moderators. Co-maintainers cannot change the project owner nor the maintainers.

    I am contacting all people with the explicit permission to administer co-maintainers/maintainers for that project. In this case, that is just you.

    Best regards,
    Alberto Paderno
    -- Drupal.org site moderator
    -- Drupal.org project moderator

    I changed the status, since we are waiting for a reply.

  • 🇦🇲Armenia edo888

    Hi,

    I do not accept co-mainterners.

    @apaderno I do not like your policy about accepting offers when there is no response.

    Thanks!

  • 🇳🇴Norway gisle Norway

    The policy that is expressed in the message from @apaderno is long established at Drupal.org and is described here: How to become project owner, maintainer, or co-maintainer . More specifically, see steps 5 and 6 in the procedure described. If you don't like it, you can try to get it changed.

    My personal opinion is that if site moderators were not allowed to add new maintainers when project owners are totally unresponsive to posts the project's issue queue and to personal messages, the Drupal ecosystem would rapidly become a garbage dump made up of a mix of abandoned modules and wild forks.

    There are too many abandoned modules in the Drupal ecosystem already, but that is because nobody offers to take over when an owner goes somewhere else without arranging a orderly succession.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    As gisle made already clear, that is not my policy; it is a policy that exists from more than 14 years, even before I became site moderator.

    That policy is pretty clear: If a project maintainer does not notice the issue on the project issue, which is kept there for 14 days and shows the project name in its title, nor does the project maintainer notice the contact message sent by a site moderator, then site moderators proceed with adding the person who offered to be co-maintainer/maintainer as co-maintainer/maintainer.
    It is even what I reported in the contact message I sent; I did not omit that detail.

  • Status changed to Active about 1 year ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • Status changed to Closed: won't fix about 1 year ago
  • 🇮🇳India naveenvalecha New Delhi

    @edo888
    Thanks for the feedback. I'm marking this as "Closed(Won't fix)". Looking forward to hear your feedback on the issues in the issue queue.

Production build 0.71.5 2024