Problem/Motivation

I would like to become a co-maintainer of the view_unpublished module to merge the Drupal 10 compatibility patch along with any appropriate RTBC issues and create a D10-compatible release.

I have contributed in the D10 compatibility issue (#3299433: Automated Drupal 10 compatibility fixes for view_unpublished) and would like to contribute more to the module in the future.

I have created the issue #3345720: Offering to co-maintain view_unpublished in the project's issue queue and contacted two maintainers of the module 15 days ago. There is no response after 2 weeks, so moving this over to the project owner queue.

Proposed resolution

Add me as co-maintainer with appropriate permissions to merge code, manage issues, and create releases.

Remaining tasks

Add Fathima Asmat as co-maintainer of view_unpublished.

Comments

fathima.asmat created an issue. See original summary.

fathima.asmat’s picture

avpaderno’s picture

Title: Offering to c-maintain the module » Offering to co-maintain view_unpublished
fathima.asmat’s picture

Contacted one of the maintainers, Agnes Chisholm (https://www.drupal.org/u/amaria) on 14/03/2022.

xem8vfdh’s picture

Thanks for stepping up @fathima.asmat!

Have the maintainers been in contact or no responses? I messaged all of the registered maintainers about merging the Drupal 10 issue and haven't had any responses.

avpaderno’s picture

Assigned: Unassigned » avpaderno
Status: Active » Postponed

Only entendu can add co-maintainers. The other users are co-maintainers without the permission to administer co-maintainers/maintainers.
I am going to contact the project owner in a few moments.

avpaderno’s picture

This is the message I sent.

Hello Domenic,

I am contacting you because fathima.asmat (https://www.drupal.org/u/fathimaasmat) offered to co-maintain view_unpublished (https://www.drupal.org/project/view_unpublished), a project for which you are project owner and maintainer.

Ma you post a comment on https://www.drupal.org/project/view_unpublished/issues/3345720 about accepting or declining the offer? Without a publicly visible comment posted in that issue in the next 14 days, fathima.asmat 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.

I am contacting all the users with the explicit permission to administer co-maintainers/maintainers for that project. In this case, that is only you.

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

I changed the status because we are waiting for a reply.

xem8vfdh’s picture

thanks @apaderno. Is the someone in the drupal core community we can appeal t if we don't get a timely response who can add a new co-maintainer?

@fathima.asmat, it would be nice to hear from you as well to see if you are still interested and available.

avpaderno’s picture

thanks @apaderno. Is the someone in the drupal core community we can appeal t if we don't get a timely response who can add a new co-maintainer?

I contacted entendu and I will add fathima.asmat as co-maintainer, in the case entendu does not reply here in the next 14 days. That is the task project moderators have.

xem8vfdh’s picture

thanks a lot @apaderno!

Hopefully @fathima.asmat is still around. Have you had recent communication with that user?

avpaderno’s picture

@xeM8VfDh Not with fathima.asmat, but she commented on this issue three days ago, which means she is still interested in this.

fathima.asmat’s picture

Hi everyone,

Sorry for the slightly later response as the last few days were quite hectic. Of course, I'm still interested in co-maintaining the module. It has been three days since I contacted Agnes. I'll send a message to the core maintainer as you both suggest :) Thanks for all your support +1

fathima.asmat’s picture

Just an updated to convey that I just sent a message to Domenic regarding the offer on 17/03/2023.

fathima.asmat’s picture

Why is the issue status marked to be 'postponed'? Shouldn't it be active as it's still an active issue at-least until the 14 days?

xem8vfdh’s picture

glad to see you're still on board @fathima.asmat! Hopefully after the 14 day grace period we will be all set for you to take over the merge :)

fathima.asmat’s picture

I believe we have hit 14 days since we contacted the maintainers and @apaderno can add me as a co-maintainer?

kristen pol’s picture

Project: View Unpublished » View unpublished content
Version: 8.x-1.x-dev »

@fathima.asmat If you are still interested, then you can move this issue into the Drupal.org project ownership issue queue after 14 days. Thanks.

kristen pol’s picture

Project: View unpublished content » View Unpublished
Version: » 8.x-1.x-dev

Whoops. Didn't mean to switch the project... was searching in there ;)

fathima.asmat’s picture

Thanks Kristen. Moved the issue to the project ownership queue, https://www.drupal.org/project/projectownership/issues/3351646.

ressa’s picture

Project: View Unpublished » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Miscellaneous » Co-maintaining offer

Thanks for your generous offer to help maintain the module @fathima.asmat. Perhaps it's better to move this issue to the "Drupal.org project ownership" project, and close the new issue #3351646: Offering to co-maintain view_unpublished to maintain continuity?

ressa’s picture

Issue summary: View changes

Updated Issue Summary with sentence from #3351646: Offering to co-maintain view_unpublished.

ressa’s picture

Issue summary: View changes

Add module name and link in IS.

gisle’s picture

Project: Drupal.org project ownership » View Unpublished
Version: » 8.x-1.x-dev
Component: Co-maintaining offer » Miscellaneous

There is no point in moving this issue to the Drupal.org project ownership issue queue.

The project view_unpublished is opted in to security coverage, and fathima.asmat does not have permission to opt in to security coverage. No site moderator can add fathima.asmat as co-maintainer. Moving this issue back to the project's own issue queue

For background, please see please see How site moderators handle requests to be project owner, maintainer, or co-maintainer.

fathima.asmat’s picture

I’m not sure of the next steps here and I have checked this in #d10readiness Drupal slack channel. Berdir suggested that I partner up with someone who has permissions to progress this as an alternative way forward. Would anyone who has already commmeted on this issue with enough permissions be interested in partnering up to progress this further please?

gisle’s picture

As for next steps, there are three routes open to you:

  1. Keep trying to get the attention of the project's owner (entendu). However, there is a long time since he was active in the community, and he's not been responsive so far.
  2. You can apply Apply for permission to opt into security advisory coverage. Once you have this permission, you can move the issue to the Drupal.org project ownership issue queue and ask the site moderators to add you.
  3. You can, as suggested by Berdir, partner up with someone who has this permission. You can check whether someone has this permission by looking at their user profile. On those with this permission, there is a checkmark and the text "Can opt projects into security advisory coverage".
fathima.asmat’s picture

Thanks @gisle.

1. There has been no activity from the existing maintainers with the module in the last two years so I don’t think there is likely any chance for them to push this forward :(

2. I found the guide, but I can't see anything there on how to get that without having my own module. I don't have my own module unfortunately and I'm a budding contributor

3. I have asked in the #d10readiness channel if anyone is up for partnering up

tobiasb’s picture

\o I can help. ;-) Such a small module (LOC) and so many installation :D

gisle’s picture

tobiasb, great! You have the necessary permission, and can be added by a site moderator if the project owner has abandoned the project (which seems to be the case).

The exact process is described on this page: How to become project owner, maintainer, or co-maintainer. Make sure you follow it. Any deviation will cause delays.

To get the process started, open up a new issue in the project's issue queue where you spell out what you offer to do. For example, you may use this title for the issue: "Offering to maintain view_unpublished".

I suggest you offer to take over ownership. If the present owner is not around any more, the project is better off with a new owner.

You need to open a new issue, please see this note on the page linked above.

The site moderators will only consider the offer from one person per issue. Please do not use an issue created by another user, even if that issue has not been completed for some reason; instead, open your own issue.

xem8vfdh’s picture

thanks everyone!

klemendev’s picture

Any updates on this?

tobiasb’s picture

@KlemenDEV

A new maintainer/owner needs to be opted in to security coverage. therefore I will help and created also a request #3351691: Offering to maintain view_unpublished to fill the role.

tobiasb’s picture

Assigned: avpaderno » Unassigned
Status: Postponed » Fixed

@fathima.asmat

Lets the play begin. You can now commit to the repo. ;-)

xem8vfdh’s picture

thanks @tobiasb and @fathima.asmat 🥳

kristen pol’s picture

Thanks everyone!

tobiasb’s picture

Status: Fixed » Closed (fixed)

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