When i look at a github project, i consider the number of closed Pull Requests to know if it's qualified or not for me to use or try it.
What about yours ?
When i look at a github project, i consider the number of closed Pull Requests to know if it's qualified or not for me to use or try it.
What about yours ?
For further actions, you may consider blocking this person and/or reporting abuse
David Newberry -
Ed Alves -
Adarsh -
Radharadhya Dasa -
Top comments (11)
There are different factors, some of them are:
I agree number of stars will encourage more contributors to join the projects, so it's really an effective factor to qualify a project.
Pull Request is only helpful if there's actually communication and colloborator to help that feature landed effectively on time, because in many cases, the implementer really needs helps from the community.
It has no open bug reports and still more than one user.
But you could eventually try it and contribute back to make it greater ?
I could and sometimes I do.
I usually go with stars and latest commits, if I am in doubt I check also the issues activity (when a issue was opened, resolved, etc)
Thanks. Could you explain more why you consider those as the most important factors ?
That's about it I think
Too much issues also mean the instability of the project ?
Of course i prefer too much issues than having no issues at all. It just means that the project demand is high !
It means that demand is high as you say, I wouldn't say instability.
Take React as an example there are 276 opened issues there...
Sure. Some maintainers are just lazy enough to close useless and out-of-date issues ;)