Is this project dead? More maintainers needed?

[davidhaymond]

This repo hasn't had a commit in almost 1.5 years. The last release was almost 2 years ago. There are PRs with bug fixes that haven't been touched, and issues that haven't been addressed.

@CalebAlbers @adrianwells What is the status of this project? Are more maintainers needed? I would be happy to be a maintainer if help is needed. This is a useful tool and I would like to see the community continue to support this official version instead of relying on forks.

[CalebAlbers]

@davidhaymond unfortunately, I no longer work in the MSP industry and haven't used IT Glue actively in several years. With that said, I do still care about the community and would love to see some additional maintainers take on the project.

If that is something that you or anyone else is interested in, I'd be more than willing to help set up push access to the repo. The most useful immediate thing would be some help reviewing some of the outstanding PRs that are open. I'll also see if I can carve out a few hours of weekend time to catch up on the current state of affairs to help things along.

I went ahead and pinned this issue for anyone else who is passing by.

[davidhaymond]

@CalebAlbers Thanks for the quick response! I would be honored to serve as a maintainer, for at least as long as I work at a shop that uses IT Glue.

Other than getting existing PRs and issues taken care of, I am particularly interested in enabling cross-platform support. Being able to use the module in CI/CD scenarios or Linux virtual machines would be immensely useful for all sorts of automation.

[CalebAlbers]

That's fantastic to hear! I appreciate the willingness to help 🙂

Being able to use the module in CI/CD scenarios or Linux virtual machines

This is definitely something near and dear to my heart, given my current non-MSP career. I see you made some nice research notes over in #43 - I'll read up on everything and write up my thoughts there. If there are other areas generally that you are interested in tackling, let's track them via issues, too, and cycle feedback that way.

[CalebAlbers]

It seems that a decent chunk of the existing open PRs are bug fixes or small feature adds. Perhaps we could both run through them and add some reviews/approvals and push out a minor release soon without much trouble?

Tangentially, I created #147 to track getting publishing set up with GitHub Actions, which should make things significantly easier and pave the path for testing on PRs, etc.

[adrianwells]

Thanks @davidhaymond for volunteering to help. @CalebAlbers thank you for the continued support here. Thank you to @ecspresso for continued efforts and actively helping answer issues/questions over the years. (Also, thanks to others helping out here!)

I've not been as active on this project due to other commitments but welcome the opportunity to collaborate further and it'd be refreshing to re-energize this project. 🚀

[davidhaymond]

It seems that a decent chunk of the existing open PRs are bug fixes or small feature adds. Perhaps we could both run through them and add some reviews/approvals and push out a minor release soon without much trouble?

I've reviewed and commented on the existing PRs. I will go through the issues as well as time allows.

[CalebAlbers]

Alrighty, I merged all the current PRs; thanks a ton for reviewing them and reviving this project!

Do any of you have anything else you'd like to see in a v2.2.0 release? If not, I'll go ahead and push one out with all the current changes, and anything new in the issues can be addressed after the fact.

[davidhaymond]

I think it's fine to push out a release now, and hopefully we can follow it up in a few weeks with another release with fixes for some of the higher-priority issues like UTF-8 support (#12, #97, #103). I hope to contribute some PRs for these issues soon.

[CalebAlbers]

Alrighty, a new GitHub release was made for v2.2.0. I'm having some trouble publishing the module, so I'm going to spin up a VM and try it from Windows tomorrow. WIll update the thread then. Cheers!

[davidhaymond]

Thanks for all your work, @CalebAlbers! I'm going to prioritize getting the module working on Unix platforms in the coming weeks.

[davidhaymond]

@CalebAlbers I have a significant amount of work I want to push through in the upcoming weeks, but I don't want to overload you. My offer to become a maintainer still stands so I can help with reviewing and merging PRs; is that something you're open to?

I'd like to get out a bugfix release soon to fix the longstanding UTF-8 bug, and then tackle Linux support and the backlog. Setting up a CI/CD pipeline to automate testing and releases will also be helpful.

[davidhaymond]

