3 ms·
First you have to find a project you would like to work on. After that it usually goes like: - Adding New Features Is it a new feature I want to add to the pr
by westoque 13y ago
First you have to find a project you would like to work on. After that it usually goes like:
- Adding New Features
Is it a new feature I want to add to the project? If yes, find out if someone is already doing this feature, and then you have the option to work with them, otherwise, start coding and submit a pull request (or something similar).
- Fixing Bugs
Is it a bug you found while working with the project? If it is, then this is a good time to go inside the code and fix it and do the same pull request cycle.
- Performance Fixes
If you're a curious guy like me, you can go ahead and look through the source code and find places where you think performance can be improved, then start refactoring, after you're done, make sure you publish benchmarks in comparison to the old results.
Have fun coding! :-)
- thewarrior 13y agoHow do i know if I'm skilled enough ?
- s_husso 13y agoI think there is only one way to know, try :) And then just keep trying until you succeed. But I think it is good idea to first talk with the maintainers. At least if you plan on making a 'major' refactoring to the existing code. Start small and continue from there.
- westoque 13y agoJust take a deep breath and dive into the code. You'll be surprised at how skilled you are. :-)
- leviathan 13y agoAs other said, just dive in. And if you're lucky to have your patch criticized and ripped to pieces, you'll learn a lot more from that than you would have if you just work alone. And next time, you'll know to think better about how your code interacts with the rest of the project before submitting another patch. This will give you a lot of insight on how to work nicely with others, without stepping on each others' toes.