Problem/Motivation

I'm happy to help co-maintain this project. Mainly to get it ready for the jump to Drupal 10. I can't promise to help much beside that, but for that, I'm definitely happy to give a hand.

This is linked to the great work that Kristen Pol is organizing over in #3342443: META: Adopt contributed projects for Drupal 10 readiness.

Steps to reproduce

Reference: https://www.drupal.org/project/tmgmt_crowdin

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#13 2303_29233939.png28.86 KBavpaderno

Comments

heddn created an issue. See original summary.

heddn’s picture

heddn
Primary language English
Location Illinois
commented

A PM linked to this request was sent to the maintainers also today.

heddn’s picture

heddn
Primary language English
Location Illinois
commented
Project: Crowdin Translation Plugin » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Miscellaneous » Co-maintaining offer
Issue summary: View changes
Status: Active » Needs review

During the original opening of this request on Feb 24, I sent PMs directly to project maintainers CrowdinTeam and volodymyr.kyshenia. There is no response after 2 weeks at this point, so moving this over to the project owner queue.

Hi there, I've opened
https://www.drupal.org/project/tmgmt_crowdin/issues/3344300 asking to
add me as a co-maintainer. This is part of a larger effort to get some of the
more popular Drupal modules upgraded to support Drupal 10. I can't promise
I'll be around much beyond the Drupal 10 upgrade, but you never know either.
Thanks for all the great work you started with this module. It is a very
helpful module for Drupal ecosystem.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Category: Support request » Task
Status: Needs review » Postponed

I contacted Beytok.

Hello Vitalii,

I am contacting you because Lucas (https://www.drupal.org/u/heddn) offered to co-maintain Crowdin Translation Plugin (https://www.drupal.org/project/tmgmt_crowdin), a project for which you are maintainer.

Ma you post a comment on https://www.drupal.org/project/projectownership/issues/3344300 about accepting or declining the offer? Without a publicly visible comment posted in that issue in the next 14 days, Lucas will be probably made co-maintainer (user with all the permissions on the project, except the permission to administer co-maintainers/maintainers).
None of the current co-maintainers/maintainers will be removed from site moderators, nor will the project owner be changed. A co-maintainer cannot remove the existing co-maintainers/maintainers nor change the project owner.

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

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
beytok’s picture

beytok commented

Hi,

Thank you so much Lucas for your interest to Drupal plugin in Crowdin. We are happy to see you here and your help is much appreciated! We added you to this project and you have Maintain issues access now.

Thank you so much for making Crowdin better.

P.S. Thank you Alberto for reminder :)

Have a productive day!

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Postponed » Fixed
heddn’s picture

heddn
Primary language English
Location Illinois
commented
Status: Fixed » Needs work

Managing tickets doesn't give access to commit the D10 patch in #3329498: Automated Drupal 10 compatibility fixes. That was my hope in opening this request. If someone would just commit that code, I don't really even need to maintain this project. And I would still count this as a win for the larger community. Moving back to NW (that feels like the right status) to see if we can reconsider the level of access.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Usually, users who offer to become co-maintainers at least want to be able to commit code. Being able to assign issues to themselves or credit users is the least reason for being co-maintainers.

I know, users who have only the permission to maintain issues are still co-maintainers, but if users do not expressly ask to get only specific permissions, they are willing to get more permissions. That is why the message sent from site moderators describes co-maintainer as a user with all the permissions on the project except the permission to administer co-maintainers/maintainers.

heddn’s picture

heddn
Primary language English
Location Illinois
commented

So, what happens in a week when the 2 week time period passes? Is this in some sort of limbo now? I'm confused with the process as it currently stands.

heddn’s picture

heddn
Primary language English
Location Illinois
commented

2 weeks ago it was stated that I could be the co-maintainer. But that access wasn't granted. What are the next steps now?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
StatusFileSize
new 2303_29233939.png28.86 KB

@heddn Your current permissions are: Write to CVS, Edit project, and Maintain issues.

screenshot

I was waiting for a comment on this issue, but apparently your permissions have been changed without a comment.

heddn’s picture

heddn
Primary language English
Location Illinois
commented
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

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