@Celerium @ecspresso I've decided to go ahead with development on my own fork and you are welcome to contribute. I've merged #160 and #152 and also added the long-awaited UTF-8 patch (#12). Once @CalebAlbers is available, we can merge our downstream work into this repo and push out a new release.

I still have hopes that we can get the ball rolling on this official repository and make it a great tool for the IT Glue community!

[davidhaymond]

@CalebAlbers @adrianwells Any update on this? I would like to make progress on this project but would like to avoid forking if possible.

[jonwbstr]

Thanks!

Slight correction, this is a community supported repository, it's not official.

On Tue, May 2, 2023, 7:12 PM David Haymond @.***> wrote:

@Celerium https://github.com/Celerium @ecspresso https://github.com/ecspresso I've decided to go ahead with development on my own fork https://github.com/davidhaymond/powershellwrapper and you are welcome to contribute. I've merged #160 https://github.com/itglue/powershellwrapper/pull/160 and #152 https://github.com/itglue/powershellwrapper/pull/152 and also added the long-awaited UTF-8 patch (#12 https://github.com/itglue/powershellwrapper/issues/12). Once @CalebAlbers https://github.com/CalebAlbers is available, we can merge our downstream work into this repo and push out a new release.

I still have hopes that we can get the ball rolling on this official repository and make it a great tool for the IT Glue community!

— Reply to this email directly, view it on GitHub https://github.com/itglue/powershellwrapper/issues/146#issuecomment-1532266232, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADXTPAC4VGQX5ULCSWNHXK3XEGIGXANCNFSM6AAAAAASPBNOCI . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[davidhaymond]

@jonwbstr Thanks for the correction; bad word choice on my part. I meant to say that it is the de facto community standard, and I don't want to splinter the community by publishing ITGlueAPIv2 or something.

[adrianwells]

@CalebAlbers Hi. Is it possible to grant @davidhaymond permissions to help with this repository? It does not seem I have this permission.

[CalebAlbers]

@adrianwells @davidhaymond I would love to, but unfortunately I don't have permission to do so either.

I've asked IT Glue on a few occasions to grant me a higher level of access over the past year and a half, but nothing has happened so far.

Unfortunately, I regret moving this repo from my personal account to the larger ITG organization 😕 - it was well intentioned (to improve visibility), but it came at the cost of not being able to maintain things independently.

[adrianwells]

Thanks @CalebAlbers for the reply and insight. Maybe @davidhaymond contact ITG to advocate for access?

[CalebAlbers]

Please feel free to mention my name and request as well. I had reached out via my contacts at the partner advisory council

On Thu, Sep 7, 2023, 10:50 PM adrianwells @.***> wrote:

Thanks @CalebAlbers https://github.com/CalebAlbers for the reply and insight. Maybe @davidhaymond https://github.com/davidhaymond contact ITG to advocate for access?

— Reply to this email directly, view it on GitHub https://github.com/itglue/powershellwrapper/issues/146#issuecomment-1710754422, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABWH36RZW22OX5V4H47A3WLXZIXP7ANCNFSM6AAAAAASPBNOCI . You are receiving this because you were mentioned.Message ID: @.***>

[davidhaymond]

@adrianwells I would be more than happy to contact IT Glue. Is there a specific email address I should use to get in touch with them?

If that fails, perhaps we should recenter development efforts around Caleb's original repo under his account?

[adrianwells]

@davidhaymond perhaps IT Glue support ticket? Additionally, I reached out to my contacts referencing this issue.

[davidhaymond]

@davidhaymond perhaps IT Glue support ticket? Additionally, I reached out to my contacts referencing this issue.

I've opened a support ticket, and the rep said they were checking internally with the product team. I'll keep you updated.

[TheMonzel]

Hi all, @davidhaymond: you got any news on this? If not, I can/will also ping the Product Management.

[davidhaymond]

@TheMonzel I have not received a response from IT Glue yet. Please feel free to reach out to see if we can get someone to address this.

[CalebAlbers]

I've reached out yet again but haven't heard a response either.

[davidhaymond]

I've been granted write access to this repository so I'm now able to merge PRs. I'm looking forward to working with this community!