From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Adding use-package to core Date: Thu, 17 Nov 2022 09:33:47 +0200 Message-ID: <83k03udoh0.fsf@gnu.org> References: <871qq2gbml.fsf@gmail.com> <83o7t6g7w8.fsf@gnu.org> <871qq2n89a.fsf@posteo.net> <83h6yyg0l5.fsf@gnu.org> <83v8nedqxp.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23631"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, relekarpayas@gmail.com, johnw@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Nov 17 08:34:31 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 1ovZPq-0005s5-OM for ged-emacs-devel@m.gmane-mx.org; Thu, 17 Nov 2022 08:34:30 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ovZPW-0007Km-U3; Thu, 17 Nov 2022 02:34:11 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ovZPC-0007Hp-B3 for emacs-devel@gnu.org; Thu, 17 Nov 2022 02:34:03 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ovZPB-00070h-VH; Thu, 17 Nov 2022 02:33:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=UBYak+G2mntKUsaILs/QuJfMPefUfLn+S6qevSjZGa8=; b=Pmd9DcE5IsL9 wpgIIw4VyBuLEIB6n1Qo2DCy7+zqvvlTN1eO3CWsoTnKWsIQ9/8iaYwrN3Q2Osa+T4vuuMxW/TvZM ZUOsx5VdJyZQ8woQ3rrMQWfjcVMuhPLOyhE2OdD7LkPvnN0qFmTMHVQYgq/IObZg9A5SaqZ0bVeOf +zvSO/PxkOdpoDlQXjaRAYtY6Z5YFJr+x/t5Yi0hfu3Xd2E6RqSPwEtYOFI8i+LftxZhyeNKEFzCi Ljj4VkkpbFlFdEhGt/WZ0R7SigaLB6mfxc3ToyivIoS0QruTgSc6P63bsyvlE4usv87/C7FM8el/w XqNMjLemIuzOrv/Atjrbyw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ovZP8-0005LM-Tc; Thu, 17 Nov 2022 02:33:47 -0500 In-Reply-To: (message from Stefan Kangas on Wed, 16 Nov 2022 23:17:18 -0800) 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:300019 Archived-At: > From: Stefan Kangas > Date: Wed, 16 Nov 2022 23:17:18 -0800 > Cc: philipk@posteo.net, relekarpayas@gmail.com, johnw@gnu.org, > monnier@iro.umontreal.ca, emacs-devel@gnu.org > > Eli Zaretskii writes: > > >> We could archive it after some grace period, say 3, 6, or N months. > >> > >> At the beginning of that period, we could add a comment to all open > >> issues and pull requests, saying where to report the issue. At the end, > >> we could do it again. Then we archive. > > > > And in the meantime someone will have to monitor the GitHub issues and > > update debbugs? > > In this scenario, I think so, yes. One way of doing it just to close > any _new_ issues immediately, asking them to use bug-gnu-emacs instead. > I'm already getting all the notifications as it is, and I'd be happy to > do that for the duration. (I'd expect a trickle rather than a storm.) We'd need Someone(TM) to volunteer to do these mundane and ungrateful tasks. > On the other hand, maybe it would be less confusing to just archive the > repository and be done with it. If I'm not mistaken, it would be hard > to migrate all issues to debbugs automatically, since GitHub works with > user names and not email addresses. So this option probably means > losing some bugs, and maybe frustrating some bug reporters. Maybe it's > worth it: I don't know. It will certainly mean less work for us, as we won't need to watch the GitHub repository and synchronize it with debbugs. > I guess ultimately what we choose to do depends how important it is for > us to preserve existing feature requests and bug reports in a form where > we can continue working on them (e.g. by closing fixed issues). We can include a reference to the original issues in debbugs reports. Then people who need that can look up previous discussions.