Notable by its absence [LWN.net]

Notable by its absence

Posted Jan 4, 2025 19:54 UTC (Sat) by willy (subscriber, #9762)
In reply to: Notable by its absence by alison
Parent article: Some things to expect in 2025

That absolutely could happen! It's happened before; one could include the Lustre folks who, while not closed source, are out of tree and make few contributions to the mainline.

I certainly have had offers to do closed source projects ... and haven't accepted them. I used to get offers to be CTO at various startups which is hilarious from multiple points of view (I would be a terrible CTO). I was also offered the opportunity to work on NVMe firmware.

I'm not saying I can't be bought, but it'd have to be a lot of money or a really interesting project for me to find it worth doing. I did take close to three years off from kernel contributions while I was at Intel to work on NVMe, and I think we can all agree that worked out well for everyone.

There are still a lot of companies who are interested in hiring kernel developers to contribute to upstream. Anecdotally, that seems to be the largest pain point -- they want to get their changes upstream but don't know how to do it. Hiring someone with a track record of getting patches upstream is a good way of solving this problem with money.

to post comments

Notable by its absence

Posted Jan 6, 2025 4:41 UTC (Mon) by tim-day-387 (subscriber, #171751) [Link] (1 responses)

Slightly off-topic, but Lustre is still working (perhaps slowly) towards inclusion in mainline. The code is in much better shape compared to when the client was kicked out of staging. Of course, there's still a lot more to be done. But I'm optimistic Lustre could land in mainline someday.

There's a tracking ticket in the Lustre Jira and an update from James Simmons at LUG24 about the ongoing work for those curious.

Notable by its absence

Posted Jan 6, 2025 16:47 UTC (Mon) by joib (subscriber, #8541) [Link]

Seems the big mistake last time was that the in tree version was more or less a fork occasionally maintained by a few people, whereas users and developers ignored it and continued with the out of tree version.

If they want to make a success of it this time, I think they will need to adopt an upstream first approach.