Contribute as a Developer call to action is confusing

[RichardLitt]

On the participate as a developer page, the section 'Contribute to an Open Source Project' has an icon saying 'Find out how to Contribute'. Unlike the two other icons, this is not a link, but an email link with a mailto:, which automatically opens a draft email in the client's default mailer.

I'm not sure if this is the best way to encourage contribution. I don't know what to write in that email, or who it is going to.

Something like the contribute.md boilerplate would be a better introduction, in that I could learn whether I can bug triage, develop, fork, etc.

I'm not saying this isn't the right way to do it; just, there may be alternatives that will more actively encourage contribution. What do you think?

[sloria]

@RichardLitt Thank you for the suggestion. You make a good point.

I like the idea of linking to a contributing document. We currently have developer docs, but as it stands, these are more for internal use than for community use. @JeffSpies @erinspace Thoughts on drafting a contribution guide for 3rd-party contributors? Perhaps we revise the index page of our internal dev docs to make them more public-facing?

[RichardLitt]

👍 for linking to a contrib document.