|
|
|
|
|
by radicality
1420 days ago
|
|
I spent many years at FB, but no longer there, but that doesn’t even sound like a ‘special case’? Every engineer at Fb has access to pretty much all the code, and after an internal code review for your code change, you can get it committed to the internal repos.
For open source things, something syncs the external and internal changes ocassionaly I think. I imagine the problem here was that now external people can’t comment on internal PRs etc. I even remember some of my internal commits making it into FBs open source code on GitHub, even though at the time I had no idea that this specific area of FBs codebase is open source. |
|
This process is problematic, though. The "special case" is the standard process at FB: to make external contributors second class citizens.
They have their reasons, but doing this pushes the locus of discussion and action to the place where work happens fastest: inside the company. That means that the interests of FB engineers drive the project; in other words, not open.
That argument is I'm sure open to some logical nitpicking. But the evidence speaks for itself: Facebook open source projects aren't responsive to the outside community, and they language when FB's priorities shift. So their strategy has been pennywise, pound foolish in my view: they get the short term benefits of an "open" project, but they're incapable of actually being good open source custodians.