Node.js integration has been automatically opened to new maintainer applications, as it has releases for Drupal 8 which will be marked unsupported on 2 Nov, 2021, but no release yet for Drupal 9. Your Drupal 7 releases will not be affected.

This is an adaptation of our existing process for transferring project maintainership.

After the standard 14-day waiting period from this issue being opened, and if an existing maintainer has not closed it, this project becomes eligible for new maintainers. Those new maintainers will not need to wait for existing maintainer approval.

Next steps:

  • An existing maintainer may close this issue and opt out of this accelerated process.
  • A prospective new maintainer can take this issue after the 14 day window has elapsed and take the following steps to be added as a maintainer:
    • Comment here explaining why you would like to maintain the module.
    • If the project is opted in to security coverage, confirm that you have previously received security coverage opt-in permission.
    • If an existing maintainer has not commented, move the issue to the Drupal.org Project Ownership queue, by editing the “Project” field on this issue.
  • The Drupal.org site moderators will review the issue, and if it meets the requirements can grant you maintainer access.

Issue fork nodejs-3237094

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

System Message created an issue. See original summary.

jvanja’s picture

jvanja commented
Title: nodejs project open to new maintainer applications on 5 Oct, 2021 » Node.js appears to be unsupported.
Project: Node.js integration » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Miscellaneous » Abandoned/unsupported projects
Issue summary: View changes
le72’s picture

le72
Location Yerevan 🇦🇲
commented
Issue summary: View changes

Hi, flagging here as ready to maintain this project.
We use it in a couple of projects and the minimum TODO is to apply all patches submitted in a queue and validated by the community and me also.

le72’s picture

le72
Location Yerevan 🇦🇲
commented

Ping

Stacuma’s picture

Stacuma commented

Hi!
I have been working with the module and I would like to help with the update.

Thanks,

Stacuma opened merge request !4

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented

I just stumbled across this issue, were there are offers to help out maintaining the project from jvanja, le72, and Stacuma.

First, you need to read the issue summary carefully. Please notice this bullet point:

If the project is opted in to security coverage, confirm that you have previously received security coverage opt-in permission.

Node.js integration is opted in to security coverage. This bullet point has not been addressed by any of you. I see that neither le72 nor Stacuma have not received security coverage opt-in permission, and cannot be added as a maintainer by a site moderator. You may want to read: Apply for permission to opt into security advisory coverage if you want to pursue this

jvanja has the required permission, but the offer is nine months old.

jvanja, are you still interested in maintaining this?

le72’s picture

le72
Location Yerevan 🇦🇲
commented

Hi, gisle. How do you check if one have security coverage opt-in permissiom?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

@le72 On https://www.drupal.org/u/le72, you read Can opt projects into security advisory coverage. On https://www.drupal.org/u/jvanja, for example, that isn't reported.
This means you can be added as maintainer from site moderators, but jvanja won't be added.

This issue also needs to be moved to the Drupal.org project ownership queue. You can do it, if you are willing to be added as maintainer of this project.

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented

Thank you apaderno. I see that I made an error in comment #9, when I said that le72 did not have this permission and that jvanja had. My apologies. Should stop posting past midnight.

apaderno closed merge request !4

le72’s picture

le72
Location Yerevan 🇦🇲
commented

Thank you @apderni. It’s in sync with my understanding, that why I wandered and asked gisle.
No problem @gisle.

le72’s picture

le72
Location Yerevan 🇦🇲
commented
Project: Node.js integration » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Miscellaneous » Maintaining offer

Moving to the queue.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: nodejs project open to new maintainer applications on 5 Oct, 2021 » Offering to maintain Node.js integration
Assigned: Unassigned » avpaderno
Category: Support request » Task
Status: Active » Fixed

I added le72 since he can opt projects into security advisory coverage.

Status: Fixed » Closed (fixed)

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