Should this project be considered dead?

[EugenMayer]

No offense, just asking myself if @emre is no longer active.

If not, does it make sense to pick a community fork as the successor or simply invite interested contributors? They are already a number of forks

[emre]

Can you send the links of active forks?

[DonDebonair]

@EugenMayer can you respond to @emre's question? I'm curious as well what forks exist...

As for this project being dead: on the one hand there are 8 open PRs and 17 open issues, which indicates response times are slow, on the other hand storm could be considered rather finished. It does what it should do and does it well. What activity should there be then?

[EugenMayer]

IMHO: One thing is assured, its not finished. It has a lot of enormous quick wins which are very hard to work around right now.

e.g. either fix the status codes or add insert-or-update .. which is basically the single most needed operation when you use storm in automated setups. And to be honest, on non automated, simple setups i guess a lot of people simply use plain old .ssh/config and edit it, thats about it.

to @emre ... asking me which fork is promising seems to be the wrong way to go about it. I am just a user, i cannot really judge. If you care so little right now and cannot dedicate time to check the forks with your knowledge applied, pick the most active forks and invite them as contributors to this project.

You will do less harm then good i would assume

[emre]

to @emre ... asking me which fork is promising seems to be the wrong way to go about it.

Not exactly asked which fork is promising. I wanted to see the active forks. Currently, Github says there are 147 forks and I don't know which one of them is actively maintained and developed. I don't know any easy way to find out.

Since you have posted this originally:

If not, does it make sense to pick a community fork as the successor or simply invite interested contributors? They are already a number of forks

I thought, there are some active forks you are aware. But, I believe that's not the case?

If you care so little right now and cannot dedicate time to check the forks with your knowledge applied, pick the most active forks and invite them as contributors to this project.

Everyone is free to contribute to the project via pull requests. I have left it stalled for a while but they will be reviewed at some point.

[EugenMayer]

IMHO not many or very few will contribute to a project with that many PRs open and uncommented.

[DonDebonair]

@EugenMayer maybe you should be a little less aggressive about this. @emre built this in his spare time and contributed it as open source. Now he doesn't have time, or maybe he doesn't feel like maintaining this anymore. That's his right.
Instead of complaining about it, and mentioning what features are so sorely missing, maybe you should start contributing those new features.

As for other developers not wanting to contribute because of open PRs and issues, I'd like to see some data/research on this, because it seems like bullshit. Open PRs and issues are in fact a very good reason to contribute so a project. It means your contributions are needed and thus valued.

Lastly, if you're unhappy with the progress of storm, and you think other forks are more ahead and/or provide features you want, you should just do some research yourself to figure out what fork best fits your needs, and start using that fork.

[EugenMayer]

@dandydev Did i complain about him not maintaining it anymore? Could you quote that part? I help you, i did not. A sarcastic tone i have chosen, i would admit.

I did in a form complain about him not picking up the task to either:
a) find a successor and promote it
b) invite direct contributors to his project to help him not being the bottleneck.

Both of those tasks include, that i fully understand that he does not feel like putting time into it is something for him (right now, or ever). Thats more then legit. But putting 1% of the effort went into storm in securing its forthcoming is something that seems more then legit too.

What i see here is rather overprotecting the project until its "hugged to death". No hard feelings and not the first time i see that happen.

Long story short, i am using a fork, a fork we patched. And you might want double check if your characetization of mine fits your picture by clicking on my github account. I would at least say, i am about to "get used to contributing", and not a "complainer about missing contribution while not doing anything". I am used to "code is gold".

But whatever, the last thing i wanted here is fighting about whos effort it is. @emre feel free to close this issue anytime, its gone the wrong route anyway.

[nicolascb]

https://github.com/nicolascb/nssh

[f]

@EugenMayer As you probably know, open source on GitHub doesn't work that way. If you want a feature or bug you would open an issue about it. And if you can develop that feature, you would open a PR for it. People will review it.

Committing code rarely doesn't mean it is dead, it's simply feature complete and does not need to be updated frequently. If storm was not working I could understand your concern but I don't see any problem with the Storm right now.

[emre]

I did in a form complain about him not picking up the task to either:
a) find a successor and promote it
b) invite direct contributors to h project to help him not being the