About this talk
Interested in trying out Open Source contributing, and can't find a project you're comfortable in?
Maybe you found an issue but the scope is too big to start?
There are other ways to get into Open Source! In this talk, we'll cover non-code contributions, the different types there are, and how to get started in a way that works for you.
Spoiler: This is how I got my start in Open Source!
Talk Recording
Slides
Resources
- Non-code Contributions at Kubernetes
- How to Make Non-Code Contributions
- My slides
- Open Source Etiquette
- Working in Public
- Give back to Open Source, make an impact, build your career!
🌈 Comment below and ask me questions — I might just answer them during my live speaker discussion!
About me
Hi! I'm Ramón — a software engineering and developer relations contractor based in Vienna, Austria.
I've spent the last twelve years being directly involved with small businesses and startups getting their apps off the ground or back in shape!
My main motivation is community. I've worked with software builders both new and experienced and dedicated my time to organising conferences, workshops and other events aimed at helping empower folks in their tech journey.
Feel free to reach out on Twitter!
This on-demand talk is part of CodeLand 2022 — a virtual conference brought to you by CodeNewbie & DEV on June 16 & 17, 2022.
Top comments (62)
For developers who would be new to open source, would contributing to a project via documentation be better as a first step into open source? What are tips of writing documentation for code that does not contain unit tests?
In my experience Angela, that's a good way to start 'cause, even if you do know how to code, maybe you get insecure in the beginning... so, contributing with docs, fixing typos or translation, for instance, could help you get used to the routine of contributing and overcome some apprehensions you may have. In other words, is a great way to settle in!
That said, I'm a newbie myself, but.. IMO, I guess the best way to get to know good documentation is to start reading good documentation yourself haha 😅 I mean, pick up a great and well-known project (it could be sth you're studying) and start reading it, picking up the structure, the language, the style... What do you think?
Thank you for your question and @rafaelbpires for your great reply!
The advice on reading good documentation is great. After all, documentation is supposed to help us solve problems with the project we're using/contributing to. So our fresh perspective is super valuable!
I have a book recommendation! It's called Docs for Developers:
link.springer.com/book/10.1007/978...
Really helped me understand how to not just write but appreciate good documentation.
But absolutely, any questions, concerns or issues you might have are highly appreciated by maintainers that care about good developer experience :)
Wish you all the best!
Hi Ramón, thanks for your talk :)
Do you that is think effective the label "good for beginners" or "easy-start" to mark some issue or PR to review for newbies? How can we encourage newcomers to start in our projects?
Thank you so much, Dennis!
Absolutely a helpful convention to have! These repos can then be listed at places like Good First Issue:
goodfirstissue.dev/
And even moreso, I'd highly encourage, if possible (and energy allowing!!), to have a "mentorship available" or "mentorship provided" tag for issues, so folks know you're happy to pair with them on those!
Thanks for your answer.
In the past I attend to Wikimedia Hackathon (I'm part of Wikimedia movement, Wikipedia, Wikidata, etc), and my question about newcomers is who says "easy-to-start" issues are really easy to start, because in some cases the easy is create a new button or filtering a list, but both tasks needs a lot of knowledge about Mediawiki (triggers, coding practices and gerrit).
We (developers) have some problem to say what is easy 😅
@amitchell05 , I'm with you. I would be more nervous about contributing documentation than code because of how important it can be to newbies like me.
Totally with you Michael. That's why I think our power as newcomers to a project can really be valuable for the onboarding processes of documentation!
Great talk! Can you talk about a few reasons why you're passionate about Ruby on Rails as a community?
Thanks, Gracie!
For me it has to be hands down the community here. When I started getting into tech communities about eight years ago, they welcomed me with open arms, and I was so grateful to be able to pay it forward for others coming in later.
I learned a lot about how to be a good community member, the importance of inclusivity, the joy of learning and of course, teaching!
The events, conferences, the people, the opportunities have been incomparable for me, and I wouldn't be in the place I am in tech without them. 💜
How can open source maintainers make their projects more accessible for non-code contributions at the README level?
Thanks for the question Brian!
I think outlining the need for help in these areas at that level is critical. Same goes for having a set of things for making these inclusive and approachable:
Just some ideas, but I'm sure there are more!
Thank you for such a fun talk that not only educated but treated the material with GR8 care, your presentation was on point and motivating. I wonder what your opinion is in regards to the inclusiveness of the Latino communities in the aspect of both Web/Software Dev. Do you think that the culture needs more leadership from the scientific, engineering, gaming or any related technologies ?
Thank you so much, Pablo!
This is a really good question that I'm unfortunately not fully qualified to answer, as I'm living in Europe, but I'll try my best.
I can only do my best to reflect the best values of the community so that people on my level of privilege can be uplifting, welcoming, inclusive, and not gatekeep others, and minimize harm.
There are exemplary people and communities out there doing work beyond. For example, there's Pachi (did you see her talk? It was outstanding):
community.codenewbie.org/codeland2...
In the Developer Relations world, there is a growing Spanish-speaking community of folks supporting each other:
twitter.com/i/communities/15153900...
All in all, I have to continue to listen, learn, and use my platform to amplify others. As Scott mentioned yesterday, lend my privilege!
I really appreciate your opinion and honesty. It is an honor to hear from you and your positivity, Europe must be an amazing time for developers. I assume that GDPR is the norm for many of your frameworks and policies. Thanks for the resource to the community through that twitter link, I 100% agree that the community should be welcoming, uplifting and inclusive. Here in the U.S. I have not come across groups that have Latino Leadership, I am looking for a grassroots org that welcomes all.
Indeed, lend a privilege...
So many fun ideas surrounding open source outside of coding, Ramon! Thank you very much for your talk. I've been feeling the pressure over the past year due to my lack to output of hobby code and wondering what I've actually contributed on the whole. I really need to reset my mind to what I can do when I'm not working on coding projects. This is such a great reminder!
Thank you so much! I definitely don't want to encourage overdoing it or feeling like you always have to be having output.
Good contributions come from a happy, rested, eager mind, so taking time to rest is also critical!
And remember, there are so many projects out there (including our own) that need that care and that help is so appreciated :)
Amazing talk Ramón. Getting into open source is indeed not as easy as it sounds. But with your great tips, other doors are opening now for everyone to contribute to open source in any way they feel comfortable with.
Thank you so much, Julia!
There are so many facets to open source that need helping with that folks should totally feel free to contribute and make their way into others :)
I'm not sure when I might be ready (at a level of knowledge) to get involved in an open source project in any way.
I'm a big believer in the fact that you're ready the moment you start using a project. Asking questions is a critical part to open source contributions. Your experience onboarding onto a tool or project is what maintainers need the most, after ages being so focussed on the code.
You've absolutely got this! 💜
Thank you so much Ramon. Your energy and excitement is infectious! As a total aside, I just learned about the wild hamsters in the Central Cemetery in Vienna, how cool.
I... did not know about these, thank you so much! 🐹
Tech is not just coding. Rather there are other areas also surrounding it where we can contribute also.
Thanks for this wonderful talk.
You put it better than I could have hoped to, thank you so much! 💜
Always welcome