From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: ELPA contributions? Date: Tue, 13 Oct 2015 12:30:11 +0100 Message-ID: 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> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1444735871 1724 80.91.229.3 (13 Oct 2015 11:31:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 13 Oct 2015 11:31:11 +0000 (UTC) Cc: Eric Abrahamsen , emacs-devel To: Phillip Lord Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 13 13:31:11 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 1ZlxnQ-0005r1-6E for ged-emacs-devel@m.gmane.org; Tue, 13 Oct 2015 13:31:08 +0200 Original-Received: from localhost ([::1]:33882 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZlxnP-0008Tk-Jh for ged-emacs-devel@m.gmane.org; Tue, 13 Oct 2015 07:31:07 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38460) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZlxmY-0008Ps-1D for emacs-devel@gnu.org; Tue, 13 Oct 2015 07:30:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZlxmW-0006n9-SP for emacs-devel@gnu.org; Tue, 13 Oct 2015 07:30:13 -0400 Original-Received: from mail-lb0-x22c.google.com ([2a00:1450:4010:c04::22c]:33273) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZlxmW-0006mw-Lj for emacs-devel@gnu.org; Tue, 13 Oct 2015 07:30:12 -0400 Original-Received: by lbbk10 with SMTP id k10so16135167lbb.0 for ; Tue, 13 Oct 2015 04:30:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=H+buMhQlf5FmvhPImC43iFRmGREjXElj5Wt/zJHRfkQ=; b=AfZiqovILB9M8pVBttEN4hMyQTvYs5Na/YBZhF3ahp8ImqBltSwL+UJpbRiINdz8Zr YITV1PlVQapjSLxQbHNrExrUmn1XK5C0Ol+yWZzHVNmRt1Peoh/2/2aR8gWu58mkCj0N njxKrJPHaBghe76IoPJQGDnQBHivIRx41/vs/KIk2AGjmuNoFHpmQmvpalRwD055LFdG iptgay9biJrIk42o3fCxcxwALNH8HXXqISBNe2+8cbaXaAYFRP3WWypBXSNopLsudshv GRZBJBL9QGlxLk++dJK25QYns6h3zj50ngf1KXznpauXhArYCIvvQLD1STR0CX9iECRC DSuw== X-Received: by 10.112.184.137 with SMTP id eu9mr14658859lbc.21.1444735811998; Tue, 13 Oct 2015 04:30:11 -0700 (PDT) Original-Received: by 10.25.27.78 with HTTP; Tue, 13 Oct 2015 04:30:11 -0700 (PDT) In-Reply-To: <878u77t8jw.fsf@russet.org.uk> X-Google-Sender-Auth: RpMoJ-mHKqAbXzm1iGRRwEvTPLU X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::22c 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:191446 Archived-At: 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..