Re: DebianBug links (was Re: Complex conversion issues)
On Sun, Jul 27, 2025 at 11:31:40AM +0800, Maytham Alsudany wrote:
[...]
> I checked the Apache access logs and couldn't find requests to the
> bugstatus endpoint.. I'm either looking in the wrong place or equests to
> it are not logged.
Thanks - that's interesting, but not worth spending more time on.
[...]
> This functionality could be used for TODO trackers like
> https://wiki.debian.org/Javascript/Nodejs/Tasks/electron maybe?
>
> One of the things I really think this could be useful for is the "Debian
> Status" column at https://wiki.debian.org/FreedomBox/LeavingTheCloud ,
> where it solely relies on manual updates to packaging status.
Both very interesting use cases!
There was some talk on IRC about the wiki's mission statement, and these would
move us from a statement like "providing a place for the community to add
documentation they can't put anywhere else" to "providing workflows for the
community to manage their information". I think that's an improvement,
but it's worth flagging up the increase in scope.
[...]
> Thanks for the discussion, the points you're raising are very interesting ones.
I also enjoyed this conversation, but I think we've reached a conclusion.
The only thing we disagree about is the probability of needing to force-refresh
the cache, which is functionally just a disagreement about whether to tack
an extra service on the end of the technology stack.
The worst case scenario would be that we go with the solution you describe,
it ossifies and can't be changed, then someone comes along with a workflow
that's more time-sensitive than the technology allows. If that happens,
we can just tack the extra service on the end when the time comes.
Reply to: