From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 15AD1158086 for ; Wed, 3 Nov 2021 21:50:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 26737E090E; Wed, 3 Nov 2021 21:50:38 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6552EE0903 for ; Wed, 3 Nov 2021 21:50:37 +0000 (UTC) Message-ID: <3295e14fe8dd5ffa2bab5111533be8aa2890e1fe.camel@gentoo.org> Subject: Re: [gentoo-dev] Common Lisp project is empty From: Michael Orlitzky To: gentoo-dev@lists.gentoo.org Date: Wed, 03 Nov 2021 17:50:32 -0400 In-Reply-To: References: <2f3e558beab963b3c7d80d69dc94d4a0f6fad14e.camel@gentoo.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: 9f58d5f5-4fed-485f-8653-257273881c86 X-Archives-Hash: fed0d4d018e7a8968e4ae77f5fcc13db On Wed, 2021-11-03 at 16:25 +0100, Max Zettlmeißl wrote: > On Wed, 3 Nov 2021 at 14:15, Michael Orlitzky 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.