3 ms·
A quick google search yielded this list of open source projects written in Python: http://pythonsource.com/ http://pythonsource.com/ I have no idea what size a
by dbingham 16y ago
A quick google search yielded this list of open source projects written in Python: http://pythonsource.com/ http://pythonsource.com/
I have no idea what size any of them are, and whether or not they are looking for contributors.
More important than either of those considerations is whether or not you - to quote another recent discussion here - "give a damn" about them. Are you interested in this project? Would you use the final product? Can you think of ways to improve the final product?
If the answer to any of those questions is no, then you probably shouldn't be working on that project. Look for a different one.
If you're really set on Python, then go down that list and check out each project. Check out the program, app, whatever and see if it excites you. Is it something you would use early and often? Do new feature ideas start spilling out of you brain as soon as you open it up? That's the project for you to work on.
- apotheon 16y agoAgreed. I'd say a good approach would go something like this: 1. have a taste for using simple, clean tools 2. when in need of software, see if you can find simple, clean tools that do what you need 3. prefer those that use languages you know or would like to learn 4. use them for a while and see if you like them and develop a sense of what kind of contributions you could make 5. check out the source to see if you can get a clear enough concept of it to develop some good patches If all of that works out, submit your patches. Voila: you're an open source contributor.