Bug#139957: period at the end of short description?
>>"Chris" == Chris Waters <firstname.lastname@example.org> writes:
Chris> I'd rather have this be a guideline than a rule. So, I'm not sure
Chris> policy is the right place. (Sure wish we had someplace else where
Chris> guidelines could go.) But if it does go in policy, I think "should"
Chris> might be too strong.
I would have less objection were this couched as a
``recommends'' rather than a should rule, given that this is a
purely subjective, aesthetic view, with little technical relevance.
Chris> If we're going to discuss leading caps or not, I agree with Branden:
Chris> not unless it would be capitalized for other reasons (i.e. "GNOME").
If we are going to bloat policy like this, the subtitle
analogy that Colin used, in my _opinion_, is convincing.
Chris> Maybe we can make it a footnote. (Footnotes aren't normative, are
They are not part of policy, no. I would actually be in favour
of adding the convention about capitalization and periods as a
footnote, complete with the sub title analogy.
"Well, it's garish, ugly, and derelicts have used it for a toilet.
The rides are dilapidated to the point of being lethal, and could
easily maim or kill innocent little children." "Oh, so you don't like
it?" "Don't like it? I'm CRAZY for it."
Manoj Srivastava <email@example.com> <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
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com