[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#108416: Format of short description should be mandated

>>"Sebastian" == Sebastian Rittau <srittau@debian.org> writes:

 Sebastian> Currently, most package start the short package
 Sebastian> description with a capital letter, but some don't. Also,
 Sebastian> some short descriptions end with a period, some don't. I
 Sebastian> think, policy state, what is correct.  (I would prefer
 Sebastian> capital letter and period, but that's just a personal
 Sebastian> preference.) Of course, policy shouldn't be too strict
 Sebastian> about that as there may be cases where for example a
 Sebastian> capital letter doesn't sense (e.g. aRts is a name that
 Sebastian> should be spelled just like that, also please respect
 Sebastian> non-english package description translations).

	Must policy be invoked for every picayune little detail of
 packaging? This change has to do with aesthetics, folks, dodgy
 capitalization does not really detract from the information available
 to users to make a selection.

	There are a number of things that one may find desirable
 (proper kerning in printable documentation is one), indentation of
 shell scripts, proper variable naming in configuration files, ad
 infinitum. However, policy is _not_ a compendium of recommended
 practices -- it is meant as a *minimal* set of guidelines that are
 imposed on package developers to aid in interoperability and
 integration of packages on Debian (unfortunately, policy started life
 as documentation for dpkg, so that was kinda blurred in the past). 

	I think this proposal fails to meet the ``Why does this need
 to be policy''cut, at least in my opinion. 

	Shouldn't we be moving towards making policy minimalist;
 rather than loading it with rules (all motherhood and apple pie
 rules, no doubt), bloating policy, just because we can?

 wondering how soo his typos would be declared serious bugs
 "In corporate life, I think there are three important areas which
 contracts can't deal with, the area of conflict, the area of change
 and area of reaching potential.  To me a covenant is a relationship
 that is based on such things as shared ideals and shared value
 systems and shared ideas and shared agreement as to the processes we
 are going to use for working together.  In many cases they develop
 into real love relationships." Max DePree, chairman and CEO of Herman
 Miller Inc., "Herman Miller's Secrets of Corporate Creativity", The
 Wall Street Journal, May 3, 1988
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Reply to: