7 Mar
2006
7 Mar
'06
2:36 p.m.
On 3/7/06, Jim Stuttard <jim.stuttard(a)btinternet.com> wrote:
On Tue, 28 Feb 2006 12:45:29 -0000, jeremi joslin
<jeremi23(a)gmail.com>
wrote:
Yes, I agree with you. I thinkthe better is to have 3 websites:
* the project description and documentation (only committers and
contributors can write)
* the released demonstrations (only committers and contributors can write)
* the sandbox with applications in developpments and users test.
(everyone can read and write)
Jérémi
--
Blog: http://www.jeremi.info
LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724
Project Manager XWiki: http://www.xwiki.org
skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com
I want to separate the demonstration of what
XWiki can do and the
sandbox from this website.
Just a few thoughts FWIW.
There are some different roles to consider in refactoring:
Guest
User
Application developer
Core developer
These different audiences/roles obviously have different perspectives on
and information needs wrt. production, test and development code.
# Guest story
A guest might wish to look at or have already found some XWiki.com hosted
site and want to know more about this
great software. A link to the demo might be one of the best recruiting
grounds for new users. A demo website would integrate all stable
applications as a kind of XWiki Full. They might then be directed to an
xwiki.com subscription
or download.
# User story
I just use the built-in applications. I will not be learning how to
add/integrate new applications. I need to know
xwiki syntax and menu instructions.
# Application developer story
I need download, installation, application, plugin and integration
instructions.
# Core developer story
Needs the works. I don't want to work on bugs in 0.9.80 if they're fixed
in later code. I need to understand the
build, test, release cycle beyond just a build number. I need to know what
tests have failed for a
particular development or test build (cos of course there should always be
some in these two stages).
Getting a system which allows continuous refactoring seems quite important.
So I suppose I'd suggest partitioning the site into development, test,
production. I'm used to developing on 3 servers
with 3 databases so that schemas can be upgraded without impacting
performance on the test server etc.
I conclude that the main xwiki.org production site is for user and
developer info with community services; the production site with all bells
and whistles is the demonstration site; and the sandbox is probably a test
site.