From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Payas Relekar Newsgroups: gmane.emacs.devel Subject: Re: Adding use-package to core Date: Thu, 17 Nov 2022 12:54:47 +0530 Message-ID: <87a64qrqau.fsf@gmail.com> References: <871qq2gbml.fsf@gmail.com> <83o7t6g7w8.fsf@gnu.org> <871qq2n89a.fsf@posteo.net> <83h6yyg0l5.fsf@gnu.org> <83v8nedqxp.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33590"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.8.11; emacs 29.0.50 Cc: Eli Zaretskii , philipk@posteo.net, 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:51:37 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 1ovZgO-0008aC-E6 for ged-emacs-devel@m.gmane-mx.org; Thu, 17 Nov 2022 08:51:36 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ovZfj-00063F-CQ; Thu, 17 Nov 2022 02:50:55 -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 1ovZMA-0005sp-2H for emacs-devel@gnu.org; Thu, 17 Nov 2022 02:30:46 -0500 Original-Received: from mail-pg1-x52f.google.com ([2607:f8b0:4864:20::52f]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ovZM6-0006Xd-4G; Thu, 17 Nov 2022 02:30:40 -0500 Original-Received: by mail-pg1-x52f.google.com with SMTP id n17so1235518pgh.9; Wed, 16 Nov 2022 23:30:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:in-reply-to:date :subject:cc:to:from:user-agent:references:from:to:cc:subject:date :message-id:reply-to; bh=gTLNzsOTURuDCP/MqY1BFTAgxGtvixuO/QqNSsjd8WE=; b=FwTCr7k+UNi1zxH9MHXdHjdLnhvWFr0nQKy9aQqoVg/NWodoT1o2MIls2o+yaGXlNL 6yItrNMVaFqiaI4dMb5UnwfbdcXRJMrSIXEBfJaLsoi1Efy7O3ZQKrmaJOsZyF51Fbnd TJ9+vK9hh4CV19oI5iIw7eFC/faUWvSU8BvzYFGlEBjhp+xqrsj5hv7Tqm5EcVa846OP HqKtqaAn0c+8+7ig2G5BGVl8lCHvLqCdJze6t76MwqABt4OuUjGG3CmyWIJZ2eEIIB7A Oayle9RU1bg0qHxvZNDRAfTqmTPGkqPH6XUqLBCNsDjavepKH557lUXOu/4+O6G7VJW4 dhQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:in-reply-to:date :subject:cc:to:from:user-agent:references:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=gTLNzsOTURuDCP/MqY1BFTAgxGtvixuO/QqNSsjd8WE=; b=rtyt1uvOFGcbSrOuJJmYWR24UUEaBo65KtBvsqu5u778cnOtNRbGP+Kg4bDmQlghK3 NmAZ+KKvxoH1wx29+BTm2Jwu1BsA9/aN8nZMRx0Ds+a/3uBcWQxpz9Il1J3I0oIOraHn iEqSNhso641+Sj5q/3KM4Tzj03xoXBDEmj/FSJ9juOqjQ4WoESn4P2AVSmLrS2jHW44H tDQlThKdwdxwVVgwFRZVV08eyyNWbdZYJ/xOjWkNEeDTKEl4OfbO0EBYDORmIcFxMOIW YzNbqIn0QJkMmVMJA7Q4sjlYpZbZGEg96vtP+RFTKvQHLQH6/EQTtD/BBm7teoTS8bTx DRTg== X-Gm-Message-State: ANoB5pmj7sPBrHITIv6zkt123buss1VbD4duTghTbDB/6ICanum5ZA1I fyi73I0KJ2PPO6EF2UKMCas= X-Google-Smtp-Source: AA0mqf5ma5AY+VckrGf209ZyafUr/D7DPI/iwq6laCheS5I/e5ji8DBLNYgVe7ubbJu8YRIz9/8nkA== X-Received: by 2002:a65:67d1:0:b0:476:87ad:9d78 with SMTP id b17-20020a6567d1000000b0047687ad9d78mr1010052pgs.169.1668670235784; Wed, 16 Nov 2022 23:30:35 -0800 (PST) Original-Received: from localhost ([150.107.26.23]) by smtp.gmail.com with ESMTPSA id e5-20020a056a0000c500b0053e468a78a8sm303982pfj.158.2022.11.16.23.30.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 16 Nov 2022 23:30:35 -0800 (PST) In-reply-to: Received-SPF: pass client-ip=2607:f8b0:4864:20::52f; envelope-from=relekarpayas@gmail.com; helo=mail-pg1-x52f.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 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Thu, 17 Nov 2022 02:50:49 -0500 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:300022 Archived-At: Stefan Kangas writes: > 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.) Agree, and thank you for picking this up! > 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. I would be in favor of this one. Mostly because it reduces administrative burden. Also, I expect any issues serious enough will get re-reported on debbugs anyway, and considering use-package has been around for a while, there shouldn't be too many of them. > 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). > > BTW, it might be worth taking a look at Eglot on GitHub to see how Jo=C3= =A3o > handled this: https://github.com/joaotavora/eglot Eglot is still being maintained by Jo=C3=A3o, while use-package cannot expe= ct such commitment from John. If Stefan or anyone is willing to volunteer, we can continue addressing issues/PRs on both Github as well as mailing list, but it must be a commitment at least until the repo is archived. There is also the fact that use-package has fewer expected changes in future while Eglot has long road of evolution ahead. It makes sense for eglot to keep both avenues available for users/contributors, while use-package does not have as much need. --