Add contribution 101

[mbohlool]

Add a contribution document explain the structure of the repo and best practices to start developing. Topics includes (but not limited to):

• What is generated, semi-generated, and manual
• What is base repo and how it is related to this repo
• How to update generated client
• What should be fixed in preprocessing script and what should be an upstream fix
• What should be commit and how many commits my PR should have

[ebbeelsborg]

Perhaps also some guidelines on how and when one should write different types of tests (unit, integration, e2e...)?

[mbohlool]

That is a good idea. I can start something and then we can all contribute to it.

[fejta-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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[micw523]

/remove-lifecycle stale

[roycaihw]

/assign

[roycaihw]

What is generated, semi-generated, and manual
What is base repo and how it is related to this repo

The original design was https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/csi-new-client-library-procedure.md

Also it would be great if we have document around how to run tests in this repo. Ref: kubernetes-client/python-base#126 (comment)

[micw523]

/assign

[scottilee]

@micw523 any update on this and #910?

[micw523]

Thanks for the ping - it will be done - I just returned from a conference and regained my desktop.