From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: John Yates Newsgroups: gmane.emacs.devel Subject: Re: [External] : [ELPA] Package cleanup Date: Tue, 29 Mar 2022 19:05:21 -0400 Message-ID: References: <20220329004337.nzeew6dlyqxm7wat@Ergus> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23972"; mail-complaints-to="usenet@ciao.gmane.io" Cc: "emacs-devel@gnu.org" , Jimmy Aguilar Mena To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Mar 30 01:07:41 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 1nZKw8-00060q-MH for ged-emacs-devel@m.gmane-mx.org; Wed, 30 Mar 2022 01:07:40 +0200 Original-Received: from localhost ([::1]:53128 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nZKw6-0006PH-Ss for ged-emacs-devel@m.gmane-mx.org; Tue, 29 Mar 2022 19:07:39 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:48068) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nZKu7-0005Rv-MQ for emacs-devel@gnu.org; Tue, 29 Mar 2022 19:05:35 -0400 Original-Received: from mail-ot1-f49.google.com ([209.85.210.49]:40517) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nZKu6-00058v-2A for emacs-devel@gnu.org; Tue, 29 Mar 2022 19:05:35 -0400 Original-Received: by mail-ot1-f49.google.com with SMTP id o20-20020a9d7194000000b005cb20cf4f1bso13769516otj.7 for ; Tue, 29 Mar 2022 16:05:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3xoKnzltu7H3pZot344F7rVguo8TtH7JJ9Wq33GN0Yk=; b=ald16kSthGBm+gB9JA6I2K2sOhR+2kDtlz7tam0oHjZ7lPv5w6i8H9JYvBdDmiUCaZ EZfZ09I0CiT+w8zG5QvirO+wVGWBN4JR/C93tJ1MySNItUjoON0l4ldZnPZsP+WpRTVb PGPXOlGhIeXfScpjvLbs5025m3mxYWrzgw7AP2xiLi7w+4v1sNnal0+W83785aF6MUCz y0lOfmo7oJ/Cdg7VlQyyJ2qZ7Cdrh4Bx05CEEmynCvS2blsmJBzyegEpzQG2Oo3ZHBG4 NP9SWA8v4enJuvOMwtQcGD80Z5DuxXJmvNnvImvO4JmZXcV5v+6fR2IcYKWu4f0CkwQV 9T+Q== X-Gm-Message-State: AOAM5311zV2gpDfjX9ciV8MBC2jDlklwzyZ5PJ3bV+VOB///QdoltPR+ rShDRqT500o1bEkO4kzQP6vfshXjpN8LDdYwaMYvlK3/ X-Google-Smtp-Source: ABdhPJwSjnHkc+arzHT7PzXTzWu5ZTbDN6a+oizrP3DZ3L83JIFfNnnudGih2Gi71pRwpgklGif2zE9bDnmssSkt7Bw= X-Received: by 2002:a05:6830:4121:b0:5c9:4d2b:7364 with SMTP id w33-20020a056830412100b005c94d2b7364mr2195834ott.366.1648595133005; Tue, 29 Mar 2022 16:05:33 -0700 (PDT) In-Reply-To: Received-SPF: pass client-ip=209.85.210.49; envelope-from=john.yates.sheets@gmail.com; helo=mail-ot1-f49.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no 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:287572 Archived-At: On Tue, Mar 29, 2022 at 6:05 PM Drew Adams wrote: > But again, whether some package starts to result > in problems where it didn't previously doesn't > follow from its not having been updated for 5 > years. Similarly, it doesn't at all follow that > a package that's been updated a lot doesn't have > problems, including doesn't introduce new problems > from some recent update. > > Bugs and curating/testing are different from the > question of update frequency or recentness. Full agreement. Same holds true for a package on github. Lack of update is merely a vague proxy for abandoned. And, as you point out, abandonment does not imply non-functional. But if there is no mechanism to, at least, identify decay then, over time, the ratio of high quality packages to those of lesser quality drops. Not a great recipe for brand maintenance.