Instapage plugin 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.

Comments

System Message created an issue. See original summary.

jascote’s picture

jascote commented
Project: Instapage plugin » Drupal.org project ownership
Version: 8.x-3.37 »
Component: Miscellaneous » Maintaining offer
Issue summary: View changes

I would like to maintain this module to help incorporate fixed issues. There are a few in particular that are blocking this module's use related to D9 support, including this which I've created a patch for: https://www.drupal.org/project/instapage_cms_plugin/issues/3140829. Until those are in an official release using this module is blocking D9 updates. It's seems like the issue queue is not being addressed at all by the current maintainer. I can help.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Category: Support request » Task
Status: Active » Fixed

I added jascote as maintainer, since the project is not covered by the security advisory policy.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: instapage_cms_plugin project open to new maintainer applications on 5 Oct, 2021 » Offering to maintain Instapage plugin

Status: Fixed » Closed (fixed)

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

jascote’s picture

jascote commented

Hi. I was added as a maintainer but now as I'm trying to push and create a new release I seem to no longer have access. Can you help get me added as maintainer again? Thanks.

avpaderno’s picture

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

@jascote I re-added you as maintainer (user with all the permissions on the project).

avpaderno’s picture

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

If it happens again, please leave a comment here. Maintainers had about 5 months to close this issue, but they didn't close it. Once the issue is moved to this queue, they cannot remove any maintainer added following the procedure described in the issue summary.

konrad.stalega’s picture

konrad.stalega commented

@apaderno please stop adding people outside of our company. We finished working on supporting Drupal 9 and it is in our internal tests.

avpaderno’s picture

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

@konrad.stalega Please see the issue summary. Please stop removing maintainers.
You had 5 months to close this issue, which you didn't. Once this issue passes to this queue, you cannot anymore decide which users should be added as maintainers.

konrad.stalega’s picture

konrad.stalega commented

So what can we do to regain full control of our project? We had an email domain change, and it happened that our email: developers@instapage.com wasn't migrated to a new domain, that was why we didn't see your message and couldn't react.

This plugin is to help our customers use our platform within your CMS. Our policies do not allow people outside of our company to commit code to our software.

ivanstegic’s picture

ivanstegic commented

@konrad.stalega This module is open source, by definition, because you have uploaded it to drupal.org. Your company's policies have no bearing on the matter. If your company posted this code as open source but really meant to keep it proprietary, it should have done so in another forum.

@apderno Is this a violation of the COC? https://www.drupal.org/dcoc

konrad.stalega’s picture

konrad.stalega commented

We'd like to kindly thank you @jascote for your willingness and initiative to help moving our module forward.
We'll have your commits in the consideration, your activity led us to increasing our focus for maintaining this module for the drupal community. Due to the rules and acceptance criteria we have in our company for the Instapage module releases we still have to be the one releasing and approving the changes.

@apaderno, @ivanstegic The problem we had comes from the communication issue, but we fixed that. We should receive proper notifications from drupal.org in the future.
Without full control of the maintainers group, we would probably need to block our API access to this version because of unauthorised changes and Drupal users of this module will lose the convenient way of updating their code. Nobody wins.
We can agree for outside contributors who may suggest changes, to follow open source principles, but you surely understand that we have to decide what exactly goes to the current release of the module.
Once again, thank you @jascote, if you'll have any other suggestion towards improving this module, please feel free to reach out to us.

Regarding to maintenance plan: our main goal is to adjust the plugin to be in sync with any changes on the Instapage API side.