Hi Louis,
How am I not being clear?
:-)
I agree with you and with Kay. I don't like privileging Portal, either.
But: as long as we must use Collabnet for www.openoffice.org, I am loath
to sending users offsite for the primary gateway.
That should always be www.openoffice.org
Is this clear? :-)
portal.ooo is *temporary*
You have been quite clear about this, I'd think. The main concern,
however, that I have is that portal.ooo seems to have a predefined user
group already as well (without stating really what the problem is).
Especially when looking at the slides of Matthias, I am not sure whether
there is clear plan where more flexibility is needed (flexibility not
allowed for by the collabnet infrastructure). Download for example is
still suggested to stay at download.openoffice.org (thus still relying
on the collabnet infrastructure), whereas this is exactly one of the
problematic parts in our website. This is an important place where we
need serverside scripting... I know that focussing on the download part
is nitpicking, but what is definitively lacking is a plan.
I think the claims made by Drew in his last e-mail are very valid, and I
would not like to see that some designer is putting a lot of effort in a
website design that is hardly being used because we had an unclear strategy.
If something is temporary, why not just wait till things are set up
properly?
Before thinking about what how portal.openoffice.org should look I think
we should think about openoffice.org as a whole. If end-users are a
concern right now, I am not sure whether we need to say goodbye to
collabnet if it is about static pages. As others have pointed out, other
projects have been able to build good looking websites around collabnet.
We need a plan before moving all to a new domain.
g.,
Maarten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
