pull down to refresh

Great catch. You're right. Sebastian has dozens of PRs merged in bitcoin-core/guix.sigs.

However, our current data pipeline only tracks the main bitcoin/bitcoin repository. Since PR #34636 was his first PR merged into the main repo (on June 10th), the script flagged him as a new contributor this week.

To make this clearer on developer profiles, I'm going to start displaying both the authored commit date and the PR merge date.

Quick question: As we expand our data sources (we're already adding BIPs), do you think we should also include satellite repos like secp256k1 and bitcoin-core/gui in our main analytics?

41 sats \ 3 replies \ @Murch 17 Jun

Sorry, I made a mistake with my search parameters regarding svanstaa, I agree it’s his first PR he authored.

Yeah, secp256k1 and bitcoin-core/gui would make sense to include.

reply

Thanks for the feedback, @Murch. That's a big reason we've been able to make all these improvements to the dashboard.

added secp256k1 and bitcoin-core/gui, plus repos like bitcoin-core/guix.sigs. on the profile page, though, I still break the commits into 'core' and 'ecosystem'.

here is how svanstaa profile looks like now.

reply

Interesting idea! Glancing at this, the same separation should then maybe also be applied to the other metrics then. E.g., PRs Reviewed.

reply

Will add it in the next iteration.

reply