Add contributing guidelines and issue template

[fershad]

This PR adds:

• A project license file
• Project contributing guidelines
• An issue template for proposing new methodologies for addition to the DIST Methodologies Map

[cloudflare-workers-and-pages]

Deploying dist with    Cloudflare Pages

Latest commit:	c158ee2
Status:	✅  Deploy successful!
Preview URL:	https://1ff9996f.dist-1ii.pages.dev
Branch Preview URL:	https://fi-contributing.dist-1ii.pages.dev

View logs

[hanopcan]

Hey @fershad

Thanks so much for these! Do I understand correctly that these are all files inside the github repo rather than content on the website? Which is fine, just want to make sure I haven't misunderstood the context in which I'm reviewing these 😁

On the license, we mention the license in the footer of the website. Do you think we should link the two so they cross-reference each other?

Issue template looks great and I think we can ship.

Contribution page looks good. Again, I'm wondering how to cross-reference a bunch of this text with the /get-involved page. Where is the canonical set of instructions/guidance. Do we need one?

Whatever the response to the above comments, I don't think they are blockers. More thoughts on opportunities to reduce burdens of maintaining the same content in multiple places (which sometimes in fairness, you just can't avoid).

I think these good to ship and I think we should get them out into the wild! I'll leave you to merge the PR and consider the above comments. Cheers Fish!

[fershad]

@hanopcan these files live in the repository, and for most open source projects are things that you'd expect to find alongside the code.

• License: The license file contains the full content of the CC BY-SA 4.0 license. It just makes it super clear under which license this project is being made public, and can be thought of as a supplement to the links at the bottom of the website. I'm not sure what you mean by "linking the two" - are you thinking put a link to the same web page that is linked to from the footer?

• Contribution: This is again a supplement to the content on the Get Involved & Methodologies Map pages. The file in this PR governs general contributions to the project, rather than specifically for the Methodologies Map (though there is a section for that process as well). The purpose is again to guide people on how to contribute to the project overall via the GitHub repo (i.e. creating issues, what templates to use etc.)

Does this clear it up?