Felix Lechner via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org> writes:
> Hi,
>
> I enabled an experimental barebones feature that broadcasts Debbugs
> changes on #guix. It's another technical feature that could improve the
> speed at which bugs are being closed.
Hello, this seems like a good idea in general.
>
> Please let me know what you think!
I have a few notes:
- Wouldn't it make more sense to put it to a different channel dedicated
for this, where people, who want to follow it, can see it?
- Seems like all issues are sent, not just those filtered for Guix. Does
that make sense? I am not that interested in other project issues
- Could at least the project be printed?
- Currently it seems that only id and 'changed' is printed, what about printing
what changed how - name of the issue + created/closed/other state
update, new message (if that is a thing) etc.
I don't remember ids of issues and I doubt there are people who do,
so it seems to me like printing just the id without any more context
(name) doesn't really serve much value and one has to open the issue
somewhere else.
Also, I don't really have much experience with Debbugs, so pardon the
simple question, but is it possible to somehow list issues with recent
activity somewhere? Like if I used emacs debbugs? (not necessarily new
issues, but even old issues with a new message)
Regards,
Rutherther
