Re: [xwiki-devs] [Proposal] XWiki Watch publicly available on xwiki.org

Vincent Massol wrote: > On Jul 25, 2008, at 10:15 AM, Anca Paula Luca wrote: > >> Vincent Massol wrote: >>> I'd be fine with >>> http://www.xwiki.org/xwiki/bin/view/ExternalNews/WebHome >>> but I think it's better to have a top level domain name for >>> several >>> reasons: >>> * better visibility >>> * easier to go to rather than having to go xwiki.org and click >>> on a >>> link >>> * easier for upgrades (XE on xwiki.org and watch are separate) >> this makes me +1 for a separate wiki. I would have had it in the >> watch wiki on >> xwiki.org but, since the goal is to have the latest version of >> watch >> running >> there, we need to make sure it is freely upgradable (which can >> require upgrading >> the underlying XE). >> >> Otherwise, I still think it should be on watch.xwiki.org rather >> than >> xwiki.org >> for consistency reasons, since it would be a demo of watch -- that >> is the main >> purpose as I see it, allowing people to click around and have a >> quick look >> without having to download, install, etc. > Then we still have a disagreement :) > > Right now (and I'd like to keep it this way) all wikis on the > xwiki.org domain are for *real*. They are not test platforms for > people to see how xwiki works and have some fun trying it. They > have > real usages (documentation of the xwiki software). > We have one exception: this is playground.xwiki.org which is there > for > people to test and play around. > > Thus my proposal is: > > 1) have a new wiki (news.xwiki.org, same as we have jira.xwiki.org, > svn.xwiki.org and maven.xwiki.org) which will be our news "portal". > Note: It will also listen to the xwiki.org Blog feed. > 2) have a Watch space in playground.xwiki.org for people to try out > Watch. it makes a lot of sense, so: +0 for 1: it would be nice to have it, it would be nice to have it working properly (having people *really* collaboratively watching) but that is not the purpose I started this thread for.

+1 for 2, since this one is :). But now we're back one mail to the upgrade problem: I would like to have always the last version of watch running in the playground, which could require platform / XE upgrades, from time to time, since the plugins & modules that watch is using don't really have their own lifecycle, yet.