-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
status: 2023q1: clusteradm: minor changes #155
Conversation
Improve the appearance of each indented paragraph that falls below a list item (bullet point). Let's note that indented paragraphs are not a feature of AsciiDoc. (We have a good example of improving a report by not requiring indents, unfortunately I can not find the example.) Add full stops. NIC.br uses uppercase 'NIC' at <https://nic.br/>. Your.Org uses uppercase 'O' at <https://your.org/contact.php>.
Since the FreeBSD website is now mostly static, we have begun deploying infrastructure to mirror www.FreeBSD.org and docs.FreeBSD.org around the world in FreeBSD project-managed mirrors. | ||
* Create a new search database engine for internal FreeBSD.org searching needs like mailing list and docs | ||
* Create a new search database engine for internal FreeBSD.org searching needs like mailing list and docs. | ||
|
||
FreeBSD Official Mirrors Overview: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the colon here, should the subsequent paragraph become a list item? (Compare with uses of colons and list items above.)
Alternatively, use a subheading (without a colon).
@@ -12,22 +12,27 @@ In this quarter, the team has worked on the following: | |||
* Regular support for FreeBSD.org user accounts | |||
* Regular disk and parts support (and replacement) for all physical hosts and mirrors | |||
* Improve the PowerPC package builders + |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel that a full stop is needed in places such as this.
The two sentences that follow do have full stops.
Is this the example you are serching for? |
Thanks for the thoughts and ideas; I'll submit an update soon. |
Reported by: grahamperrin Pull Request: #155
That was it, thanks. |
<https://myren.net.my/> was unreachable (502, bad gateway) when I opened <freebsd#155>, I didn't mention it at the time. Still unreachable. In the Wayback Machine: <https://web.archive.org/web/20220701074213/https://www.myren.net.my/>. <https://www.mohe.gov.my/en/services/research/myren> might be a suitable alternative address.
#155 corrected use of uppercase for NIC.br and for Your.Org. #156 found a working alternative to a page that is no longer reachable; and English alternatives to two Japanese pages. Other minor changes, to make internal/about consistent with the status report that is changed by PRs 155 and 156. Approved by: dbaio Pull request: #157
Improve the appearance of each indented paragraph that falls below a list item (bullet point).
Let's note that indented paragraphs are not a feature of AsciiDoc. (We have a good example of improving a report by not requiring indents, unfortunately I can not find the example.)
Add full stops.
NIC.br uses uppercase 'NIC' at https://nic.br/.
Your.Org uses uppercase 'O' at https://your.org/contact.php.