ensure glossary is up-to-date, appropriate, and consistent for User Manual, Run Book, and Specification

[kiniry]

trafficstars

[cjerdonek]

A couple suggestions:

• add a few terms around open source (e.g. "open source," "copyleft," etc)
• alphabetize the entries

[cjerdonek]

PS - since the glossary is big, it looks like it would be easy to script alphabetizing it (e.g. in Python by splitting on \n* **, sorting, and then joining again). Or even just splitting on \n\n.

[kiniry]

Thanks for your input @cjerdonek. @mkiniry, make sure to add those terms and work with us to get the full glossary done for the phase-3 release.

And yes, @cjerdonek, we did intend to auto-sort the list. Feel free to provide a script in a PR. ;)

[cjerdonek]

I added a script in PR #481. You don't need to check it in if you just want to use it once.

[sfsinger19103]

There are several @review comments still in the glossary. What procedure do we want to use to resolve them? E.g., @sfsinger resolves them using her best judgment and asks for review from @kiniry?