talk description wording
what do yall think about this talk description ?
Open-Source maintainers and team leads, let's face it: bringing people into a project is way harder than it looks, even more so in the open-source space where maintainers can't help everyone individually. As maintainers and active team members, we must make this process as easy as possible for first-time open source contributors and new team members. We'll go over the most common problems faced by first time contributors and see how to address them to make your projects more accessible.
10 Replies
It's very formal and (probably) appropriate for the setting. I don't like it :p
But me not liking it doesn't mean it's not good
who would you phrase it ?
like what part of it do you think is too much formalititatizazism
It reads as very corporate. If that's the target audience then job well done. But you didn't tell us anything about what it's for or who it's aimed at
"Open-Source maintainers and team leads" is not aim enought ?
Casual open source? Corporate-backed open source? Dude in their parent's basement in Idaho open source?
all of them
onboarding sucks everywhere
Remember that .NET is open source, which is a lot different than 11ty
yeah, but I'm pretty sure contributing to them is both as hard, not in the same ways but for the same reasons
- inexistant contribution guide
- undocumented tooling
- hidden processes
- poor or inexistant initial setup guides
- unclear code style policies
My point is that it looks like you're trying to talk to a bunch of MS reps about onboarding new contributors to .NET. It's very formal and corporate. Which is great if that's the audience. But "all open source maintainers" is piss poor targeting, since that's such a large group with little overlap as to be a worthless target "audience".
but that is the target audience, the projects themselves might be all different, but that doesn't make the premise less true, on the contrary even