Request for Guidance on Contributing to the Go Project
Alireza Arzehgar
Dear Go Developers,
I am eager to become an open-source contributor to the Go project. While I know that many people explore the Go source code and make minor changes or fix comments, I am looking to make more substantial contributions that are effective, and beneficial to the Go community.
I am unsure how to start working on an issue. Which issues are suitable for beginners? Are there specific modules or packages that need assistance, where I could contribute? Should I explore the source code to identify problems to report and submit CLs? I feel that this approach may not align with how experienced developers typically contribute. I want to act as a genuine developer with a clear goal of advancing the Go project. However, I am uncertain about where to begin and which areas of the codebase require my efforts. Should I focus on learning about sorting algorithms and exploring the standard library to enhance functions, or should I delve into cryptography and examine related packages?
I acknowledge that I am new to this level of development, but I am motivated and confident in my abilities. I understand that my request may come across as presumptuous, but I am seeking a roadmap to help me make meaningful contributions. I would appreciate any tasks or guidance you could provide. I am committed to contributing for the long term and can dedicate time every day. I am willing to read any technical materials or books that may be recommended.
I am here for open source, and I would greatly appreciate your assistance in helping me become a valuable member of this community. My GitHub username is alirezaarzehgar, and my general resume can be found here.
Thank you for your time, attention, and consideration.
Best regards,
Alireza Arzehgar
Jorropo
Hey great interest here.
It's hard to recommend a roadmap because knowledge is not a checklist of items to know.
I would start working on anything even if it feels too hard. You can pick something from the bug tracker, browse the code, or some personal problem you found. There is no shortage of issues.
Anything you can show is a problem to anyone is usually worth fixing. Altho you should know about the compatibility promise and the proposal process. (Tldr adding anything in public API or language is much more procedural than changing something already there.)
If you get really stuck you can ask here or on slack (#contributing channel probably).
--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/golang-dev/3af0d6c5-780e-4f8d-aed9-1c23488befdbn%40googlegroups.com.
Ian Lance Taylor
It's often best to start working on an issue that matters to you. That
provides a natural motivation to investigate how the current code
works and improve it.
Another approach is to take an area that you happen to already know a
lot about. That may suggest ways in which the Go packages fall short.
That said, in the issue tracker we have the label "Suggested" which is
for issues that may be of interest to new contributors. We also have
the label "help wanted", although that tends to be more for issues
that require specialized knowledge or are specific to particular
architectures or ports. Also more generally the label "NeedsFix"
applies to issues that seems like real, if minor, bugs, that need a
fix. And "Documentation" is for issues that are focused on improving
the documentation.
Hope this helps.
Ian
Alireza Arzehgar
Alireza Arzehgar
I will explore the "Suggested" issues to learn about their context and address them as soon as possible.
I hope my efforts will be useful for the Go community.
Respectfully,
Alireza Arzehgar