[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Site Maintenance
From:       John Rizzo <jrizzo () johnrizzo ! net>
Date:       2001-12-14 17:47:30
[Download RAW message or body]

On Friday 14 December 2001 15:46, Dirk Mueller wrote:
> On Fre, 14 Dez 2001, John Rizzo wrote:
> > Ok so one step at a time right.  I believe that I can accomplish much of
> > this using zope as the content management system.  I would like to take
> > the current incarnation of the site and duplicate it using zope.  I would
> > use all the usefull utilities such as templates, caching, etc that are
> > available through zope.  Much of the dynamic sections of the site that
> > use php can still be leveraged since integrating php with zope is
> > trivial.  Once this proof of concept is available and consistant with the
> > existing site I can make it available to other people that are interested
> > in helping with the site and see what they think.  Any appropriate
> > changes could be made.  Then when its ready would could implement it as
> > kde.org.
>
> How do you want to implement revision control by using Zope ?
>

There is a standard module that allows you to create a version of the site.  
Any changes made in this version are not visible to anyone working outside 
the version until the version is committed.

> I do understand that Zope is easier to use for Webdesigners and
> content-providers than the traditional html editor+php method. However
> security wise this opens a can of worms. :(

Like most things if the system, in this case zope, is implemented correctly 
most security considerations can be handled correctly.  Obviously nothing is 
ever 100% secure but zope can be configured to be as secure as the current 
methods.

>
> The advantage of using the traditional method is that it doesn't matter
> much which way you used to create the site - with Zope the only effective
> method known to me is to use the Zope management interface itself.
>
> So there is no way to talk you into going the traditional way with
> contributing via CVS ? :)

Its not that I am opposed to cvs but rather that I would like to start making 
it easier for people to contribute.  Contrary to the abilities of most of the 
kde community most people do not want to have to learn things like cvs to 
write a document.  People who are good at documentation are not necessarily 
good at the same tools developers use.  I hope by using a web interface to 
ease this burden and therefor get more/better documentation available to the 
users and developers.

Please keep something in mind.  Microsoft with all of their bad attributes is 
good at what they do.  If they think that it will increase profit and market 
share they will do it.  One of the things they do is provide incredible 
documentation to their developers and users.  This makes more poeple want to 
use and develop with Microsoft related tools.  We need to do the same.  True 
most of you guys are good coders and you know the ins and outs of kde very 
well but for people like me who may have the desire and talent it can be 
dauting at time to try and figure things out because it just isn't documented 
well or at all.  

Please try to not respond with "the source is your documentation" kind of 
comments.  This only shows ignorance, immaturity, and alienates potential 
developers and users.  We need to make people want to use and develop for kde 
and we can do that by offering them a community that nourishes their desires 
and talents. :-)

>
> Dirk
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<

So unless anyone else can offer something better I am going to start working 
on things this weekend.

-- 
John Rizzo		jrizzo@johnrizzo.net
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]