Jeff Turner wrote:
On Fri, Mar 08, 2002 at 12:00:11PM +0100, Santiago Gala wrote:
...
Then could we perhaps have a news@jakarta list for this sort of thing? A
lot of people find announcements like this relevant and interesting.
On a related (technological) note:
We Jetspeed people (actually Raphael Lutta) put one year ago RSS
channels, for our own purposes of showing them in the demo Jetspeed setup:
http://jakarta.apache.org/jetspeed/channels/apache.ocs is an Open
Content Syndication feed
http://jakarta.apache.org/jetspeed/channels/jetspeed.rss is a channel
for Jetspeed
http://jakarta.apache.org/jetspeed/channels/turbine.rss is a channel for
turbine
The RSS mechanism could be easily used for news and content syndication
@apache. Channels can be added, generated, etc. for different projects
or activities, and used for dynamic linking to apache news from outside
the web site.
Sounds nice. Is this demo Jetspeed setup actually live somewhere?
I have a copy running at
http://hisitech.com/jetspeed/ (rather out of date, and messed up by
hundreds of people customizing layout).
David Taylor uses to have one around http://bluesunrise.com/jetspeed
There are portals using Jetspeed around (see
http://jakarta.apache.org/jetspeed/site/usejetspeed.html), but most use
their own feeds.
Adding some weblogs as newsfeeds would be good too. Weblogs are
wonderful things. Have a look at http://www.need-a-cake.com/
Any JAMES people lurking here? Would it be possible to rig up a mailet
that wraps incoming posts in XML and makes them available as an RSS feed?
That way we could have an easy-to-use news submission process.
FYI (for those who weren't aware), there's a new xml-forrest project
project at xml.apache.org, specifically for things like this.
I knew this one.
Another FYI for Jetspeed people: Cocoon is very much encroaching on your
portal turf ;) See
http://www.need-a-cake.com/stories/2002/02/14/cocoonPortalFirstLook.html
I know. Further, cocoon and Jetspeed people should team together to
ensure that Sun's JSR#168 standardizes around a reasonable Portlet API
specification, specially WRT SAX stream portlets, so that Cocoon can
implement a portlet container respecting the standard and using Cocoons
streaming capabilities at the same time. Jetspeed will be conformant to
the ByteStream or SAX stream API rather easily, and at due time, using
jsp and/or Velocity.
--Jeff
(idling.. friday evening..)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]