Create CONTRIBUTING.md

[jfkhoury]

Description

More to come, the first stab at a contribution model that applies to internal and external contributors.

Motivation and Context

We need our contribution model to be crystal clear.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (non-breaking change which does not add functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA or I'm an Adobe employee.
• I have made any necessary test changes and all tests pass.
• I have run the Sandbox successfully.

[carterworks]

Is there value in including instruction on our testing and code quality standards?

It needs to:

• have functional (and maybe unit tests)
• have been tested on alloyio.com and maybe another page, and
• (maybe) include a page on the sandbox or a demo in github.com/adobe/alloy-samples
• Pass formatting and usage standards (npm run format and npm run lint)

[jfkhoury]

Is there value in including instruction on our testing and code quality standards?

It needs to:

• have functional (and maybe unit tests)
• have been tested on alloyio.com and maybe another page, and
• (maybe) include a page on the sandbox or a demo in github.com/adobe/alloy-samples
• Pass formatting and usage standards (npm run format and npm run lint)

Yes, absolutely! Thank you for the suggestions, I will make the change.

[jonsnyder]

Love it!

[jfkhoury]

@carterworks It turned out I did mention the functional tests and sandbox. Can you re-review, please so I can merge this version? Thanks!