[eveningsteps]

Maybe that was explained in Rego's September talk [1] but went over my head, but how does Igalia steer Servo? I can understand that when the project was under Mozilla, there were people primarily from, or tied to Mozilla keeping it afloat. Since Igalia is a _consulting_ agency, I don't suppose they work on code themselves, so what do they do to, well, attract new people and keep existing contributors in the loop?

[1]: https://blogs.igalia.com/mrego/servo-a-new-web-engine-writte...

[Tpt]

Igalia is a quite specific "consulting" agency that employs developers and get contracts from client to implement specific features or fix specific bugs, usually around FOSS. They have people who knows how to contribute to Firefox, Chrome, WebKit, Linux, Mesa... It's the go to company if you want to get something done in these projects when not having the resources for that in house.

For example they work for Valve to make the Radeon drivers better and got a grant to get basic MathML support done in the three major web browsers.

[zipy124]

Igalia are implementation consultants not management consultants. They are who you get in when you need the expert in some field to fix your problem, usually by writing the code themselves. For example if you're writing driver code and you have problems you call them. Or if your Valve and you are having trouble with the linux graphics stack you might call them[1] etc....

[1]: https://www.igalia.com/2025/11/helpingvalve.html

[nicoburns]

> Since Igalia is a _consulting_ agency, I don't suppose they work on code themselves

They absolutely do work on the code themselves. They have a small but active team working on it full time. They are a _software_ consulting agency who's primary product is writing code.

Regarding "steering", there is a Technical Steering Commitee who meets monthly (https://github.com/servo/project/tree/main/governance). Several but by no means all members of the comittee are from Igalia.