Post #1052190
2026-04-10 17:04 UTC
Replies (4)
-
@lexoyo@framapiaf.org 2026-04-10 17:43
@nycki of course, great initiative Look for issues tagged "good first issue" or "help wanted" Choose a tool you use maybe?
-
@butchrobot@shork.nerdmusic.net 2026-04-10 17:42
@nycki@critters.gay Depends on the project. Here's some advice: Many projects are small and would love contributors to get in there and get their hands dirty, without asking for permission! Other projects are small but want people to be particular about the quality of their contributions and the quality of bug reporting. Some projects (like React or Python or Linux or whatever) are massive and maintainers are stressed and swamped. In general, you don't need to ask for permission to submit quality code. Pick projects that interest you, and start small. Under the Projects tab on GitHub (and other Git hosts), for example, you can see things like Kanban boards or lists of open and active issues. Most large projects also have IRC and Discord, where you can ask questions. But I tend to keep it to the PR stream. Solid PR's make great resume content (beyond just being a great way to hone your craft); they demonstrate effective technical communication AND technical rhetoric!
-
@Wintergr33n@lingo.lol 2026-04-10 17:16
@nycki #GetFediHired
-
@brib@bribstodon.xyz 2026-04-10 17:50
@nycki Couple of things I've done: As @lexoyo suggests, look for any issue tagged with "good first issue", those are likely to be easier to fix.Find a project you like but think there could be improvements for. Submit this improvement in the project's bug tracker, and see how the maintainer responds. You can also submit PRs directly, although some projects prefer you file a bug report first (it depends project per project). Not every project is super responsive to newbies, so it's worth trying out a few and seeing which you like best