What are the most important points when connecting to an open source project?

Question

Disclaimer: I did check other issues that were related to each other, but it is much wider and less specific, its goals are also completely different (so please read first before deleting!):

Now that there is How to Ask Smart Way Questions , as well as How to Report Bugs Effectively (both of which are extremely helpful when interacting with users), it seems that there is no similar comprehensive guide on how to successfully participate in the project open source, specially written for new applicants.

So what do you think are the most important factors, subjects, and issues that you need to point out in such a guide?

The goal is to come up with a preferred complete list of general guidelines for participating in open source projects in general, written for new users / contributors who want to participate.

Ideally, open source projects can simply point out new contributors to the stackoverflow link for this question.

Some things for beginners:

• determine the nature of your contributions (source code, documentation, support / help).
• identify project requirements
• determine technical requirements during application (i.e. assembly conditions)
• Define the patch process.
• point to social problems, limiting factors - the need for patience ...

Answer 1

• Make sure you like the theme, technology used, etc.
• Make sure you can hack it. Joining a project that is extremely domain specific or just technically complex can be demotivating.
• Make sure you have time to contribute. I ritually download (and boot) from open source projects when there is very little activity.

Answer 2

Take a look at creating open source software ( http://producingoss.com/ )

Answer 3

• More on version control
• Documentation can be a good way to get started. It helps you learn existing things from a usability point, at least
• Learn about the community around the project. Will they bring new opportunities for beginners? If not, then you will have to look for corrections in some or several existing errors.

I did not mention the technical requirements of the project, since you want to contribute to the project if you have already read and understood them.

Answer 4

I think that leadership could be done quite easily, and not even for too long. In fact, I'll hit him now:

So, you have decided that you want to participate in an open source project, but do not know where to start. You're not alone! You are what is known as wannabe. Indeed. Code is available. Is free. Use the program. Read the code. To repair things. Write a new code. Scratch your own itch. If you are not already doing this, then honestly answer yourself silently why you are not doing this. If you used the program and did not jump up and the screams should be fixed, then you are either from your league or not a coder at heart. The end.