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: Brand new clojure support in Emacs ;-) Date: Sun, 03 Sep 2023 19:07:57 +0300 Message-ID: <83cyyz6y02.fsf@gnu.org> References: <87il9kksqz.fsf@dfreeman.email> <87a5uw9ivs.fsf@posteo.net> <87ttt42gna.fsf@dfreeman.email> <87wmy080kn.fsf@posteo.net> <83v8djcydl.fsf@gnu.org> <87350ndquw.fsf@dfreeman.email> <83350ncbns.fsf@gnu.org> <87cyzrjbd8.fsf@dfreeman.email> <83zg2vav46.fsf@gnu.org> <87o7j99304.fsf@dfreeman.email> <87zg2hsyrd.fsf@dfreeman.email> <87h6ontwfv.fsf@posteo.net> <87r0nlngmo.fsf@posteo.net> <2d6a9558-4a4f-47e8-9122-62c7665e5f73@app.fastmail.com> <87ledn1dyu.fsf@posteo.net> <8bf9ac13-d620-4b5c-8e03-de21c4d85506@app.fastmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9077"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, joaotavora@gmail.com, rms@gnu.org, danny@dfreeman.email, emacs-devel@gnu.org, manuel.uberti@inventati.org To: "Bozhidar Batsov" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Sep 03 18:09:01 2023 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 1qcpem-00028X-Bs for ged-emacs-devel@m.gmane-mx.org; Sun, 03 Sep 2023 18:09:00 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qcpeG-0006le-MU; Sun, 03 Sep 2023 12:08:28 -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 1qcpeD-0006k6-NF for emacs-devel@gnu.org; Sun, 03 Sep 2023 12:08:26 -0400 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 1qcpeC-0000wa-Fe; Sun, 03 Sep 2023 12:08:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=PLd8MilfYE8bZG5duJY7GqtiCdVlJ0UyV8pSV0Yiha4=; b=qIEQrjpVE3xyCi3KcYHn PVw7oPGRKtiVggNoKGXUy0S0sJViMIg72IgLcDpY3VImyGci5UJDqeDgWMNIY67cX+QQbH+ujEnSl ZiYHNb7hsRKg58sCntPvOYz/oCdm9zW3n85Ux1hULSuGNHFkjj1i5XZj6Xrvhhrkt48/pPZt+gmtO OwiR6UXVv74AtS5bd08H9e6zrMQeL5q1qcmgFyhMPXdkZBhKxV5dAT5ygRG1TVtThua90U055Kky5 ApElP+0Nm8zN9vrFAI5HBflu/QKdt5O5RLht4lWKwO0PXdsxj5EwP2uQE4EKC3KFi3HRq9GPv0xY6 CTPqRw7oQRdm4g==; In-Reply-To: <8bf9ac13-d620-4b5c-8e03-de21c4d85506@app.fastmail.com> (bozhidar@batsov.dev) 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:309999 Archived-At: > Date: Sun, 03 Sep 2023 17:37:07 +0200 > From: "Bozhidar Batsov" > Cc: João Távora , > "Richard Stallman" , "Danny Freeman" , > "Eli Zaretskii" , "Emacs Devel" , > "Manuel Uberti" > > - where are issues reported? I don't want to use the Emacs issue tracker, but that'd be unavoidable > for something built-in, so instead of having one issue tracker you end up with two (one of which I > really dislike) There's no requirement to use debbugs for your package, even if it is in core. Org, for example, doesn't. When people submit bug reports about Org to debbugs, we redirect them to the Org list. > - some patches will be submitted on GitHub, some on emacs-devel - I highly doubt that all the > clojure-mode maintainers would be willing to deal with this Same here: there's no requirement to have patches submitted directly to us. Quite the contrary: as long as you and your colleagues actively develop and maintain the package, we'd prefer that patches are first reviewed by you. > - discussions related to problems/ideas would be happening in different places Again, not a requirement. But yes, the developers should be available on emacs-devel, because issues could pop up here. You could have a representative, though, not all of you. > - there's also so overhead of keeping the GitHub repo and the code in Emacs in sync Ihor and others should correct me, but what overhead do you have in mind? We already have a few packages that are basically developed outside of Emacs and only merged with Emacs from time to time, so you will not be the first package to go that way. > I can go on and on about this - hybrid development models simply come with a lot of overhead. I get > that here many people think that GitHub is the root of all evil, but political preferences aside - it's the > largest forge in the world by a huge margin and I think it provides unique benefits to projects that > can't be replicated elsewhere. At least not today. I think the difficulties are not as great as you imagine. And our opinions about GitHub are not relevant if the package is regularly merged into emacs.git.