Offering to co-maintain Simple Style Guide

Created on 20 June 2024, 5 months ago
Updated 23 July 2024, 4 months ago

Problem/Motivation

I use this module to generate a styleguide for using unCSS for a couple sites I maintain. This is an important module for my sites, so I would like to offer to co-maintain the module.

There are several issues that have been awaiting approval.

If you allow me to be a co-maintainer, I will:

* Adopt GitLab CI and fix the tests
* Release a Drupal 11 compatible version
* Clean up the issue queue

I have recently done similar work for the Rename Admin Paths and Alternative
User Emails modules.

Thank you for your consideration.

I reached out to xpersonas by sending an email via the contact form on June 29 and have not yet received a response.

💬 Support request
Status

Fixed

Version

2.0

Component

Miscellaneous

Created by

🇯🇵Japan ptmkenny

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @ptmkenny
  • Assigned to apaderno
  • Status changed to Postponed 5 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    Only a maintainer can be considered active on drupal.org. I am going to contact him.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    This the message I sent to xpersonas.

    Hello Justin,

    I am contacting you because Patrick ( https://www.drupal.org/u/ptmkenny ) offered to become co-maintainer for Simple Style Guide ( https://www.drupal.org/project/simple_styleguide ), a project you created for which you are project owner and maintainer. (You actually are the only maintainer who has any activity on that project. This means you are the only maintainer I will contact.)

    May you post a comment on https://www.drupal.org/project/projectownership/issues/3455976 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
    In the case you accept the offer, you can also add Patrick as co-maintainer, but this is not necessary, as project moderators can add co-maintainers/maintainers to any project.
    Without a comment posted on that issue in the next 14 days, Patrick will be probably made co-maintainer.

    Neither project moderators nor site moderators will 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.

    A 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. In the case the permissions given to Patrick are less, may you explain why in a comment posted on that issue?

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

    The status is still Postponed because we are waiting for a reply.

  • 🇺🇸United States xpersonas

    Hello apaderno and ptmkenny,

    I appreciate the offer. At this time I would like to continue to be the sole maintainer. It's been a bit of a year for me, but I am trying to get everything caught up again. I have begun cleaning up the issue queue and prepped for D11. I released version 2.0.1 today with many of those changes.

    I'm going to continue to work through the remaining items regarding the Gitlab CI template and others. I definitely appreciate the help with merge requests and/or patches. This is one of the few modules I have written that I use on every site and rather enjoy. Therefore, at this time, I would like to keep it under my wing. At least until a later time when I may not be able to keep up.

    Thank you again

  • 🇯🇵Japan ptmkenny

    Ok, thank you for the reply!

    It looks like the 2.0.1 release hasn't happened yet on Drupal.org, but I'm looking forward to it!

  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • Issue was unassigned.
  • Status changed to Fixed 5 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    Since this offer has been answered, I am moving this issue back to the project queue.

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

Production build 0.71.5 2024