Reporting Extension Compatibility

[Aptronymist]

As we are now beginning to maintain our own extension index, which absorbs the a1111 index as well as actively searches for new extensions, the issue of compatibility is of course increasing.
As you likely know, not many devs (thanks to ones that do!) actually go out of their way to ensure compatibility with SD.Next, Vlad has helpfully created a much more extensive json controlled list that we can fill in when we find extensions are in/compatible, with the original backend, diffusers backend, and SDXL specifically.
There is now a post in Resources on the discord server, however I'm creating this here as well for users or extension devs/maintainers to do their own reporting.

We have 3 criteria that must be evaluated:

1. Does the extension install/function properly in the original LDM (sd1.5/2.x) backend?
2. Does the extension install/function properly in the diffusers backend?
3. Does the extension install/function properly in the diffusers backend when using SDXL models?

If there are errors or any oddities when the extension installs itself, updates, or when it's being used, please include that information as well in the notes or comments posted here or on discord.

I have created a simple json template to use. Note that we also will also take working and improved forks of known extensions, particularly unmaintained ones.

	{
		"name": "Extension name",
		"url": "https://github.com/somebody/something.git",
		"description": "short description- sentence or so",
		"long-description": "long description - don't go crazy",
		"note": "any needed notes, such as: Fork of <https://github.com/example>"
		"branch": "if a specific branch of the extension is needed, place the name of it here, example: dev",
		"status": #
	}

This is the internal repo that you can create PRs to if you have done your own testing and have verified with all 3 criteria above that an extension does or does not work. You can also just post the info here or on discord and I will collect them and handle the PR. Long descriptions are not necessary, but encouraged, even a small summary taken straight from the page is adequate for both description fields. Notes are entirely optional, use only if there something... notable.

I'll include a screenshot here for easy reference as to what each field should be:

Also note, if you wish, you of course may drop by the repo of any extensions that you want to be able to use, but cannot for some reason due to errors and the like, and POLITELY request that they take a look at SD.Next and consider adjustments to ensure compatibility.
Please include that we are always happy to work with them in identifying and tracing down issues and providing some assistance in ensuring compatibility. That has always been our policy with any other developers that want to collaborate.
This wiki page contains the basics of what Vlad's guidelines are for any extension's behavior, often times they do not conform to these simple principles and that is what causes errors, but if there is something particularly troublesome on our end we can look at adding in compatibility code.