What is going on with this repo?

[suparious]

I have been watching and reading every comment and pull request in this repo for several weeks now.

I don't see any progress being made in reviewing and merging these (71) pull requests. From the comments, it seems that this repo's author is resisting any large changes. I would like to understand more about this.

I see so many forks of this repo, but all are just unchanged versions of this repo from many months ago.

What is the strategy, how can I help? I don't want to just be another person that forks this repo and gives up on it.

[BetaDoggo]

I don't think it's that he's against large changes, he's just busy with other stuff and hasn't been reviewing pull requests. There isn't really anything that can be done unless Automatic decides to allow other contributors to merge or a large enough portion of the contributors decide to switch to a fork.

[FullBleed]

I don't think it's that he's against large changes, he's just busy with other stuff and hasn't been reviewing pull requests. There isn't really anything that can be done unless Automatic decides to allow other contributors to merge or a large enough portion of the contributors decide to switch to a fork.

Everyone has to be so careful what they say because any implied criticism or question is immediately met with accusations of "looking a gift-horse in the mouth" quickly followed by admonishments to "fork it and do it your damn self!"

But, it would be a shame to see a project with this much momentum and community support fizzle out and fracture because the one person with commit rights ghosts it for weeks at a time. Few people would begrudge auto for "taking a break" given the speed this project has been moving... but to do so without any communication with the community does seem a bit careless.

[f0lie]

Plus there are definitely people here who can be maintainers. There are already people here who are helping with triaging bugs and maintaining useful extensions downstream.

To be fair, it is extremely overwhelming to deal with rapidly growing repos like this. The amount of work is equal to a full-time job.

[Kilvoctu]

"fork it and do it your damn self!"

Pretty much. Welcome to open-source, I suppose. Progress is made by those who put forth the effort. All the source code is right here; forking is an intended feature of Github.

Auto manages this repo way different than I would. I'm obsessively concerned about communication and replying to feedback.
However, I've mentioned elsewhere this is Auto's repo; he can do what he wants, even if that includes letting it fizzle out 🤷‍♀️. A fork would take over in that case.

Here is an example of open source at work.

[toyxyz]

Auto has not been active not only in this repo, but also in other communities for the time being. Perhaps he's busy with other things and doesn't have time to attend here.

[Centurion-Rome]

Has anyone active fork which continues work?

[sarpsomer]

You don't even know how to use github and here systematically commenting about the future of the repo in discussions. If you know how to use discussions; you should have known it is only 3 clicks to find out active forks.

https://github.com/AUTOMATIC1111/stable-diffusion-webui/forks?activity_threshold=1mo&include=active&page=1&sort_by=stargazer_counts

[biship]

One person can't realistically manage this repo. It has more favorites then the SD2.0 repo now...
About time to add some more maintainers!

[Centurion-Rome]

yep, otherwise, people will move to other repo

[f0lie]

Yea, this repo grew at breakneck speed and the forks still are.

https://useful-forks.github.io/?repo=AUTOMATIC1111/stable-diffusion-webui

There are already some forks with hundreds of commits ahead of this one and over 100 stars.

[drax-xard]

This fork seems to be actively worked on: https://github.com/vladmandic/automatic

[FullBleed]

This fork seems to be actively worked on: https://github.com/vladmandic/automatic

@vladmandic 's fork definitely looks like a contender! Love the developer transparency, too.

[FartyPants]

wow it seems almost shadowing the commits here plus adding hundreds of their own... 287 commits ahead, 6 commits behind.
Edit: I could not run that repo, no matter how hard I tried.

[vladmandic]

i try to merge from upstream whenever possible plus create prs upstream for any of my new code when applicable so its not just in my fork.
so there is little functional difference. still, all the custom api/cli stuff is separate plus a lot of opinionated customizations and bringing some optional extensions to be part of core.

[toyxyz]

And he's back!

[sarpsomer]

I have been following this repo for a while. Each time he is idle for a time; someone definitely posts similar stuff. Ask these questions beforehand;

• What is your rush? Have you completely mastered every extension, script, models and your workflow ?
  (I am following channels, discussion boards, extensions in a daily basis and giving quite a lot of time; still hardly keeping up.)
• If you have big improvements why haven't you forked the repo ?
• Would other maintainers keep the similar code quality and safety ?
• Have you tried other web user interfaces for stable diffusion ?
  and so on;

If you couldn't answer these questions. I can only think that these posts are a way to pressure the owner psychologically. A rather ill intention.

I hope this repo will continue as the way it is.

[suparious]

I just didn't realize the trend or waves with this community. I have read all the comments on this thread and will take all this in before making any similar post. Thank-you for taking the time to lay it out for me.

[myndxero]

Well, the author of the dreambooth extension discovered a serious exploit or something with the version of gitpython that's required by webui, so hazard bumped it up to the next safe release with his plugin. disenfranchised a lot of the dreambooth people for several weeks as it was discovered almost right away.

I get that you don't want to see people becoming grumpy and entilted-sounding, but it shouldn't be a one-way street. this is massively popular and widely used in a space moving way (too) fast it's hard to keep up. especially with solo authority to approve changes.

All I'm saying is that it's a two-way street, or should be.

PS - i don't know github works too well, im not up to date on programming or anything anymore, but i wonder if there's a way to put the main repo on a parallel track while auto is away or taking a break etc, functionally like a fork allowing anyone authorized to confirm merges and directing anyone using git pull on the main repo to it for that time as well? protects the integrity of the main repo, doesnt hold up anyone else wanting to contribute.

i don't know auto, i don't know his mindset, how he feels etc, just would be neat if there was a common ground scenario when entering a dormant period of time from him.

[suparious]

Thank-you for all the feedback. This was the first time interacting with a community and I have learned from all the comments.

The recent changes have helped me make progress in getting xformers working with a pytorch that can run on cuda 12.

There are better way I could have gone about inquiring on progress an how I could help. I should have paid more attention and spent more time wording my question + subject title.

Thank-you for for the patience.

[blackhatma]

Just a friendly reminder that Auto1111 owes you nothing & you are not entitled to his work. Whatever he may be doing at any point in time for however long is absolutely none of your business. Truly not trying to be an asshole here, its just how it is really. He has done a lotttttttt of work as it is, and even allowed us all to have access to all of his hard work.