24 Jul
2008
24 Jul
'08
9:35 a.m.
Vincent Massol wrote:
On Jul 23, 2008, at 5:40 PM, Anca Paula Luca wrote:
Since Watch is implemented using the XWiki documents & objects model, user
rights follow the same model as all XWiki. Guest users use the rights we give
them: for viewing / navigating through the reader, view right is enough, whereas
any edit (add feed, tag/flag/trash/mark as read articles) requires edit rights.
Unless there is a problem with giving edit rights to guests, I don't see exactly
what is the issue with having guests use the reader.
Hi devs,
As it has been already mentioned a couple of times, I strongly believe
that XWiki Watch should be accessible in a sandbox on xwiki.org, for
everyone to try it out and explore its features and for us to get an
open real-life test of it.
There is a document dedicated to the issues that might prevent this at
http://watch.xwiki.org/xwiki/bin/view/Development/XWatchOnXWikiOrg ,
please fill it in with any opinions you have!
Here's my +1 for having an installation of XWatch publicly available
on
xwiki.org, WDYT?
Sure, we've already discussed it as I wanted to install it but
discovered it wasn't possible at the time. I wouldn't call it a
sandbox as I think it could be used for real and contain feeds related
to xwiki and anything relevant.
Here are some issues I can think of:
1) Allow unregistered users to view and use the reader 2) Provide ability to undo changes done by users (the
revert feature
of all wikis). This is especially important in a public instance: it
needs to be easier to revert an error than it is to create one!
As mentioned earlier, all Watch data is stored in xwiki documents & objects, so
reverting is as easy as it can be in any other instance of xwiki.
Now, there is a problem with what we understand by reverting changes in a "feed
reader". The first example that comes into my mind is when a user adds a feed
source, say unwanted. Since the feed articles fetched from that are stored in
xwiki documents, revert (wiki-way) would mean deleting the feed, but that would
not trigger deleting all fetched articles. While from a feed reader point of
view, reverting this change would probably mean deleting all fetched articles
too. For this particular example this is not a problem because deleting a feed
with all fetched articles is implemented in watch reader interface, but there is
a general problem of actions and concepts interpretation in Watch: seeing it as
a wiki vs. seeing it as a feed reader.
3) Good performances
Depending on the type of database used and the database setup, XWiki Watch can
get a little heavy for (arguable) large database sizes (~10000 fetched
articles), but I think using it on xwiki.org would help better estimating these
type of problems.
I think that if we have 1) and 2) we could start using it on xwiki.org.
Thanks
-Vincent
[snip]
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs