Most of the advice about reading the docs is relevant. GitHub didn't invent those conventions, the whole README/CONTRIBUTING/LICENSE thing has been around for a long time. I remember being so impressed with Perl back in the mid 90's because it was so freakin simple to install, get up and running, and get help when you needed it.
After that, you should email the lead dev(s) and ask how you can contribute. Many projects have a mailing list and that's usually the best place to start.
Comments
Most of the advice about reading the docs is relevant. GitHub didn't invent those conventions, the whole README/CONTRIBUTING/LICENSE thing has been around for a long time. I remember being so impressed with Perl back in the mid 90's because it was so freakin simple to install, get up and running, and get help when you needed it.
After that, you should email the lead dev(s) and ask how you can contribute. Many projects have a mailing list and that's usually the best place to start.