From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: What to do about unmaintained ELPA packages Date: Mon, 30 May 2022 18:53:20 -0400 Message-ID: References: <87k0a42fc9.fsf@posteo.net> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15331"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 31 00:54:25 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nvoHI-0003oc-LP for ged-emacs-devel@m.gmane-mx.org; Tue, 31 May 2022 00:54:24 +0200 Original-Received: from localhost ([::1]:48088 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nvoHH-0003AM-HP for ged-emacs-devel@m.gmane-mx.org; Mon, 30 May 2022 18:54:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38858) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nvoGH-0002Q1-8M for emacs-devel@gnu.org; Mon, 30 May 2022 18:53:21 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49608) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nvoGG-0001zW-VP; Mon, 30 May 2022 18:53:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=sCrfqB66XQgc/tgAoQl1aPnfGLlcvUEOeThcAlWPDPE=; b=b8BOdbq4ZCw/ HCkllSW86Fu0ZDjFmxijuHUrMte5HAUggoeBd5A7dE992F8AwxjvNnAH8dA4WGex83XQ1KGRBUhdf +EOrcoMbyFJLerBj5YLlAeX96M86Vt+B2RYd2U5AcLm/HI6RScuol/Q2hv3i4QPbGB9Odlt4pUzqf jaYYh04fZhrgE3AvAG0ej+PgUJkJ2zXVvA8kLMvFa/2ejYThIPlmMRWr51475TxDOQdedCOoY3I/M v5b6d5j9sSpuD75c98Ay6LYe/bWTbfdbvCfdHpwb0j2BzUcT+WFLb9+yA1prfwYSGlZCuaT5EDtXg KORLv732a7c/mTyFaRGXAg==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1nvoGG-000763-Ng; Mon, 30 May 2022 18:53:20 -0400 In-Reply-To: <87k0a42fc9.fsf@posteo.net> (message from Philip Kaludercic on Sun, 29 May 2022 23:34:14 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:290389 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > I'd like to ask, if there some point at which should one should go from > regarding packages like these from "de facto unmaintained" to "actually > abandoned"? Perhaps if there was no real activity for over a year, > despite constant contributions? Would it make sense to call for anyone > new to take over maintaining the package? There is no need to have a rigid rule about this, but we should have a rough guide to go by. "Serious problems go unfixed for a year" sounds like enough reason to judge that there is a problem in maintaining that package. We don't need a rule about what we do if that happens, but we should take note of such packages and decide what to do. If a package is important enough, we might want to take action sooner than that. We can fix any GNU ELPA package if we see fit. We should try to discuss that with its maintainers first, but if they are nonresponsive, we don't have to wait to satisfy some rule. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)