3 ms·

I've started making a decent amount of commits to a public repository, and I almost feel embarrassed having my stats there because the commits have been rather

by easton 6y ago

I've started making a decent amount of commits to a public repository, and I almost feel embarrassed having my stats there because the commits have been rather marginal. I wish there was a way to block the specific numbers or block certain repositories from filling the stats.

sdesol 6y ago
> I wish there was a way to block the specific numbers or block certain repositories from filling the stats. This is somewhat related, but I'm working on impact based metrics that doesn't focus on commits, but is based on a contribution formula that I'm currently working on. You can get a sense of how the formula works by switching to the impact view in the following link: https://public-001.gitsense.com/insights/github/repos?q=window%3A30&r=github%3Amicrosoft%2Fvscode&v=repo https://public-001.gitsense.com/insights/github/repos?q=wind... As a side note, if you want, DM me your public repos and I'll add them to my public index list, as your contributions might have a greater impact that you may think. Plus it will provide me with more data points for refining my formula.
ocdtrekkie 6y ago
First, yes, commits is a terrible metric, because it lacks both the nuance of the size of commits and the substance of the commits. Also different projects have different norms around commits. Some people commit each step along a process, some force-push updates to their branches so a given improvement sits in a single commit. There's no good direct comparison between work across projects. That being said, don't feel like "rather marginal" commits is unhelpful. Support, docs, and tweaks are woefully undervalued parts of public projects, and you don't have to be building core features to be a big part of adding to the long-term success of a project. Don't sell yourself short.

3 ms·

I've started making a decent amount of commits to a public repository, and I almost feel embarrassed having my stats there because the commits have been rather

by easton 6y ago

sdesol 6y ago
> I wish there was a way to block the specific numbers or block certain repositories from filling the stats. This is somewhat related, but I'm working on impact based metrics that doesn't focus on commits, but is based on a contribution formula that I'm currently working on. You can get a sense of how the formula works by switching to the impact view in the following link: https://public-001.gitsense.com/insights/github/repos?q=window%3A30&r=github%3Amicrosoft%2Fvscode&v=repo https://public-001.gitsense.com/insights/github/repos?q=wind... As a side note, if you want, DM me your public repos and I'll add them to my public index list, as your contributions might have a greater impact that you may think. Plus it will provide me with more data points for refining my formula.
ocdtrekkie 6y ago
First, yes, commits is a terrible metric, because it lacks both the nuance of the size of commits and the substance of the commits. Also different projects have different norms around commits. Some people commit each step along a process, some force-push updates to their branches so a given improvement sits in a single commit. There's no good direct comparison between work across projects. That being said, don't feel like "rather marginal" commits is unhelpful. Support, docs, and tweaks are woefully undervalued parts of public projects, and you don't have to be building core features to be a big part of adding to the long-term success of a project. Don't sell yourself short.