From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: What to do about unmaintained ELPA packages Date: Mon, 30 May 2022 09:08:18 +1000 Message-ID: <877d642agm.fsf@gmail.com> References: <87k0a42fc9.fsf@posteo.net> <8a6d74f7-b78f-3dad-1bd5-f41354f4391f@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28656"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.7.24; emacs 28.1.50 To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 30 01:21:04 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 1nvSDX-0007J4-QX for ged-emacs-devel@m.gmane-mx.org; Mon, 30 May 2022 01:21:03 +0200 Original-Received: from localhost ([::1]:55690 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nvSDW-0007L6-8Z for ged-emacs-devel@m.gmane-mx.org; Sun, 29 May 2022 19:21:02 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34218) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nvSCR-0006ZS-Ho for emacs-devel@gnu.org; Sun, 29 May 2022 19:19:55 -0400 Original-Received: from mail-pl1-x62e.google.com ([2607:f8b0:4864:20::62e]:38747) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nvSCP-0005Rb-MV for emacs-devel@gnu.org; Sun, 29 May 2022 19:19:55 -0400 Original-Received: by mail-pl1-x62e.google.com with SMTP id n18so8857777plg.5 for ; Sun, 29 May 2022 16:19:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:user-agent:from:to:subject:date:in-reply-to:message-id :mime-version; bh=zXksd6XuaeMN2qI8bqCRzRUgLh89Dwx0itbNCi2l/Ik=; b=kGvo71rcXuLd18mYQPqRY0JVKKbN27sg9WEsBLyzlGY0Sd0h0zBZMkBhjwKZlxt7vq XLzWpb74paeNDbPu7NLhPsx5mRizvkN1VcKN+dUURHuB2rZSD4T2XNSg9k/pQBLPchOp WToCtoR6yzNbZvXvub97SFy8pSVZJW8kq0ocXKtj2bn3vGHuOIvvk1NH96nf+p0MGy4y 8m3yRJvbk3gBs21Q6SNXWAu4R8lHBv6XzomyEYo8lumMGv1AJR2sZsjZ9CBNWoeML8CA kEwzwBaMFutRae2LvGNx8zTb4pZUY+HvbYuVfAwWDoT10uye+n3ceaCNdHFNhQwVcktF N2OQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:references:user-agent:from:to:subject:date :in-reply-to:message-id:mime-version; bh=zXksd6XuaeMN2qI8bqCRzRUgLh89Dwx0itbNCi2l/Ik=; b=QwS1B/wUWilqyuEgLqQGm0cle/BwJeYV2QtRIpeJ6TNxig/sbWgdDSRsU1D60zAm/c CyxXeq5c6CEiHCOE7JzqVhQDti6zUvpNVx5fsWj7hredkTeliTHohiXP/hPqORhA87eh W8yQ9HKOnQmbFmXhm1fWVututDYRL4gYg7l4oPs0YiY1TsrKY1JOKQev4sOJdkgJkJ1/ zPh7UTIicFH6RdvnVL5RHGs7dZRzJpyGA7I0JFQaEP6NaFNdwnXhFW8fqDeg9pkKhIPX jkBLNO3uZyJDHbsx1IeFQ6DwnVeYFoA2vntagzhh4bZpRCZcVWb2m0pn0MSSWny4DT9w w9Mg== X-Gm-Message-State: AOAM530MnWb/xcdRnlRax89ADmlk9b1cFTajpP6xYj5mcobCLVh9aTSH kXZVsZamcutHAn7W6nBsIiS5hUPyGIo= X-Google-Smtp-Source: ABdhPJwX1+dhRwKTycjVyv5pocRgn9V/Ec63j/yk3hTI3A0c1hmfvGfnbTcv3guxZY4vcGyWM6sznA== X-Received: by 2002:a17:90a:550d:b0:1e2:eb94:588e with SMTP id b13-20020a17090a550d00b001e2eb94588emr4244112pji.15.1653866379092; Sun, 29 May 2022 16:19:39 -0700 (PDT) Original-Received: from dingbat (220-235-29-41.dyn.iinet.net.au. [220.235.29.41]) by smtp.gmail.com with ESMTPSA id g22-20020a056a001a1600b0050dc7628148sm7465868pfv.34.2022.05.29.16.19.37 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 29 May 2022 16:19:38 -0700 (PDT) In-reply-to: <8a6d74f7-b78f-3dad-1bd5-f41354f4391f@yandex.ru> Received-SPF: pass client-ip=2607:f8b0:4864:20::62e; envelope-from=theophilusx@gmail.com; helo=mail-pl1-x62e.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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:290366 Archived-At: Dmitry Gutov writes: > On 30.05.2022 00:34, Philip Kaludercic wrote: >> There are some popular packages on GNU ELPA (and I expect NonGNU ELPA) >> that are practically unmaintained. One example would be Yasnippet that >> has been gathering issues and pull requests on GitHub, mostly without >> any comments whatsoever. For example, see >> https://github.com/joaotavora/yasnippet/issues. Does anyone know of any >> other packages of this kind? > > Talking about yasnippet in particular, it more in the "stable" rather than > "bitrotten" category, so I wouldn't worry about it too much. > > Or definitely not resort to measures like removing the reference to the > upstream. > >> 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? 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. > > Personally, carrying over the development on ELPA would seem counter-productive. > Both due to the reduced potential community of contributors and reporters, and > because of the wealth of reports, discussions and docs that reside at the > currently dormant upstream. Kinda passive-aggressive, too. > > I think the best step right now would be to try to contact Noah and ask to share > commit access. And if not Noah, then Joao -- he's definitely still around. I would agree. First step is to try contacting the repository owner. I notice in the case of yasnippets, they are active in other projects, so there may be a good reason none of the issues or PRs are getting action in that repo. I'm not sure there is a 'one size fits all' answer here. We probably need to look at each case individually. I do think both ELPA and non-GNU ELPA would likely benefit from some statistic showing number of weekly/monthly downloads and/or possibly some heuristic quality metric i.e. number of open issues, whether the package has a test suite, number of compiler warnings, days since last update etc. While none of these are likely sufficient metrics on their own, perhaps a combination could be useful as an indicator. One unfortunate tendency in the current climate is to consider anything which has not had an update in some time to be abandoned. However, it could simply be it has reached a stable point of maturity where fewer updates are necessary or critical enough.