Bring back "Guidelines for Contributing"

[ksuess]

#3643 (comment)

[netlify]

✅ Deploy Preview for volto ready!

Name	Link
🔨 Latest commit
🔍 Latest deploy log	https://app.netlify.com/sites/volto/deploys/63249a66e68e5866a3be5541
😎 Deploy Preview	https://deploy-preview-3644--volto.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[cypress]

---

Test summary

348 • 0 • 15 • 0

---

Run details

Project	Volto
Status	Passed
Commit	873dc2a
Started	Sep 16, 2022 2:55 PM
Ended	Sep 16, 2022 3:06 PM
Duration	10:27 💡
OS	Linux Ubuntu - 20.04
Browser	Chrome 105

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[stevepiercy]

Thanks for taking this on, @ksuess!

For the record, the original file contributing/index.md was an earlier version of, and therefore redundant to, developer-guidelines/design-principles.md. This restoration moves the content of the original contributing/guidelines.md into developer-guidelines/contributing.md, with some clean up.

Review coming shortly.

[stevepiercy]

We now have a Plone GitHub organization CONTRIBUTING.md. When a repo, including Volto, lacks a CONTRIBUTING.md file in its repo, then this will be displayed. Clearly this is not what we want.

I would suggest that we add a CONTRIBUTING.md file at the root of this repo, that contains only the following:

# Contributing to Volto

See [Contributing to Volto](https://6.dev-docs.plone.org/volto/developer-guidelines/contributing.html).

More information about GitHub Community Health Files, specifically About contributing guidelines.

[stevepiercy]

Lots of obsolete stuff needed changing.

Feedback appreciated.

[stevepiercy]

Replace everything below this comment with the following.

## Code Quality

All pull requests must pass tests, documentation builds, and other code quality checks.
Contributors are strongly encouraged to run these checks locally before creating a pull request.
These checks are enforced automatically on every pull request, so you might as well save time and frustration by doing these checks locally first.

Specifically:

-   {doc}`./linting`
-   {doc}`./testing`
-   {doc}`./acceptance-tests`

If after reading this you become hesitant, don't worry.
You can always create a pull request, mark it as "Draft", and improve the above points later, requesting help from the community.

Welcome to the Plone community, and thank you for contributing!

[stevepiercy]

Thank you! LGTM!

[sneridagh]

Thanks!