From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Yoni Rabkin Newsgroups: gmane.emacs.devel Subject: Re: add emms to ELPA Date: Sat, 18 Oct 2014 19:16:57 -0400 Message-ID: <87fvelx91y.fsf@rabkins.net> References: <871u7mpszc.fsf@kanis.fr> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1413674248 16542 80.91.229.3 (18 Oct 2014 23:17:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 18 Oct 2014 23:17:28 +0000 (UTC) To: Emacs Development List Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 19 01:17:23 2014 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 1XfdFS-0007hA-Tl for ged-emacs-devel@m.gmane.org; Sun, 19 Oct 2014 01:17:23 +0200 Original-Received: from localhost ([::1]:37992 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XfdFS-0002p5-5o for ged-emacs-devel@m.gmane.org; Sat, 18 Oct 2014 19:17:22 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41471) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XfdFC-0002ov-Bc for emacs-devel@gnu.org; Sat, 18 Oct 2014 19:17:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XfdF7-0006K8-5J for emacs-devel@gnu.org; Sat, 18 Oct 2014 19:17:06 -0400 Original-Received: from smtprelay0229.hostedemail.com ([216.40.44.229]:55695 helo=smtprelay.hostedemail.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XfdF7-0006F9-1L for emacs-devel@gnu.org; Sat, 18 Oct 2014 19:17:01 -0400 Original-Received: from filter.hostedemail.com (ff-bigip1 [10.5.19.254]) by smtprelay08.hostedemail.com (Postfix) with ESMTP id 54CCF29DDE8 for ; Sat, 18 Oct 2014 23:16:55 +0000 (UTC) X-Session-Marker: 796F6E69407261626B696E732E6E6574 X-HE-Tag: watch25_1feccc9629e02 X-Filterd-Recvd-Size: 2645 Original-Received: from yrk-ThinkPad-T410.rabkins.net (c-75-69-93-148.hsd1.nh.comcast.net [75.69.93.148]) (Authenticated sender: yoni@rabkins.net) by omf05.hostedemail.com (Postfix) with ESMTPA for ; Sat, 18 Oct 2014 23:16:59 +0000 (UTC) X-Ethics: Use GNU In-Reply-To: (Stefan Monnier's message of "Fri, 28 Jun 2013 18:59:13 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.94 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 216.40.44.229 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:175548 Archived-At: Hello. I've picked up the maintainership of Emms and am slowly going through the backlog. Stefan Monnier writes: >> emms is an emacs music player >> https://www.gnu.org/software/emms/ >> Since it's already a GNU project, I think all the paperwork is taken >> care of. > > As Richard explained, there's no such guarantee, but indeed > copyright.list includes a 16 assignments for EMMS, so it seems very > likely to the paperwork has been taken care of. Please check with > the maintainer. I went through the AUTHORS file included in Emms and compared it to the entries in copyright.list. Every person except one listed in the AUTHORS file has either an assignment for Emms or for Emacs on file (and some, like me, have both). I tracked down the commit for the one person who didn't have any assignments with the FSF, and it turns out that commit is a trivial single line of change: http://git.savannah.gnu.org/cgit/emms.git/commit/?id=c4a18712be3b036a2336db631a534d0e3ce162b9 I've removed his name from the AUTHORS file and placed it in a THANKGNU file instead. Could there have been significant commits in the past from people who were not included in the AUTHORS file? Perhaps, but I can't think of an trustworthy way of figure out if this is the case. >> I might have time to include it in ELPA. > > It would be great. The only potential problem is how to keep the `elpa' > code up-to-date. I.e. either move the focus of development directly in > the `elpa' branch, or get someone to take on the responsability to sync > the two (both ways) on a regular basis. I think that syncing makes sense so that other contributors can still commit to Savannah without needing to learn of a new place to send their modifications. -- "Cut your own wood and it will warm you twice"