On Tue, Nov 3, 2009 at 11:23 PM, Alan Burlison <[email protected]> wrote:
> There's been some recent discussion around how best to provide aggregation
> of the OpenSolaris blogger's feeds.

For blogs.opensolaris.org or planet.opensolaris.org? The two are
rather different.

Do we want to keep planet with manual editorial control? I think there
are advantages
to doing so.

> The main problem seems to be the
> overhead of managing all the feeds,

Part of that is the restriction on it being a Sun employee. However, it seems
to me that your suggestion can be used to work around that.

> so I'd like to propose the following:
>
> 1. Auth is extended with an additional field for each user, which will
>   contain the URL of their blog feed, if they have one.

Just blogs? Twitter? In other words, is this a point solution or an
extensible mechanism?

While we're on the subject, what about adding a hackergotchi field?
(Which could be used outside a blog aggregator.)

> 2. An XML-RPC interface is provided so that Planet can extract the list
>   of registered feeds (we already have a Python interface to Auth).

Now, if there were a way of putting a filter on that so it could be processed
then it would be more flexible: allowing planet (just as an example) to
manually select a subset. I'm thing of a more general case of the following:

> 3. An XWiki macro is provided to display just the feeds for a specific
>   CG/UG/P.
>
> We already have a 'Homepage URL' field, that will remain unchanged.
>
> We will only export feed info for people who have Leader, Affiliate or
> Developer status to prevent malicious injection of feeds in to the ones we
> aggregate.
>
> By doing this we can remove the current pain of having to manage all the
> feeds centrally.
>
> If that sounds OK, I'll log a RFE.

Generally, it seems good. Centralising the feeds so that changes only need to
be done once is a good thing.

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
_______________________________________________
website-discuss mailing list
[email protected]

Reply via email to