Offering to co-maintain CROP API

Created on 27 May 2024, 6 months ago
Updated 30 July 2024, 4 months ago

Hi,

I noticed that you were looking for a co-maintainer for the CROP-API Project.

I'm already working on a number of modules that use CROP and I'd like to be able to help continue to develop this module.

Please do not hesitate to contact me.

Sincerely

DrDam

💬 Support request
Status

Postponed

Version

2.0

Component

Miscellaneous

Created by

🇫🇷France DrDam

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

Comments & Activities

  • Issue created by @DrDam
  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    The maintainer are phenaproxima , slashrsm , and woprrr . Two of them logged in right today, and the other one logged in at least once in the past 12 months.

  • Assigned to apaderno
  • Status changed to Postponed 4 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    I contacted all the maintainers. This is the message I sent to slashrsm.

    Hello Janez,

    I am contacting you because DrDam ( https://www.drupal.org/u/drdam ) offered to become co-maintainer for Crop API ( https://www.drupal.org/project/crop ), a project you created for which you are maintainer.

    May you post a comment on https://www.drupal.org/project/projectownership/issues/3450184 💬 Offering to co-maintain CROP API Postponed 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 DrDam 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, DrDam 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 DrDam all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3450184 💬 Offering to co-maintain CROP API Postponed .

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

    The status is Postponed because we are waiting for a reply.

  • 🇸🇮Slovenia slashrsm

    I am open to adding DrDam as a co-maintainer. Can you work on a few issues in the Crop API issue queue and help move them into thh RTBC state. Get in touch with me (through d.o. contact form) after doing so and we'll continue from there.

  • 🇫🇷France DrDam

    All right, we'll proceed as it.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    @slashrsm Thank you for your reply!

  • Issue was unassigned.
  • 🇮🇹Italy apaderno Brescia, 🇮🇹
Production build 0.71.5 2024