Re: The wgo CMS can't wait more

[Marc Laporte <marc marclaporte com>]

Lee Tambiah wrote:

> Not only do we need the CMS but we need a new mockup design from Mairin which I have been waiting around for. 
> With regards to the CMS some of the links on the page for testing dont work (but maybe as im behind a proxy) 
> but i cannot access the Plone CMS at http://demo.gnome-cn.org/ or the Midguard URL (but sure i have accessed 
> this at home so probably is proxy). At current we have 5 CMS for our options, could we not short list, I dont 
> think TIKI WIKI is what we want at all just from looking at it,

Hi Lee,

Several weeks ago, the CMS evaluation appeared urgent & imminent. So I 
took some time to answer the Gnome's requirements point-by-point.
http://gnome.rclaporte.com/TikiGnomeEval
http://live.gnome.org/GnomeWeb/CmsRequirements/TikiEval

While I understand that you want this done as soon as possible, I would 
appreciate if you wait for the skin to be integrated before judging 
"from looking at it". In the middle of August, I asked here on this list 
for a mockup. I was told, in essence, to put a basic mockup until the 
real one is ready.

For many many reasons too long to explain here, I think Tiki 
CMS/Groupware would be an excellent solution for your needs. And I think 
it would be excellent for Tiki as well, as is for example the KDE wiki: 
http://wiki.kde.org/

When available, I will integrate the look & feel into a Tiki template 
and will show whoever's interested how it's done. Tiki is very easy to 
theme but I'd rather demonstrate with actions and code than with my 
words :-)

In the end, maybe another CMS will be chosen because of reason X, Y or Z 
(And I know it's not just features, it is also community, documentation, 
etc) and I will learn from this as an opportunity to improve.

Best regards,

M ;-)


> and Plone is just a major monster which is going to require python coders and is over complex for us. As most of us are PHP devs our decisions should also be influenced towards this after all we are going to maintain it and customizing the CMS. 
>
> Pesonally I think the CMS for use would either be Drupal or Midguard in our case, but there is no point of a 
> personal opnion as Quim rightly says we need to proove that it does what we require it to do. If we could 
> drop PLONE and Tiki, then we can concentrate on the most likely ones. As there seems to be much anticipation 
> regarding the choice at moment I will start looking into evaluating and give my few bucks worth.
>
> If we look at the Drupal Page at:-  
> http://live.gnome.org/GnomeWeb/CmsRequirements/DrupalEval it has upto 40 table rows for feedback. Thats a lot to test! Can't we reduce it by half?
>
> Some of the things I have suggested are to speed the process up by cutting it down a little. Do you agree?
>
> Regards
>
> L. Tambiah
>
> GNU/Linux Enthusiast
>
>  

--
M ;-)

//////////////////////////////////////////////////////////////////
/                                                                /
/ Marc Laporte       <|>                  http://marclaporte.com /
/ Avantech.net       <|>                     http://avantech.net /
/ Tiki CMS/Groupware <|> http://tikiwiki.org/UserPagemarclaporte /
/                                                                /
//////////////////////////////////////////////////////////////////