From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: NonGNU ELPA Date: Wed, 25 Nov 2020 08:52:11 +0300 Message-ID: References: <87v9eg4gm5.fsf@gnu.org> <87o8k7yt7n.fsf@gnu.org> <87ima56h1a.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4015"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Cc: emacs-devel@gnu.org, bandali@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 25 07:51:55 2020 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 1khoeg-0000wm-Qz for ged-emacs-devel@m.gmane-mx.org; Wed, 25 Nov 2020 07:51:54 +0100 Original-Received: from localhost ([::1]:45478 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1khoef-0000wX-Rc for ged-emacs-devel@m.gmane-mx.org; Wed, 25 Nov 2020 01:51:53 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39584) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1khodF-00081O-Js for emacs-devel@gnu.org; Wed, 25 Nov 2020 01:50:25 -0500 Original-Received: from static.rcdrun.com ([95.85.24.50]:56027) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1khodD-0006FE-TO; Wed, 25 Nov 2020 01:50:25 -0500 Original-Received: from localhost ([::ffff:41.202.241.56]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by static.rcdrun.com with ESMTPSA id 00000000002C0006.000000005FBDFEAD.0000429C; Wed, 25 Nov 2020 06:50:21 +0000 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=95.85.24.50; envelope-from=bugs@gnu.support; helo=static.rcdrun.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, SPF_HELO_PASS=-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:259767 Archived-At: * Stefan Kangas [2020-11-24 23:06]: > I have three questions: > > Would it be useful to prepare a template for such a communication? > > Could we prepare a canonical URL for the GNU ELPA package > requirements/rules outlined in a previous email by Richard? I assume it > would be placed under https://elpa.nongnu.org/requirements.htm or > something similar, once Amin can get that hostname working. > > Should we add a special file to nongnu.git for recording the kind of > arrangement we decide on? I imagine that our ideal case would be number > one above. Perhaps we would only need to note anything down when we > have a different arrangement from the first case. Some thoughts: You should take notes by date on the relation with the developers as that helps greatly other developers to understand what it is. Any communication with developer as it is public should be quickly accessible from such notes. If there is specific decision or anything in the mailing list to be noted, you may insert URL to the message in such notes. Note could contain: - dates of notes - names and contact information - sources URLs and changes of such - references to previous decisive communication objects