Re: [xwiki-devs] XWatch UI Proposal

Hi, I've read the proposal and I like it in general. Nice work! <roadmap/general ideas> Stepping back a little and talking about roadmaps I think we should eat more our own dogfood, meaning we should use XWatch internally for our needs and find out what's useful for us first. This would be a good process to define what's useful for others too. Personally I'm not using any of the Watch UI right now. All I use is the resulting RSS feed (this one: http://watch.xwiki.com/xwiki/bin/view/WatchCode/PressReviewRss?space=XWikiS…) I don't know how others in XWiki are using XWatch but I have the feeling we could learn a lot from that. I think there needs to be some incentive for users to use the tool (the filtering/categorizing part) they'll just use it as a basic RSS aggregator (as I do). I don't have the full answer to that but I can think of several ideas: 1) Its scope could be extended so that it supports different input sources (as discussed previously and also by Guillaume in this thread): a) Mails from mailing lists (this would require difference actions, like "closed discussion", "associate jira issue", etc. b) Documents in a WebDAV store c) XWiki Documents (pages) - This could be a nice way for people to classify/navigate in a wiki. 2) Integration with external tools. For example if I could flag articles directly from my favorite RSS feed readers without having to open XWiki Watch I'd definitely start tagging/filtering. I think this could be done easily by adding HTML at the beginning or end of feeds provided by XWiki Watch. We could add some Flag/Comment links there that would open inline (Javascript - I think most feed readers would support that). </roadmap/general ideas> WDYT? Thanks -Vincent Note that solution 1) a), if done correctly could potentially solve our need for a forum. What I'd like right now from a forum is 2 things: the ability to extract some statistics (namely to list the top 10 contributors) and to tell when a thread is closed or not (it's not closed if the question asked has not been satisfactorily answered). I know we're getting a bit away from the initial Watch idea but I think it could broaden its usage and it would definitely fit in the "organize and categorize information" domain. On Jul 14, 2008, at 9:29 AM, ★Ecaterina Valica wrote: