Offering to co-maintain Flickr API Integration

This project has opted into ecurity coverage.

The procedure for Taking over unsupported (abandoned) projects says:

When opening an issue for a project that has opted into security coverage, you must explicitly say in the issue summary if you have that permission. If you aren't sure about having that permission, write that in the issue summary.

That information is missing in the issue summary.

Thanks for updating the issue summary. Apaderno has the required access level to check out your profile for permissions.

cbrody has set Git on drupal.org, but he doesn't have the vetted role. As far I can see, there aren't applications to get that role from him.

Thanks, apaderno.

This means that the site moderators can not add cbrody as a maintainer to the project before he gets permission to opt into security coverage, See Apply for permission to opt into security advisory coverage for details.

Cbrody can still be added by one of the project's present maintainers.

Those who can add maintainers are;
- https://www.drupal.org/u/dakku - and:
- https://www.drupal.org/u/lolandese

You may want to reach out to both of them by means of a PM.

Postponed until cbrody gets permission to opt into security coverage, or one of maintainers responds.

The project link is https://www.drupal.org/project/flickr_api. The sole maintainer is dakku.

I contacted dakku and sent this message.

Hello Janak,

I am contacting you because Chris (https://www.drupal.org/u/cbrody) offered to co-maintain the Flickr API Integration module, a project you created, for which you are the project owner and the sole maintainer.

May you write a comment on https://www.drupal.org/project/projectownership/issues/3219676 about accepting or declining his offer? Chris doesn't have the vetted role, which means that Drupal.org site moderators won't add him as co-maintainer. Either you accept his offer, or Chris applies to get the vetted role. In the latter case, without you declining his offer, Drupal.org site moderators could add Chris as co-maintainer, once he gets the vetted role, but not before 14 days are passed.

Best regards,
Alberto Paderno
-- Drupal.org site moderator
-- Drupal.org Git administrator

The Flickr module has switched "owner" a few times in the past but after the new maintainer has been very active in the issue queue. Infact, it had been in "seeking new maintainer" status following the Open Ownership Pledge (finding co-maintainers) | Maintainership | Drupal Wiki guide on Drupal.org.

In any case, patches that involve D9 readiness are more than welcome. For now, I do not see any issues in RTBC status.

It is suggested to provide first a list of patches written by the potential (co-)maintainer to show understanding of the module code. We will be more than happy to add co-maintainers after that happens.

lolandese,
thank you for responding, and also for taking the time to explaing what is expected from someone offering to help out maintaining the project.

There is nothing for the site moderators to do here, moving back to the project's own issue queue to be dealt with by the project's existing maintainers.

Moving to the right issue queue.

The only project linked in the issue summary was "Flickr", re this snapshot: - https://www.drupal.org/node/3219676/revisions/12338808/view

If you link to the wrong project in the issue summary, expect me to get it wrong.

Actually, the phrase in the IS was I have a requirement for this module (as a dependency of the <a href="https://www.drupal.org/project/flickr">flickr</a> project) in a Drupal 8 site. This issue was posted for a project whose name is Flickr API Integration. (See comment #2.)

Since the project owner (and sole maintainer) didn't reply, this issue still belongs to the Drupal.org project ownership queue.

Hi cbrody, thanks - I have added you

@dakku Thank you for your reply!