Final call for maintainers

[fgrehm]

Hey folks! 👋

Life, as it tends to do, has progressed for me in such a way that I am no longer able to devote time to maintaining this plugin, especially as I no longer use it on a daily basis for more than 5 years now.

As such, this project has been neglected and I apologize for that.

If anyone is willing to step up and take over maintaining this project so it gets the attention it deserves please reply to this issue. I'll do my best to follow up here or over email.

I'm going to close all open issues and PRs, I'll also tag them all as ignored just so it's easier to find them in case anyone wants to resume the work here.

If no one steps up within a week or so I'm going to archive the project ☮️

Thanks in advance!

---

This is a follow up of #143

[brainchild0]

May I ask, why not just leave the issues open as well as the project? In case someone does wish to resume work on your behalf, it would only be harder after such events.

[fgrehm]

Hey @brainchild0! Thanks for reaching out.

To be very honest, I'm not even sure what's the state of the plugin at this point, I haven't been using or following vagrant for many years now and I have a feeling it might not even work anymore.

In the case it does and ppl want to step up, they can easily go through the linked things above and try to come up with some sort of plan of action before I give out write access. There were things lingering for many years already without any action which in my opinion just generates noise. I believe that closing them all sets the right expectations 😅

The reason I'm going to archive is that the project is really unmaintained and I still get GitHub notifications about issues / comments / PRs every now and then, generating noise in my own personal inbox 😬

If u are interested in keeping the fire burning LMK!

[brainchild0]

I'm not sure whether it is possible to block e-mail notifications, or simply to lock the issue tracker without any change to existing entries. My thought is that as long as the effort has been taken by various visitors to report issues, then many of the reports must have some value. Thus, it would help encourage anyone considering assuming a maintenance role to make readily availalble the benefits of such effort, of both the reporting and the sorting of them. It would be much harder for someone new to the project, compared to someone with present familiarity, to comb through the entries in the issue tracker, for finding those most relevant to the current project state.

As it seems you have considered the nuances more deeply than is possible based on my background, I suppose my suggestion ultimately has limited value.

[fgrehm]

Thanks for sharing your thoughts! really appreciate 💟

The thing is, #143 was open for over 7 years and no one has stepped up for realz to keep the project going. This issue and my initiative around closing open PRs and issues was my last resort to catch attention and figure out if the project is relevant enough for folks to resume it. I also just realized that some folks might even have a fork that is active, but I haven't checked (ping @davividal in case it is)

TBH, I'm out of ideas here and I personally don't use the project. Leaving things open without anything actionable would not help IMHO. I'd love to be "proven wrong" though and am open to change 😅

The only that I know for sure is that I haven't used the plugin and don't have any plans to use it in the short / near term but am happy to pass on the torch to anyone that shows any interest on it like you just did and also is willing to triage previously opened bugs / PRs etc...

In any case, thanks for sharing your thoughts again!

[fgrehm]

FWIW - GitHub even suggests closing things before archiving projects, so I'm not totally crazy 😄

[brainchild0]

I'd love to be "proven wrong" though and am open to change

I understand the sense of the remark, but the ultimate question is simply whether someone would choose or not to continue the project. To such ends, I have not perceived the choices as the ones most helpful, but I respect they are not ones, as it seems, you have made lightly or rashly.

FWIW - GitHub even suggests closing things before archiving projects, so I'm not totally crazy smile

Yes, but is emphasizing the observation not begging the question of whether archival is the preferred choice, if the hope, as a best-case scenario, is changing ownership?

Perhaps advice on the more particular subject is available from GitHub, though the relevance of such advice is questionable, if not tied closely to the technical design of the platform.

This issue and my initiative around closing open PRs and issues was my last resort to catch attention and figure out if the project is relevant enough for folks to resume it.

I think less drastic measures would be more common for the desired effect, such as posting comments in open issues, in a project readme, or as a pinned issue, drawing attention to the project now being formally designated as unowned.

[fgrehm]

I think less drastic measures would be more common for the desired effect, such as posting comments in open issues, in a project readme, or as a pinned issue, drawing attention to the project now being formally designated as unowned.

I tried 😅 , the notice on project's README has been around for multiple years and I've personally commented on many of the PRs I closed saying I'm not working on it

Dunno, my hope is still for someone to step up and take action, this plugin saved MANY MANY hours on my day to day work back when I created it almost 10yrs ago 👴 I'm just not sure where Vagrant fits into ppls workflows these days 🤷

[brainchild0]

I think the tool is very useful. It's wasteful to pull an entire build environment from a remote site, when local storage is so abundant.

I respect your frustration trying to draw attention. I'm not sure that archival would be helpful, but you might consider posting an announcement to the vendor's community forum, if you have not do so already.

[fgrehm]

Alright folks, the time has come to archive this project. Thanks a lot for your input @brainchild0 but unfortunately no one stepped up, even after spamming a bunch of ppl over issues and PRs.

I'm always open to unarchiving it. If anyone is interested on resuming the work here please reach out to me through twitter or by other means listed on my personal website.

Many ❤️ s to everyone that contributed or attempted to contribute over almost 10yrs of this project existence, really appreciated ❤️‍🔥