Offering to co-maintain RobotsTxt

Created on 25 July 2024, about 1 year ago
Updated 27 August 2024, 11 months ago

We depend on RobotsTxt module for flexible robots.txt management on websites. There has not been much activity in this module and the last stable release was in 2022. I would like to get it compatible with Drupal 11 and help fix some of the open issues on this module so upgrades beyond Drupal 10 can happen smoothly.

📌 Task
Status

Fixed

Version

1.0

Component

Co-maintaining offer

Created by

🇺🇸United States kevinquillen

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

Comments & Activities

  • Issue created by @kevinquillen
  • Assigned to apaderno
  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • Status changed to Postponed 12 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    The following are the people who have the Administer maintainers permission and who must be contacted.

    David Strauss
    ccjjmartin
    generalredneck
    Todd Nienkerk

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    This is the message I sent to David Straus, the project owner.

    Hello David,

    I am contacting you because Kevin ( https://www.drupal.org/u/kevinquillen ) offered to become co-maintainer for RobotsTxt ( https://www.drupal.org/project/robotstxt ), a project for which you are project owner and maintainer.

    May you post a comment on https://www.drupal.org/project/projectownership/issues/3463806 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
    In the case you accept the offer, you can also add Kevin as co-maintainer, but this is not necessary, as project moderators can add co-maintainers/maintainers to any project.
    Without a comment posted on that issue in the next 14 days, Kevin will be probably made co-maintainer.

    Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

    I am contacting all the people who can administer co-maintainers/maintainers for the project.

    As last note: This offer is about being co-maintainer, which for us means somebody who does not have all the drupal.org permissions on the project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
    If there is any reason for not giving Kevin all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3463806 .

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

    I am still contacting the other maintainers.

    The status has been changed because we are waiting for a reply.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    This is the last message I sent.

    Hello Todd,

    I am contacting you because Kevin ( https://www.drupal.org/u/kevinquillen ) offered to become co-maintainer for RobotsTxt ( https://www.drupal.org/project/robotstxt ), a project for which you are maintainer.

    May you post a comment on https://www.drupal.org/project/projectownership/issues/3463806 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
    In the case you accept the offer, you can also add Kevin as co-maintainer, but this is not necessary, as project moderators can add co-maintainers/maintainers to any project.
    Without a comment posted on that issue in the next 14 days, Kevin will be probably made co-maintainer.

    Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

    I am contacting all the people who can administer co-maintainers/maintainers for the project.

    As last note: This offer is about being co-maintainer, which for us means somebody who does not have all the drupal.org permissions on the project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
    If there is any reason for not giving Kevin all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3463806 .

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

  • 🇺🇸United States david strauss San Francisco, CA

    I support adding Kevin as a maintainer. He has a credible history with the Drupal project and the relevant expertise to maintain this module.

  • 🇺🇸United States generalredneck Texas, USA 🇺🇸

    Sounds good. Never got anything from Kevin via contact form that I can find. Otherwise i would have done the same. Need to double check my notification settings on that issue queue cause I didn't see an email come through for the issue created

  • Status changed to Fixed 12 months ago
  • 🇺🇸United States generalredneck Texas, USA 🇺🇸

    In the words of HeMan

    You have the power!

  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • 🇺🇸United States kevinquillen

    Thanks so much!

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024