From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: URGENT - which-key FSF contributor status Date: Thu, 20 Jun 2024 19:22:52 +0000 Message-ID: <87msnf4dwz.fsf@posteo.net> 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 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36580"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Justin Burkett , 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 21:23:57 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 1sKNO1-0009FC-3a for ged-emacs-devel@m.gmane-mx.org; Thu, 20 Jun 2024 21:23:57 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sKNN7-0003mf-E3; Thu, 20 Jun 2024 15:23:01 -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 1sKNN5-0003lo-3o for emacs-devel@gnu.org; Thu, 20 Jun 2024 15:22:59 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sKNN2-0003ZA-Pt for emacs-devel@gnu.org; Thu, 20 Jun 2024 15:22:58 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id D0164240103 for ; Thu, 20 Jun 2024 21:22:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1718911374; bh=Nj4z+/8AUkCEnn5pTiSVK3QcXpZhTUdYgaYKluI2AB8=; h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:From; b=fi5CvBzznAYLrBbgxI9hP+P/ffdS0I4FuyXR0gyJRFWt23Okk2jvJx1bChjhbcfgl S8v42MYESsd3RlglmbHGFjnhKLofwCAIRYF9tZMkCxt5WIVuV85qNcXQWvB5SQgqWE AuyiO2XR7buj/PT911otiYA/3+3jrvVkltWxFSjFyKHgELleq8qLfS9VPFnAk8eyz5 njBOXEJdLRFWS/CQhYH2CfQHfZnEqnsbFq0AsVPKCv5kgf/ITVJkrGiFfTpVBmttg1 m4Msow7uYOnBpYGaN+TdGH+oTuxDj46iW3aaTreawAQ3DMXivGdP3XXy+ZoD09t05o JpZLFPEAu591A== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4W4r3x3qtYz9rxD; Thu, 20 Jun 2024 21:22:53 +0200 (CEST) In-Reply-To: (Stefan Kangas's message of "Thu, 20 Jun 2024 11:25:01 -0700") OpenPGP: id=7126E1DE2F0CE35C770BED01F2C3CC513DB89F66; url="https://keys.openpgp.org/vks/v1/by-fingerprint/7126E1DE2F0CE35C770BED01F2C3CC513DB89F66"; preference=signencrypt Received-SPF: pass client-ip=185.67.36.66; envelope-from=philipk@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, 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=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:320337 Archived-At: Stefan Kangas writes: > 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. That would certainly be one option, and one of the simpler ones. You could also ask for access to emacs.git, if you think you'll be needing it. > 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.) IIRC Eglot bugs are still sometimes reported on the old bug tracker, but that is being sunset. > 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. -- Philip Kaludercic on peregrine