Make the abandonment more obvious

[fredden]

This pull request aims to make it more obvious to end users that this repository has been deprecated, and that issues and pull requests can be submitted to the new repository.

[Potherca]

Although this is a step in the right dirction, it might be even more effective if this repo was archived..

@jrfnl Has the topic of archiving this repo come up yet? (A quick search did not show anything in the issues to that effect)

[jrfnl]

Although this is a step in the right dirction, it might be even more effective if this repo was archived..

@jrfnl Has the topic of archiving this repo come up yet? (A quick search did not show anything in the issues to that effect)

@Potherca It has been discussed and decided against (for the time being). Archiving the repo also means that all issues and PRs become read-only and no new comments are allowed, while for some issues/PRs (for now) it is still helpful to be able to inform people if something has been fixed via the new repo/ask them to move a discussion/PR to the new repo etc.

The intention is to eventually archive the repo, but not yet.

[Potherca]

In that case, it might be worth merging this MR (or something similar) and/or creating an issue to pin instead of the current "Future of..." issue to warn people there (As they apparently don't read the README).

I'm curious if, using issue forms, it might be possible to create an template that doesn't actually have any fields (so it can be a warning only and nothing else)¹

Footnotes

1. I might play around with that and try it out² ↩

2. ^{Who am I kidding. Hold my beer. 🫱🍺} ↩

[jrfnl]

@Potherca I don't think anything will be merged here anymore, so please don't waste your time.

[Potherca]

That's okay, I've trying to get a good grip on GitHub Issue Forms, so was is just fun practice. I did manage!

For shits and giggles: https://github.com/potherca-blog/this-project-has-been-abandoned-issue-template