<p>This is more a general software or open source question. It has an excellent answer <a href="https://opensource.stackexchange.com/questions/1143/floss-projects-how-and-where-can-i-start-contributing">here</a>.</p>
<p>In summary the usual rules apply:</p>
<ul>
<li>join a project you are interested in and best need yourself for other purposes</li>
<li>join a project written in a language you like</li>
<li>get acquainted with the project:</li>
<li>join the project-specific communication channels and <em>listen</em></li>
<li>look at the issue tracker and try to tackle a small problem first</li>
<li>ask questions, but don't be demanding or impatient. Often people do OSS work on smaller projects in their own free time.</li>
<li>get acquainted with the expected coding style and adhere to it</li>
<li>ask for feedback on your submissions, and expect initial rejection. Mind they are not personal but meant to keep the project well-organized. Just rinse &amp; repeat. Developers respect is earned by continued and good submissions much more than by grand ideas of what could be done or even should be done (then just do that instead of telling others to do).</li>
<li>Kindness goes a LOOOONG way. Every project is different.</li>
</ul>

CC BY-SA 4.0
2024-02-23T09:43:43.270Z
2024-02-23T09:43:43.270Z
planetmaker
<p>I want to join as a contributor, e.g., making pull or merge requests on GitHub, in an existent open source astronomy project. How do I start? What's the typical scenario?  Writing directly to the repository owners? Knocking some doors?</p>
<p>[This question might be naive or opinion-based, I'm not 100% sure if it's a good question for this SE; I have no problems on closing it]</p>
<p><strong>Context</strong>: I did the astro BSc. but I'm currently working as a back-end dev. As graduate studies are not in my plans for this year, I really <em>need</em> to get my hands in science-related code and I think this would be a great idea.</p>

CC BY-SA 4.0
2024-02-23T06:07:06.413Z
There is nothing different abot asrtonomy here,  I suggest you ask you question to the people at [opensource.se]
James K
CC BY-SA 4.0
2024-02-23T10:22:27.607Z
I’m voting to close this question because it is not about astronomy. While this is a good question, this part of the StackExchange network simply is not the right place to ask this question.
David Hammen
<data-analysis><software><data-pipeline>
How can I join as contributor to open source code on GitHub?
nuwe
# How can I join as contributor to open source code on GitHub?

(Asked by: username_0 on 2024-02-23)

I want to join as a contributor, e.g., making pull or merge requests on GitHub, in an existent open source astronomy project. How do I start? What's the typical scenario? Writing directly to the repository owners? Knocking some doors?

[This question might be naive or opinion-based, I'm not 100% sure if it's a good question for this SE; I have no problems on closing it]

**Context**: I did the astro BSc. but I'm currently working as a back-end dev. As graduate studies are not in my plans for this year, I really *need* to get my hands in science-related code and I think this would be a great idea.

**Tags:** data-analysis, software, data-pipeline
> **Comments:**
> **username_1**: There is nothing different abot asrtonomy here,  I suggest you ask you question to the people at [opensource.se]  
> **username_2**: I’m voting to close this question because it is not about astronomy. While this is a good question, this part of the StackExchange network simply is not the right place to ask this question.  

---

## 1 answers

### Answer by username_3 on 2024-02-23. Score: 4 | Accepted answer

This is more a general software or open source question. It has an excellent answer [here](https://opensource.stackexchange.com/questions/1143/floss-projects-how-and-where-can-i-start-contributing).

In summary the usual rules apply:

* join a project you are interested in and best need yourself for other purposes
* join a project written in a language you like
* get acquainted with the project:
* join the project-specific communication channels and *listen*
* look at the issue tracker and try to tackle a small problem first
* ask questions, but don't be demanding or impatient. Often people do OSS work on smaller projects in their own free time.
* get acquainted with the expected coding style and adhere to it
* ask for feedback on your submissions, and expect initial rejection. Mind they are not personal but meant to keep the project well-organized. Just rinse & repeat. Developers respect is earned by continued and good submissions much more than by grand ideas of what could be done or even should be done (then just do that instead of telling others to do).
* Kindness goes a LOOOONG way. Every project is different.


---

