On Mon, 16 Dec 2013 00:33:09 +0900 David Maiorino <maiorinoda...@gmai.com> wrote:
> Package: wnpp > Severity: wishlist > Owner: David Maiorino <maiorinoda...@gmail.com> > > * Package name : Open Time Zone Converter Package name should follow certain rules [1]. To cite the relevant bit: Package names (both source and binary, see Package, Section 5.6.7) must consist only of lower case letters (a-z), digits (0-9), plus (+) and minus (-) signs, and periods (.). They must be at least two characters long and must start with an alphanumeric character. So a name like "open-time-zone-converter" would do. > Version : 1.0.0 > Upstream Author : David Maiorino <maiorinoda...@gmail.com> > * URL : https://github.com/DMaiorino/TimeZoneConverter > * License : MIT/X > Programming Lang: Java > Description : A simple app to convert the time and date between > two different zones. I think currently there's no place for the word "app" in the (boring, official) documentation. It's being used colloquially (read: in a geek slang) to refer to mobile applications (those for iOS, Android etc), and it's also used officially by Microsoft to refer to their Metro-style (Windows RT API) applications. So I'd rephrase the description to be something like "A program to convert dates and times between two different time zones". > This simple app, developed in Java, is to allow the user to convert > the time between two timezones. To enhance the user experience, I > have included features such as: > > 1. Allow the user to choose a timezone for only certain regions. > 2. Allow the user to save/restore the current time zone info. > > The time zones are taken from the Java TimeZone Class. > > The code is currently maintained on GitHub > (https://github.com/DMaiorino/TimeZoneConverter) I think there's no place for "I have..." in the long package description: it has to be as neutral as possible. The reason is simple: when the user reads it in their package management front-end of choice, there's no sensible subject to which they could apply that "I". So just use something like "To enhance the user experience, this program allows (1) ... (2) ...". You could use "provides for" instead of "allows", but these are lesser details. The remark about the word "app" applies to the long description as well. See [2] for more info. 1. http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Source 2. http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-debian-control -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
