We do the same. We use a #news channel. We also include feeds for Rubygem releases, product blogs, security related mailing lists and so on. It’s a nice way to create a shared view of a dev supply chain.
Shameless plug: If you'd like to subscribe to a lot of these feeds together, I made a OPML generator a long time ago that generates a OPML subscription feed for all of your starred repositories on GitHub.
Generate your feed, and then import it in your RSS Reader.
Nice looking site and cool of you to make this. I’m wary of giving my email address to more companies. Even free, ethical sounding ones. It would be nice if rather than sending emails, you created consolidated RSS feeds that digested everything.
So a problem I've hit with this, is that if you subscribe to the RSS feed of releases, it gives you all ...tagged versions, I think? It's not just release releases; you'll get notified for alpha/beta versions and versions that are tagged but not quite yet officially released. This makes it noisy enough to reduce the value quite a lot.
I like this feature and use it quite a bit. I used to use yahoo pipes to mush a bunch of different repos into a single chronological feed to watch all of the projects my teams worked on. I liked that rather than having to click through lots of different feeds.
I’ve been meaning to write something to do that for the many years since yahoo pipes was euthanized.
Yes, it's certainly not a very generic solution but it was my special itch to scratch.
These days, I don't have much patience trying to find a solution for something the content provider should have done by themselves and installing a large program to do it which then might not even scratch my itch exactly like I want it to ... yeah, I rather invest an hour or two and come up with a simple solution of which I at least understand the limitations.
Static files are bliss. They might not be up to date to the millisecond but you will never have a problem pulling them or otherwise your whole service is going down in flames anyway.
If you do need real time updates, you wouldn't use RSS anyway, so this is a very workable compromise.