added some contributions guide

[RohitRathore1]

No description provided.

[bkamins]

Ah - and you might add that if a PR is not finished yet and SHOULD NOT be reviewed yet then it should be opened as DRAFT (in this way I will know I can ignore such PR until it is made non-draft or the author asks for a review).

[bkamins]

Also maybe mention somewhere (if it is not mentioned yet) that all PRs and issues should be made against the main branch not against the current release as this is one of the most common problems.

[RohitRathore1]

Also maybe mention somewhere (if it is not mentioned yet) that all PRs and issues should be made against the main branch not against the current release as this is one of the most common problems.

Ohh, okay. I am making the required changes. Thanks for reviewing

[bkamins]

Code organization comments before I review again:

1. Can you please add line breaks to very long lines?
2. Ca you please use punctuation at the end of lines (in particular when making bulleted lists)

[RohitRathore1]

Made required changes.

[RohitRathore1]

Fixed errors which were requested by @nalimilan

[bkamins]

For a reference: you can assume that @nalimilan noticed that. We need to wait for his approval. In general expect that things take several days when working on PRs (so this means that it is good to have several things in parallel in the pipeline if you can spend more time on working on the package).

[nalimilan]

Fine with me if it's OK for you @bkamins.

[bkamins]

Thank you!