![twitch curse client download twitch curse client download](https://mac-cdn.softpedia.com/screenshots/Twitch-Desktop-App_22.jpg)
So it was, I think, several thousand maintainers who had written this open letter to GitHub, published in a dear-GitHub repo. Obviously, everybody’s using GitHub, but have they been taking the steps to really understand on a deeper level what maintainers are doing on their platform, and what they need from GitHub? I think right around then the Dear GitHub letter came out, if you guys remember that… And then around the same time I was talking to GitHub about what is their relationship to open source developers in the broader community. I had a grant from the Ford Foundation to publish Roads and Bridges, which was kind of like my field report at the time. So yeah, I was just sort of like writing about it, didn’t really have a plan. But for all these smaller libraries and projects that kind of go unseen and unnoticed, who’s really taking care of those? It’s critical infrastructure for how the world works and runs today, but so many maintainers feel burned out, stressed out, like they’re having to do this in their spare time, and don’t have any really direct way of working on open source - but it’s something they really love - other than the biggest porjects, like Linux, for example, where you can find a job working on those kinds of things.
![twitch curse client download twitch curse client download](https://cdn.dribbble.com/users/2066835/screenshots/5060951/media/8a09c378b81e0af18e30e237d82d2bb4.jpg)
The big thing we were talking about then was “Everybody is relying on open source at this point.” It’s not just this side hobby thing. So I was just continuing to write, and had a lot of open source maintainers reaching out, and just folks that are peripherally involved in open source. We did our first interview together shortly after that, but I still didn’t really have a plan… I think that was pretty early on. You can follow along if you want.” I got a really great response to that blog post. I wasn’t working anywhere at the time… And then I wrote this blog post that just sort of like announced that I’d been having these interesting conversations with maintainers, and that open source didn’t really seem – it felt like there was just stuff missing from the narrative of how open source was actually working on the ground… And just saying like “I’m gonna be writing and researching about this in public. I was just going around, talking to open source maintainers, trying to just dig into my own research project. Yeah, it start with this open-ended exploration that didn’t really have any goal to it. We talked through the reasons she wrote the book in the first place, Nadia’s thoughts on the future of the internet and the connection of creators to the platforms they build their followings on, and we also talk about the health of projects and communities and the challenges we face internet-at-large as well as right here in our backyard in the open source community. Obviously we go way back with Nadia…and having a chance to now talk with her through all the details of her new book Working in Public, this was a milestone for this show and Jerod and I. That podcast is still getting listens to this very day! If you weren’t listening then, or can’t remember…don’t worry…the back catalog of Request for Commits is still online and subscribe-able via all the podcast ways. If you’re an old school listener you might remember the podcast we produced with Nadia and Mikeal Rogers called Request for Commits.
![twitch curse client download twitch curse client download](https://icon-library.com/images/twitch-desktop-icon/twitch-desktop-icon-14.jpg)
Nadia Eghbal is back and this time she’s talking with us about her new book Working in Public.