Offering to maintain View access per node

Contacted rafuel92 on 4.10.2023

I would appreciate that. This module is currently blocking the upgrade to Drupal 10 in one of my projects.

I’ve added you as maintainer

Please add andrechun as maintainer. He offered it. I just wanted to give support to his offer.

Hello

@andrechun, @kreatIL

When can we expect a new relase for D10 compatibility?

@dimitriskr: I don't know. I was added as maintainer here by accident.

I'm going to replace vapn by permissions_by_term → in my project. So the issue (unable to update to D10) will be fixed for me within next days.

I was only given limited access and don't have permission to create a new release.

Hello,

I am a drupal.org project (and site) moderator. I chime in just to notice that, while maintainer can be used to mean person with at least a permission on a project hosted on drupal.org, in this type of offers we give to maintainer a specific meaning, as reported in Offering to become a project owner, maintainer, or co-maintainer / Terminology → .

A maintainer has full permissions on the project: make commits, edit the project node, add or remove co-maintainers/maintainers, change the permissions given to each co-maintainer/maintainer, maintain issues, and administer releases. Differently from the owner, any user with the Administer maintainers permission, or other users like drupal.org administrators or drupal.org site moderators, can make a maintainer a co-maintainer by removing one of the permissions a maintainer has.
When not differently specified, the owner is included in the list of maintainers.

With the permissions given to andrechun, he is just a co-maintainer.

A co-maintainer does not have all the permissions on the project. Usually, a co-maintainer can commit code; most often, co-maintainers are given all the permissions, except the permission to administer maintainers/co-maintainers; the exact permissions each co-maintainer has are assigned by a user with the Administer maintainers permission. (As long as a user does not have all the permissions on a project, that user is a co-maintainer for that project.)

Consider also that the permission to commit code in the drupal.org repository for the project is not sufficient for most of the activities on the projects. For example, andrechun cannot even give credits to people who helped in issues opened for the project.

I removed kreatIL from the co-maintainers, since he did not offer to be co-maintainer for this project.

@andrechun: Maybe you should move this issue to the Drupal.org project ownership issue queue

https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

On #3399693: Offering to maintain View access per node → , I explained that project maintainers can also decide to make co-maintainer a person who offered to be maintainer.
I can only point out that Offering to become a project owner, maintainer, or co-maintainer / Terminology → give the exact meaning we use for maintainer, but that is relevant if the project maintainer misunderstood the request, not if the project maintainer deliberately made the person co-maintainer (which means also giving a single permission to the person, which again could be intentional).

As a side note, the user interface for project permissions uses maintainer to mean every person with at least a permission on a project. In fact, the permission to administer co-maintainers/maintainers is Administer maintainers.

@apaderno Since I already requested to have access but only receive limited access. What would be the best way forward while the current owner is not active? Can others offer to maintain the module?

hello @andrechun, i've added you the administer releases and administer maintainers permissions

@rafuel92 Thank you! D10 compatible release is now available!

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