Update CONTRIBUTING guidelines (#4192)

* Update CONTRIBUTING.md

.github/ISSUE_TEMPLATE/issue_report.md

@@ -8,7 +8,13 @@ assignees: ''
 ---
 
 <!--
-Before filing an issue, please reproduce with the latest version of Jib.
+Please follow the guidelines below before opening an issue:
+1. Ensure the issue was not already reported. 
+2. Open a new issue if you are unable to find an existing issue addressing your problem. Make sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
+3. Discuss the priority and potential solutions with the maintainers in the issue. The maintainers would review the issue and add a label "Accepting Contributions" once the issue is ready for accepting contributions. 
+4. Open a PR only if the issue is labeled with "Accepting Contributions", ensure the PR description clearly describes the problem and solution. Note that an open PR without an issues labeled with "Accepting Contributions" will not be accepted.
+
+Please reproduce with the latest version of Jib.
 
 If you are encountering errors pulling or pushing to remote registries,
 please check our Frequently Asked Questions before filing an issue:

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,14 +1,12 @@
 Thank you for your interest in contributing! For general guidelines, please refer to
 the [contributing guide](https://github.com/GoogleContainerTools/jib/blob/master/CONTRIBUTING.md).
 
-Before filing a pull request, make sure to do the following:
-
-- [ ] Create a new issue at https://github.com/GoogleContainerTools/jib/issues/new/choose.
-- [ ] Ensure that your implementation plan is approved by the team.
+Please follow the guidelines below before opening an issue or a PR:
+- [ ] Ensure the issue was not already reported. 
+- [ ] Create a new issue at https://github.com/GoogleContainerTools/jib/issues/new/choose if you are unable to find an existing issue addressing your problem. Make sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
+- [ ] Discuss the priority and potential solutions with the maintainers in the issue. The maintainers would review the issue and add a label "Accepting Contributions" once the issue is ready for accepting contributions.
+- [ ] Open a PR only if the issue is labeled with "Accepting Contributions", ensure the PR description clearly describes the problem and solution. Note that an open PR without an issues labeled with "Accepting Contributions" will not be accepted.
 - [ ] Verify that integration tests and unit tests are passing after the change.
-- [ ] Address all checkstyle issues. Refer to
-  the [style guide](https://github.com/GoogleContainerTools/jib/blob/master/STYLE_GUIDE.md).
-
-This helps to reduce the chance of having a pull request rejected.
+- [ ] Address all checkstyle issues. Refer to the [style guide](https://github.com/GoogleContainerTools/jib/blob/master/STYLE_GUIDE.md).
 
 Fixes #<issue_number_goes_here> 🛠️

CONTRIBUTING.md

@@ -1,7 +1,13 @@
+
+This project is currently stable, and we are primarily focused on critical bug fixes and platform evolution to ensure it continues to work for its supported use cases.
+
 # Contributing to Jib
 
-We'd love to accept your patches and contributions to this project. There are
-just a few small guidelines you need to follow.
+Please follow the guidelines below before opening an issue or a PR:
+1. Ensure the issue was not already reported. 
+2. Open a new issue if you are unable to find an existing issue addressing your problem. Make sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
+3. Discuss the priority and potential solutions with the maintainers in the issue. The maintainers would review the issue and add a label "Accepting Contributions" once the issue is ready for accepting contributions. 
+4. Open a PR only if the issue is labeled with "Accepting Contributions", ensure the PR description clearly describes the problem and solution. Note that an open PR without an issues labeled with "Accepting Contributions" will not be accepted.
 
 ## Contributor License Agreement