Databases
StackOverflow2013
Postsdbo
POWhat are the most important points when getting involved in an open source project?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat are the most important points when getting involved in an open source project?
    text
    copied!<p>Disclaimer: I <strong>did</strong> check other questions that seemed related, but this one is much broader and less specific, its goals are completely different, too (so, please do read first before deleting!):</p> <p>Now, while there's "<a href="http://www.catb.org/~esr/faqs/smart-questions.html" rel="nofollow noreferrer">How To Ask Questions The Smart Way</a>", and also "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html" rel="nofollow noreferrer">How to Report Bugs Effectively</a>" (both of which are extremely helpful when interacting with users), there doesn't yet seem to be a similarly comprehensive guide about "how to get successfully involved in an open source project", specifically written for new aspiring contributors.</p> <p>So, what do <strong>you</strong> think, are the most important factors, items and challenges that need to be pointed out in such a guide? </p> <p>The goal would be to come up with a preferably comprehensive list of general guidelines about contributing to open source projects in general, written for new users/contributors who are eager to get involved.</p> <p>Ideally, open source projects could simply point new contributors to the stackoverflow link of this question.</p> <p>Some things for starters:</p> <ul> <li>determine the nature of your contributions (source code, documentation, support/help)</li> <li>determine the project's demands</li> <li>determine the technical requirements when contributing (i.e. build environment)</li> <li>determine the process of properly contributing patches</li> <li>point out the social challenges, limiting factors - need for patience ...</li> </ul>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload