Drupal provides project owners with the ability to follow issues on their projects. Simply go to your My Projects page and you can see an overview of your projects and even grab a RSS feed of the latest issues. But, if you are just a project co-maintainer or a contributor who doesn't actually have access to a project there is no nice and easy place to follow the issues on that project. I used Yahoo Pipes to solve this problem because it outputs RSS, has quick add buttons for sites like My Yahoo and Netvibes, can be added to a page as a badge, and it provides JSON and PHP access.
The image above shows the simple pipe I created. I went to each of the issues pages, grabbed the RSS feed for that issue list, and inserted it to Feed Fetch. I followed that up by using sort to bring the newest issues to the top (you can sort this is any way you like). And, then I output that. I can now view this in a number of different ways and places.
If you want to get fancy you only need to pull in one RSS feed. The variable called projects in the feed URL can be a comma separated list of project nodes.
awesome!
Great idea Matt! I am going to set this up for the contrib modules that I regularly use and support for the sites I manage.
Thanks!
Mark
no need for pipes?
So from your last note, it looks like that there would be no need for pipes(?)
Depends How You Use It
If you are just looking for an RSS stream there is no need for pipes (unless you are looking for something like different states on each project). Anyone with a bit of comfort manipulating the variables in the url can add projects into an RSS stream right from drupal.org.
I tend to use pipes because I'm looking for different states and versions on projects. For example, I used the advanced search and got a listing of issues on the jQuery Update module that are only for drupal 6. On other modules I follow I want all versions. I can't do this without piping different feeds together.
Another reason I use pipes is that I use features like the badge it offers to insert pipes into places I don't have an RSS reader.
great
Great explanation, thanks :) I also did a pipes mashup for tracking localization commits earlier which can also take a parameter, so I was curious why you use Pipes specifically. http://hojtsy.hu/blog/2007-mar-20/yahoo-pipes-wizardry-drupal-translatio...
A positive side effect of
A positive side effect of using pipes and not directly requesting feeds from drupal.org is that pipes feeds are cached.