Conversation

The older I get, the more I appreciate it when a project has a very high level description of what it is somewhere prominent. It makes it much easier for me to get a handle of what it's about.

In the olden days, this as the NAME section in its manual page, but, alas, nobody cares about those anymore.

In spirit, this is the first line of a git commit message.

1
0
0
@liw This reflects me on cover letters of large patch sets. Putting weird acronyms and reference to spec is only good for details. You still need to write the story and let the reviewer use the acronyms and spec to check the minor details.
0
1
1