3 ms·
Author here. I am still exploring useful metrics for classifying open source projects. My initial intent was to find a way to judge if given project is a good u
by gieksosz 6y ago
Author here. I am still exploring useful metrics for classifying open source projects. My initial intent was to find a way to judge if given project is a good use of time for a first time contributor, someone not affiliated with original authors.
- detaro 6y ago> My initial intent was to find a way to judge if given project is a good use of time for a first time contributor, someone not affiliated with original authors. so what does this contextless number you submitted here tells us about that? Please be careful with spreading around stats like that without context.
- gieksosz 6y agoThanks for feedback. In principle it is a measure that says - this repo will handle your PR quickly, but the base chance of it getting merged is low. The result in this case is skewed by spam however. Until I find a way to filter the spam PRs from counting it will remain uneven for repos like this one.
- detaro 6y agoThat's exactly the problem. If you present a number but it's uneven for all kinds of reason it's a bad measure. And people will go around and unfairly point at projects being "bad for new contributors" with how you present it.
- gieksosz 6y agoSpam filtering is at least something I should be able to tackle in a somewhat reliable way. I am worried about telling outsiders from insiders, there are many ways projects go about organizing their contributors! Some use GitHub organizations and give contributors membership (easy to tell apart) some others invite to collaborate via giving access rights (also easy) but some others do neither of those things.