Problem/Motivation

I've been supporting this module for a couple of years now. To better offer guidance to contributors and have a bit more control over the future of the module, I wish to become a maintainer instead of co-maintainer.

Currently the only plan is to update the repository default branch and also accept new (co-)maintainers if needed.

The other plans with GitLab CI integration and fixing the quality and testing steps will be done anyway regardless of getting the role or not. But it will help to have the default branch switched.

Thank you for your consideration.

I could not reach out to the owner by sending an email via the contact form as the contact form is not available.

Steps to reproduce

N/A

Proposed resolution

Give Tim Diels the maintainer role instead of co-maintainer.

Remaining tasks

N/A

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Comments

tim-diels created an issue. See original summary.

tim-diels’s picture

Status: Active » Needs review
tim-diels’s picture

Project: Mask Field » Drupal.org project ownership
Version: 2.1.x-dev »
Component: Miscellaneous » Maintaining offer
Assigned: dbiscalchin » Unassigned

Waited for 2 weeks without any response. Moving this over accordingly.

avpaderno’s picture

Title: Offering to become a maintainer instead of co-maintainer » Offering to maintain Mask Field
Project: Drupal.org project ownership » Mask Field
Version: » 2.1.x-dev
Component: Maintaining offer » Miscellaneous
Status: Needs review » Postponed (maintainer needs more info)

The issue needs to stay in the project issue queue for at least two weeks, with a title that includes the project name, to allow the interested people to see the issue in the global tracker.

tim-diels’s picture

@avpaderno It was in the issue queue for 2 weeks. It could have a better title yes. But can we move it back to the "Drupal.org project ownership" issue queue? Not sure what the "Postponed (maintainer needs more info)" is for?

avpaderno’s picture

Status: Postponed (maintainer needs more info) » Active

I apologize: The status was probably changed because I was going to ask something, but then I found the answer myself.

What I mean is that the issue needs to stay at least 14 days in the project queue, with the title I set. The title needs to contain the project name (and the type of offer) to make the issue visible to people who see the new posts in the global tracker page, to allow people who have a reason to comment in these offers (including the project maintainers/co-maintainers) to comment on the offer.

tim-diels’s picture

Project: Mask Field » Drupal.org project ownership
Version: 2.1.x-dev »
Component: Miscellaneous » Maintaining offer
Status: Active » Needs review

I think we waited long enough now so moving this issue.

tim-diels’s picture

avpaderno’s picture

Status: Needs review » Active
avpaderno’s picture

Assigned: Unassigned » avpaderno
Category: Support request » Task
Status: Active » Fixed

dbiscalchin has last logged in more than two years ago. I made tim-diels, who was already co-maintainer, a maintainer.

Status: Fixed » Closed (fixed)

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