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 and release frequency Date: Sat, 24 Oct 2020 10:08:04 +0300 Message-ID: References: <8lm0yhtuul6tmc.fsf@iki.fi> 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="17883"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/+ (1036f0e) (2020-10-18) Cc: Antoine Kalmbach , emacs-devel@gnu.org To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 24 09:09:26 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 1kWDg6-0004XZ-Do for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Oct 2020 09:09:26 +0200 Original-Received: from localhost ([::1]:48362 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kWDg5-0002ih-Fu for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Oct 2020 03:09:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50992) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kWDev-00029z-4H for emacs-devel@gnu.org; Sat, 24 Oct 2020 03:08:13 -0400 Original-Received: from static.rcdrun.com ([95.85.24.50]:48141) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kWDet-0007EJ-2k; Sat, 24 Oct 2020 03:08:12 -0400 Original-Received: from localhost ([::ffff:41.202.241.51]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by static.rcdrun.com with ESMTPSA id 00000000002A0B3A.000000005F93D2D8.00006A9C; Sat, 24 Oct 2020 07:08:07 +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-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/24 02:08:11 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] 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:258402 Archived-At: My proposals for plan of action for ELPA on nongnu.org are following, and they are not in any order: - [ ] establish goals purposes for non-GNU ELPA. My proposal for purpose is to provide useful GNU Emacs packages as free software meant for inclusion into fully free and FSF endorsed free system distributions. Guidelines for free software system distributions on https://www.gnu.org/distros/free-system-distribution-guidelines.html should apply for non-GNU ELPA and for GNU ELPA as well. - [ ] set up the mailing list for non GNU ELPA. My proposal would be: nongnu-elpa-devel@nongnu.org as maybe it would be good not to mix it with emacs-devel - [ ] Find contact information of many developers and invite developers personally to contribute their packages, they can start contributing already by using the mailing list and collaborating with others. - [ ] discuss the set of policies or principles for non-GNU ELPA. For example do we really want to see Python packages wrapped inside of the GNU Emacs package? I don't. - [ ] obtain server space for hosting of a website - [ ] decide on sub domain or URL, it could for example https://elpa.nongnu.org - [ ] replicate GNU ELPA website in similar fashon on ELPA on nongnu.org without changing much, keep informing public on the website of the project's progress - [ ] provide hosting and shell access to set up git and free code hosting platform familiar to many developers using Github. Such free code hosting platform is https://gitea.io/en-us/ or Gitlab.com, I would prefer first. It looks similar to Github, look here: https://gitea.com/gitea/gitea-vet and there is problem with one Javascript, they have to be asked to publish the license properly. - [ ] install such git hosting, install Gitea or Gitlab or other web based git whatever be decided as best - [ ] use already made software for GNU ELPA to develop in same fashion for elpa.nongnu.org, as not to change drastically well established workflows - [ ] propose improvements to workflows both on GNU ELPA and non-GNU ELPA, and collaborate with emacs-devel - [ ] start distributing few packages, and keep including other packages - [ ] when time seem right, include the package repository specification in GNU Emacs - [ ] welcome and invite developers to switch to free hosting at nongnu.org - [ ] welcome and invite developers to contribute their packages to GNU ELPA and transition their package. Futurem may become blended. - [ ] keep doing all well established actions just as GNU ELPA is doing to provide more free software for purpose of expansion of fully free operating systems. - [ ] add additional scripts or support to help various other GNU/Linux distributions to easily package both GNU ELPA and non-GNU ELPA packages Jean