From: | Oleg Bartunov <obartunov(at)gmail(dot)com> |
---|---|
To: | Nikolay Shaplov <dhyan(at)nataraj(dot)su> |
Cc: | pgsql-www(at)lists(dot)postgresql(dot)org |
Subject: | Re: Streaming commtifest as RSS feed |
Date: | 2018-01-29 21:34:16 |
Message-ID: | CAF4Au4wCRLocs-bazZm5q8uHxkowSqd+cZrBrWX7sH8NOVODfg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Tue, Jan 30, 2018 at 12:27 AM, Nikolay Shaplov <dhyan(at)nataraj(dot)su> wrote:
> Hi!
>
> For my own purposes I wrote a script that creates an RSS feed of new patches
> submitted to commitfest (so I can choose one I can review).
>
> Not it just parses the commitfest site (and caches what can be cached)
>
> It now works online at http://perl.nataraj.su/commitfest-rss/commitfest-rss.pl
>
> The script itself is in the attachment.
>
> It perfectly suits me, but I think others may also need something like this.
> For example a feed of "ready for commiter" patches or feed of patches with
> "commited" or "returned with feedback" statuses.
> Or may be even some per patch feeds with the history of status changes.
>
> I think that these all things is better to write taking data right from the
> commtifest DB.
> If you need such feeds, and perl is acceptable as an implementation language,
> I can write script for all these cases.
Good idea ! It should quite easy to implement in commitfest web engine
https://git.postgresql.org/gitweb/?p=pgcommitfest2.git;a=summary
>
> --
> Do code for fun.
From | Date | Subject | |
---|---|---|---|
Next Message | Nikolay Shaplov | 2018-01-30 14:10:36 | Planet: some problems with changing feed url |
Previous Message | Nikolay Shaplov | 2018-01-29 21:27:40 | Streaming commtifest as RSS feed |