Re: [MAINTENANCE] Org orphanage?

[Jonas Bernoulli]

Thanks for offering to help out Corwin!

>> Speaking for myself, I can help:
>> [...]
>> - review the bonafides (experience/involvement and, via Eli/SM,
>> assignment status ) for prospective adopting maintainers
>
> Not sure about emacsorphanage side, but for things we decide to manage
> on sr.ht, we can all discuss new maintainers on this mailing list. The
> maintenance requests should also go here.

The orphanage is often first brought up in the package's issue tracker,
or on Melpa's issue tracker.  Sometimes I bring it up, sometimes a user
of a package makes us aware of a stale package.

In general that makes sense, but for Org-related packages this mailing
list makes more sense (not least because it is read by people interested
in Org, i.e., potential future maintainers).

>> - assign permissions
>> - move repos
>> - apply well tested patches to orphaned packages
>
> I think you can participate in issue discussion for the existing
> orphaned packages first. (The problem is that you do not have a record
> contributing to Emacs/Org mode. I can only see two trivial commits
> 64d211179db and a70a3449417 in Emacs)

I only want to give far reaching permissions to people who have
maintained larger Emacs-related projects for a long time.

It's great that you are volunteering to do some work, but I am not
looking for more people to manage the whole project, just individual
packages.

If you are interested in that kind of work looked through the list of
orphaned packages for something that interests you and then offer to
maintain that.

>> - apply well tested patches to orphaned packages

If you see any pull-requests that you consider suitable for merge but
haven't gotten any response from any of the maintainers of the orphanage
or the volunteer who maintains the respective package, then feel free to
ping @emacsorphanage/core.

>> Irrespective of whether worg curators should help with this (or some
>> other vols, or just the org maintainers, or...), I think it would make
>> sense to document these "responsibilities" (and the detail of the
>> plans made in this thread, in general), along with the whos and hows.
>
> +1

I'll try collecting existing resources and maybe write some new ones,
but I have a lot on my plate, so this will likely take a while.