From owner-svn-ports-head@FreeBSD.ORG Tue Jan 28 10:14:54 2014 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 16AB63F2; Tue, 28 Jan 2014 10:14:54 +0000 (UTC) Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CAA141DBC; Tue, 28 Jan 2014 10:14:53 +0000 (UTC) Received: by mail-pb0-f53.google.com with SMTP id md12so175154pbc.40 for ; Tue, 28 Jan 2014 02:14:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=2NTvARHg2Mgdga8fG0lRSDxACktWe8zPFxghROQXhpI=; b=UI5VhXPam7zsTjemUHQq3ntog9+XFAupzDmVppeRENiSLo/s3fPRorLnZhfPfNOvFi aXGYo6AdmETy9001P9rJIGf2YiJBv8CFa/P/D/cc9LPuRsbfmeRIwva7KMZkcdg66Nas ZiEGuMRo4DRQytXmcjMbihXiV/3cZB9N7wuClrWYk9BKq8AiMkLW8KhMuz5WixRa7bno /3POrXu1ki9wbTJWv0uDNp+BJ5J9LvtCG82UNoCI/u3MUbi8CTWHcjLuwlNqMfqbrtyQ RuIyONb2WQoJDQuwY/Fe3gRh/0X4jZQRbGKQTd0iY4U2dob4VbUC4VJ3LG2Ym8yPJasl /gmw== X-Received: by 10.68.180.66 with SMTP id dm2mr552761pbc.143.1390904092987; Tue, 28 Jan 2014 02:14:52 -0800 (PST) Received: from [192.168.1.7] (ppp59-167-128-11.static.internode.on.net. [59.167.128.11]) by mx.google.com with ESMTPSA id da3sm40833079pbc.30.2014.01.28.02.14.49 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jan 2014 02:14:52 -0800 (PST) Message-ID: <52E78316.7010708@FreeBSD.org> Date: Tue, 28 Jan 2014 21:14:46 +1100 From: Kubilay Kocak User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Thunderbird/27.0 MIME-Version: 1.0 To: Ruslan Makhmatkhanov , Alexey Dokuchaev Subject: Re: svn commit: r341401 - head/www/py-requests1 References: <201401271318.s0RDInCu014881@svn.freebsd.org> <20140127140508.GA68244@FreeBSD.org> <52E66ABB.5000002@FreeBSD.org> <20140127143457.GB71123@FreeBSD.org> <52E7785A.1070804@yandex.ru> In-Reply-To: <52E7785A.1070804@yandex.ru> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: koobs@FreeBSD.org List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 10:14:54 -0000 On 28/01/2014 8:28 PM, Ruslan Makhmatkhanov wrote: > Alexey Dokuchaev wrote on 27.01.2014 18:34: >> On Tue, Jan 28, 2014 at 01:18:35AM +1100, Kubilay Kocak wrote: >>> By default, most Python maintainers use the short description found in >>> either the modules setup.py metadata, or the short tag/summary from the >>> projects site verbatim, unless there is good reason to do so. In this >>> case: http://docs.python-requests.org/en/latest/ [...] >>> >>> For what it's worth, "for human beings" is almost a convention in Python >>> land for modules with 'beautiful developer API\'s' >> >> Right, in Python land it is. However, as a generic packager (that is, >> FreeBSD Project) we should provide package descriptions (that includes >> both COMMENT and pkg-descr) that can be comprehended by anyone, not just >> someone necessarily coming from the Python land. >> >> In this particular case, more neutral COMMENT, like "convenient (or easy >> to use) HTTP module/functions bundle" would IMHO be better. >> >> This is just my nit picking of course; no need to take any immediate >> action(s). >> >> ./danfe > > It's doubtful that Joe Average occasionally getting this port as > dependency will ever care about what it does. While to "someone coming > from the Python land" the meaning of it would be quite obvious. > This might be true, but I will grant Alexey that the "Python people know what it means" is the weakest of my arguments. My second point still stands; that the comment meets all the criteria I can think of for a short yet descriptive summary of what a port is, and/or what it provides. "HTTP library written in Python for human beings (Version 1.x)" It is; version 1.x of, a library, for HTTP, written in Python, for humans. On second look however, I *should* also be including the commas where they exist upstream (commas matter!,) though I dont know if we like commas in COMMENTS :) ./koobs