Re: [L-A Lokalisointi] Portal domain name and development

Aschwin van der Woude <aschwin.van.der.woude-VgemUZeIY8Ow/[email protected]> Fri, 05 Mar 2004 10:39:52 +0200
Newsgroups gmane.comp.internationalization.finnish.general
Organization Linux-Aktivaattori ry
Message-ID <1078475992.2927.26.camel@workstation>
On Fri, 2004-03-05 at 01:53 +0200, Tero Kuusela wrote:

> 
> If you don't plan on changing the layout radically several times in the
> near future, I don't see the problem in using TWiki to keep the content
> up-to-date. But that's just me, perhaps others here have other opinions.
> 
> > So, my choise is to stay with Apache, move to a new server, give CVS (or some
> > other form of) access to others interested in working on the site, and
> > possibly transition to some content management system at some time in future.
> > 
> > But, if someone is interested in taking the responsibility of developing the
> > site with TWiki and maintaining it in future, please speak up. I don't have
> > much (if any) time right now anyhow, so I would be glad if someone else took
> > the development of the site.
> > 
> 
> As I understand it, you were already offered the chance to get the
> layout converted to TWiki by Aschwin and just having to take care of the
> content together with the rest of the localisation working group.
> Perhaps Aschwin can clarify this if I understood incorrectly, but I
> certainly seem to have understood it differently than you did.

Absolutely, I would be happy to convert the current portal layout to a
twiki-template.

> Note, though, that by no means do I think that TWiki would be an ideal
> solution for such a portal, but it's what most people in L-A already
> know, what we already have, easy and quickly deployable. I see it as 
> Good Enough For Now(TM).

In fact we started looking into alternatives. After Marko raised the
issue, we realised TWiki might no longer suit all our needs. The choice
of Twiki was made a long while ago, and surely some of our requirements
have changed since.

We would like to select a CMS that suits all our needs, and this
includes the needs of the working-groups, the different projects and all
who are somehow involved with Linux-Aktivaattori.

If we want to meet those needs, we need to know what they are. Thats why
we started an open process of selecting this CMS, and its progress can
be followed from our website[1]. If anybody has feedback about it or
additional requirements, please add them to the page or let me know.

[1] http://www.linux-aktivaattori.org/view/Bazaar/
ContentManagementSystem

> L-A provides resources for it's working groups. Note, _it's_ working
> groups. You are not separate from L-A, although you are free to leave it
> if the group so wishes. Generally, it's a good idea to use the available
> resources instead of finding new ones. But, at least currently, L-A does
> not force working groups to use their resources.

In my opinion we should adopt use of supplied resources as a
requirement. If a working-group would like more independence it can
always go its own way. I just hope we can fulfil the needs of the
working-groups as long as possible.

I believe a common CMS for our projects and working-groups is crucial.
It is beneficial for all of us in two aspects. First of all maintaining
a single CMS minimises the work-load on our already overloaded admins.

Secondly and perhaps even more important, a single CMS makes it easy for
Linux-Aktivaattori members to participate in various projects and
working-groups. They would only need to learn one CMS once, and be
productive afterwards.

This, however, does not mean special requirements have to be met by the
CMS, like a dictionary. Such specialised information can and probably
should be provided by a separate tool. But such tool should be web-based
and use a familiar layout.

These are of course my thoughts on the matter, if you have other ideas
or criticism I would be happy to know about it.

-Aschwin