Hi, Maxim Cournoyer <maxim.courno...@gmail.com> writes:
> Hi, > > Attila Lendvai <att...@lendvai.name> writes: > >>> I personally find the mailing list useful for getting quick overview of >>> what is happening and whether there is something interesting I should >>> pull. >> >> >> i think RSS readers serve that usecase better. codeberg seems to support RSS. > > I was thinking RSS would be better suited for that as well, but didn't > know Codeberg supported that! That's nice! Tomas, is this something > you'd be interested in trying out? If you use Gnus for emails, it also > supports RSS groups, and we have some doc covering that for Cuirass > (info "(guix) Cuirass Build Notifications") you can refer to, it should > be similar. I took a quick look and I am unsure how to use the atom feed provided by codeberg, I have ran into few issues. Only feed I found is this[0] one, but that seems to mix together various information. For example, I see this record in it: --8<---------------cut here---------------start------------->8--- admmq commented on pull request guix/guix#739 --8<---------------cut here---------------end--------------->8--- Granted, that information can be useful, but not as replacement for guix-commits. I was not able to find a feed just for commits (across all branches). The formatting is also not great, there is an entry per push, not per commit. But I could probably live with that. Another problem I am not sure how to address is that the feed has just 30 entries. I think neither Atom nor RSS defines any pagination, so I am not sure how to go about not missing anything. Email works fine, since it is pushed based. I am not sure how frequent polling I would need to do. Taking into account that it includes also the comments and such, that Guix repository is pretty active and that there are only 30 entries in the feed, I would probably need to check close to every second to make sure I do not miss anything. Which seems excessive. Any suggestions? Tomas 0: https://codeberg.org/guix/guix.atom -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
