On Sat, 2006-07-08 at 15:46 +0200, Murray Cumming wrote: > I think this is very debatable. For instance, guadec.org was (is) far from perfect and, in fact, it lacks many points any decent website should have. None of the points you make have direct relation with the CMS, but to our lack of planning and resources. guadec.org never had an editors team as such. tavon planned a structure, applied and it was almost never touched. Myself I wrote most of the texts and at some point I didn't have time to write more. Other people contributed in the easiest way: posting a message in the forums. We didn't have time/resources to do it better. > 1. Many people had difficulty finding information on the website due to: > 1.1 the difficult-to-use structure. Our fault. > 1.2 the lack of structure. For instance, information was often simply > posted to the forums instead of being added to the main pages. These > forum posts were almost impossible to find as soon as they had left the > front page. Our fault. Also, we had to unable the search engine due to outdated packages in the server. > 2. Almost nobody edited the pages, suggesting that they had some > difficult in doing this compared to a wiki. This is probably why they > (even you) used the forums. Even if you had changed the main pages, it > would not have been easy to see what had changed recently, and it's > currently impossible to view changes for a single page. This is doable with Drupal and many non-wiki-alike CMSs. > I don't know whether these problems are due to the use of Drupal itself, > but it did confirm my fears that Drupal might force us to create a web > site that consists of news items. Not at all. You can build Drupal sites with the news and forum modules deactivated (to put an extreme example). The solution is to plan a good structure and get a team of regular editors working following the plan, not simply posting news on the fly. > I have filed bugs for some of the things that make use of Drupal > difficult compared to a wiki, and which make it like a news site, but I > doubt that this is the full list: > http://bugzilla.gnome.org/show_bug.cgi?id=341885 Probably 30' of a Drupal sysadmin. > http://bugzilla.gnome.org/show_bug.cgi?id=341225 Probably 30' of a Drupal sysadmin. > http://bugzilla.gnome.org/show_bug.cgi?id=334750 This might take longer, but it's doable. It has a component of personal taste (seems not to bother to many Drupal admins) but I guess it's about tweaking a bit of CSS and perhaps Drupal code. > http://bugzilla.gnome.org/show_bug.cgi?id=334747 Probably 30' of a Drupal sysadmin. I mean, we can't expect a CMS to fit all our needs when installed out of the box. We need to care that the CMS chosen is able to integrate all the changes we need, and the default candidate keeps being able to integrate them. Sometimes is about configuring and installing additional modules. Sometimes will be about hacking and producing our own modules. The API and the module development are fully documented, so it is about our owj resources, basically. > I did want us to have time to review guadec.org as the drupal test site > before committing to drupal for gnome.org. I don't believe that > guadec.org has proved that drupal is good enough for gnome.org, and I'm > not confident that we would fix drupal problems easily for gnome.org if > we couldn't fix them for guadec.org. Replicating the current wgo on a Drupal CMS can be done fairly easily. Many GNOMErs wouldn't probably notice it. From that point integrate improvements is just a matter of planning and execution. > In particular, guadec.org > completely failed to demonstrate that drupal is capable of supporting > translated sites. Well, nobody offered to translate any content. At some point I stopped chasing Spanish and Catalan speakers because nobody seemed interested enough. Drupal i18n module was not even activated. In December 05 we started a discussion about Drupal capabilities for translated websites - http://mail.gnome.org/archives/gnome-web-list/2005-December/msg00120.html . Now it's time to fix the requirements and find if Drupal or the alternative CMS candidates can accomplish them. About Baris concerns about security. Drupal is a widely used platform. This makes it interesting for hackers finding holes, and they eventually find them. Security announcements are published at http://drupal.org/security (you can subscribe to reveive updated by email) and patches follow the announcements instantly or in few hours/days. Said that, we need to know for sure that the tools we are using are secure. Therefore I will be more than happy if you try to beat the CMS(s) we choose. -- Quim Gil /// http://desdeamericaconamor.org | http://guadec.org
Attachment:
signature.asc
Description: This is a digitally signed message part