Kissaki

Mh, I don't think saying hello is the problem, only when it is the only thing. I've never heard of "no hello" as a concept before. And dislike the crossed out hello images on the club website. A respectful hello as an opener to the question seems appropriate.

What immediately came to mind is "Don't ask to ask, just ask". But that's not regarding a hello opener.

StackOverflow has "How do I ask a good question?". But that's very verbose and elaborative, very extensive.

Last time I looked for something similar I didn't get anything.

The form of how questions can or should be asked depends on context as well. So I'm not sure there's something that would fit all forms of communication or platforms.

What I would likely do, if I had the need for it, is prepare a text template to copy and paste like "[Hi/Hello.] Please write your full question context in one message so there's no round-trip delay or interruptions and the intended question message completeness is obvious."

If it's just occasionally I'll just write it then and there myself.

I'm just glad we didn't end up with this one (seen in the ticket)

Damn, sad story behind the color

I had never heard of opkg. I looked it up:

opkg: Fork of ipkg lightweight package management intended for use on embedded Linux devices;

ipkg: A dpkg-inspired, very lightweight system targeted at storage-constrained Linux systems such as embedded devices and handheld computers. Used on HP's webOS;

Wikipedia has no dedicated pages for either of them. I guess they're quite niche.

I've used it at work. But the manual management/maintenance of a commit list makes it practically infeasible. I've use it for bit cleanup commits, but not since. When blaming, the previous revision is just one click away anyway. The maintenance doesn't seem worth the effort.

I guess a commit message tag and script that generates it automatically could make it viable. But I've not found the need to yet.

I looked into the document and man, that's a lot of points.

Skimming it, it's all very vague and does acknowledge states autonomy over what they consider legal or not. But there is so much in it, and the general broad and cooperative and sharing nature of it certainly warrants skepticism and concern - especially with how different cooperating states can be, and how such a push may have unintended side effects.

Who are these people you portray? Do they even exist?

The China equivalence is so far off. The surveillance systems, the press coverage, the open criticism, and the pretext/goals are all very different between China and this.

In German we say "doppelt hält besser". Is there an English saying like that? "Twice is stronger/more stable/holds better."

Lol at taking over open tabs from Chrome.

Does the default-enabled dialog happen in EU too? Seems unlikely to be GDPR conforming, which requires explicit, informed consent, with an equal decline option.

Installable alternative: https://zealdocs.org/

Given that it is high level, I assume you did not want to include this. I'll mention it here in a comment either way. Text form in the commit message.

I really like using conventional commit messages and introduced it in my projects. We defined a few types, and more leniently choose optional scopes. It's very useful for categorizing and skimming through commit lists, and for generating changelogs/release notes. `fix(account): Use correct hasing xy"

Consistent imperative form is important to me too. The commit message examples talks about "Summary of changes", which has no verb, and so, may mislead to a different undesirable form of summarizing changes. ("Change xy" instead of "changed xy" or "[now] does xy [at runtime]" or "did z".)

I didn't fully read it, only skimmed, so excuse me if I missed mentions of the commit message text form. It seems very elaborate otherwise.