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

List:       kde-zine
Subject:    Re: [Kde-zine] in reply to Andreas
From:       Andreas Pour <pour () mieterra ! com>
Date:       2001-07-12 18:48:30
[Download RAW message or body]

Darian Lanx wrote:
> 
> Hello
> 
> Well the XML spezifikation, along with the tags we require is in the XML
> module in the CVS. if you want, I can send you the XML module, since
> anonymous checkout is for some odd reaosn broken right now.

Yes, please do (privately).

> Dirk and I, along with Herve decided not to use a databse backend. There is
> no need to add additional overhead using a databse deamon, for that our turn
> around is far too low. 

I don't care what you do with the backend, that's your department.  If I
store it in a database now you can retrieve the values easily.  I can
send it to you in a CSV file or in whatever format you want, as long as
the fields are separate in the database I can throw any separator
between them you ask for.

> We have about 20 days static data and then in the 10
> days when we tag the new release and generate the html the data gets moved.
> We decided it is faster and more secure to leave everything on the hard disk
> and do not put another "mediator" between data storage and publishing
> "system".

Well, I don't agree with your reasoning, but that doesn't matter, since
it's your project.  Using a database does not slow the page down, unless
you use a stupid roll-your-own database like Zope does.  At kde.com, for
example, the database is never the bottleneck, and we get quite fast
times when accessing the mail database (which is about 200MB in size). 
The nice thing about a database is you can easily switch programming
languages, backends, servers, split database from client, provide info
in different formats, etc.
 
> Furthermore, it would not be smart for us to put the data into a database
> now, it would make porting a whole lot harder on us. Then rather do it in
> simple HTML.

I think you don't understand my proposal :-).  I put it in a database on
the promo.kde.org end.  When your backend is ready, I can give you the
database, or the data in it, whichever you want.  All I am saying is, we
can keep the fields separate so later a script can genreate your XML
files, rather than requiring manual intervention.
 
> Futhermore I do not think a zine which gets published monthly is interesting
> to naybody if it only has 2 articles. Every publication of the zine should
> have at least 10 artilces, 

We can dream, but I also don't think we should shut the zine down if we
get only 2 articles.  Plus when you are online I don't know what you
mean by publishing "monthly" -- don't the articles get released as soon
as received?  The "hold until it's stale" approach makes sense only in
printed issues, which we don't have yet.  Once we get 10 articles a
month will maybe be the time to consider a printed version.

> of course some might not be very long, but at
> least a different topic is covered. Gathering 10 articles within 20 days or
> even 25 shoudl be doable. If not, cut that number down to 5 or 6, yet 2 is
> far too less imho.
> 
> Anyways.
> From aporting point of view, static HTML is the easiest to deal with.

I doubt it but if that's what you want I can give you that at the end as
well.

Ciao,

Dre
_______________________________________________
kde-zine mailing list
kde-zine@master.kde.org
http://master.kde.org/mailman/listinfo/kde-zine

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