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: Fri, 23 Aug 2013 11:05:03 -0400 Message-ID: References: <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> <5216BADA.3080200@yandex.ru> <52174EFD.7070908@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1377270317 28363 80.91.229.3 (23 Aug 2013 15:05:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 23 Aug 2013 15:05:17 +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 17:05:21 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 1VCsvP-0005w7-Md for ged-emacs-devel@m.gmane.org; Fri, 23 Aug 2013 17:05:19 +0200 Original-Received: from localhost ([::1]:37356 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VCsvP-0003cy-7L for ged-emacs-devel@m.gmane.org; Fri, 23 Aug 2013 11:05:19 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42282) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VCsvG-0003cp-Ei for emacs-devel@gnu.org; Fri, 23 Aug 2013 11:05:16 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VCsvB-0004ci-B6 for emacs-devel@gnu.org; Fri, 23 Aug 2013 11:05:10 -0400 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:50261) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VCsvB-0004aU-6R for emacs-devel@gnu.org; Fri, 23 Aug 2013 11:05:05 -0400 Original-Received: from pastel.home (lechon.iro.umontreal.ca [132.204.27.242]) by pruche.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id r7NF53h8002957; Fri, 23 Aug 2013 11:05:04 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id AC2E263154; Fri, 23 Aug 2013 11:05:03 -0400 (EDT) In-Reply-To: <52174EFD.7070908@yandex.ru> (Dmitry Gutov's message of "Fri, 23 Aug 2013 15:01:01 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV4679=0 X-NAI-Spam-Version: 2.3.0.9362 : core <4679> : streams <1024538> : uri <1515318> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.22 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:162993 Archived-At: >> Currently your README.md contains nothing but a pointer to the webpage. >> Clearly, it's not that important to include every one of those elements. > When you see a pointer, you just follow it. Having a piece of text there > would be different. Ideally, the README would be a copy of the homepage, tho (and the same text would be used for ELPA's and MELPA's readme.txt). So you only need to maintain one text, which is then copied to all places. > But doesn't putting different information in different places make sense to > you, at least on some level? Hmm.... what an idea!? > For example, http://elpa.gnu.org/packages/company.html includes the contents > of NEWS.md, which looks great. > It could similarly combine README.md and Commentary. OK, that sounds promising, except I don't know how to combine them. Could you define clearly "the division of work" between the two? Or maybe we should just concatenate them and let the authors figure out how to divide the work between the two? One other issue is that Commentary does not have any markup, and I'd like to use markup more actively (e.g. converting into HTML when including it in packages/company.html, and rendering it on-the-fly in describe-package). [ Now, obviously we'd need a good on-the-fly rendering, which we don't have yet, so maybe the markup format won't be MarkDown anyway. ] Stefan