Allow @stduhpf and @Green-Sky to approve PRs

[iwr-redmond]

@stduhpf is a prolific coder with many PRs added to this project. It would be helpful to provide @stduhpf with write access to this repository so that development of stable-diffusion.cpp can continue when @leejet is unavailable.

[Green-Sky]

If direct write access is not desired, we can do some review requirement from a review team. Like @stduhpf and myself.

[stduhpf]

@Green-Sky I think a review team is a better idea. Since I'm more active than @leejet right now, giving me direct write acess would kinda feel like taking over, and I don't want that.

[Green-Sky]

Yes. llama.cpp does that too. I claim that was one of the reasons why it took off and scaled so well in the early days.

[ggerganov]

In the settings of the Github repo, you can create a rule that requires a number of approvals to merge a PR. For example:

This is what we use in the llama.cpp repo and it works OK IMO.

[iwr-redmond]

Thanks for your feedback, everyone. I've updated the issue title to reflect the discussion.

[wbruna]

Perhaps we could have a 'staging' branch too, for more involved changes? That way, additional functionality could be pre-merged and better tested without disrupting the releases. There is a lot of relatively simple pending PRs that could probably be integrated just by exposing them to more testing.

I could also help with reviewing and testing PRs (as long as that doesn't count as approval; I'm not that familiar with the codebase).

[iwr-redmond]

Copying the comments from #696 for easy reference:

@kgigitdev:

I'm sure that nobody would take offence if a temporary (friendly, and prominently attributed) fork were created to contain suitably-approved merged and conflict-resolved branches from all the developers who have pending PRs, as well as lots of useful work that is currently being duplicated across lots of forks.

@Green-Sky:

If we ended up doing this, I would ask @ggerganov to host that project at the ggml org. But let's wait a while longer and see what @leejet ends up doing.

[SkutteOleg]

Hopefully optional PRs remain optional, and the library does not get bloated. Though current open PRs seem to be alright.