Offering to maintain Phing Drush Task

The procedure → for being added as a maintainer to a project says you should first post your offer in the project's issue queue (i.e. do not start out by posting in the Drupal.org project ownership issue queue). By posting your offer in the project's issue queue, you make sure that the project's current owner and most active users see your offer and can comment on it.

It also 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. If you do this, please add the details (who, means of contact and when) to the issue summary.

The project has, in addition to the owner, two additional maintainers that may accept your offer. While you are not required to contact anyone, I recommend doing so, as it my lead to a mere timely resolution of the issue.

I am moving this to the Phing Drush Task issue queue. You can move it to the Drupal.org Project Ownership issue queue if there is no response in 14 days.

I tried to connect to one co-maintainers on Drupal slack. He don't have permission to add new maintainers.

These can add new maintainers:

• pbuyle →
• fdewinne →
• pol →

You should connect to them via the "Contact" for on their user profiles, in addition to Drupal slack.

Hi,

Though I don't use Slack very often, I have indeed received the notification.

I understand your eagerness to maintain the project, and I appreciate your initiative. However, I noticed that you've been working with Drupal for only three weeks. While your enthusiasm is commendable, I must admit I'm a bit apprehensive about entrusting the project to someone who's been registered for such a short time. This concern leads me to suggest a more gradual approach.

How about we start by having you submit pull/merge requests for some initial tasks? After some time and successful collaboration, we can re-evaluate your involvement and possibly expand your responsibilities.

Please let me know if this approach works for you or if you have any questions or concerns.

Regards

Yes @pol,
We can go ahead with this approach.

Cool, thanks!

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