Re: What about WordPress or something similar?

[Stefan Rotsch <linux stefanrotsch de>]

Thomas Wood wrote:

> - Migration: How easy would it be to migrate the existing users, data, 
> files, screenshots and the rest to a CMS? I think this would be 
> especially hard for users, since I can't see anyway that passwords could 
> be transferred (unless the new CMS supports exactly the same method for 
> storing passwords as art-web currently does).
I know this would be the most difficult task. But a decision should be 
based on the benefits of a CMS vs. the difficulty of migration.

> - Features: We would still have to do a lot of work to implement the 
> plugins needed to handle art-web specific data and pages. There is a lot 
> more metadata associated with backgrounds and themes than is obvious. 
> Also, themes and backgrounds are not handled the same way as you might 
> expect (backgrounds have many more requirements than themes). A third 
> type of item may also appear soon, in the form of collections of other 
> items.
I must admit I haven't taken a look at the a.g.o. sources yet.

> - Control: If you move to a CMS you loose control of your source code to 
> a certain extent. I don't particularly have any motivation to read and 
> learn another CMS's source code just to make some minor (but possibly 
> vital) changes. There are several people already familiar with the bulk 
> of the art-web code, and it is probably much easier to get to grips with 
> due to it's (relative) small size.
That's true for sure. On the other hand, what would you want to edit if 
thinks work well and bugs get fixed by the community; you simply would 
have to install a new version of the CMS?!?

> There are also factors out of our control, such as restrictions placed 
> on us by the gnome.org system policies and procedures (this is the 
> reason it has not been possible to implement a file upload system until 
> recently).
ACK.

> Not to mention the time and effort people have put in to coding art-web. 
> It would be a shame to throw this all away, so I personally would not 
> like to see art-web replaced with an external CMS.
That's an issue, too. But it is also about weighting the benefits of a 
CMS against telling people 'their' code won't be used anymore.

I hope you get me right: I don't want to "sell" a CMS to you. But when 
looking at the tasks on the ToDo list, from my point of view it would be 
an option to think about the migration to an CMS, instaead of 
iplementing that bunch of features on our own.

Independant of deciding which way to go, I just want you to know I'm 
willing to help working on a.g.o.

Stefan
--
Stefan Rotsch

http://www.stefanrotsch.de/
207D 9E6E DDE5 9FC4 0DA8 B1F7 1A01 9AF6 97D2 295D