Remix.run Logo
numbsafari 2 hours ago

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.

EarlKing an hour ago | parent [-]

> 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.

Tenured professors are not engaged in commercial product development.

numbsafari 21 minutes ago | parent [-]

> The goal of this "faculty" would be sustainable OSS maintenance (which involves both leadership and contribution), rather than publishing research and teaching classes.

OSS isn't commercial, per se.

Universities "ship" plenty of "products":

https://www.rcac.purdue.edu/services/hubzero

https://www.scala-lang.org/scala-core/