Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintainer for this repo and the library #161

Open
func0der opened this issue Feb 20, 2021 · 2 comments
Open

Maintainer for this repo and the library #161

func0der opened this issue Feb 20, 2021 · 2 comments

Comments

@func0der
Copy link

Hey there @yohang ,

this repo and the library does not get the love it deserves.
There are multiple open issues and a LOT of PRs ready to be merged or at least tested. People invest in this repo an obviously the interest in this repo is big with over a million installs on Packagist and over 150 forks here on GitHub.

Since you seem to be unable/unwilling to maintain this library for the community on your own, would you be willing to enable one of your contributers (if they are willing) to moderate and administer this library for or at least with you?

@winzou
@navitronic
@RonRademaker
@Padam87
@liuggio
@tortuetorche
@tompedals
@pborreli
@nidup
@defrag
@arikal
@realshadow
@K-Phoen
@acorncom
@dannykopping
@ksn135
@reiz

The other path would be to mark this project as abandoned, so people would stop installing it and then realize that there are (known) bugs, that are not fixed or missing functionality that is not merged, even when the work is done.

This should neither be attacking nor judgemental.
I know, it is hard to maintain open source and interact with a community if you already have a demanding life out there in the real world and a company whatsoever.
But I also think, that it is unfair to the community to let them use software without a clear message that this library is not maintained actively.

@Padam87
Copy link
Contributor

Padam87 commented Feb 20, 2021

@func0der Hi,

With all do respect to @yohang, who did an amazing job on this library, I think this can be considered EOL, or at least end of support.

symfony/workflow is more polished, and is supported by a proper organization. No single developer can compete with that on a side-project level.

@func0der
Copy link
Author

@yohang please mark this library as abandoned. There is no shame in that.
But since there are issues open, that have not been fixed for over 4 years and PRs that are ignored, it should not be used anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants