Re: [BuildStream] Proposal: spreading responsibility and maintainership [Was: 1.4 Release timeline]

[Tristan Van Berkom <tristan vanberkom codethink co uk>]

On Wed, 2018-12-12 at 10:03 +0000, Angelos Evripiotis wrote:
> Heya,
[...]
> Ah yes, if you’re not already an RSS person then you may have some
> hurdles. I’ve found it to be a great way to stay informed from lots
> of sites though.
>
> Personally I’m paying for a 3rd party aggregator, “Feedbin”, which
> polls the feeds I’m interested in. I can use their web interface to
> catch up on feeds.
>
> I also have a paid client on my phone “Reeder”, which connects to the
> aggregator and gives me a nice on-the-go experience.
>
> With feeds you do lose the nice reply-to-comment functionality. It
> also doesn’t have diffs, maybe I’d augment them with those if there’s
> enough interest. There’s also the possibility of data loss, since it
> is polling-based and has a 20 item history.
>
> I think the main value added would be the filtering I’ve already done
> in setting up separate feeds. I also like keeping it separate from my
> email, I treat it mostly as news. I still have email notifications
> set to ‘participate’.

A quick google shows this as my first result:

   https://ifttt.com/applets/147561p-rss-feed-to-email

Would I be totally off base to think that if we just had:

  * A machine to run a very lightweight service
  * A simple enough node.js script

We could implement the same with a couple days of work ?

Maybe bypass RSS altogether and use gitlab's same notification system
that we use to drive our IRC bot, to deliver a filtered stream of
emails to a list of subscribers ?

Cheers,
    -Tristan