Correct policy for new ports' summary standard format

[crees]

Summary

This patch fixes the policy for new ports' summary standard format on Bugzilla in such a way that it is consistent with what bugs triagers prefer.

[crees]

Do you have a rendered version? I think the diff is missing a bit.

en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml

417–419

We report?

[salvadore]

Sorry, I was copying the diff from a bug report I created long time ago and I copied it wrong. Now it should be fixed.
If anyone wants to see the bug report, you can find it at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232816

By the way, on that PR the patch already got approved by koobs.

[crees]

Docs approval granted. Not sure if Mat wants to comment as it's a bugs part.

[salvadore]

Thanks!

When we know about Mat, please keep in mind that I have no commit bit, so someone else should commit the patch for me. Thanks.

[crees]

Ok, no worries, I'll commit when Mat approves.

[mat]

en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml

419–423

What is this <span class="quote">?

422

"short description of the port" was just right, why complicate it with some obscure variable expansion.

[mat]

en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml

422

Oh, do you mean the content of the COMMENT variable in the port?

If so, it would be preferrable to leave the "short description of the port" so that it is easy to understand, and maybe add a note saying something like:

To describe the port, the content of the <varname>COMMENT</varname> variable can be used.

[crees]

There are a couple of tagging issues I'll fix before committing, yes.

I'll use your COMMENT example.

[crees]

This matches your suggestions.

Let me know if you're happy to proceed.

[crees]

I'll deal with whitespace separately.

[mat]

Except for whitespace, this looks ok.