kvinogradov

Joined 6 years ago

Karma
164
Submissions
52
Member since
May 29
https://kvinogradov.com/
View on Hacker News

Recent submissions

Comment · 8 months ago
We explicitly explained to the IRS that our endowment plans to make awards and grants to individual OSS developers and maintainers in the US and other eligible countries. Given our limited target scope — not just any software, but critical nonprofit independent OSS — it was acceptable, and the IRS approved our 501(c)(3) status. And we plan to operate within what is described in our application.
Comment · 8 months ago
The endowment model is complementary to direct donations, which many of OSE donors make. For example, I did this a lot: https://kvinogradov.com/algo-sponsors. Some people do this privately, and the largest public case among our donors seems to be https://ziglang.org/news/300k-from-mitchellh/

It requires choosing projects, and most people don't have time for this.

But the main problem is that such funding is simply not sustainable: corporate annual budgets for OSS are volatile, and individual donations are extremely volatile. It is not great for the critical infrastructure we all rely on.

The Open Source Endowment enables truly sustainable funding and also decreases the entry barrier for new OSS donors because it does not require choosing a specific project. A la buying the S&P 500 ETF instead of stock picking.

> Congratulations, you managed to pick out the two projects in the set that make it merely "mostly" (instead of "entirely") frivolous.

Out of curiosity, which founding donors specifically would qualify under your criteria for a "serious" project? If the founders of HashiCorp, Elastic, ClickHouse, Supabase, Nginx, and curl seem like a mostly frivolous band to you...

Comment · 8 months ago
We don't require a membership to participate in GitHub discussions, but it is required to be invited to closed events and to be part of the OSE governance.

The global average salary of a software engineer is $5,906/month, and the OSE membership is $83/month ($1,000/year), so it would require donating ~1.4% of gross income. This aligns fully with the 1-2% of income that an average U.S. individual donates every year, and we are targeting more senior engineers, not the average ones.

So it is affordable for our target audience, but requires some personal commitment. To be efficient in the long term, an endowment must be managed by people who have skin in the game.

It would also be irresponsible to have people who can't or don't want to personally donate $1,000 to our cause, or people outside of the tech industry, managing a multi-million-dollar community fund focused on solving a pretty niche industry problem. Otherwise, the endowment ends up being as efficient as a typical government!

Comment · 8 months ago
It can be a recurring grant if a target OSS project continues to be highly valuable, but risky. When it loses value or is derisked (e.g. by extra funding), then grant priority will naturally move to another project.
Comment · 8 months ago
Thanks for sharing the context, it's really helpful. For full transparency, I am not a high-net-worth individual either, and I also grew up dirt-poor and now am a modestly successful 34-year-old tech dude.

We are not building yet another HNWI-focused nonprofit, but a grassroots community endowment. It targets a donor like you – a regular tech industry worker who can support things they truly care about with a $1-100k donation. I think many developers love open source, don't they?

We intentionally targeted launching the endowment with a $0.5-1m initial size and many donors because:

1) It is not attractive for regular donors to support a project that is heavily funded by HNWIs. Let's say if I were able to donate to the Gates Foundation, it would be like peeing in the ocean and wouldn't matter. However, I am eager to support projects with peers among donors because it makes a difference. And that's the way to make OSE scalable and outlive all its founders.

2) It is important to maintain high decentralization of funding, which enables good community governance and accountability. Having a few outsized donors at the start kills it. Our donor Herfindahl–Hirschman index is ~1800 now.

3) As a VC (maybe a bit old school), I think that it is responsible to limit funding size at very early stages and grow it later together with achieved milestones and decreasing risks. It helps to build more efficient organizations.

Just take a look at https://endowment.dev/community - we obviously targeted notable founders at the start, but now it is a healthy mix with many everyday developers. You're welcome to join them.

Of course, OSE will look for large donations. But the goal is to raise them in balance with growing a community of smaller donors, maintaining decentralization and scalability.

Comment · 8 months ago
There are areas where we experiment and take risks: raising the first-ever endowment for open source, making it very lean and digital-first, relying on bottom-up funding and governance instead of large corporate donors, etc.

But all other areas should be as low-risk as possible — like accounting, legal, and investment management of a community endowment fund. We are exploring a few ideas on how to grow the fund faster than the market without increasing its risk profile, but they are complementary to a very conservative core strategy.

Besides OSE, I am a full-time VC — that's the area where investors are bold and invest in off-norm opportunities, but it lies on the totally opposite side of the investment risk spectrum. And directly mixing them does not seem like a good idea.

Comment · 8 months ago
Software has its own lifecycle, and the funding should not stick indefinitely to a specific project. Meanwhile, our grant format might evolve into some type of limited tenured positions for maintainers, which support the most critical yet risky projects. But this target scope should be dynamic and adapt to the market—global consumption of OSS; otherwise, we may end up maintaining COBOL in 2100...
Comment · 8 months ago
Comment · 8 months ago
“super minimal that requires less management and operating costs” - that’s exactly our current setup, and always will be the target!

Now OSE has no paid employees - the team is 100% volunteers. Its Board Directors and the Executive Director are required to personally donate $1000+/year. Operating costs are close to zero.

As organization evolves there might be higher operating costs, but our commitment to keep them as low as possible.

Comment · 8 months ago
Now the Open Source Endowment is a very small organization that starts with ~$5k microgrants. It is not enough for a living but still should help maintainers not only financially but also by allocating attention.

As it grows bigger, the grant size will also grow. One can help with this by donating and bringing in new donors!

Comment · 8 months ago
OSE has a diverse community of donors, and most of them are not even close to that net worth level. Around 75% of our donors contributed in $1-200k range. We think that every donation matters, and hugely respect everybody supporting open source.

May I ask what it’s the right share of net worth one should donate to OSS? And what’s this share in your personal case?

Comment · 8 months ago
Sure - we donate our own money to this endowment fund and carefully choose partners who have a solid reputation and can deliver maximum efficiency. I don't think we will have any of them in former socialist countries,except for those based in Berlin :)
Comment · 8 months ago
Comment · 8 months ago
The explanation is simple — nobody can predict exact annual returns, and they tend to fluctuate. We aim to spend at least 5% per year on OSS grants and need to decide if we can spend more on them or should reinvest based on specific annual results. And target earnings should overcome inflation.
Comment · 8 months ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton