Skip to content

Q: Maintenance #5

@tomjn

Description

@tomjn

Hello!

I'm evaluating using this in conjunction with a vagrant project, and I'm wondering what governance of the org is.

I ask because pretty much every vagrant plugin for modifying hosts files has been abandoned or put in a limbo state, even if people were willing to contribute the original author went AWOL with no way of delegating to a new maintainer.

I see this library is based on one such project, and that there are a few go based alternatives that are in similar boats.

I'd really like to avoid having to maintain a legacy ruby vagrant plugin :( I'd rather write a wrapper around a CLI tool like this. Is there an associated project that relies heavily on this that has some maintainer overlap? Or a process for if the current maintainers no longer use/need the project for me or someone else to contribute fixes?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions