Offering to co-maintain igbinary [#3488565]

Problem/Motivation

Hi,

I have been using the igbinary module in my projects skeleton since 2023/01/01. So on professional projects as well as side projects (in production).

I have been (a little bit) active in the issue queue in the following issues:
- #3330477: Make igbinary usable without needing module enabled.
- #3321482: Drupal 9 & 10 compatibility
- #3463342: Drupal 11 compatibility

Currently the latest commit from the 2.0.x branch is from 2022/11/16 (2 years old) while there are issues in RTBC in the issue queue. And the module is not marked for D11 compatibility.

I had contacted the project owner @mkalkbrenner on Slack in private message on 2024/09/02 asking if I can help on the module maintenance, without reply since then. I can copy/paste the message if needed for the record.

Proposed resolution

I would like to push the project forward by:
- cleaning the issue queue
- creating a new project release, even alpha state, to at least ease usage with Composer instead of a dev branch cloned by Composer
- opt-in for security coverage

Remaining tasks

Waiting for maintainer's reply.

Comments

Comment #1

20 November 2024 at 09:19

grimreaper created an issue. See original summary.

Comment #2

grimreaper

French

France 🇫🇷

commented 27 November 2024 at 08:15

Hi,

I have just contacted @mkalkbrenner using his contact tab, asking for feedback.

Comment #3

grimreaper

French

France 🇫🇷

commented 9 December 2024 at 08:55

Project:	Igbinary	» Drupal.org project ownership
Version:	2.0.x-dev	»
Component:	Miscellaneous	» Maintaining offer
Issue summary:	View changes

Hi,

Since I don't have any reply, per https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or..., I am moving this issue to "drupal.org project ownership" issue queue.

Comment #4

avpaderno

he/him

Italian

Brescia, 🇮🇹 🇪🇺

commented 12 December 2024 at 12:32

Component:	Maintaining offer	» Co-maintaining offer
Assigned:	Unassigned	» avpaderno
Category:	Support request	» Task
Status:	Active	» Postponed

mkalkbrenner logged in at least once in the past seven days. I am going to contact him in the next 4 hours.

Comment #5

avpaderno

he/him

Italian

Brescia, 🇮🇹 🇪🇺

commented 12 December 2024 at 18:39

This is the message I sent.

Hello Markus,

I am contacting you because Florent (https://www.drupal.org/u/grimreaper) offered to become co-maintainer for igbinary (https://www.drupal.org/project/igbinary), a project you created for which you are project owner and sole maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3488565 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Florent will be probably made co-maintainer.

Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

As last note: This offer is about being co-maintainer, which for us means somebody who does not have all the drupal.org permissions on the project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
If there is any reason for not giving Florent all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3488565.

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

The status has been changed because we are waiting for a reply.
Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder an action is required for this offer.