Documentation-Driven Development (DDD) could be a useful paradigm here. Don't consider a feature complete, that is don't merge any PRs, until the corresponding documentation for that feature has also been added and reviewed. On Fri, Aug 9, 2024 at 1:32 PM Tobias Wendorff < tobias.wendorff@tu-dortmund.de> wrote:
Am 2024-08-09 15:57, schrieb JK Laiho:
Using modern Podman features requires scrounging together information from scattered sources (the docs site, RedHat blogs, this mailing list, Reddit, GitHub issues...) plus the ability to figure out what info is still relevant.
I have to agree here.
Podman has the "disadvantage" (which is actually an advantage from a software point of view) that it is being actively and massively developed. Things change so quickly that the docs can't keep up and the users are left behind. And even worse: the great new features and their advantages often remain unrecognised because they have a one-liner somewhere in the changelog. That makes me sad, because the innovations are really cool.
Perhaps AI could be used to write the commits more prominently in a changelog (alongside the professionally curated changelog, of course). _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io