[numbsafari]

Something I’ve been curious about for a while is why more universities don’t get involved in sponsoring critical projects. In theory it could provide an interesting non-academic path for students and professors and, as you’ve pointed out, the funding model of the U would make sense here.

I’m curious… would you consider having a “faculty” of “tenured” maintainers who receive livable funding and support based on a history of significant contribution? I could imagine something like “named chairs” and professorships you see for some tenured folks in academia. This could be useful for key project leaders, and contributors. In addition, any kind of function to train and develop the next generation of maintainers?

[mentalgear]

This would very much make sense and generate direct real world products. However, I fear academia is in itself a very competitive space for resources that doesn't necessarily want to open up for outsiders.

[shimman]

Well universities have no qualms about making private relationships to help subsidize private research. Let's not worry about problems that don't exist or are trivially solved.

[EarlKing]

Well, speaking in the case of the US, this would constitute product development which is well outside the scope of what a 501(c)(3) organization should be doing, which could thereby jeopardize their tax status? Or, in the case of a state-run university, this raises all kinds of issues regarding how tax money is being given away to random schmoes instead of benefitting the public at large.

So, yeah, there's plenty of reasons why they don't do that.

Open source wouldn't have a funding problem if people would stop being so averse to just paying for what they use. Maybe... the world should stop expecting something for nothing.

[numbsafari]

Using the model of the university and various tenured profs, I'm not sure what you are saying is true. But, perhaps it's a misunderstanding of what I was intending.

I see this more as a way to answer the question of things like the maintainers of OpenSSL or sudo. One approach is to fund the "project" and let it deal with all of these questions. Another approach would be to fund the people themselves. So, have a faculty of expert software maintainers, vetted by the governance structure of the OSE. Within that faculty, you could have "adjuncts" and "residents" who have a time-bound grant and set of obligations. If they are successful and their work continues to be relevant, they could eventually apply for one of a defined set of "tenured" positions. Those positions would guarantee them independence and a stable source of income in order to continue their role as a maintainer.

The goal of this "faculty" would be sustainable OSS maintenance (which involves both leadership and contribution), rather than publishing research and teaching classes. So, similar overall structure and approach, but differing goals.

[KK7NIL]

> Well, speaking in the case of the US, this would constitute product development which is well outside the scope of what a 501(c)(3) organization should be doing, which could thereby jeopardize their tax status?

Doesn't this apply only to for-profit products? There's plenty of 501c3's with free "products".

[pjmlp]

Which is why app stores and SaaS products thrive, they provide the mechanisms to actually pay for the software one uses.

[whit537]

I love this. Reminds me of MacArthur Foundation's genius grants as well. Linux Foundation has fellows, but it's a small % of budget.

[trueismywork]

They do. Most big breakthrough software even today is made by university and national labs