Offering to co-maintain Commerce Cart API

Created on 24 July 2023, over 1 year ago
Updated 26 July 2023, over 1 year ago

I see a lack of resources to maintain this module from maintainers.

Feel free to add me as a co-maintainer of this module
We are using it within YMCA Website Services distribution

I'll take care of RTBC issues and release management

Thank you in advance

💬 Support request
Status

Closed: won't fix

Version

1.0

Component

Miscellaneous

Created by

🇺🇦Ukraine podarok Ukraine

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

Comments & Activities

  • Issue created by @podarok
  • 🇮🇱Israel jsacksick

    Hi Podarok, I do not see any contribution from you in the issue queue? Care to share your plans?

  • Status changed to Needs review over 1 year ago
  • 🇺🇦Ukraine podarok Ukraine

    I'm going to test and release Drupal 10 of the module as well as work on the issue queue

  • 🇺🇸United States mglaman WI, USA

    Hey! Sorry, no one pinged me to review the D10 issues. I missed that in the noise of other projects. @podarok a nudge and I would have reviewed and unblocked this. I'm going on vacation but I can kick tires on this on Monday the 31st.

  • 🇺🇦Ukraine podarok Ukraine

    That's why I'm offering help, once I have access - vacation becomes not a blocker for the community to upgrade their projects to Drupal 10

  • 🇺🇸United States mglaman WI, USA

    But I wasn't on vacation the past few months. I don't always monitor each module's issue queue. A friendly ping in Slack or contact via Drupal.org would have helped resolve this earlier :)

  • 🇺🇦Ukraine podarok Ukraine

    I understand
    There is an issue of finding who should I ping and also Drupal.org is doing a good job of sending notifications about issues statuses.
    The number of projects is very large, and not always maintainers are on Slack. It's unclear what should be chosen as a communication channel.

    This is not a blaming or shaming game, this is a need, which community dictates to us, e.g. if since releasing Drupal 10 maintainers had no chance to check automatically created Drupal 10 fix, which means maintainers are not using the module and are not spending resources on updating the module in their projects and if someone else has resources - we need to help those people instead of becoming a bottleneck.

    But that's just my thoughts, would be great to get this module released for Drupal 10 when you have a chance.
    Thank you

  • Status changed to Closed: won't fix over 1 year ago
  • 🇺🇸United States mglaman WI, USA

    Closing this as a won't fix. We've resolved the problem, a release is pending.

Production build 0.71.5 2024