Offering to co-maintain Multiple Node Menu

It would be great, this is a very necessary module, both for multilanguage and reusing the same node in several links in the menu would make things much easier because the only way for now is to do everything manually

Since this project is covered by the security advisory policy, site moderators will not add as maintainers/co-maintainers people who cannot opt projects into security advisory policy. Moving this issue to the Drupal.org project ownership queue will have the get this offer back to this queue.

apaderno, is there a reason that this should not move forwards?

AstonVictor, are you still interested in being added to the team?

yep, I'm ready to maintain the module

@gisle We hope this module is updated soon, because this solves a problem that Drupal has with multiple nodes in the menu

Yes, I am planning to spend some time on processing this.

However, the procedure for being added to the project's team as a maintainer is described here → .

For instance, it says that when opening an issue, it is useful to contact the current project owner via the contact tab on their Drupal.org user profile page (and/or other means of contact that exists) to let them know about the issue you posted regarding maintainership, and to add the details (who, means of contact and when) to the issue summary.

This has not been done in this case (and the other issues about project ownership that has been opened by AstonVictor). I am planning to repair this by sending PMs to all members of the project's team to get the process restarted. A site moderator have to wait at least two week after sending the PMs before overriding the team's prerogative of managing the team themselves.

However, I am quite busy and it may take a few days before I shall be able to find the time to do this.

AstonVictor,
thank you for offering to help out co-maintaining this!

However, the present team must first get a change to respond to your offer. I've sent those that are contactable (recidive. nehajyoti and PeteS) a PM asking for them to comment here:

Co-maintainer-offer for Multiple Node Menu

Hi, I am a site moderator at Drupal.org.
A co-maintainer-offer for Multiple Node Menu has been posted.
Please see:
https://www.drupal.org/project/projectownership/issues/3414723 💬 Offering to co-maintain Multiple Node Menu Active
and respond.

You may reject or accept the offer, but a public response will be appreciated.

If there is no response, AstonVictor will be added as a co-maintainer by the site moderators.

For the maintainership offer process, please see: https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

Postponing for now. Please set back to “Active” if there is no response in 14 days.

@aslonVictor , @gisle

I am still interested to maintain the module full time. Is it possible for @asonVictor to create sepeate issues for the issues mentioned in the description. I would commit and release the the stable & latest version of the module.

The issue summary just says "I want to create a stable release for Drupal 10 and fix all open issues", so there are no need for @AstonVictor to create new issues. Those he wants to fix are already in the issue queue, ready to be worked on.

There are 8 open issues in the "Any 8.x-*" version, broken down to the following statuses:

• 2 RTBC
• 2 Needs review
• 4 Active

It does not appear that @AstonVictor has not engaged in any of those issues (so far). Since there is an active maintainer around, the site moderators can not add @AstonVictor as a maintainer. I am moving this back to the project's own issue queue to be processed by the current team (to add him, or to close out this issue).

The best way forward would be for @AstonVictor to triage or otherwise work on these open issues, and for the current team to commit and release them. Please make sure that proper credit is given.

PS: Currently the project only has an alpha-release that is not compatible with Drupal 10, the default branch in gitlab is "master", and there appears to be lots of outdated issues still open. IMHO, this project could do with some TLC. If you don't have the time to fix this yourself, adding another co-maintainer to the team is well worth a consideration.

Hi @nehajyoti,

thanks for your reply.
If you are still working on the module It will be great. I hope you'll post a new release soon.

in that case, I'm going to close the current issue