8 Jun
2007
8 Jun
'07
1:23 p.m.
On Jun 8, 2007, at 1:04 AM, Ludovic Dubost wrote:
Hi,
XWiki Watch is a GWT based Feed Aggregator with collaborative
features.
It has the following features:
- Feeds, Groups and Keywords configuration using an AJAX interface.
Configuration are managed by spaces.
- Storing of articles themselves in XWiki pages using the
FeedPlugin's capabilities
- AJAX UI to navigate articles, open the content
- Collaborative tagging, commenting and flagging of articles, store
a 'read' status
- Filtering UI to see only articles from a group, a feed, only
flagged articles, matching a keyword, etc..
- TagCloud of tags applied to articles
- Text analysis feature on the content of articles matching a filter
- Press Review feature allowing to generate an HTML or PDF page
listing articles and comments matching a filter
- Look and Feel adapted to the Albatross skin by Laurent Lunati !
- Packageable as an XWiki Application (xar) that can run on XWiki
1.1M2 (currently the trunk) with correct plugins activated
(FeedPlugin, AutoTag, ZipExplorer)
XWiki Watch is based on the new GWT App framework included in the
XWiki Core GWT API (XWIKI-1334)
Some code I will propose to move to the core GWT API (A choice
dialog and a Wizard manager)
I'd like to propose a vote for:
1/ Create a new project XWiki Watch
2/ Opening the developement of XWiki Watch (build documentation,
provide a RoadMap, etc..)
3/ Decide where to commit it
4/ Decide weather or not to provide a different dev and users lists
+1 to add XWiki Watch as a new project inside the XWiki ecosystem.
Some time ago there was the Curriki project (GELC) added to the XWiki
source tree. Recently there was the XEM project added too. And now
this new XWiki Watch. Lots of good things. However we need to
formalize how we do development for these and how the communities
around these products are structured.
Here's my take on your questions:
* Put the XAR sources in trunks/xwiki-applications/xarlet/watch
* Question: Are there any Java sources required apart from the plugins?
* We create a JIRA project for it. I can do it.
* For the lists, I propose we keep the same lists for now and then
see what happens. If we get too many emails, people complain, etc
it'll be time to create new list. I like to do the simplest possible
thing first and only do something more complex if required. A good
thing for now would be to use something like "[Watch]" in the subject
when discussing xwiki watch (and [XEM] when discussing XEM). The XEM
project for example has produced a lot of emails yet (apart from JIRA
emails) so it wouldn't warrant having a separate user and dev lists.
Curriki OTOH is sending quite a lot of emails to the commits list so
we might want to separate the commits list. Anyway, let's start
simple for Watch.
* We need to reorganize xwiki.org too so that we can transform it
from a web site for XWiki-the-wiki-product to a web site about the
XWiki open source ecosystem which is currently made of: XWiki the
wiki (we need a name to differentiate it from XWiki the brand), XEM,
Curriki (GELC) and now XWiki Watch. Ideas welcome.
What do others think?
Thanks
-Vincent