From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: vc-fossil to non-gnu elpa? Date: Mon, 04 Jan 2021 01:29:04 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15693"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: ams@gnu.org, emacs-devel@gnu.org To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 04 07:30:04 2021 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 1kwJNU-000403-TY for ged-emacs-devel@m.gmane-mx.org; Mon, 04 Jan 2021 07:30:04 +0100 Original-Received: from localhost ([::1]:45952 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kwJNT-000407-Vr for ged-emacs-devel@m.gmane-mx.org; Mon, 04 Jan 2021 01:30:04 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57078) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kwJMe-0003Tq-BX for emacs-devel@gnu.org; Mon, 04 Jan 2021 01:29:12 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:27021) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kwJMb-0006bN-3l; Mon, 04 Jan 2021 01:29:11 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id BFBC280922; Mon, 4 Jan 2021 01:29:06 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 6A28E8091C; Mon, 4 Jan 2021 01:29:05 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1609741745; bh=WLxUfIpW4Cd5//tOpvA/GRggaIqtFkp9mIp+vSkV4Y4=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=d1l9Y8f8TkxgmniN9E+kLPF/GfxIJXn34t2ayMM/obLrUwFkCqcQLu33cvQN0hijG yuim3VcNtzhWk0u7a5wbREPHwAjoZZ40o0WUH+ezvZogS6ViQtaJkevtCXKpBVuE+e lAfckxSKdAwT+twjLN/1s/LSM2q6VVHLpCd0H6st2oV3Pd2r0kxDXrfUjuRQM6Zgua ch5Cwb60fxHGAGYPAXDqC4CFzhb6WnVHsEmwitvA/l3CfHUNwlbqlx2sl+j+tjhUHr +yy2VoP6PprnJ0l4xNWelMPmZbglo6W84FznmaC6PtQLlt0e5bsI6+IQn6KBbPTKdM JQ9JRLmJfGjGw== Original-Received: from alfajor (unknown [104.247.243.191]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 27DFC120473; Mon, 4 Jan 2021 01:29:05 -0500 (EST) In-Reply-To: (Richard Stallman's message of "Mon, 04 Jan 2021 00:15:55 -0500") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:262398 Archived-At: > If the package meets our criteria, putting it into NonGNU ELPA is > _not_ the next step. The next thing we need to do is have a > conversation with its developers. That doesn't need to happen beforehand. It can happen in parallel or even afterwards (it's sometimes much easier to get a constructive discussion going with the other side when they can see the actual package we build and the problems we faced and the solutions we chose, and other times it's helpful to get their input on how to solve those problems. One size doesn't fit all). > We are just beginning to figure out how to have that conversation, so > we can't describe how to do it. Therefore, please tell us about the > package and we will take care of that aspect. I'm not sure who you're thinking of with this "we", because I definitely have no intention of doing that for packages other than the ones I add. Stefan