New wiki chapter:
Whonix ™ Binary Images Policy
Could you please review my minor by comparison title and description changes?
For Whonix 16, let’s please do a “staged rollout”, i.e. not post on too many announcement channels right on first day of release.
A post was split to a new topic: Kicksecure (not Whonix!): using /etc/hosts to block advertisements and trackers
I had to look up what a kibibyte is. I learn something everyday.
The Notable Changes in a release announcement are based on git commit log. A recommend practice for git commit messages is:
“Use the imperative mood.”
For example:
Disabledracut
module resume in VMs since it might break the boot process if built insidechroot
. https://gitlab.com/whonix/vm-config-dist/-/commit/ee07d87be47c3c48f4369b5816876d5d826999a4
This then gets rewritten in (Stable Release: Difference between revisions - Whonix) on Stable Release - Whonix to:
- Disabled
dracut
module resume in VMs since it might break the boot process if built insidechroot
. https://gitlab.com/whonix/vm-config-dist/-/commit/ee07d87be47c3c48f4369b5816876d5d826999a4
Which might be more appropriate for the wiki. Should I ignore that git commit messages best practices part and try change my habits to use “descriptive mood” instead of “imperative mood”?
I am wondering if some effort on @torjunkie’s side for maintaining Stable Release - Whonix could be lowered.
Maybe Notable Changes
could be left out in release announcements by me.
- To avoid duplication.
Notable Changes
would then be auto generated in mediawiki markup instead of markdown makeup (forums). I could post them in the wiki instead. (Maybe with a comment if still in testing and not actually stable yet or wiki pending moderation as long as not in stable yet.)
Then there would be no need to copy/paste (and duplicate) them from forums to wiki. And fixes on top of my writeups would still be very much welcome.
Also if it seems useful… Feel free to edit my forum posts with the usual very much appreciated enhancements that are happening in the wiki all the time all over the place.
Other suggestions to simplify the changelog writing process?
To be honest, I hadn’t thought about it too much - I just preferred that phrasing. Happy to go either way.
It would be good if you can edit the stable release notes going forward, and just reference it in your forum post. Saves a lot of time. Then I’ll just do any finer edits later on.
This will be done that way from now. I’ve adjusted the changelog auto generator to use your chosen format. Example:
- Fixed
grub-live
(initramfs-tools
version).
([archive]
link is added by a mediawiki extension.)
Thanks.
As some dipshit keeps editing the “Contact” wiki page with spam, suggest you lock that page to contributors only.
Nobody should really be adding things there anyhow except for a few select people.
Done.
I don’t understand why this was removed:
A rule of thumb is to select
Y
orI
for packages coming from {{project_name}}, andN
for packages coming from other distributions. Otherwise settings affecting anonymity, privacy and security might be lost.
Users will inevitably come across this issue and won’t know whether to a) accept (Y or I), b) select N (possibly losing anonymity etc benefits in the process) or c) flip a coin.
If it doesn’t belong on that page, then where? Or are you saying this is no longer an issue?