Improvements to encourage contribution

[scottdover]

I recently returned from All Things Open and a session around encouraging contributions in open source projects. Here's a short list of various improvements I think we can make.

• Setup a video/screenshare demonstrating how to make a contribution
• Include a code of conduct (example: hhttps://github.com/saucelabs/sauce-docs/blob/main/docs/contributing/code-of-conduct.md)
• Make sure contribution guidelines are clear by stepping through them as if you've never worked on the project
• Right now, it's very unclear what to do with the license agreement: https://github.com/sassoftware/vscode-sas-extension/blob/main/CONTRIBUTING.md#contributor-license-agreement
• https://github.com/sassoftware/vscode-sas-extension/blob/main/CONTRIBUTING.md#get-started: Under this section, ctrl+shift+b doesn't seem necessary (it's covered by launch client) and "Switch to Debug viewlet" may be better labeled "Click 'Run and Debug' in the VSCode activity bar"
• Expand SUPPORT.MD to include links to create a bug or feature request, with some clarification of when to use which option.
• Clarify when to use an issue vs a discussion

I don't think any of these changes are super urgent, but wanted to get your thoughts @scnwwu @clangsmith @jefurbee

[scnwwu]

I'd like to add my findings about contributors appreciation. There're some Github Actions that can automatically build it, for example (some issues though).
But I found that on the project homepage on Github, there's already a built-in Contributors section under the About and Releases sections on the right side bar. Any visitor can click into each contributor or project contribution statistics graph. So I think it's already good enough.

[scnwwu]

Regarding the Get started steps, I agree with you. Just want to provide some background that it was originally copied from vscode official sample. I just looked at it and it also had some updates, for example
microsoft/vscode-extension-samples@ac51835