HNHacker News
TopNewBestAskShowJobs

kvinogradov

164 karma · joined May 29, 2020

https://kvinogradov.com/
submissionscomments
kvinogradov··on I algorithmically donated $5000 to Open Source
Totally agree! Actually I had outlined similar ideas and even an example (Pydantic) in https://news.ycombinator.com/item?id=42353209

In a nutshell:

- Algorithmic does not always mean automatic. An algorithm can have a human-in-the-loop element, as S&P500 or NASDAQ Composite have.

- Future versions of the index will account for known funding of OSS owners and maybe even exclude well-funded companies.

kvinogradov··on I algorithmically donated $5000 to Open Source
Yes, that would be a very useful risk metric! Assuming access only to public APIs (GitHub, package managers, etc.), how would you define the bus factor in terms of data? I am thinking about # unique contributors over the last X years.

It's funny that the experiment uncovered exactly such a case: a person from Nebraska got my donation as the first income from his open source contributions over the last 18 years and shared this on Linkedin:

https://www.linkedin.com/feed/update/urn:li:activity:7269812...

kvinogradov··on I algorithmically donated $5000 to Open Source
Thanks!

1) Yes. My plan is to continue iterating on this approach and publish more data later, including projects and some other inputs (PyPI, etc.)

2) Maybe. I prefer the full transparency and have planned to publish the code too, but some comments suggest that it might not be ideal. Need to think more about this.

kvinogradov··on I algorithmically donated $5000 to Open Source
It does not seem that Randall Munroe (xkcd) accepts public donations, but he recently released his own book, which can be bought at https://xkcd.com/what-if. I've just ordered.
kvinogradov··on I algorithmically donated $5000 to Open Source
While some mistakes are probably inevitable (like it happened with Tea protocol), sourcing a wide range of metrics from multiple sources, fixing bugs and building reasonable guardrails can prevent them from repeating.

For instance, given that my algo-donating aims to support the global OSS supply chain (not to distribute any crypto tokens like Tea did), it could potentially even focus only only "old" repos. They carry higher maintenance-related risks, but it will take years to distort such target area for donations.

kvinogradov··on I algorithmically donated $5000 to Open Source
There are some relevant tools for this, such as https://thanks.dev. While it doesn't work as a usage-based billing, at least it provides a way to fund all dependencies.

However, the issue is that most organizations relying on OSS are not tech companies. They mainly have no clue about OSS sustainability (e.g., airports and hospitals) and are unlikely to ever fund their own software supply chains, unfortunately. That's why there should be a data-driven index to address the global OSS supply chain, not only any particular ones.

kvinogradov··on I algorithmically donated $5000 to Open Source
Exactly! The idea is to use available data for evaluating the value and risk of OSS and then allocate donations accordingly to the wide algo-based systemic index, not to a narrow set of manually picked projects (usually large or popular ones).

The current algorithm is far from being perfect (it's an MVP) and will never be, but with more measurable inputs and after multiple iterations with the help of the community, it can lead to an analogue of "S&P500" for OSS, that's worth using for donating to reduce the risk of the global OSS supply chain we all rely on.

As with publicly traded companies, having a decentralized set of private donors with skin in the game helps a lot to efficiently evolve the approach and make it harder to exploit in the future. And on the contrary, I would not trust an algorithm created and maintained by some state-owned or simply very large institution.

kvinogradov··on I algorithmically donated $5000 to Open Source
Hey HN community, thanks a lot for your great feedback and actionable critique!

It was a simple MVP for personal OSS donations, and I have many considerations on how to evolve it and especially to prevent it from becoming a victim of Goodhart's Law at scale. Some of them:

1) Value and Risk scores shall include more metrics: dependencies, known funding, time since the last dev activity, active contributors, etc. A wider set of connected but relatively independent metrics is harder to fake. Also, it will help to exclude edge cases — for instance, I auto-donated to Pydantic (it's a great OSS), but such support is unlikely needed as they have raised $12.5M Series A from Sequoia this year.

2) Algorithmic does not mean automatic. While I see a strict, measurable, and ideally fully transparent methodology crucial for donating, it does not mean that all inputs shall be automatically generated. For instance, in the stock ETF world, one can generally rely on such metrics as "annual financials" for trading because they are annually audited (although it does not prevent fraud in 100% of cases). In the OSS world, data from trusted ecosystem actors can also be part of the equation.

3) Many guardrails are possible: limited budget per project, manual checks of top repos with the most anomalous changes in metrics. Also, if we target the sustainable maintenance of OSS the world relies on (I do!), then new projects (1-2 years) will unlikely get high scores - that adds another protection layer.

Given the interest in this topic, I am going to continue developing this algorithm further and expand it to other ecosystems (e.g. JS/TS and Rust). Your feedback here is very valuable to me, and those who would like to help make the algo better or donate through it are invited to the newly created gist:

https://gist.github.com/vinogradovkonst/27921217d25390f1bf5e...

kvinogradov··on I algorithmically donated $5000 to Open Source
Thanks. That's a start experiment - I am going to donate more using this approach in the future and hope that other people will join me in this non-profit initiative.

While any particular donation I made to OSS maintainers is small, it seems important that the recipients get more attention and maybe will be less likely to burn out in the future. For instance, some of them (btw, from Nebraska!) did not receive anything for 18 years of contributing to OSS before last week: https://www.linkedin.com/feed/update/urn:li:activity:7269812...?

kvinogradov··on I algorithmically donated $5000 to Open Source
Thanks. There is no ideal set of metrics for value, but some measurable ones correlate with it. The more reasonable inputs are accounted for, the harder it is to game the system.

Regarding is-odd, it would unlikely receive a high score even with the current primitive version of my algorithm, as it already includes the package size among the "risk" set.

kvinogradov··on I algorithmically donated $5000 to Open Source
This spending comes from my personal pocket and does not even create any tax relief. I just think that Open Source is important and want to efficiently support it.
kvinogradov··on Open Source Contributors Analysis and Deep Dive into OS Databases
Contributors are important for open source startups, but they were barely measured (usually — only # total contributors). Why not use MAU, retention, LTV and other classic user metrics for them?

The article introduces this fresh approach and applies to all open-source databases (350+) in the world, revealing the top-20 by new/active contributors, retention, engagement, etc.

kvinogradov··on Show HN: Sidekick – the fastest browser built for work
I had been using Google Chrome for ages and permanently tried various extensions and other browser projects.

Only Sidekick managed to become a new default browser for me due to its incredible speed and UX.

kvinogradov··on Open Source Benchmarks for Languages and 20 Fastest-Growing OSS Startups (Q3)
I have collected Github data on all repos with 1K+ stars and share some insights on programming languages and the fastest-growing open-source startups in Q3 2020.

We even made the index of such companies and plan to update it every quarter.

← PreviousPage 2 of 2