From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: What to do about unmaintained ELPA packages Date: Sun, 29 May 2022 17:41:14 -0400 Message-ID: References: <87k0a42fc9.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22841"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 29 23:42:02 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 1nvQfh-0005ka-IV for ged-emacs-devel@m.gmane-mx.org; Sun, 29 May 2022 23:42:01 +0200 Original-Received: from localhost ([::1]:35274 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nvQfg-0002yq-Co for ged-emacs-devel@m.gmane-mx.org; Sun, 29 May 2022 17:42:00 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50306) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nvQf4-0002Hs-BK for emacs-devel@gnu.org; Sun, 29 May 2022 17:41:22 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:18645) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nvQf1-0000uw-Md for emacs-devel@gnu.org; Sun, 29 May 2022 17:41:21 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 63E604400B6; Sun, 29 May 2022 17:41:18 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id AE3AA44240C; Sun, 29 May 2022 17:41:16 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1653860476; bh=QpGoITHP+fhB3o67pmLT+vF+wOTHRev0mUuy/m86ttk=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=XAWztoN2C1Y4ai48F5rOoO4K6MVfXDBZqaVppC2HY44dNfQt6z6HDhMX+B0kYh+E1 Xl11bV/six7cjjjllIxs4PYqruzWidfi999xq55CEky6NT7IhvNctytZVAArIr+rlu TE6942Db6tJ22Vc3VuabVkw7evsGPmcB9+uGcfMnvQEb6NtQ+kZTfQD2SeKrE/oi0i uPHu+iHJaTQAOvzEjbEfLHnuLDri8yxpjjNdvY31sbusLjl92uSrYdRaLA8q695wdW pA1zWv0gNNyx6/l8VIBfs9fVHDZEA3eSa5hA6mIvdsQT0w29YQCn+7L2vRIR7FDERX NvGbd1t+3Qkog== Original-Received: from pastel (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 6E3FC12036E; Sun, 29 May 2022 17:41:16 -0400 (EDT) In-Reply-To: <87k0a42fc9.fsf@posteo.net> (Philip Kaludercic's message of "Sun, 29 May 2022 23:34:14 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:290364 Archived-At: Philip Kaludercic [2022-05-29 23:34:14] wrote: > 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? Of course, especially for popular packages. > Or depending on how long the package has been unmaintained, how > popular the package is, how much effort it would take to apply the > changes one could modify the package in elpa.git/nongnu.git and inform > the maintainers that if they decide to start working on the package > again, that there are downstream changes that they should look at. Yes, we can use `:url nil` to indicate that `elpa.git` is considered as "the upstream". Of course, it's better if the current upstream can be modified to point back to us as the upstream so as to try avoiding accidental divergence in the future. Stefan