Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.In the 'Maintainers' tab of a project, I can assign anyone that has a Drupal.org account to a maintainer of my project, regardless if they have agreed to the Git agreement on their user profiles or not. This actually caused confusion in real life due to similar names: #2033397: Offering to co-maintain Views Slideshow JCarousel Thumbs that wouldn't have happened since the errant user should have never been visible in the list.
| Comment | File | Size | Author |
|---|---|---|---|
| Selection_060.png | 49.61 KB | Dave Reid |
Comments
Comment #1
Dave ReidNoted in IRC that the user could be assigned not the 'Write VCS' checkbox, but if that checkbox *is* checked, then it should fail validation.
I'm not sure if this should be filed against project, or drupalorg.
Comment #2
drummThis is either a project or versioncontrol issue. Project module should have a way to disable unavailable checkboxes. And versioncontrol should do what is needed to use that.
Comment #3
kreynen CreditAttribution: kreynen at University of Colorado Boulder commentedI believe this was resolved in a different way from any of the suggestions. I recently added jeor0980 to https://www.drupal.org/project/google_cse, but when he tried to visit https://www.drupal.org/project/google_cse/git-instructions he was told something like "git account not configured" with a link to configure it.
So while I was still able to add him as a maintainer, there wasn't any confusion about why he couldn't create a branch. Since this is 4+ years old, I'm just going to move it to fixed.