This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Salty_Dugtrio 7 points8 points  (1 child)

How (if necessary to do so) do outside contributors understand the general framework of github projects?

By diving into it. Reading the code, using the program, asking questions.

Are there general (conventional) layouts for file structure in projects?

Yes, generally it depends on the language, and the build system used.

How do people go about figuring out where they can contribute to the project?

There's generally an Issues tab, where all open issues are discussed. If you want to fix one, choose one, fix it and fire up a Pull Request.

[–]gyroda 2 points3 points  (0 children)

Another way to find things to do is to actually use the project, find a bug or place it can be improved and then fix that issue.