this post was submitted on 13 Jun 2023
6 points (100.0% liked)

Free and Open Source Software

17926 readers
34 users here now

If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

Hi, I dont know if this is the right comunity to ask, please tell me otherwise. I apologize for my poor English, I'll try my best!

I'm a professional software developer with about 10 years of experience. I have only worked on closed-source enterprise projects throughout my entire career. I am not familiar with the workflow involved in FOSS projects.

Is there a guide that summarizes or documents all the information or standards you need to know to contribute to any FOSS project? This includes the standards for commit messages, tags, and how to propose a new feature or report a bug.

I understand that this may be basic information for many of you, but for me, it feels a bit overwhelming. Also, I think that I'm afraid of working on a codebase that I'm not familiar with. There is also a fear of my own code being judged online. You know, you can never escape imposter syndrome.

I appreciate any info, hopefully I'll be helping on improving some of my favourite apps in the future.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Actually, same here! I used to get overwhelmed by just the thoughts of contributing to GitHub projects too, because I think my code was kinda bad and I didn't want to get judged at. Whenever I thought about repo maintainers/reviewers, I always imagined that they would be all like Linus Torvalds, and I was afraid of getting shamed for my poor code, lol!

I was lucky because I had skills in drawing arts, so I started by contributing icons to an Android icon pack project, which didn't really require coding skills, and is actually something I know I can do. The maintainer of my first contribution turned out to be a very friendly and cool person instead of someone grumpy and direct I always had images of in my head! From there, I gradually learned about the tools and coding a project.

I think the truth is if you want to contribute, even when you think your code isn't up to standard, you really still need to start somewhere. If you don't feel any confident, start forking a small project with some incomplete milestones that you know is something you can do, I think? Some projects that have chatrooms that you can ask if you aren't sure about anything should be a really good place to get started too.

Just remember that not all reviewers are out there to chew on your code, lol.