text stringlengths 0 2.08k |
|---|
I am doing exactly that right now at home. I'm in a comfortable chair, I'm wearing my hoodie because it's freezing in here, I have some water, and I'm contributing to this podcast. Maybe I'm extremely low maintenance, but if you tick off those basic human needs and people are very comfortable and are starting to do the... |
The main thing is that people have support, which is probably the hardest part. Node Together, for example is teaching people Node.js, and you spend six hours in a room with, obviously, regular breaks; you have a bathroom, you have some food and drink, and then you just support each other. It doesn't have to be fancy. |
**Nadia Eghbal:** \[55:56\] How much hands-on support do you think organizers should expect to give to people that haven't contributed before for an in-person event? Because I was surprised by this. |
**Charlotte Spencer:** You should probably assess the skill levels of the people. Hoodie had done events where it's your first ever contribution, but they've also done events where "Hey, it's just some friends who are quite confident in their abilities hacking together" and a shared goal. So know the comfort level of t... |
Again, we go back to intention. What is your intention? Know that from the beginning; communicate with the project, and then it just comes down to admin, which is difficult... But once you know the intention, it's easier to do. |
**Mikeal Rogers:** Also, a pro tip: if you're targeting new people, be prepared to spend the first hour at least just setting up their environment. |
**Charlotte Spencer:** Oh, yeah. |
**Mikeal Rogers:** That's what new means. New does not mean, "I am here with your entire source code, repository checked out and the build system working." That's not what that means. |
**Charlotte Spencer:** Yeah... |
**Nadia Eghbal:** Very good point. |
**Charlotte Spencer:** The first hour of Node together is like "We're now gonna get set up and we're not gonna move on until people have installed Node. Then we're not gonna move on until people have installed this npm package", because if we let people race ahead, then people get left behind. Things like Rails Girls (... |
Obviously, if you can't make the setup event, then there'll probably be some extra preamble at the beginning of the event trying to help people again. But be prepared to be taking people through a setup. There's absolutely no way that people are gonna be fully prepared. |
I used to do JavaScript workshops, and it was more than a handful of times that people turned up without a laptop. So maybe even having spare laptops where people can just run a repl or something, you know? Disaster planning is something that you learn very quickly when you're an events organizer. Assume that everythin... |
**Mikeal Rogers:** Yeah. |
**Nadia Eghbal:** And then on the maintainers side, it's natural I assume that some people are just gonna try to game the system, submit things that are not great for the sake of saying they contributed. Are there things at events that the event organizers themselves can do to reduce from happening? |
**Charlotte Spencer:** Well, if the event organizers are actually maintainers of the project, you can be like "Well, I'm not accepting this pull request, and here are the reasons why - because all you did was add some spacing in one commit and then take away some spacing in the second commit. That's not a pull request.... |
If you're not a project maintainer, hopefully you'll feel comfortable enough to be like, "Look, we are not expecting you to do something amazing, but we do expect you to do something where the positives outweigh the negatives. Bear in mind that someone has to sit there and review this pull request. And if they've got 5... |
\[59:59\] That should be the tagline of open source - "We're not here to make people be sad, we are here to contribute and be a community." The only time I really see spammy PRs is when we have events like Hacktoberfest and 24 Pull Requests. I know that a few project maintainers are struggling... To some degree I am wi... |
Maintaining a project is a lot of emotional labor, so I have to be the person to be like, "Look, this is not something that I would consider to be something that I can put into this project. I'd appreciate it if you didn't do such pull requests." |
They're obviously just doing it for a T-shirt, but it's really difficult... You have to be that person who weighs the values of other people's work, and that's really dangerous territory. We had this conversation with Andrew Nesbitt's project 24 Pull Requests a year or a year and a half ago, being like "There are lots ... |
So I think in the end people removed pull request counts from all profiles or something like that, and made it so that everybody's contributions were valuable. Because it is not for me to reasons - unless it's obviously spamming - what is and what isn't valuable in general to a project. |
**Nadia Eghbal:** So looking ahead, beyond Your First Pull Request and beyond becoming a full-time regular contributor, what happens when people's personal circumstances change and open source projects are not something they can spend a lot of time on? How can those projects navigate the flux from contributors who, you... |
**Charlotte Spencer:** It can be pretty daunting if you're a small project. When the Hoodie editorial team started, it started over the Christmas period, which was a terrible mistake, because obviously people went "Yeah, this is awesome" and then disappeared for like three weeks; that's going to happen, but we need... ... |
The best thing to do is have someone who can take over from that work, so if this person goes off sick, then Gregor or Jenn step up to write the newsletter for that Friday, or something like that. And I'll make sure to make some time to review whatever comes out of that if the regular person's not there, and things lik... |
\[01:03:51.10\] It's kind of like a tag team, no one's ever gonna be available at all times, so you need -- and this is just a general rule for projects, and even in the workplace... Don't pigeonhole anybody, because if only one person can do the thing -- I think it's called "the bus factor", like "What would happen if... |
In fact, I'd encourage people to spend less time working on open source at points in their life, because it can turn into a second job and it can be very exhausting. But yeah, as a project maintainer, be prepared that people could go away at any point. So if you have abandonment issues, then that's something obviously ... |
Easier with larger projects like Node.js, probably. We've got it quite down well in the editorial team, but there have been times in Hoodie where the only work that's being done is a greenkeeper doing an automatic pull request to update a Node version or something. Lulls are fine. Hopefully, lulls mean that people are ... |
**Mikeal Rogers:** And people should take naps, people who take care of each other; in and of themselves, for sure. \[laughs\] |
**Charlotte Spencer:** Oh, yeah. I'm about to stop giving my open source talk because it's being done now, but my next talk is about self-care, and naps, and stuff. Everytime I give my open source talk, the most quotes phrase on Twitter is "Take more naps", because 1) they're great, and 2) you're probably overworking y... |
**Mikeal Rogers:** That's a great note to leave it on, until we have you come back to talk about self-care for another 90 minutes. |
**Charlotte Spencer:** Oh yeah, I'd love to. |
**Mikeal Rogers:** It will be awesome! Great, thank you so much for coming, this was great! |
**Nadia Eghbal:** Thanks, Charlotte. |
**Charlotte Spencer:** So we're actually ending on me threatening people, that's how we're ending this podcast... \[laughter\] |
**Nadia Eghbal:** Sounds about right! |
**Charlotte Spencer:** I love everybody and I am a very non-violent person. Disclaimer. |
**Mikeal Rogers:** Thanks for coming, it was great! |
• Founding of Brave and its open-source basis |
• History of Netscape and its impact on the browser landscape |
• Creation of JavaScript and its standardization |
• Rise and fall of Netscape, including Microsoft's entry into the market |
• Founding of Mozilla as an escape pod from Netscape's struggles |
• Development of Firefox from Mozilla code |
• Early browser wars and emerging monetization models |
• Implementing tabbed browsing in Phoenix and Chimera |
• Mozilla's Roadmap update in 2003 by Hyatt and the speaker |
• Benefits of open source development: zero cost to users, multiple engines developed in the open (Chromium/Blink, WebKit, Mozilla) |
• History of browser development: Netscape, Microsoft IE, Apple Safari, Google Chrome |
• Business models for browsers: advertising revenue from search deals, neglecting browser development as secondary business focus |
• WebKit's origins as a fork of KHTML and its struggles with HTML compatibility |
• Dave Hyatt's recruitment by Google and Apple's limited investment in WebKit |
• The Techtopus case, an alleged Sherman Clayton antitrust violation involving Google, Apple, Adobe, and Intel colluding to suppress salaries and limit talent poaching |
• Brendan Eich's dinner conversation with Sergey Brin, Larry Page, and Mitchell Baker about Steve Jobs' request to not hire Dave Hyatt |
• Maciej Stachowiak and Darin Adler's role in WebKit and their decision to make it an open-source project |
• The impact of large companies' interests on the development of web technologies |
• Google's use of WebKit for Chrome and its financial relationship with Mozilla through search revenue |
• Google vs Bing and the importance of a default search engine |
• Microsoft's struggle with browser market share and competition from Chrome and Safari |
• The economics of browsers and the cost of maintaining a browser business |
• Brave's sustainability model and revenue streams (search partnerships, microdonations, and ecommerce) |
• The challenges of competing with Google and other established players in the browser market |
• Brave's vision for frictionless small payments |
• Concerns about Google and Facebook's dominance in advertising and data collection |
• The need for browser vendors to prioritize user privacy and security |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.