chore: create NEWS.md

[moul]

Addresses #24 (comment).

I'd like your opinion on writing super long markdown lines to be more unix-friendly (grep, etc.) versus using the current method of having multiple lines in the raw files but preserving a single line in the generated markdown.

[jaekwon]

What's more grep friendly?
I don't expect everyone to split everything so it more or less fits in 80 chars.
But I will do it for you. And the resulting file is readable via vim or emacs.
I'm not sure what you're referring to otherwise.

[moul]

The "grep-friendly" feature allows accepting very long lines to ensure the date is always visible. Another option is to have multiple lines per day, still keeping them grep-friendly within 80 characters.

I tested the other option and found it works better on emacs/vim, but not as well with markdown rendering, unless we avoid embedding links to issues.

I'm curious about the format you have in mind. Could you please share?

[jaekwon]

Is this news? #59

[moul]

The question is more directed towards others. Personally, I connect daily and check the unread blue label.

There are two main strategies for news:

1. Keep it simple and expect people to invest time and effort, avoiding laziness. This may result in fewer people but potentially higher quality.
2. Provide simple news that can be used as a weekly report or automatic tweets, making it more accessible to a larger audience.

We can implement strategy 1 here and rely on the community to implement strategy 2 outside of the repository. This way, the repository can focus on building while external communication is managed separately.

The advantage of using 2, if implemented progressively like a changelog file, is that it makes it easy to check the git history/blame of the NEWS file. However, this competes with the already satisfactory feature of GitHub history.

I would appreciate additional opinions from more concerned individuals.

[moul]

I'm glad to help with the news about fireside chat (#53), but someone with stronger English skills might be better suited. We can schedule a call every two weeks to share updates (with screen sharing). During the call, we can engage in an AMA, discuss topics, and delve into details with the participants.

I believe it has the best ratio of low effort to high impact. It will facilitate the community in sharing news on social networks.