Add that failure to discuss large PRs with devs might lead to closure

.github/PULL_REQUEST_TEMPLATE/BugFix.md

@@ -1,18 +0,0 @@
----
-name: Bug Fix
-about: Add a bug fix this project!
-title: "[Bug Fix] Short Form Title (50 chars or less.)"
-labels: bug
-assignees: 'WithoutPants, bnkai, Leopere'
-
----
-<!-- Please make sure to read https://github.com/stashapp/stash/docs/CONTRIBUTING.md and check that you understand and have followed it as best as possible -->
-<!-- Explain what your bugfix seeks to remedy in a short paragraph. -->
-# Scope
-
-<!-- Declare any issues by typing `fixes #1` or `closes #1` for example so that the automation can kick in when this is merged -->
-## Closes/Fixes Issues
-
-<!-- What have you tested specifically and what possible impacts/areas there are that may need retesting by others. -->
-## Other testing QA Notes
-

.github/PULL_REQUEST_TEMPLATE/Feature.md

@@ -1,17 +0,0 @@
----
-name: Feature Addition
-about: Add a feature to this project!
-title: "[Feature] Short Form Title (50 chars or less.)"
-labels: enhancement
-assignees: 'WithoutPants, bnkai, Leopere'
-
----
-<!-- Please make sure to read https://github.com/stashapp/stash/docs/CONTRIBUTING.md and check that you understand and have followed it as best as possible
-Explain what your feature does in a short paragraph. -->
-# Scope
-
-<!-- Declare any issues by typing `fixes #1` or `closes #1` for example so that the automation can kick in when this is merged -->
-## Closes/Fixes Issues
-
-<!-- What have you tested specifically and what possible impacts/areas there are that may need retesting by others. -->
-## Other testing QA Notes

.github/pull_request_template.md

@@ -0,0 +1,39 @@
+<!-- Thank you for submitting a pull request! Make sure to follow the contributing guidelines and this template. -->
+
+## Description
+<!-- Please write a clear and concise description of what the pull request does. -->
+
+
+
+## Related Issue
+<!-- Please link the issue your pull request is referring to. -->
+
+
+
+## Testing
+<!-- Describe the testing steps you have performed. -->
+
+
+
+## Screenshots
+<!-- For visual changes, please add before and after screenshots. -->
+
+
+
+## Checklist
+<!-- Mark [x] to indicate completion. -->
+
+- [ ] I have read and understood the [Contributing](docs/CONTRIBUTING.md) document.
+- [ ] I have read and understood the [AI Usage Policy](docs/AI_POLICY.md) document.
+- [ ] I have made corresponding changes to the documentation (if applicable).
+
+## AI Usage Disclosure
+<!-- Mark [x] to indicate completion. -->
+- [ ] I have used AI tools to assist with this pull request, and I have disclosed the tools and how I used them below.
+<!-- If you used AI to assist with this pull request, please disclose what tools you used and how you used them. -->
+
+
+
+## Additional Context
+<!-- Add any other context about the pull request here. -->
+

README.md

