Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CONTRIBUTING.MD and CODE_OF_CONDUCT.md #46

Merged
merged 6 commits into from
Jan 17, 2023
Merged

Conversation

dedece35
Copy link
Member

No description provided.

@dedece35 dedece35 requested a review from olegoaer January 13, 2023 23:10
@dedece35 dedece35 marked this pull request as draft January 13, 2023 23:10
@dedece35
Copy link
Member Author

First submition of CONTRIBUTING.md and CODE_OF_CONDUCT.md
nexts step : get starter_pack info and some of my best practices (unit tests, check stringly the code)

@dedece35 dedece35 marked this pull request as ready for review January 15, 2023 22:06
@dedece35 dedece35 requested a review from jhertout January 15, 2023 22:10
@jhertout
Copy link
Contributor

Good start for me. It makes the project more "official".

For the section "Some rules from experience", I imagine you have not finished but for the rule you added "Protections against ClassCast exceptions" why did you not add it directly in Programming Practices"? I am not sure it is a good idea to have an other section that talks about "Programming Practices" after the "Tests" section. I find this confusing and it is like these last rules are less important than the others before while there are not.

@dedece35
Copy link
Member Author

Hi @jhertout,
I've just finished my modifications with my last commit. Please check it.
I keep "Some rules from experience" as last section because, there are all experience tips like "ClassCast exception" or "unit tests".

@jhertout
Copy link
Contributor

Hello @dedece35,

I persist to think that the rules "Protections against ClassCast exceptions" should be in the section "Programming Practices" and "Unit tests" in tests. There are "from experiences" but when I see them here at the end of the document in this section, I feel like there are less important than the others just because there are our rules. But well, it just my opinion and it can stay like this if we want.

An other point: you put a table of contents in the Contributing.md file. I think it is a good idea and maybe we should have one, at least in the CODE_STYLE.md, to quickly remind the rules without having to go through the document.

I quickly go through the English of the files and cannot see mistakes but I am not a specialist.

Except these points, the documents are very clear and give a good entry point for new users (and old users too :)).

@dedece35
Copy link
Member Author

Hi @jhertout,

modifications wanted done.
thank you for review.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@dedece35 dedece35 merged commit f70a661 into main Jan 17, 2023
@dedece35 dedece35 deleted the MD_contributing_code branch January 17, 2023 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants