Greg Wooledge [2025-05-20 16:49:28] wrote:
> On Tue, May 20, 2025 at 16:38:16 -0400, Stefan Monnier wrote:
>> In contrast my proposition means that when a new release happens we just
>> get a new set of pages, which start empty (this part can be done fully
>> automatically) and can be filled progressively, which should be much
>> more amenable to crowdsourcing.
>
> I have multiple problems with this proposal.
>
> 1) Most pages don't actually become obsolete with a new Debian release.
> The number of incompatible changes in a new release is usually
> pretty small.
>
> 2) Re-creating the *entire* wiki every time there's a new release is
> a stupidly ridiculous amount of effort. Not just the initial act
> of moving creating a whole new versioned page for every existing
> nonversioned page -- which by *itself* is already ridiculous --
> but then there's the step of rewriting the whole wiki.
>
> Rewriting.
> The.
> Whole.
> Wiki.
>
> Do you even hear yourself?
>
> 3) Who's this "crowd" that you're planning to "crowdsource" all of
> this work onto?
I'm quite aware of these holes in my proposal.
I do think they can be plugged to some extent.
E.g. when a page doesn't exist but a page for an older version does
exist, we could show that older page with a note saying something like
"this is for version FOO so it may be outofdate, but maybe it's still
relevant".
So while a new version may start completely empty, visiting its pages
would still show the same info as before, save for the added
outofdate notice.
Stefan
