Skip to content

Should this Project Fork or Become Managed by a Group? #41

@engineerjoe440

Description

@engineerjoe440

Hi @dparrini, and community!

I want to offer an open conversation about whether this project should fork, or move to group maintainer-ship to allow splitting out the work of maintaining, accepting pull-request, responding to issues, and providing new releases. I would like to get your thoughts, @dparrini, since this is originally your work, and I don't wish to make this feel as though I'm suggesting that this project be taken away from you. You've got a really awesome project, and its clear you've put a lot of time, energy, and heart into the project.

I wonder if the project's slow-down is due to other factors that have just kept you from being active with it. I know that's something that comes up a lot for developers (myself, included). So I wonder if sharing some of this work would be helpful to you?

I know that I would be willing to jump in and offer my hand where I can. I'd be happy to work alongside you as a maintainer. Alternatively, if you're no longer interested in maintaining this project, I'd be happy to help the community sustain a fork where possible.

Thank you so much for your work on this project, and again, I want to emphasize that this is something I'm interested in helping you wherever possible. I really would hate to "steal" your project from you. That is not my goal, in any way.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions