chore: enhance contributing guidelines (#970)

Author: metcoder95

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,26 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+---
+
+## Description
+<!-- A clear and concise description of what the bug is. -->
+
+## Reproduction
+<!-- Please provide a minimal code snippet or repository that reproduces the issue. You can follow a [Minimum Reproducible Example](https://stackoverflow.com/help/minimal-reproducible-example)-->
+
+```js
+const piscina = require('piscina');
+// ... (Add reproduction code here)
+```
+
+## Environment
+- **OS**:
+- **Node.js version**:
+- **Piscina version**:
+
+## Expected Behavior
+<!-- What did you expect to happen? -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,16 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+---
+
+## Goal
+<!-- What problem are you trying to solve? -->
+
+## Proposal
+<!-- A concise description of the solution you'd like.If this involves an API change, please describe the new API. -->
+
+## Alternatives
+<!-- What other solutions have you considered? -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,26 @@
+## Overview
+
+<!-- Briefly explain the goal of this Pull Request. -->
+
+## Category
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation
+- [ ] Maintenance (refactoring, dependency updates, etc.)
+
+## Contribution Checklist
+
+<!-- Please verify the following before submitting: -->
+
+- [ ] I have reviewed the [guidelines](../CONTRIBUTING.md) for this project.
+- [ ] I agree to follow the [Code of Conduct](../CODE_OF_CONDUCT.md).
+- [ ] My code adheres to the project's style and conventions.
+- [ ] I have added tests to cover my changes.
+- [ ] All tests passed locally.
+- [ ] I have updated relevant documentation.
+
+## DCO Sign-off
+
+- [ ] I certify that I have the right to submit this contribution under the open source license ([DCO 1.1](../CONTRIBUTING.md#developers-certificate-of-origin-11)).

CONTRIBUTING

@@ -0,0 +1,48 @@
+# Piscina is an OPEN Open Source Project
+
+## What?
+
+Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.
+
+## Rules
+
+There are a few basic ground-rules for contributors:
+
+1. **No `--force` pushes** on `current` or any `vX` branches, or modifying the `git` history in any way after a PR has been merged.
+2. **Non-current branches** ought to be used for ongoing work.
+3. **External API changes and significant modifications** ought to be subject to an **internal pull-request** to solicit feedback from other contributors.
+4. Internal pull-requests to solicit feedback are *encouraged* for any other non-trivial contribution but left to the discretion of the contributor.
+5. Contributors should attempt to adhere to the prevailing code-style.
+6. At least two contributors, or one core member, must approve pull requests before merging.
+7. All integrated CI services must be green before a pull request can be merged.
+8. If it is not possible to reach a consensus in a pull request, the decision is left to the lead maintainer's team.
+9. Semantic Versioning is used.
+
+## Releases
+
+Declaring formal releases remains the prerogative of the project maintainer.
+
+## Previous Versions
+Every version of Piscina has its own branch. All Piscina related changes should be based on the corresponding branch.
+
+Piscina's adhere to one active release line and a maintanance release line within a single year, rotating on a yearly basis.
+
+Version	| Branch | Status
+------- | ------ | ------
+current	| branch | main 
+v4.x	| branch | v4
+v5.x	| branch | v5
+
+
+## Developer's Certificate of Origin 1.1
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
+
+(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
+
+(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
+
+-----------------------------------------

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2020 James M Snell and the Piscina contributors
+Copyright (c) 2026 James M Snell and the Piscina contributors
 
 Piscina contributors listed at https://github.com/jasnell/piscina#the-team and
 in the README file.