If no one intends to join, we should drop the following to maintainer-
needed:

app-misc/rlwrap
dev-libs/ffcall
dev-libs/libsigsegv
dev-lisp/alexandria
dev-lisp/asdf
dev-lisp/cl-ppcre
dev-lisp/cl-ppcre-unicode
dev-lisp/clisp
dev-lisp/clozurecl
dev-lisp/clx
dev-lisp/cmucl
dev-lisp/ecls
dev-lisp/flexi-streams
dev-lisp/gcl
dev-lisp/hyperspec
dev-lisp/sbcl
dev-lisp/trivial-gray-streams
dev-lisp/uiop
virtual/commonlisp

The full package list is available at p.g.o but those above have no
other maintainer.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 3 Nov 2021 at 14:15, Michael Orlitzky <mjo@gentoo.org> wrote:

If no one intends to join, we should drop the following to maintainer- needed:

I use some of those packets daily. Is there a way to join the Common
Lisp project without currently having maintainer status or is that not intended?

Especially dev-lisp/sbcl is important to me. I use the majority of the mentioned software, but the distribution of the libraries usually
happens through different channels, so I did not install those via
portage. When taking those over I'd have to look into how they are
packaged. Maintaining the Common Lisp implementations on the other
hand should not be a major problem. I regularly build SBCL and CLISP
from source on systems which don't provide it in another way or don't
support current system calls which the binary version expects. I also
have experience writing ebuilds.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 2021-11-03 at 16:25 +0100, Max Zettlmeißl wrote:

On Wed, 3 Nov 2021 at 14:15, Michael Orlitzky <mjo@gentoo.org> wrote:

If no one intends to join, we should drop the following to maintainer- needed:

I use some of those packets daily. Is there a way to join the Common
Lisp project without currently having maintainer status or is that not intended?

I don't think you can join the project, but you could still be added as
an additional proxy maintainer for those packages you care about. That
would let you take care of them using pull requests once everyone is
made aware that common-lisp@ isn't going to respond to RFCs.

Then if the common lisp project is ever disbanded, you would remain as
the sole maintainer of those packages rather than having them go to maintainer-needed.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Michael Orlitzky <mjo@gentoo.org> writes:

On Wed, 2021-11-03 at 16:25 +0100, Max Zettlmeißl wrote:

On Wed, 3 Nov 2021 at 14:15, Michael Orlitzky <mjo@gentoo.org>
wrote:

If no one intends to join, we should drop the following to
maintainer-
needed:

I use some of those packets daily. Is there a way to join the
Common
Lisp project without currently having maintainer status or is
that not
intended?

I don't think you can join the project, but you could still be
added as
an additional proxy maintainer for those packages you care
about. That
would let you take care of them using pull requests once
everyone is
made aware that common-lisp@ isn't going to respond to RFCs.

At the risk of over-committing myself (I'm stretched a bit thin
myself),
I'm willing to be in the Common Lisp project as long as Max does
the
heavy lifting.

I've recently taken interest in getting Nyxt in tree and it
depends on SBCL and a few other in-tree Lisp packages. However,
I'm not strong on Lisp environment, and will gladly yield to
anyone better suited.

WKR,
Aaron

--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iOwEARYKAJQWIQQEC6Ot+QKFRWIXfOT/l1wNKJSl0QUCYYPlfF8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MDQw QkEzQURGOTAyODU0NTYyMTc3Q0U0RkY5NzVDMEQyODk0QTVEMRYcdGl0YW5vZm9s ZEBnZW50b28ub3JnAAoJEP+XXA0olKXRxoABAMbMsd1wiRm+Z7RHcMEonu4G/bXg rKMqMkr4EtzHKcmzAP0R8esmIBFjJmbsfM6XwJXKh9FaunpEOTSrbPdcHo02Bw==asx1
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)