Groove 2.5.
Team blogging |
Groove founder Ray Ozzie and his teams have always pretended to build application software. But what they have actually delivered are the operating systems of the future -- years ahead of schedule. The XML business Web is only now achieving the architecture that Lotus Notes laid down 15 years ago: message-oriented exchange of semi-structured documents. As today's operating systems catch up with that paradigm, Ozzie is tackling the next set of challenges in Groove: drop-dead simple secure collaboration, presence management, coordination of user and device identities, and ad-hoc group group formation. [Full story at InfoWorld.com.]
The scenario shown in the screenshot uses Tim Knip's Groove interop tool -- a Radio UserLand add-in based on Groove Web Services -- to create a genuinely new experience of team blogging. Until now, team blogging has meant that a group of folks post to a common weblog. This setup does that too, but it also does something I find much more powerful -- it synchronizes the inputs to the collaborative process, as well as the output. In this case, the input is the combined set of RSS feeds subscribed to by the members of the shared space. Everyone knows that everyone else is seeing the same feeds. Discussion can grow around items in those feeds, and can take various forms: replies to the forum that receives the feeds, IM-style text chat, Roger Wilco-style voice chat. ... [Jon's Radio]
Team blogging with Groove. Hmmmm... Doesn't this present some possibilities for new-age project teamrooms? I wonder if you have to have both Radio and Groove running, or if you can upstream from Radio to a single Groove box (server?). If the latter was the case, then I think you could definitely get some traction around it. The problem with having both Groove and Radio running is that it takes up 40 - 60 MB of precious memory on a developer's box.
8:38:17 AM 
|
|
