On Mon, Aug 10, 2015 at 7:25 AM, Duncan <1i5t5.dun...@cox.net> wrote:
> ** summary bug number standardized to GB#xxxxxx or #xxxxxx or similar, > short enough for summary, easily identified. GB# would be distinctly > gentoo and could be expanded to KDEB#, GNB# (gnome), FDOB#, etc, for > If you're going to prepend the project, just spell it out. Don't invent new acronyms and abbreviations. Don't add a B suffix to everything. If it's the same everywhere, then it is meaningless, and just confuses things. I know what KDE is, but I'd have to go Google for what KDEB is (Is that KDE B? K Debian?), and hope Google indexed the above email from gmane or something. Don't prefix bugs with #. 1. It doesn't apply to every system: Random Project using Jira is going to have bugs like RP-123. You'd have to insert it in the middle of the identifier like RP-#123. 2. It is a relatively useless prefix at best: In the bug tracker UI, you search for 123, not #123. At worst, it makes the identifier invalid (as in the Jira example).
