The post was deleted
Does the Magazine article need be re-posted to howto here? It looks complete and standalone. Why?
This is the main question here.
Another question is, if this is really a good article. It is pretty long, has a lot of specific guides and the solution is kinda bad? It doesnt really show how to swap a package, likely because this is not possible currently.
This is supported right now. Support equivalent to dnf swap · Issue #3138 · coreos/rpm-ostree · GitHub tracks adding more documentation for it.
I don’t think we should replicate Fedora magazine articles on the forum.
You are also adding a lot of “how-to” posts here, and those would probably be better posted either as:
- Official documentation PRs. This works only for the things we support.
- Fedora Magazine articles (where they can be reviewed and checked before publication). This has a broader scope, but still need to meet some constraints.
- As articles on your own blog for example where there would be no such constraint.
Given the way Discourse works, “how-to” posts here can not easily be updated and will likely quickly become obsolete.
Removed atomic-desktops, coreos, iot, kinoite, proposed-howto, rpm-ostree, silverblue, sway-atomic
Yes I will work on putting these howtos in the right places.
It is not correct that posts cannot be edited in the future. But you need the right Trust Level in this Forum to do that.
I am sure if you ask for it, people can bump you up to TL4
Actually until recently, people even struggled to get Documentation PRs merged, but that is hopefully over for now.
I did not say that they could not be updated. I said it wasn’t easy.
Relying on TL4 users to update posts on the forum does not scale. This is also not the responsibility of those users. This is why we have documentation in git that anyone can make a PR to with any special privileges.
Well this is not about me, this is about making it possible for everyone to update them.
They should be able to if you make them a “wiki” post in discourse.
As an example, you should be able to edit this post.
Thanks, didnt know this was the solution.
@siosm I agree that this is also not perfect. Solutions like the wikipost (allowing TL2+ users to edit afaik) can help.
These howtos started in kind of a void, from the forum to the forum. I prefer writing in markdown, having a preview, writing on the phone etc.
A submission process could be done with categories, where proposed-howto is not indexed by search engines and blocked to TL2+ only, and only after a week with votes, restricted to TL2+, the post is rejected or accepted as a howto.
Docs using Git have a pretty big barrier, if it is just that editing on the phone is not easy. Or that making multiple changes at once, with separate discussions, requires having multiple git branches branched off before the first edit, …
Or the model where it needs active merging instead of a veto process, sometimes causing updates to fail.
Or that it needs knowledge of Asciidoc without an editor.
This is not perfect and also an experiment, but I think it could have some potential.
The purpose of this post just was to increase search engine results with more accurate search words. Lol I see how that is controversial