4 ms·
That's a lot of words, but I'm not sure what I get from them. Here's my take: If you want to contribute to open source, start with using open source software e
by palata 3y ago
That's a lot of words, but I'm not sure what I get from them. Here's my take:
If you want to contribute to open source, start with using open source software even if there is a better proprietary alternative. Only when you use code can you contribute meaningfully to it. Maybe it's a bug fix, maybe it's a small feature you need. Maybe it's a package for your distro. Whatever you need. And if you actually need it, then the best way is to do it in a fork and use it. When you feel like it works for you, offer to contribute it back upstream. It is fine to ask guidance to the maintainer while you do it, but don't expect them to work for you.
Avoid meaningless contributions just for the sake of contributing, like making a package for a distro you don't use ("I use Ubuntu myself, but let me contribute an Arch package I won't ever test"). Or features you don't need but think would be cool. And stop opening 10 feature requests per day: either you code them or you don't, but nobody cares about what you think would be good features. Bug reports are fine if you give proper instructions to reproduce ("sometimes it fails for me plz fix" doesn't qualify as "proper instructions").
And always remember: whatever the maintainer(s) merge becomes their burden, meaning that they don't do it lightly. If they don't want your contribution, don't take it personally: maybe they can't commit to maintaining it, or just don't feel like maintaining it. It's their right, you don't pay them. Just keep your fork in that case.
- gwd 3y agoThis is pretty much exactly what the article says.
- palata 3y agoWe have a pretty different definition of the word "exactly", then :-).
- markx2 3y ago"Only when you use code can you contribute meaningfully to it." I disagree. I started using WordPress in January 2004. I was invited to join Automattic in 2006. I never once wrote any code or even tried. What I did do was a huge amount of Support in the wordpress.org forums, and I write the first guides covering everything from changing your password in the database (there was no other option at the time), how to insert adsense, lots of CSS stuff and more. I know of other current Automattic employees who came that same forum route. Code is needed obviously, but you also need people who will support others in using the program you create. When I started in the forums I would see the then current WP devs replying to questions. Matt in particular would reply, but he replied as a dev would talk to another dev. He was always technically correct but he wasn't really good at explaining. I - and others - could explain in a way that people understood. I would like to think that the very positive and helpful way the forums were run was a helpful step when people were looking to what blogging software to use at that time.
- palata 3y ago>> Only when you use code can you contribute meaningfully to it." > I disagree. I am a bit confused, because then you go on talking about contributing to support and documentation. I never said anything about those, I was talking about code. Only when you use code can you contribute meaningfully to the code. Obviously you don't need to know the codebase to help people use the software. Or did I misunderstand what you are saying?
- markx2 3y agoAh, this is my misunderstanding. Apologies.
- datascienced 3y agoWhat about when the lead maintainer has written 100 issues themselves with clear instructions and tagged with “great first issue” and such like?
- palata 3y agoYeah that's a good question. I am personally not a big proponent of those tags because "great first issues" are simple by definition, but if the maintainers did not fix them it means that they are low priority. Do you really need to fix a simple bug that hasn't been fixed in 2 years and that doesn't affect you? What I have seen is people trying to fix a "great first issue" for the sake of contributing something, and not actually needing it or caring a lot about it. Many times the fix was obviously not sufficient, and I ended up spending more time reviewing and supporting the new contributor than it would have taken me to write the fix myself. That would be fine if those people became regular contributors afterwards, but they didn't, so I basically lost my time. Really, the best contributions I have received were from people who actually needed them. And those people did not need an existing issue (with or without the "great first issue" tag) because they were the ones affected by it. For simple bugs they would just open a PR directly, for others they would open an issue offering to contribute and asking for help. I was always happy to help them of course: my point was that they did not need my guidance to find what to contribute.