Date: Mon, 27 Jan 2014 14:34:57 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: koobs@FreeBSD.org Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r341401 - head/www/py-requests1 Message-ID: <20140127143457.GB71123@FreeBSD.org> In-Reply-To: <52E66ABB.5000002@FreeBSD.org> References: <201401271318.s0RDInCu014881@svn.freebsd.org> <20140127140508.GA68244@FreeBSD.org> <52E66ABB.5000002@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140127143457.GB71123>