@@ -1,13 +1,14 @@
 # Stash
 
 [![Build](https://github.com/stashapp/stash/actions/workflows/build.yml/badge.svg?branch=develop&event=push)](https://github.com/stashapp/stash/actions/workflows/build.yml)
-[![Docker pulls](https://img.shields.io/docker/pulls/stashapp/stash.svg)](https://hub.docker.com/r/stashapp/stash 'DockerHub')
+[![Docker pulls](https://img.shields.io/docker/pulls/stashapp/stash?logo=docker)](https://hub.docker.com/r/stashapp/stash 'DockerHub')
 [![GitHub Sponsors](https://img.shields.io/github/sponsors/stashapp?logo=github)](https://github.com/sponsors/stashapp)
 [![Open Collective backers](https://img.shields.io/opencollective/backers/stashapp?logo=opencollective)](https://opencollective.com/stashapp)
 [![Go Report Card](https://goreportcard.com/badge/github.com/stashapp/stash)](https://goreportcard.com/report/github.com/stashapp/stash)
 [![Discord](https://img.shields.io/discord/559159668438728723.svg?logo=discord)](https://discord.gg/2TsNFKt)
 [![GitHub release (latest by date)](https://img.shields.io/github/v/release/stashapp/stash?logo=github)](https://github.com/stashapp/stash/releases/latest)
-[![GitHub issues by-label](https://img.shields.io/github/issues-raw/stashapp/stash/bounty)](https://github.com/stashapp/stash/labels/bounty)
+[![Codeberg Translate](https://img.shields.io/weblate/progress/stash?server=https%3A%2F%2Ftranslate.codeberg.org&logo=weblate)](https://translate.codeberg.org/engage/stash/)
+[![GitHub issues by-label](https://img.shields.io/github/issues-raw/stashapp/stash/bounty?logo=github)](https://github.com/stashapp/stash/labels/bounty)
 
 <h3>Stash is a self-hosted webapp written in Go which organizes and serves your diverse content collection, catering to both your SFW and NSFW needs.</h3>
 
@@ -20,9 +21,9 @@
 
 You can [watch a SFW demo video](https://vimeo.com/545323354) to see it in action.
 
-For further information you can consult the [documentation](https://docs.stashapp.cc) or access the in-app manual from within the application (also available at [docs.stashapp.cc/in-app-manual](https://docs.stashapp.cc/in-app-manual)).
+For further information see [Support & Resources](#support--resources) section.
 
-# Installing Stash
+## Installing Stash
 
 > [!tip]
 Step-by-step instructions are available at [docs.stashapp.cc/installation](https://docs.stashapp.cc/installation/).
@@ -37,7 +38,7 @@ Step-by-step instructions are available at [docs.stashapp.cc/installation](https
 >
 > As of version 0.29.0, Stash requires _macOS 11 Big Sur_ or later.  
 > As of version 0.32.0, Stash requires _macOS 12 Monterey_ or later.  
-> Stash can still be run through Docker on older versions of macOS.
+> Older versions can still be run through Docker.
 
 <img src="docs/readme_assets/windows_logo.svg" width="100%" height="75"> Windows | <img src="docs/readme_assets/mac_logo.svg" width="100%" height="75"> macOS | <img src="docs/readme_assets/linux_logo.svg" width="100%" height="75"> Linux | <img src="docs/readme_assets/docker_logo.svg" width="100%" height="75"> Docker
 :---:|:---:|:---:|:---:
@@ -45,7 +46,7 @@ Step-by-step instructions are available at [docs.stashapp.cc/installation](https
 
 Download links for other platforms and architectures are available on the [Releases](https://github.com/stashapp/stash/releases) page.
 
-## First Run
+### First Run
 
 #### Windows/macOS Users: Security Prompt
 
@@ -58,9 +59,9 @@ On Windows or macOS, running the app might present a security prompt since the a
 
 Stash requires FFmpeg. If you don't have it installed, Stash will prompt you to download a copy during setup. It is recommended that Linux users install `ffmpeg` from their distro's package manager.
 
-# Usage
+## Usage
 
-## Quickstart Guide
+### Quickstart Guide
 
 Stash is a web-based application. Once the application is running, the interface is available (by default) from `http://localhost:9999`.
 
@@ -68,59 +69,51 @@ On first run, Stash will prompt you for some configuration options and media dir
 
 Stash can pull metadata (performers, tags, descriptions, studios, and more) directly from many sites through the use of [scrapers](https://github.com/stashapp/stash/blob/develop/ui/v2.5/src/docs/en/Manual/Scraping.md), which integrate directly into Stash. Identifying an entire collection will typically require a mix of multiple sources:
 - The stashapp team maintains [StashDB](https://stashdb.org/), a crowd-sourced repository of scene, studio, and performer information. Connecting it to Stash will allow you to automatically identify much of a typical media collection. It runs on our stash-box software and is primarily focused on mainstream digital scenes and studios. Instructions, invite codes, and more can be found in this guide to [Accessing StashDB](https://guidelines.stashdb.org/docs/faq_getting-started/stashdb/accessing-stashdb/).
-- Several community-managed stash-box databases can also be connected to Stash in a similar manner. Each one serves a slightly different niche and follows their own methodology. A rundown of each stash-box, their differences, and the information you need to sign up can be found in this guide to [Accessing Stash-Boxes](https://guidelines.stashdb.org/docs/faq_getting-started/stashdb/accessing-stash-boxes/).
+- Several community-managed stash-box databases can also be connected to Stash in a similar manner. Each one serves a slightly different niche and follows their own methodology. A rundown of each stash-box, their differences, and the information you need to sign up can be found in the [Metadata Sources](https://docs.stashapp.cc/metadata-sources/stash-box-instances/) section of the documentation.
 - Many community-maintained scrapers can also be downloaded, installed, and updated from within Stash, allowing you to pull data from a wide range of other websites and databases. They can be found by navigating to `Settings → Metadata Providers → Available Scrapers → Community (stable)`. These can be trickier to use than a stash-box because every scraper works a little differently. For more information, please visit the [CommunityScrapers repository](https://github.com/stashapp/CommunityScrapers).
 - All of the above methods of scraping data into Stash are also covered in more detail in our [Guide to Scraping](https://docs.stashapp.cc/beginner-guides/guide-to-scraping/).
 
 <sub>[StashDB](http://stashdb.org) is the canonical instance of our open source metadata API, [stash-box](https://github.com/stashapp/stash-box).</sub>
 
-# Translation
-
-[![Translate](https://translate.codeberg.org/widget/stash/stash/svg-badge.svg)](https://translate.codeberg.org/engage/stash/)
-
-Stash is available in 32 languages (so far!) and it could be in your language too. We use Weblate to coordinate community translations. If you want to help us translate Stash, you can make an account at [Codeberg's Weblate](https://translate.codeberg.org/projects/stash/stash/) to contribute to new or existing languages. Thanks!
-
-The badge below shows the current translation status of Stash across all supported languages:
-
-[![Translation status](https://translate.codeberg.org/widget/stash/stash/multi-auto.svg)](https://translate.codeberg.org/engage/stash/)
-
-# Support & Resources
+## Support & Resources
 
 Need help or want to get involved? Start with the documentation, then reach out to the community if you need further assistance.
 
 ### Documentation
+
 - [Official documentation](https://docs.stashapp.cc) - official guides guides and troubleshooting.
 - [In-app manual](https://docs.stashapp.cc/in-app-manual) press <kbd>Shift</kbd> + <kbd>?</kbd> in the app or view the manual online.
 - [FAQ](https://discourse.stashapp.cc/c/support/faq/28) - common questions and answers.
 - [Community wiki](https://discourse.stashapp.cc/tags/c/community-wiki/22/stash) - guides, how-to’s and tips.
   
-### Community & discussion
+### Community & Discussion
+
 - [Community forum](https://discourse.stashapp.cc) - community support, feature requests and discussions.
 - [Discord](https://discord.gg/2TsNFKt) - real-time chat and community support.
 - [GitHub discussions](https://github.com/stashapp/stash/discussions) - community support and feature discussions.
 - [Lemmy community](https://discuss.online/c/stashapp) - board-style community space.
 
-### Community scrapers & plugins
+### Community Scrapers & Plugins
+
 - [Metadata sources](https://docs.stashapp.cc/metadata-sources/)
 - [Plugins](https://docs.stashapp.cc/plugins/)
 - [Themes](https://docs.stashapp.cc/themes/)
 - [Other projects](https://docs.stashapp.cc/other-projects/)
 
-# Architecture
+## Architecture
 
-## Backend
+You can find an overview of Stash's architecture in the [ARCHITECTURE.md](docs/ARCHITECTURE.md) document.
 
-- Go
-- GraphQL API
-- SQLite
+## Contributing
 
-## Frontend
+We welcome contributions and help from all humans who want to improve the project.
 
-- React
-- TypeScript
+Before contributing, please read the [Contributing](docs/CONTRIBUTING.md) document to understand our guidelines and processes for contributing to the project.
 
-# For Developers
+You can learn about setting up a local development environment in the [Development](docs/DEVELOPMENT.md) document. 
 
-Pull requests are welcome! 
+## Translation
 
-See [Development](docs/DEVELOPMENT.md) and [Contributing](docs/CONTRIBUTING.md) for information on working with the codebase, getting a local development setup, and contributing changes.
+The widget below shows the current translation status of Stash across all supported languages. If you want to help us translate Stash, you can make an account at [Codeberg Translate](https://translate.codeberg.org/projects/stash/stash/) to contribute to new or existing languages. Thanks!
+
+[![Translation status](https://translate.codeberg.org/widget/stash/stash/multi-auto.svg)](https://translate.codeberg.org/engage/stash/)

docs/AI_POLICY.md

@@ -0,0 +1,22 @@
+# AI Usage Policy
+
+- AI agents are not welcome to contribute to this project.
+- All issues, pull request descriptions and comments must be written by humans.
+- Fully AI-generated contributions will be closed without comment.
+
+## AI-Assisted Code Contributions
+
+AI-assisted code contributions generated with the use of LLMs are permitted under the following conditions:
+
+- AI usage and scope must be openly disclosed in the PR description.
+- You must be able to explain any line of code and design decision during the review process.
+- You must perform manual testing and describe the steps taken to sufficiently verify the changes.
+- You must take full responsibility for the code, including license compliance.
+
+We are not accepting large, complex features generated by LLMs by outside contributors at this time.
+
+## Respect Maintainers Time
+
+Reviewing PRs takes a significant amount of time. Anyone with zero effort can generate code with an LLM, but it takes a human to understand it, test it, and ensure it fits with the overall design of the project.
+
+We ask that contributors respect this by ensuring their PRs meet these standards before submitting them for review.

docs/CONTRIBUTING.md

@@ -1,35 +1,48 @@
-## Goals and design vision
+# Contributing to Stash
 
-The goal of stash is to be:
-- an application for organising and viewing adult content - currently this is videos and images, in future this will be extended to include audio and text content
-  - organising includes scraping of metadata from websites and metadata repositories
-- free and open-source
-- portable and offline - can be run on a USB stick without needing to install dependencies (with the exception of ffmpeg)
-- minimal, but highly extensible. The core feature set should be the minimum required to achieve the primary goal, while being extensible enough to extend via plugins
-- easy to learn and use, with minimal technical knowledge required
+## AI Usage Policy
 
-The core stash system is not intended for:
-- managing downloading of content
-- managing content on external websites
-- publically sharing content
+Please see our [AI Usage Policy](docs/AI_POLICY.md) for guidelines on the use of AI in contributions to this project.
+
+## Issues
+
+Bug reports and feature requests must use descriptive and concise titles and follow the provided templates. Please use the search function to make sure that you are not submitting duplicates, and that a similar report or request has not already been resolved or rejected.
+
+All issues must be written by humans. Fully AI-generated issues will be closed without comment.
+
+## Pull Requests
+
+All pull requests must use descriptive and concise titles and follow the provided templates. In addition, they must follow the the following guidelines:
+
+- You must link to an open issue that pull request addresses (see [GitHub documentation](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue) on how to do that).
+- Pull requests must be focused on a single issue or feature. Large, multi-purpose pull requests will be rejected.
+- Large features must be discussed with maintainers before submitting a pull request to ensure it fits with the overall design vision of the project. Failure to do so may result in the pull request being rejected.
+- Pull requests must include code tests that sufficiently cover the changes made.
+- You must detail the manual testing done and describe the steps taken to sufficiently verify the changes.
+- You must be able to explain any line of code and design decision during the review process.
+
+By submitting a pull request, you agree that you have read and understood and that you are in compliance with the guidelines outlined here, including the [AI Usage Policy](docs/AI_POLICY.md). 
+
+You also agree to license your contribution under the [AGPL](/LICENSE.md) license, and that all of your previous contributions to the project are also licensed under the AGPL.
+
+## Goals and Design Vision
+
+The goal of Stash is to be:
+- An application for organising and viewing NSFW and SFW content - currently this is videos and images, in future this will be extended to include audio and text content
+  - Organising includes scraping of metadata from websites and metadata repositories
+- Free and open-source
+- Portable and offline - can be run on a USB stick without needing to install dependencies (with the exception of FFmpeg)
+- Minimal, but highly extensible. The core feature set should be the minimum required to achieve the primary goal, while being extensible enough to extend via plugins
+- Easy to learn and use, with minimal technical knowledge required
+
+The core Stash system is not intended for:
+- Managing downloading of content
+- Managing content on external websites
+- Publicly sharing content
 
 Other requirements:
-- support as many video and image formats as possible
-- interfaces with external systems (for example stash-box) should be made as generic as possible. 
+- Support as many video and image formats as possible
+- Interfaces with external systems (for example stash-box) should be made as generic as possible. 
 
 Design considerations:
-- features are easy to add and difficult to remove. Large superfluous features should be scrutinised and avoided where possible (eg DLNA, filename parser). Such features should be considered for third-party plugins instead.
-
-## Technical Debt
-Please be sure to consider how heavily your contribution impacts the maintainability of the project long term, sometimes less is more.  We don't want to merge collossal pull requests with hundreds of dependencies by a driveby contributor.
-
-## Contributor Checklist
-Please make sure that you've considered the following before you submit your Pull Requests as ready for merging.
-* I've run Code linters and [gofmt](https://golang.org/cmd/gofmt/) to make sure that my code is readable.
-* I have read through formerly submitted [pull requests](https://github.com/stashapp/stash/pulls) and [git issues](https://github.com/stashapp/stash/issues) to make sure that this contribution is required and isn't a duplicate. Also, so that I can manage to close any git Issues needing closed relating to this feature submission.
-* I  commented adequately on my code with the expectation in mind that anyone else should be able to look at this code I've submitted and know exactly what's happening and what the expectations are.
-
-### Legal Agreements
-* I acknowledge that if applicable to me, submitting and subsequent acceptance of this Pull Request I, the code contributor of this Pull Request, agree and acknowledge my understanding that the new code license has now been updated to [AGPL](/LICENSE.md). I agree that all code before this Pull Request, which I've previously submitted, is now to be re-licensed under the new license AGPL and no longer the former MIT license.
-
-**In case you were unable to follow any of the above include an explanation as to why not in your Pull Request.**
+- Features are easy to add and difficult to remove. Large superfluous features should be scrutinised and avoided where possible (e.g. DLNA, filename parser). Such features should be considered for third-party plugins instead.