Redirect users to Contributing Guide Directly

[adithyaakrishna]

Description:

Instead of directing users from https://github.com/kubevirt/user-guide/blob/main/CONTRIBUTING.md to https://github.com/kubevirt/community/blob/main/contributors/contributing.md and from there to https://kubevirt.io/user-guide/appendix/contributing/ - ( which is currently giving a 404 Error. I have fixed the link and created a PR for the same here, kubevirt/community#214 ), how about we do it directly from the user-guide to https://kubevirt.io/user-guide/contributing/

Another option, we can redirect them directly to https://github.com/kubevirt/kubevirt/blob/main/CONTRIBUTING.md

So the users instead of traversing through the maze, will be taken directly from user-guide to https://kubevirt.io/user-guide/contributing/

Fixed by #710

[adithyaakrishna]

@aburdenthehand @petrkotas Would love to know your opinion on this 👀

[cwilkers]

I agree, we should point to a centralized start page for new contributors, and it looks like that is currently https://kubevirt.io/user-guide/contributing/.

For repos that have their own guide (such as kubevirt and user-guide) the individual repo's README.md should point both to the website contributing page and to the local repo contribution guide. The website guide should have a section that branches to all these individual guides in a clear way so potential contributors can get the boilerplate items like CNCF policy, KubeVirt code of conduct, and DCO signoffs in a central place before getting to more specific work.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[aburdenthehand]

@adithyaakrishna Were you still interested in working on this?
To add to Chandler's suggestion, I think pointing to our governance and membership policy documents would be really helpful as well.
I've also created #701 to include a simple style/convention guide to the user-guide contrib page.
All this needn't all be captured in a single PR, but perhaps we can make use of the Projects function of github and track this work there.

[cwilkers]

I think this was fixed in #710, we can close now.