From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.devel Subject: Re: ELPA contributions? Date: Tue, 13 Oct 2015 10:38:35 -0700 Message-ID: <87h9luactg.fsf@ericabrahamsen.net> References: <87612g5tmx.fsf@fencepost.gnu.org> <87io6cl0hx.fsf@russet.org.uk> <87lhb8ulex.fsf@ericabrahamsen.net> <87oag3d9a0.fsf@ericabrahamsen.net> <877fmrd8fg.fsf@ericabrahamsen.net> <878u77t8jw.fsf@russet.org.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1444757999 7168 80.91.229.3 (13 Oct 2015 17:39:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 13 Oct 2015 17:39:59 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 13 19:39:50 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Zm3YD-0007TI-79 for ged-emacs-devel@m.gmane.org; Tue, 13 Oct 2015 19:39:49 +0200 Original-Received: from localhost ([::1]:38401 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zm3YC-0003FM-K1 for ged-emacs-devel@m.gmane.org; Tue, 13 Oct 2015 13:39:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39398) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zm3XD-0002yt-6F for emacs-devel@gnu.org; Tue, 13 Oct 2015 13:38:48 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zm3X9-00023x-Mz for emacs-devel@gnu.org; Tue, 13 Oct 2015 13:38:47 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:43855) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zm3X9-00023r-Gd for emacs-devel@gnu.org; Tue, 13 Oct 2015 13:38:43 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Zm3X6-0006RJ-R7 for emacs-devel@gnu.org; Tue, 13 Oct 2015 19:38:40 +0200 Original-Received: from c-76-28-195-250.hsd1.wa.comcast.net ([76.28.195.250]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Oct 2015 19:38:40 +0200 Original-Received: from eric by c-76-28-195-250.hsd1.wa.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Oct 2015 19:38:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 55 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-76-28-195-250.hsd1.wa.comcast.net User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:jGHS4XJztw3UEJiSFM0CyptvaaU= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:191501 Archived-At: Artur Malabarba writes: > 2015-10-13 10:35 GMT+01:00 Phillip Lord : >> >> If I understand, a git subtree squash is not like a normal rebase; it >> does actually know about the commits that were squashed, as opposed to >> rewriting them like a rebase squash. > > Perhaps. But still, people should not squash to elpa.git. It has > downsides with no real benefits (that I know of). > > - If your package is part of elpa.git, then its commit messages should > be part of elpa.git's commit messages (even if the package is being > primarily developed somewhere else). > - The build-scripts can generate package change-logs from commit messages. > - If someone is trying to `git-blame' one of your package files, > having squashed is only going to complicate matters. > > I've added some better instructions to the Readme, but there's still > much that needs to be done to it. > >> > Also, Stefan's original recommendation was to just develop the package >> > in ELPA: no remote. >> > >> > I think this could be a more viable option if debbugs integrated with >> > ELPA a bit better. Personally, I wanted Github a tiny bit for the fame >> > and the glory, but mostly because of the issue tracking. Other people >> > probably make more use of Github's functionality (Phil mentioned pull >> > requests, etc), >> >> For my own packages, I'd moved them from mercurial on google code to >> github shortly before, so shifting the development to ELPA didn't seem >> like a good way forward. For dash, it just reflects the reality -- it >> was already developed on github and wasn't going to move. >> >> > but in my case, if I got an automatic email anytime anyone reported an >> > Emacs bug with "gnorb" in the package header... >> > >> > Hang on, back up. If `report-emacs-bug' prompted the user for a package >> > (with completion), and then I was automatically emailed with any bug >> > reports filed against my package(s) (where I'm in the Maintainer >> > header), and then I could continue that back-and-forth via debbugs, most >> > of the allure of Github would be gone for me, and I'd probably just do >> > the development within ELPA. >> >> All of that would help. > > All agreed. Some packages are always going to prefer being primarily > on Github. But having a better bug-tracker here would make it so that > fewer packages feel obligated to be on Github. For let-alist, for > instance, I wanted to develop the package here directly, so I created > a github repo with no source just for the issue tracker.. Who runs debbugs? How hard would it be to add a cc based on the Maintainer header?