Request for higher maintainer permissions for @smustgrave on Slack module

Created on 1 February 2023, almost 2 years ago
Updated 28 February 2024, 9 months ago

@adcillc if you receive this, I need your help please.

There has been a request to change the default branch of this module, which I would like to do. With my current maintainer permissions I am unable to do so, I don't have access to the settings for this project in gitlab.

After asking around I am told that I need to be listed as "Maintainer" rather than "Developer" on the members page of the repo, and that any other Maintainer can provide me with that role from that same page.

Currently the only listed Maintainer is @adcillc who we haven't seen around for quite a while (which is fine of course) so if there is no response I will seek resolution of this issue via the core team.

πŸ’¬ Support request
Status

Fixed

Version

2.0

Component

Miscellaneous

Created by

πŸ‡ΊπŸ‡ΈUnited States smustgrave

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

Comments & Activities

  • Issue created by @smustgrave
  • Status changed to Needs review almost 2 years ago
  • πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

    Given the previous maintainership update, I'm willing to go ahead and grant increased privileges. You should now have complete maintainer access. Can also add node owner access if it turns out to be needed, but first check if what you have now allows you to make the needed change.

  • Status changed to Fixed almost 2 years ago
  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Worked like a charm thanks!

  • πŸ‡ΊπŸ‡ΈUnited States adcillc

    Hello,

    Thank you for your attention.
    We have our own track for the development.
    and the new release is coming soon.
    I moved the permissions back.
    please do your suggestions as is should be on a regular basics.

    Thank you

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Would highly encourage being more transparent about the development as the 2.x release caused much community friction as no one knew what was going on

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

  • Status changed to Fixed 9 months ago
  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    So has this project been re-abandoned? Been ideal for almost a year and we had good momentum before.

Production build 0.71.5 2024