Add additional Collaborators to allow others to merge PR's

[jackson15j]

Is your feature request related to a problem? Please describe.

This package is currently broken for people with current magit/emacs29. PR merging and Maintenance to this package has dropped off since December 2022, with no public plan of support.

• There has been no new commits for the last 10 months (at time of writing).

• 245 Covers a fundamental breakage to this package.

• 246 fixes the above issue but is blocked awaiting review&merge for the last 18 months.

• This repo is the source of truth for code-review in melpa.

Describe the solution you'd like

• Add additional Collaborators to the repo with access to merge PR's.

Describe alternatives you've considered

• Transfer ownership of the repo + emacs package namespace to an interested person(s).

Additional context

• N/A

[hpfr]

I don’t know if anyone has really distinguished themselves with a fork or multiple nontrivial open PRs to the point where wandersoncferreira could feel confident adding them as a collaborator. This is a pretty large Emacs Lisp package, so it wouldn’t be good to have someone with limited experience just become a committer on the MELPA package.

Typically, the first step is for someone to fork it, merge the open PRs, and make new additions demonstrating that they understand the code base, ideally for enough time to indicate they won’t just disappear in a month or two. This issue would be a good place for anyone who is maintaining a fork to announce it so that users can modify their package recipes accordingly! Unfortunately, based on the fork network, that someone doesn’t exist yet, unless they’re not using GitHub.

If you just need a fork that has the CloSQL fix merged, try the Doom Emacs maintainer’s fork.

[pataquets]

I'd like to add that moving the repo to an organization, if it can ease administration. Maybe the Magit devs are also interested? (just a wild guess, no idea). @wandersoncferreira Adoptoposs might come handy here. /cc @smile13241324 to bring attention on the Doom Emacs fork mentioned above, since this package has been excluded in the meantime from Spacemacs on syl20bnr/spacemacs#16020.