From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Justin Burkett Newsgroups: gmane.emacs.devel Subject: Re: URGENT - which-key FSF contributor status Date: Thu, 20 Jun 2024 17:16:09 -0400 Message-ID: References: <87le4r98m9.fsf@jeremybryant.net> <86le4rjv9p.fsf@gnu.org> <87a5l78kc0.fsf@posteo.net> <87msp6o9o4.fsf@jeremybryant.net> <87sexelgnj.fsf@posteo.net> <86wmmqtmkl.fsf@gnu.org> <87wmmqmkh3.fsf@posteo.net> <87le32vyva.fsf@posteo.net> <87h6dqvy23.fsf@posteo.net> <87a5jivsha.fsf@posteo.net> 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="16230"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Philip Kaludercic , Eli Zaretskii , jb@jeremybryant.net, emacs-devel@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jun 20 23:17:17 2024 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 1sKP9g-00040u-8y for ged-emacs-devel@m.gmane-mx.org; Thu, 20 Jun 2024 23:17:16 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sKP8v-00084M-RM; Thu, 20 Jun 2024 17:16:29 -0400 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 1sKP8t-00083S-6C for emacs-devel@gnu.org; Thu, 20 Jun 2024 17:16:27 -0400 Original-Received: from mail-lj1-x22d.google.com ([2a00:1450:4864:20::22d]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sKP8q-0006Pb-CS for emacs-devel@gnu.org; Thu, 20 Jun 2024 17:16:26 -0400 Original-Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2ec0f3b9cfeso13910071fa.0 for ; Thu, 20 Jun 2024 14:16:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=burkett-cc.20230601.gappssmtp.com; s=20230601; t=1718918181; x=1719522981; darn=gnu.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=lhDHQRnXARDxZZLaxW4ed7dODe2jUFkjrF1lbRM9G38=; b=bPhXdNSkSb3zjMSlb+RNIUxmsEb0ayrick/abtCW6wscjpyN4ju/WTQM2xUd5kTZaQ als75tKHnIIKhZlwOt1caKH9cQeo8vHKeaY+c23Yrizu+iGNdYXef5LDBlhOBqluwaH+ 1dFnr5FlmbKeCZEOBLpvZ+5hppMkx3z/p+n7+2JJlipvYbrZ7ukiHzKeReQyEl+aH2kk 6qKhHTAEe+rEqBXej4F3OhsSDC540GIsJ6oPsnPos+wIhUjNGWLTuoAfCh1qBJUlTVfe QDzOIrZ20eaWyrR5VJ4GM0fVmDW0t/Tbjj6G41CPXvI3bDH23WUZsiBaxQAGQnF5uw8B qUbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718918181; x=1719522981; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=lhDHQRnXARDxZZLaxW4ed7dODe2jUFkjrF1lbRM9G38=; b=gzWyvyY2YVq2p/PEiHGbEqXpLY+gs/eOsrE3mJ/5wHHzBK66TEjaAXruLyPBMdMviR sYHPME+Yme4ACEuL/+hfLBpEJW+X9bTkZUvRXq0k2+5cbZ3Yh51RrWO2mmTIl25rfzGi O8qvxd5+NG4p8JakfiggV7ckF9mvdRedq+VX07mXTVBvQa4gJOdyMWgamp0m0ALNr4Fr WdTDd1PFnv/AbQOznw5FQW9JuGlrNe7hQQ+9JvoQ7dIGGxA0J9D/i82HQkiGFuvAk5za ERxyFscxFBY3Mcj+/Rv7EgfHiOI+an6XjVjDmSAYbFpvNJTcCBMf9rDzB8LDssykHO1s Ah5g== X-Forwarded-Encrypted: i=1; AJvYcCVDFci6PYL9BALP58HQPjL2XORCzu1o9py7CsSm01LxYVOGStZtjm/TcxJ/1+rXDHxzrLRN/O0nfo/dKXOSyOBBF55u X-Gm-Message-State: AOJu0Yzwep9zbbAbrB4WxrVnwcLOgJbjzYatO22fgJNbCgsCeF5plsIB L/4xrWx2w+PwSupdtABAnf0ptMsC+Ap6S1fLUei3bYLoelhKOEnNAT3Dc5HulWxGA1pxCuM0beQ NSDHbq7beW/WK5UANRLtl7dkp5KZUtFkbaOR43b+cyVSWyrF0u3o= X-Google-Smtp-Source: AGHT+IEGkB95IwYyPbquAk7wdNbJ2Kro7Dd/ar9T+04gw9b29WD3FAi7kfaeLvKWWe9Be2YZC+Jii28PzRDr9x+9Eg4= X-Received: by 2002:a2e:988d:0:b0:2ec:2038:9265 with SMTP id 38308e7fff4ca-2ec3cff8e23mr39968171fa.43.1718918180556; Thu, 20 Jun 2024 14:16:20 -0700 (PDT) In-Reply-To: Received-SPF: none client-ip=2a00:1450:4864:20::22d; envelope-from=justin@burkett.cc; helo=mail-lj1-x22d.google.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:320347 Archived-At: On Thu, Jun 20, 2024 at 2:25=E2=80=AFPM Stefan Kangas wrote: > > Justin Burkett writes: > > > I'd like to echo this question. Up until now, I have managed which-key > > through a github repo which then gets synced to elpa. I'm now not sure > > what to do with github and specifically contributions I get through > > there. I can archive that repo if bugs and contributions should now go > > through standard emacs channels. > > It's basically your decision as the maintainer of which-key. > > Org mode, CC mode, and others, have external repositories and merge code > back and forth. This would require you to periodically do these merges, > for example when you release a new version. This means checking for > changes in emacs.git and merging them into your tree, and then merging > the released version into our tree. > > Some other packages, for example Gnus and eglot, are now developed fully > in emacs.git and have abandoned their external repositories. Bugs for > those packages are now also always reported on our bug mailing list. > (We are also okay with preferring bug reports to go elsewhere, but we > will usually always accept bugs through our regular channels too, and > then simply forward them to you.) > > From the Emacs maintainer point of view, the latter option is always > going to be the easiest, but again: it's your decision. So please let > us know what you prefer. I'd suggest to document the parts that are > different from any other package in emacs.git in the "Commentary" of > which-key.el. > > I hope that helps, and please let us know if you have any questions. Thank you. Yes, that's very helpful. I prefer the latter option, too. I don't foresee many significant changes to which-key, and would rather have the process be as simple as possible. I will write up a notice in the readme on github and archive the project. There are one or two pending contributions, but I can send them through the emacs channels to learn about the process if that's alright. Best, Justin