From 5c94520e36031b5ac8a8b0e15e5312c649c225e8 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 14:13:29 +0530
Subject: [PATCH 01/17] Create CONTRIBUTING.md
---
CONTRIBUTING.md | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
create mode 100644 CONTRIBUTING.md
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 00000000..25b380c8
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,35 @@
+# Welcome to DiCRA contributing guide
+Thank you for investing your time in contributing to our project!✨
+
+Read our Code of Conduct to keep our community approachable and respectable.
+In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.
+
+## New Contributor guide
+Familiarize yourself with the project's goals and objectives.
+
+#### For Technical contributions,
+
+ - Install Python and relevant libraries.
+ - Preferably, set up a virtual environment. Using a virtual environment in Python can help to isolate dependencies, improve reproducibility, and enhance security by allowing you to install
+ and manage packages and dependencies needed for a specific project in a separate location from your global Python environment.
+
+
+## Making Contributions
+
+Submit contributions through pull requests
+Include unit tests with code contributions
+Consider opening an issue to discuss significant changes
+Follow coding standards and style guidelines
+Include screenshots or mockups for changes to the user interface
+Document new features and functionality
+Adhere to the code of conduct
+III. Submitting a Pull Request
+
+Include a clear and concise description of changes
+Link to relevant issues
+Address comments and suggestions during the review process
+Resolve merge conflicts (if necessary)
+IV. After Your Pull Request is Merged
+
+Your contributions will be publicly visible on the GitHub repository
+Stay involved and continue to look for ways to contribute to the project.
From 3d679f8ceb7bb287708e8a73c252466c895214c1 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 14:17:45 +0530
Subject: [PATCH 02/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 25b380c8..cfa31233 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -5,7 +5,7 @@ Read our Code of Conduct to keep our community approachable and respectable.
In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.
## New Contributor guide
-Familiarize yourself with the project's goals and objectives.
+Familiarize yourself with the project's goals and objectives. Go through [ReadMe](https://github.com/shubhamcodez/dicra/blob/main/readme.md) and [Code of Conduct](https://github.com/shubhamcodez/dicra/blob/main/CODE_OF_CONDUCT.md) to better understand our expectations of standard and enforcement guidelines.
#### For Technical contributions,
From 67f52e0d79e53a54f587381b814727668c556f1a Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 14:24:41 +0530
Subject: [PATCH 03/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index cfa31233..f8dcdb59 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -15,15 +15,17 @@ Familiarize yourself with the project's goals and objectives. Go through [ReadMe
## Making Contributions
+
+- Submit contributions through pull requests: Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors. To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes. Then, push your changes to your fork and submit a pull request from your branch to the upstream repository. Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
+ - Consider opening an issue to discuss significant changes: If you are considering making significant changes to the codebase, it is a good idea to open an issue to discuss your proposed changes before creating a pull request. This will allow you to get feedback and input from the project's maintainers and other contributors, and can help ensure that your changes align with the project's goals and direction.
+
+- Follow coding standards and style guidelines: To help ensure that the codebase is consistent and easy to read, make sure to follow the project's coding standards and style guidelines. This may include things like using a specific indentation style, following naming conventions, and commenting your code to make it easier to understand.
+
+- Document new features and functionality: If you are adding new features or functionality to the codebase, make sure to document them thoroughly. This can include adding new sections to the documentation, as well as updating existing documentation to reflect the changes. Be sure to include brief comments and descriptions of your code to help other contributors understand how it works and how it fits into the overall project.
+- Adhere to the code of conduct: It is important to be respectful and considerate of others when interacting with the project and its community. Make sure to follow the repository's code of conduct to ensure that all interactions are positive and constructive. If you have any questions or concerns, don't hesitate to reach out to the project's maintainers or other community members for help or guidance.
+
-Submit contributions through pull requests
-Include unit tests with code contributions
-Consider opening an issue to discuss significant changes
-Follow coding standards and style guidelines
-Include screenshots or mockups for changes to the user interface
-Document new features and functionality
-Adhere to the code of conduct
-III. Submitting a Pull Request
+## Submitting a Pull Request
Include a clear and concise description of changes
Link to relevant issues
From 3de58d8fc312f2869ab12becfd1290dfeb7da9ae Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 14:26:21 +0530
Subject: [PATCH 04/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f8dcdb59..b74a945b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -16,13 +16,13 @@ Familiarize yourself with the project's goals and objectives. Go through [ReadMe
## Making Contributions
-- Submit contributions through pull requests: Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors. To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes. Then, push your changes to your fork and submit a pull request from your branch to the upstream repository. Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
- - Consider opening an issue to discuss significant changes: If you are considering making significant changes to the codebase, it is a good idea to open an issue to discuss your proposed changes before creating a pull request. This will allow you to get feedback and input from the project's maintainers and other contributors, and can help ensure that your changes align with the project's goals and direction.
-
-- Follow coding standards and style guidelines: To help ensure that the codebase is consistent and easy to read, make sure to follow the project's coding standards and style guidelines. This may include things like using a specific indentation style, following naming conventions, and commenting your code to make it easier to understand.
-
-- Document new features and functionality: If you are adding new features or functionality to the codebase, make sure to document them thoroughly. This can include adding new sections to the documentation, as well as updating existing documentation to reflect the changes. Be sure to include brief comments and descriptions of your code to help other contributors understand how it works and how it fits into the overall project.
-- Adhere to the code of conduct: It is important to be respectful and considerate of others when interacting with the project and its community. Make sure to follow the repository's code of conduct to ensure that all interactions are positive and constructive. If you have any questions or concerns, don't hesitate to reach out to the project's maintainers or other community members for help or guidance.
+- **Submit contributions through pull requests:** Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors. To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes. Then, push your changes to your fork and submit a pull request from your branch to the upstream repository. Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
+- **Consider opening an issue to discuss significant changes:** If you are considering making significant changes to the codebase, it is a good idea to open an issue to discuss your proposed changes before creating a pull request. This will allow you to get feedback and input from the project's maintainers and other contributors, and can help ensure that your changes align with the project's goals and direction.
+
+- **Follow coding standards and style guidelines:** To help ensure that the codebase is consistent and easy to read, make sure to follow the project's coding standards and style guidelines. This may include things like using a specific indentation style, following naming conventions, and commenting your code to make it easier to understand.
+
+- **Document new features and functionality:** If you are adding new features or functionality to the codebase, make sure to document them thoroughly. This can include adding new sections to the documentation, as well as updating existing documentation to reflect the changes. Be sure to include brief comments and descriptions of your code to help other contributors understand how it works and how it fits into the overall project.
+- **Adhere to the code of conduct:** It is important to be respectful and considerate of others when interacting with the project and its community. Make sure to follow the repository's code of conduct to ensure that all interactions are positive and constructive. If you have any questions or concerns, don't hesitate to reach out to the project's maintainers or other community members for help or guidance.
## Submitting a Pull Request
From 977515bc2c15e7655dc6e440a2e7d9bf32d26a4e Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 14:37:42 +0530
Subject: [PATCH 05/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 35 +++++++++++++++++++++--------------
1 file changed, 21 insertions(+), 14 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b74a945b..abf2843b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,5 +1,5 @@
# Welcome to DiCRA contributing guide
-Thank you for investing your time in contributing to our project!✨
+Thank you for investing your time in contributing to our project!
Read our Code of Conduct to keep our community approachable and respectable.
In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.
@@ -16,22 +16,29 @@ Familiarize yourself with the project's goals and objectives. Go through [ReadMe
## Making Contributions
-- **Submit contributions through pull requests:** Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors. To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes. Then, push your changes to your fork and submit a pull request from your branch to the upstream repository. Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
-- **Consider opening an issue to discuss significant changes:** If you are considering making significant changes to the codebase, it is a good idea to open an issue to discuss your proposed changes before creating a pull request. This will allow you to get feedback and input from the project's maintainers and other contributors, and can help ensure that your changes align with the project's goals and direction.
+
+
- Submit contributions through pull requests: Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors. To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes. Then, push your changes to your fork and submit a pull request from your branch to the upstream repository. Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
+
+- Consider opening an issue to discuss significant changes: If you are considering making significant changes to the codebase, it is a good idea to open an issue to discuss your proposed changes before creating a pull request. This will allow you to get feedback and input from the project's maintainers and other contributors, and can help ensure that your changes align with the project's goals and direction.
-- **Follow coding standards and style guidelines:** To help ensure that the codebase is consistent and easy to read, make sure to follow the project's coding standards and style guidelines. This may include things like using a specific indentation style, following naming conventions, and commenting your code to make it easier to understand.
+
+
- Follow coding standards and style guidelines: To help ensure that the codebase is consistent and easy to read, make sure to follow the project's coding standards and style guidelines. This may include things like using a specific indentation style, following naming conventions, and commenting your code to make it easier to understand.
-- **Document new features and functionality:** If you are adding new features or functionality to the codebase, make sure to document them thoroughly. This can include adding new sections to the documentation, as well as updating existing documentation to reflect the changes. Be sure to include brief comments and descriptions of your code to help other contributors understand how it works and how it fits into the overall project.
-- **Adhere to the code of conduct:** It is important to be respectful and considerate of others when interacting with the project and its community. Make sure to follow the repository's code of conduct to ensure that all interactions are positive and constructive. If you have any questions or concerns, don't hesitate to reach out to the project's maintainers or other community members for help or guidance.
+
+- Document new features and functionality: If you are adding new features or functionality to the codebase, make sure to document them thoroughly. This can include adding new sections to the documentation, as well as updating existing documentation to reflect the changes. Be sure to include brief comments and descriptions of your code to help other contributors understand how it works and how it fits into the overall project.
+
+- Adhere to the code of conduct: It is important to be respectful and considerate of others when interacting with the project and its community. Make sure to follow the repository's code of conduct to ensure that all interactions are positive and constructive. If you have any questions or concerns, don't hesitate to reach out to the project's maintainers or other community members for help or guidance.
+
## Submitting a Pull Request
+
+ - Include a clear and concise description of changes in the pull request
+ - Link to relevant issues in the pull request description
Address comments and suggestions during the review process
+ - Resolve merge conflicts, if necessary, before the pull request can be merged
+
-Include a clear and concise description of changes
-Link to relevant issues
-Address comments and suggestions during the review process
-Resolve merge conflicts (if necessary)
-IV. After Your Pull Request is Merged
-
-Your contributions will be publicly visible on the GitHub repository
-Stay involved and continue to look for ways to contribute to the project.
+## After Your Pull Request is Merged
+Congratulations you have successfully contributed to DiCRA.✨
+Your contributions will be publicly visible on the GitHub repository once the merge is complete.
From 40132f965fbd3e995e3ea93335b1ce0280245df2 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 14:46:39 +0530
Subject: [PATCH 06/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index abf2843b..662c2af6 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -34,7 +34,7 @@ Familiarize yourself with the project's goals and objectives. Go through [ReadMe
## Submitting a Pull Request
- Include a clear and concise description of changes in the pull request
- - Link to relevant issues in the pull request description
Link to relevant issues in the pull request description
- Address comments and suggestions during the review process
- Resolve merge conflicts, if necessary, before the pull request can be merged
From 04214f333be0fd5a76453e72952895f833d35ec7 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 14:58:13 +0530
Subject: [PATCH 07/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 662c2af6..8a9cd6a1 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -5,19 +5,22 @@ Read our Code of Conduct to keep our community approachable and respectable.
In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.
## New Contributor guide
-Familiarize yourself with the project's goals and objectives. Go through [ReadMe](https://github.com/shubhamcodez/dicra/blob/main/readme.md) and [Code of Conduct](https://github.com/shubhamcodez/dicra/blob/main/CODE_OF_CONDUCT.md) to better understand our expectations of standard and enforcement guidelines.
+Familiarize yourself with the project's goals and objectives. Go through [ReadMe](https://github.com/shubhamcodez/dicra/blob/main/readme.md) and [Code of Conduct](https://github.com/shubhamcodez/dicra/blob/main/CODE_OF_CONDUCT.md) to better understand our expectations of standard and enforcement guidelines. If you have never worked with Github, I would suggest Git for [Beginners](https://youtu.be/RGOj5yH7evk) or reading the github [docs](https://docs.github.com/en/get-started).
-#### For Technical contributions,
+#### Technical contributions,
- Install Python and relevant libraries.
- - Preferably, set up a virtual environment. Using a virtual environment in Python can help to isolate dependencies, improve reproducibility, and enhance security by allowing you to install
- and manage packages and dependencies needed for a specific project in a separate location from your global Python environment.
+ - Preferably, set up a virtual environment. Using a virtual environment in Python can help to isolate dependencies, improve reproducibility, and enhance security by allowing you to install and manage packages and dependencies needed for a specific project in a separate location from your global Python environment.
+## Report bugs, add suggestions using Github's issues
+We use GitHub issues to track public bugs, take suggestions and feedback. Report bugs, improvement suggestions by opening a new [issue](https://github.com/undpindia/dicra/issues); it's that easy!
+
## Making Contributions
+While direct merges work great as we work with independent python notebooks, it can get messy and violate our standards sometimes. Here are some recommended guidelines, we insist you follow if you are contributing to the repository for the first time.
-- Submit contributions through pull requests: Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors. To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes. Then, push your changes to your fork and submit a pull request from your branch to the upstream repository. Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
+- Submit contributions through pull requests: Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors. To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes. Then, push your changes to your fork and submit a pull request from your branch to the upstream repository. Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations. Direct merges work fine too, just make sure you have the permission to do it.
- Consider opening an issue to discuss significant changes: If you are considering making significant changes to the codebase, it is a good idea to open an issue to discuss your proposed changes before creating a pull request. This will allow you to get feedback and input from the project's maintainers and other contributors, and can help ensure that your changes align with the project's goals and direction.
@@ -40,5 +43,5 @@ Familiarize yourself with the project's goals and objectives. Go through [ReadMe
## After Your Pull Request is Merged
-Congratulations you have successfully contributed to DiCRA.✨
+Congratulations you have successfully contributed to DiCRA.✨
Your contributions will be publicly visible on the GitHub repository once the merge is complete.
From b62e67cee984f52b465184f74056ce4a409939be Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 15:00:06 +0530
Subject: [PATCH 08/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8a9cd6a1..bce0b519 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -20,7 +20,11 @@ We use GitHub issues to track public bugs, take suggestions and feedback. Report
While direct merges work great as we work with independent python notebooks, it can get messy and violate our standards sometimes. Here are some recommended guidelines, we insist you follow if you are contributing to the repository for the first time.
-- Submit contributions through pull requests: Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors. To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes. Then, push your changes to your fork and submit a pull request from your branch to the upstream repository. Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations. Direct merges work fine too, just make sure you have the permission to do it.
+- Submit contributions through pull requests: Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors.
+
- To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes.
+ - Then, push your changes to your fork and submit a pull request from your branch to the upstream repository.
+ - Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
+ - Direct merges work fine too, just make sure you have the permission to do it.
- Consider opening an issue to discuss significant changes: If you are considering making significant changes to the codebase, it is a good idea to open an issue to discuss your proposed changes before creating a pull request. This will allow you to get feedback and input from the project's maintainers and other contributors, and can help ensure that your changes align with the project's goals and direction.
From 5fdd64a31abbcfa4f93c6927dd5fc848ec6752c2 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 15:00:41 +0530
Subject: [PATCH 09/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index bce0b519..2f92ae2e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -20,7 +20,7 @@ We use GitHub issues to track public bugs, take suggestions and feedback. Report
While direct merges work great as we work with independent python notebooks, it can get messy and violate our standards sometimes. Here are some recommended guidelines, we insist you follow if you are contributing to the repository for the first time.
-- Submit contributions through pull requests: Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors.
+
- **Submit contributions through pull requests:** Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors.
- To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes.
- Then, push your changes to your fork and submit a pull request from your branch to the upstream repository.
- Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
From 05b2186bf9a831cf7f4c636a67d732029e0cb198 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 15:01:28 +0530
Subject: [PATCH 10/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2f92ae2e..10afde9f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -20,7 +20,7 @@ We use GitHub issues to track public bugs, take suggestions and feedback. Report
While direct merges work great as we work with independent python notebooks, it can get messy and violate our standards sometimes. Here are some recommended guidelines, we insist you follow if you are contributing to the repository for the first time.
-- **Submit contributions through pull requests:** Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors.
+
- **Submit contributions through pull requests**: Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors.
- To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes.
- Then, push your changes to your fork and submit a pull request from your branch to the upstream repository.
- Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
From 7104af2c228d800f31d805e9a094f1bc7a2fc632 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 15:05:05 +0530
Subject: [PATCH 11/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 10afde9f..e5102fe3 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -5,7 +5,7 @@ Read our Code of Conduct to keep our community approachable and respectable.
In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.
## New Contributor guide
-Familiarize yourself with the project's goals and objectives. Go through [ReadMe](https://github.com/shubhamcodez/dicra/blob/main/readme.md) and [Code of Conduct](https://github.com/shubhamcodez/dicra/blob/main/CODE_OF_CONDUCT.md) to better understand our expectations of standard and enforcement guidelines. If you have never worked with Github, I would suggest Git for [Beginners](https://youtu.be/RGOj5yH7evk) or reading the github [docs](https://docs.github.com/en/get-started).
+Familiarize yourself with the project's goals and objectives. Go through [ReadMe](https://github.com/shubhamcodez/dicra/blob/main/readme.md) and [Code of Conduct](https://github.com/shubhamcodez/dicra/blob/main/CODE_OF_CONDUCT.md) to better understand our expectations of standard and enforcement guidelines. It is important to be respectful and considerate of others when interacting with the project and its community. Make sure to follow the repository's code of conduct to ensure that all interactions are positive and constructive. If you have any questions or concerns, don't hesitate to reach out to the project's maintainers or other community members for help or guidance. If you have never worked with Github, I would suggest Git for [Beginners](https://youtu.be/RGOj5yH7evk) or reading the github [docs](https://docs.github.com/en/get-started).
#### Technical contributions,
@@ -20,21 +20,23 @@ We use GitHub issues to track public bugs, take suggestions and feedback. Report
While direct merges work great as we work with independent python notebooks, it can get messy and violate our standards sometimes. Here are some recommended guidelines, we insist you follow if you are contributing to the repository for the first time.
-- **Submit contributions through pull requests**: Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors.
+
- Submit contributions through pull requests:
+ Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors.
- To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes.
- Then, push your changes to your fork and submit a pull request from your branch to the upstream repository.
- Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
- Direct merges work fine too, just make sure you have the permission to do it.
-- Consider opening an issue to discuss significant changes: If you are considering making significant changes to the codebase, it is a good idea to open an issue to discuss your proposed changes before creating a pull request. This will allow you to get feedback and input from the project's maintainers and other contributors, and can help ensure that your changes align with the project's goals and direction.
+
- Consider opening an issue to discuss significant changes:
+ If you are considering making significant changes to the codebase, it is a good idea to open an issue to discuss your proposed changes before creating a pull request. This will allow you to get feedback and input from the project's maintainers and other contributors, and can help ensure that your changes align with the project's goals and direction.
-- Follow coding standards and style guidelines: To help ensure that the codebase is consistent and easy to read, make sure to follow the project's coding standards and style guidelines. This may include things like using a specific indentation style, following naming conventions, and commenting your code to make it easier to understand.
+
- Follow coding standards and style guidelines:
+ To help ensure that the codebase is consistent and easy to read, make sure to follow the project's coding standards and style guidelines. This may include things like using a specific indentation style, following naming conventions, and commenting your code to make it easier to understand.
-- Document new features and functionality: If you are adding new features or functionality to the codebase, make sure to document them thoroughly. This can include adding new sections to the documentation, as well as updating existing documentation to reflect the changes. Be sure to include brief comments and descriptions of your code to help other contributors understand how it works and how it fits into the overall project.
-
-- Adhere to the code of conduct: It is important to be respectful and considerate of others when interacting with the project and its community. Make sure to follow the repository's code of conduct to ensure that all interactions are positive and constructive. If you have any questions or concerns, don't hesitate to reach out to the project's maintainers or other community members for help or guidance.
+- Document new features and functionality:
+ If you are adding new features or functionality to the codebase, make sure to document them thoroughly. This can include adding new sections to the documentation, as well as updating existing documentation to reflect the changes. Be sure to include brief comments and descriptions of your code to help other contributors understand how it works and how it fits into the overall project.
From fcb2abcfdaadb09f7dc37c9ce5fae890087e16aa Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 15:06:20 +0530
Subject: [PATCH 12/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e5102fe3..dfd1747d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -13,7 +13,7 @@ Familiarize yourself with the project's goals and objectives. Go through [ReadMe
- Preferably, set up a virtual environment. Using a virtual environment in Python can help to isolate dependencies, improve reproducibility, and enhance security by allowing you to install and manage packages and dependencies needed for a specific project in a separate location from your global Python environment.
-## Report bugs, add suggestions using Github's issues
+## Provide feedback and report bugs using Github's issues
We use GitHub issues to track public bugs, take suggestions and feedback. Report bugs, improvement suggestions by opening a new [issue](https://github.com/undpindia/dicra/issues); it's that easy!
## Making Contributions
@@ -22,10 +22,13 @@ While direct merges work great as we work with independent python notebooks, it
- Submit contributions through pull requests:
Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors.
- - To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes.
+
+ - To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes.
- Then, push your changes to your fork and submit a pull request from your branch to the upstream repository.
- Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
- - Direct merges work fine too, just make sure you have the permission to do it.
+ - Direct merges work fine too, just make sure you have the permission to do it.
+
+
- Consider opening an issue to discuss significant changes:
If you are considering making significant changes to the codebase, it is a good idea to open an issue to discuss your proposed changes before creating a pull request. This will allow you to get feedback and input from the project's maintainers and other contributors, and can help ensure that your changes align with the project's goals and direction.
From 721e39c69167bd897d9cf0c39e94089e7d384564 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 15:10:14 +0530
Subject: [PATCH 13/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index dfd1747d..32e6c2cb 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -22,12 +22,14 @@ While direct merges work great as we work with independent python notebooks, it
- Submit contributions through pull requests:
Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors.
-
- - To submit a pull request, first make sure that you have forked the repository and created a separate working branch for your changes.
- - Then, push your changes to your fork and submit a pull request from your branch to the upstream repository.
- - Be sure to include a clear and concise description of your changes in the pull request, as well as any relevant issues or considerations.
- - Direct merges work fine too, just make sure you have the permission to do it.
-
+ 1. Fork the repository to your own Github account
+ 2. Clone the project to your machine
+ 3. Create a branch locally with a succinct but descriptive name
+ 4. Commit changes to the branch
+ 5. Following any formatting and testing guidelines specific to this repo
+ 6. Push changes to your fork
+ 7. Open a PR in our repository so that we can review the changes.
+ Direct merges work fine too, just make sure you have the permission to do it.
- Consider opening an issue to discuss significant changes:
From 34025da6ccfebee8a69795cd319837d5fe333398 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 15:12:05 +0530
Subject: [PATCH 14/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 32e6c2cb..b507026f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -22,13 +22,15 @@ While direct merges work great as we work with independent python notebooks, it
- Submit contributions through pull requests:
Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors.
- 1. Fork the repository to your own Github account
- 2. Clone the project to your machine
- 3. Create a branch locally with a succinct but descriptive name
- 4. Commit changes to the branch
- 5. Following any formatting and testing guidelines specific to this repo
- 6. Push changes to your fork
- 7. Open a PR in our repository so that we can review the changes.
+
+ - Fork the repository to your own Github account
+ - Clone the project to your machine
+ - Create a branch locally with a succinct but descriptive name
+ - Commit changes to the branch
+ - Following any formatting and testing guidelines specific to this repo
+ - Push changes to your fork
+ - Open a PR in our repository so that we can review the changes.
+
Direct merges work fine too, just make sure you have the permission to do it.
From e8a96fa2f53440420b6a2c8d0b429d42eab1d592 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 15:13:54 +0530
Subject: [PATCH 15/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 16 +---------------
1 file changed, 1 insertion(+), 15 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b507026f..87c64ca3 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -19,21 +19,6 @@ We use GitHub issues to track public bugs, take suggestions and feedback. Report
## Making Contributions
While direct merges work great as we work with independent python notebooks, it can get messy and violate our standards sometimes. Here are some recommended guidelines, we insist you follow if you are contributing to the repository for the first time.
-
-- Submit contributions through pull requests:
- Pull requests allow you to propose changes to the codebase and have them reviewed by the project's maintainers and other contributors.
-
- - Fork the repository to your own Github account
- - Clone the project to your machine
- - Create a branch locally with a succinct but descriptive name
- - Commit changes to the branch
- - Following any formatting and testing guidelines specific to this repo
- - Push changes to your fork
- - Open a PR in our repository so that we can review the changes.
-
- Direct merges work fine too, just make sure you have the permission to do it.
-
-
- Consider opening an issue to discuss significant changes:
If you are considering making significant changes to the codebase, it is a good idea to open an issue to discuss your proposed changes before creating a pull request. This will allow you to get feedback and input from the project's maintainers and other contributors, and can help ensure that your changes align with the project's goals and direction.
@@ -54,6 +39,7 @@ While direct merges work great as we work with independent python notebooks, it
- Address comments and suggestions during the review process
- Resolve merge conflicts, if necessary, before the pull request can be merged
+ Direct merges work fine too, just make sure you have the permission to do it.
## After Your Pull Request is Merged
Congratulations you have successfully contributed to DiCRA.✨
From 495df7bf481468b9fca4bf8217ad8ecfb9333806 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 15:14:44 +0530
Subject: [PATCH 16/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 87c64ca3..d9cbde9c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -33,12 +33,12 @@ While direct merges work great as we work with independent python notebooks, it
## Submitting a Pull Request
-
- - Include a clear and concise description of changes in the pull request
+
+ - Include a clear and concise description of changes in the pull request
- Link to relevant issues in the pull request description
- Address comments and suggestions during the review process
- Resolve merge conflicts, if necessary, before the pull request can be merged
-
+
Direct merges work fine too, just make sure you have the permission to do it.
## After Your Pull Request is Merged
From b1ef440ae1cec1491ba881cc56cf178e13a89049 Mon Sep 17 00:00:00 2001
From: Shubham Singh <55784408+shubhamcodez@users.noreply.github.com>
Date: Sat, 24 Dec 2022 15:15:33 +0530
Subject: [PATCH 17/17] Update CONTRIBUTING.md
---
CONTRIBUTING.md | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d9cbde9c..cd3c29bd 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,9 +1,7 @@
# Welcome to DiCRA contributing guide
-Thank you for investing your time in contributing to our project!
-
-Read our Code of Conduct to keep our community approachable and respectable.
+Thank you for investing your time in contributing to our project!
+Before you start, read our Code of Conduct to keep our community approachable and respectable.
In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.
-
## New Contributor guide
Familiarize yourself with the project's goals and objectives. Go through [ReadMe](https://github.com/shubhamcodez/dicra/blob/main/readme.md) and [Code of Conduct](https://github.com/shubhamcodez/dicra/blob/main/CODE_OF_CONDUCT.md) to better understand our expectations of standard and enforcement guidelines. It is important to be respectful and considerate of others when interacting with the project and its community. Make sure to follow the repository's code of conduct to ensure that all interactions are positive and constructive. If you have any questions or concerns, don't hesitate to reach out to the project's maintainers or other community members for help or guidance. If you have never worked with Github, I would suggest Git for [Beginners](https://youtu.be/RGOj5yH7evk) or reading the github [docs](https://docs.github.com/en/get-started).