This post is being updated as the story unfolds for us… and we’re just starting to write these details in a public way, so bear with us. or don’t. this is an increasingly less rough draft. Origina...

Listening to the robot too hard. Cutting and pasting. they tell you not to do it… but sometimes we do it anyway. Today i was trying to get us (re) launched on our rad hosting provider (we’ll see ...

We’re rehosted! Since our Honorable Mention at btc++, we’ve updated our build system and migrated to a new hosting provider (let us know if you need a based hosting provider). We’ve also updated ...

Our Adventure at the btc++ Conference Hackathon in Austin As we reflect on our experience at the btc++ conference hackathon in Austin, we can’t help but feel a sense of excitement and accomplishme...

Examples of ways to analyze commit history: who reviews who? who gets the most reviews? who gets the least reviews? does anybody merge their own changes? ...

Recently, we’ve been discussing how to think about our codebases and how we can improve them to better serve the Bitcoin community. Our conversation started with the question “where do we want to g...

An Introductory Look at Our Tools for Exploring the Bitcoin Repository You can read the About page. But what else? At coreexplorer.org, we’ve been working on tools to provide insights into the B...

i think maybe i’m trying too hard to avoid a recursive search of all the commits in a given “merge Bitcoin/bitcoin” when determining if we have a “self-merge”… who knows? Here we have a commit 4b1...

Facts we should derrive: Given these desired calculations: 1) % of commits per year by contributor (# of commits by contributer this year) / # of commits this year find all commits t...