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: Wed, 16 Nov 2022 21:29:10 +0200 Message-ID: <83h6yyg0l5.fsf@gnu.org> References: <871qq2gbml.fsf@gmail.com> <83o7t6g7w8.fsf@gnu.org> <871qq2n89a.fsf@posteo.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22008"; mail-complaints-to="usenet@ciao.gmane.io" Cc: relekarpayas@gmail.com, stefankangas@gmail.com, johnw@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 16 20:29:47 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 1ovO6U-0005Xx-Tz for ged-emacs-devel@m.gmane-mx.org; Wed, 16 Nov 2022 20:29:47 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ovO66-0007QB-4H; Wed, 16 Nov 2022 14:29:22 -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 1ovO5z-0007Ov-GY for emacs-devel@gnu.org; Wed, 16 Nov 2022 14:29:16 -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 1ovO5y-0003Ok-AB; Wed, 16 Nov 2022 14:29:14 -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=+SAxcvEDjfM4ZqjFCnovc4/94efGrqlzLNYu/rbi/Xc=; b=oq4KPtFmBHq9 tfOWq8BsvlRQgA6vWf+Xg8N9UIPjsE1iiN3kvvZlx4JWxh/aZZ+ywe0MlAlVbws72Wt7ID+1scIdp LvP2v0FcBaF5TXQGwl1+P/cQUPGVMipTne4Z5naKi/cqLNfe+FO6vudf0Ik/o+5VRrBAyi5vtzIt1 xbC5Gph/lz76DaTzZHjCbgi6U085lZDsaBHAmY+tnDsh9EmFAUV/bvL2xzAQdfmKA4sF2N6/TdlM9 58pVU5VrMshjGJLVV36mkumLSxzvcwXfVzH85ZZ4+8uQ4ZIDpSJqRIUjUv4PLmxOPxqvYxl2YZpCo HWrkL2+SySMnjR4PEoMO0g==; 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 1ovO5w-0003xr-Hx; Wed, 16 Nov 2022 14:29:14 -0500 In-Reply-To: <871qq2n89a.fsf@posteo.net> (message from Philip Kaludercic on Wed, 16 Nov 2022 17:01:37 +0000) 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:299973 Archived-At: > From: Philip Kaludercic > Cc: Payas Relekar , stefankangas@gmail.com, > johnw@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org > Date: Wed, 16 Nov 2022 17:01:37 +0000 > > Eli Zaretskii writes: > > >> From: Payas Relekar > >> Cc: philipk@posteo.net, stefankangas@gmail.com, johnw@gnu.org, > >> monnier@iro.umontreal.ca, emacs-devel@gnu.org > >> Date: Wed, 16 Nov 2022 20:59:26 +0530 > >> > >> Eli Zaretskii writes: > >> > >> >> From: Payas Relekar > >> > > >> >> Once it is merged and ELPA starts tracking use-package from core, > >> >> we should probably ask John to mark the repo as archived on Github as an > >> >> added incentive to direct people to emacs-devel as well as prevent > >> >> people from creating new bugs/PRs on Github. Does that sound like a good > >> >> idea? > >> > > >> > Yes, I think so. > >> > >> This is thinking ahead, but we'll want to think about existing open > >> issues and PRs before making repo archived. > > > > I don't understand why. Even if archived, it is accessible, no? > > AFAIK you cannot respond to an issue on GH when the repository is > archived, so that would make it difficult to tackle any issues that > would require feedback or discussion in general. What is the alternative? If you copy all the issues to debbugs, you have the same problem. And it is impractical to expect us to solve all the issues before importing use-package, and also impractical to update the issues in GitHub after the import. So I don't think there's any better solution than gradually work on the issues via debbugs. That is, for every issue we want to solve, file a debbugs bug report, and then work there.