I don't know if this is unappropiate or whatever - so disclaimer: I am
not trying to start a flame war, and if my email is provoking then just
tell me and I'll promptly shut up.
(Also, this is not really relevant for any busy coders focusing on 1.2
and 1.4 releases. So if you're in the middle of working on existing
versions and have little patience for thinking beyond that or on
off-shots than just let this post be.)
I am in a situations of choosing a CMS, and since I don't find anything
I like (including, presently, Lenya) I am considering contributing to
one in order to make the dream come true. And: Currently the CMS of my
dreams is the Daisy repository at the back, and the Lenya CMS (what's
left of it after subtracting the overlap) at the front.
(To be honest: We're also close to just cashing out for a commercial
solution instead. So I'm not making promises of doing development - I
mostly want to see how feasible it is and evaluate it as an alternative.
Oh, and of course I don't expect anybody to do the work for me - just
wondering whether I should start hacking on Lenya or not and to decide
that I investigate. And of course if anybody is interested in joining
then it will increase the open source odds.)
My story with Lenya: Lenya looked very interesting initially. Then,
looking at it, I found a few disappointments in how things were done
(which I'll mostly spare you from). I was growing disappointed, but then
Lenya 1.3 (the revolution branch) raised my hopes of a sane document
organization principle. And, looking further at repositories, I found
the Daisy repo, and fell in love. Didn't really fall in love with the
Daisy Wiki though.
What the Daisy repository provides:
- XML repository with SQL-queriable metadata, versioning, branching,
alternative languages etc., a good ACL system, flat document
organisation with seperate navigation documents, and a good query
language for extracting documents (merging the URI-space information in
the document).
- The Daisy project provides a Wiki on top of this, which can't really
be used as a CMS as such. However it is an excellent developer tool for
accessing the repository.
- Note: The seperation between the Daisy repository and the Daisy Wiki
is extremely good.
My questions are simple:
- Consider what is left of Lenya after subtracting the repository,
access control, and versioning. Is it worth it trying to fit Lenya on
top, or not?
- What do people think of the idea?
(And, another point I'm not sure about including, since I am in no right
to say it, but I don't seem to be able to hold it back: Since Lenya
seems to suffer from developer shortage, why focus on creating the
repository, versioning, multi-language, access control, and querying
parts? (The Blog publication seems to rebuild its own specialized
querying, for instance) If I'm not wrong it was totally restructured as
late as during 2006...)
Now, come on, please tell me why I'm wrong :-)
Dag Sverre Seljebotn
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
