by mr_o47 on 3/22/24, 3:22 AM with 49 comments
by cdaringe on 3/22/24, 5:51 AM
My recommendation tho of course is to find an existing project you’re passionate about, find their tracker, and dig in! Few softwares are ever truly done. Make one you love even better.
by raybb on 3/22/24, 10:29 AM
I've been volunteering with them on and off for several years and it's always a lovely experience. Their backend is python and frontend mostly from python templates and some Vue for librarian stuff.
Every Tuesday they have a call on Zoom that everyone is welcome to join to share what they're working on, ask for help, and generally chat a bit. It's a great time.
Depending on what you're interested in there's a lot to do from helping build import pipelines for more book entries, writing bots to cleanup data, Performance improvements, better documenting public APIs, etc
I'm currently slowly working on a wikidata integration for their authors page. We also could use some help upgrading to Vue 3, mentors for Google summer of code would be helpful, find of ML projects needing help, moving away from old jQuery libraries, etc.
They can be quite responsive to PRs too like I blogged about here: https://blog.rayberger.org/idea-to-merged-in-less-than-30-mi...
For example, here's a small issue that could use some help on the python side: https://github.com/internetarchive/openlibrary/issues/8928
by m3nu on 3/22/24, 6:23 AM
https://github.com/borgbase/vorta
Or if you join as mentor, you will be supporting the Python Foundation.
If interested, just email the address in my HN profile.
by asicsp on 3/22/24, 4:26 AM
by rustedpy on 3/22/24, 5:48 AM
Small Python library, slowly and steadily growing in use. New contributors, junior devs welcome. Mainly just maintenance work, occasional bug fixes and small feature development. Fine someone looking for casual involvement.
by hgomersall on 3/22/24, 7:02 AM
There are loads of low hanging improvements to the build system that can be made (not least to support 3.12). Contributions gratefully received!
by yogorenapan on 3/22/24, 8:41 AM
by xk3 on 3/24/24, 2:47 PM
I have a lot of ideas for new ones, for example, I want a CLI that can take an artist name like "Theodor Kittelsen" and fetch highest quality public domain images--but I realize any implementation that does this well will be somewhat fragile so I haven't really attempted that yet. Other ideas that I have are often solved by piping output from one of my existing commands to another or adding some optional args to an existing command.
by samsquire on 3/22/24, 11:07 AM
I feel for the author of this comment, you want to help out and work on stuff you have energy at the beginning, I find it easier to write my own code than to get up to speed with someone else's code. Because you lose steam or the activation energy to get the project built and ran and then played with and customised/changed/"hacked on" is a major effort.
I have been thinking a lot on an idea inspired by compiler design: intermediate representations and term rewriting.
If software features were an arbitrary stack of crisscrossing intermediate representations that are rewritten and mutually recursive/referential or parsed or transpiled into actual code, then we could inspect the intermediate representations to work out how things work.
It would be nice to narrow down on a piece of behaviour and see how it works from end-to-end. But in practice, you have an opaque wholeness of a codebase to understand.
A modern system or codebase at a company or mature open source project: it's like those games of wooden sticks or wooden bricks jenga where they're arranged in a pile and you're piling things on-top of things and if you unsettle it slightly, it falls over or doesn't work.
I used a piece of software called OpenGrok which renders a large code base as clickable surfable wiki in the browser. So you can explore codebases.
I have a primitive python SQL database on my github that can execute simple graph cypher queries, simple joins of multiple tables, "dynamodb" style queries and document database queries.
by roschdal on 3/22/24, 7:58 AM
by Keppl8R on 3/22/24, 6:22 AM
Maybe share more info on what you like so we can suggest something you might enjoy?
by not_your_vase on 3/22/24, 5:26 AM
It is however much easier if you contribute to a project that you already know and use personally.
by mihaitodor on 3/22/24, 10:42 AM
by stavros on 3/22/24, 9:51 AM
by Siecje on 3/22/24, 10:30 AM
I have been working on a static site generator which uses Flask.
https://github.com/siecje/htmd
I have been learning trio (async Python library) by implementing beanstalkd.
by alx_m on 3/22/24, 10:01 AM
by a1o on 3/22/24, 10:12 AM
https://github.com/ericoporto/agstoolbox
There are a few number of open issues but if you play with it and find something else you want to add just open an issue and ask about it.
by eysi on 3/22/24, 5:43 AM
I have no experience with the platform myself, just bumped into it by coincidence when my OSS project (written it Typescript) was featured
by BMSR on 3/22/24, 6:56 AM
by mdev23 on 3/22/24, 12:35 PM
by gunnarde on 3/22/24, 10:53 AM
by setheron on 3/22/24, 5:37 AM
I have a project now in Python. Feel free to reach out.
by vram22 on 3/22/24, 7:38 AM
Plus, if you create your own project, you can make it into a product, and try to market and sell it.
It's fun!