From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: ELPA commit freeze Date: Thu, 22 Aug 2013 20:51:17 -0400 Message-ID: References: <871u5w1tpy.fsf@yandex.ru> <520FA630.8080003@yandex.ru> <5211BBC8.40408@yandex.ru> <52133662.1000900@yandex.ru> <5213FA1C.3080700@yandex.ru> <52147393.9070509@yandex.ru> <5215364A.9000605@yandex.ru> <52155933.4080509@yandex.ru> <5215D018.70308@yandex.ru> <52167F22.3020501@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1377219093 24056 80.91.229.3 (23 Aug 2013 00:51:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 23 Aug 2013 00:51:33 +0000 (UTC) Cc: emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 23 02:51:35 2013 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 1VCfbC-0004R7-4B for ged-emacs-devel@m.gmane.org; Fri, 23 Aug 2013 02:51:34 +0200 Original-Received: from localhost ([::1]:34329 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VCfbB-0003kM-AP for ged-emacs-devel@m.gmane.org; Thu, 22 Aug 2013 20:51:33 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60492) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VCfb3-0003ic-0x for emacs-devel@gnu.org; Thu, 22 Aug 2013 20:51:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VCfax-0004my-6f for emacs-devel@gnu.org; Thu, 22 Aug 2013 20:51:24 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:43218) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VCfax-0004ma-1b for emacs-devel@gnu.org; Thu, 22 Aug 2013 20:51:19 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFHO+LNT/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLDiYSFBgNJIgeBsEtkQoDlymNUYFegxM X-IPAS-Result: Av4EABK/CFHO+LNT/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLDiYSFBgNJIgeBsEtkQoDlymNUYFegxM X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="23032206" Original-Received: from 206-248-179-83.dsl.teksavvy.com (HELO pastel.home) ([206.248.179.83]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 22 Aug 2013 20:51:11 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id A90FD66D7D; Thu, 22 Aug 2013 20:51:17 -0400 (EDT) In-Reply-To: <52167F22.3020501@yandex.ru> (Dmitry Gutov's message of "Fri, 23 Aug 2013 00:14:10 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 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:162987 Archived-At: > To have the description recognized by both Elpa and Melpa, currently I'd > have to keep the same text in README.md and Commentary. And > describe-package' buffer from Melpa would end up looking better due to not > having extraneous info. I don't think MELPA is very important here. I guess you use it so as to distribute snapshots of the code, but I think we need that for ELPA anyway (we already have it for Org, tho it's terribly ad-hoc). So assuming we'll have a "GNU ELPA snapshots" archive (help welcome), this is a non-problem. >> Why? Why not move the info from company.el to README.md (where it can >> be made prettier while you're at it)? > It already has a homepage that has all that info. It's prettier than the > github page due to having some dedicated styling. > Putting the same stuff on the homepage and in README.md would, again, result > in duplication, or at least some non-trivial work by automating the export > from the latter into the former. It's doable, but the link works just > as good. You currently have duplication between Commentary: and the homepage. I'm just suggesting to move that duplication from Commentary: to README.md. So duplication-wise it's no worse than what we currently have. Stefan