he/him 
I've been thinking about one unavoidable part of company governed open source projects. The power dynamic between company employees and contributors.
Show this thread
-
In a regular open source project, to become a maintainer, there's a long transition between contributing and then eventually having a large say over the project and then being inducted as a maintainer.
Show this thread
But it's common for company employees to join the internal team and become instant maintainers. Not to say they won't work just as hard, but the transition is instant and might not feel as deserved.
-
-
I don't think it's bad, just sets a different tone for those contributing to the project. This also goes for projects governed with a foundation. Sponsorships typically fill the same role, "buying" maintainership.
Show this thread -
Is it that big of a deal? It's a lot more nuanced than I can describe here, and every scenario is different. I'm also typically in the position of maintainer so I could be exaggerating how a new contributor may feel.
Show this thread -
New conversation -
-
-
I’ve thought about this too. More than any amount of competence or particular perspective, I think the root cause for this is that the person is committing a large amount of time to the project, so they’re “worth” investing in. They’re also easier to pull in if something breaks.
-
External contributors usually have much more limited (and non-constant) time to dedicate. That said, I haven’t seen folks try to make explicit space to onboard and include new contributors who *do* have that much time to commit. I’d be very interested to see someone attempt that.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.