Jörn Nettingsmeier wrote:
hi everyone!
first of all, a happy new year to everyone. after a couple weeks off,
i'm back.
apologies for disappearing for so long after the usecases handler
rewrite - i'll look into the remaining bug reports over the next few
days.
the reason i was silent for a while was that i had to write off a
rather major project i was doing, because it became evident that lenya
1.4 has not reached a level of maturity where it could be deployed to
> 100 users and still let me sleep soundly at night. moreover, i had -
and still have - serious doubts about the long-term sustainabilty of
the lenya ecosystem, which was the main reason to pull the emergency
brake. bugs can be fixed, but an unsustainable community is very hard
to work around.
the ecosystem is a result of the quality of Lenya. If Lenya is no good,
then people will not use it and hence people will not join the ecosystem.
I tried many times to explain what I think needs to be done to make
Lenya good, but people disagreed resp. just did something else.
That's ok with me, because I don't need to be proven right and I don't
have to be the one ruling this community.
It's just sad to hear that you seem to experience what I had experienced
more than a year ago and I can only hope that some people
learn from that.
apart from financial aspects, the cancellation of the project was
quite painful in terms of job satisfaction. so there was a strong
incentive to hit the lists with some serious whining and sarcasm. in
order to avoid that, i decided to just shut up, move away for a while,
get some rest and start afresh later. which, as it would seem, is now :)
during my time off, there has been frantic activity on the list (most
notably by andreas, who kindly addressed many of the issues i found
most pressing, thanks!), but also prolonged periods of stagnation, the
most frustrating being the botched 1.2.5 release.
as i said, i would not bet much on lenya at the moment. the features
are nice, and for small projects it's cool, because they can always be
migrated away easily if lenya implodes. but for larger deployments
with many authors, the costs of re-training staff alone are
prohibitive, which means that using lenya is just too risky.
so what to do about it?
there's a couple of things that come to mind.
first, that a bunch of 1.2 users and developers really need to get
their act together and get 1.2 out the door. i cannot understand why
this is not happening, especially there seem to people running a
business based on 1.2. (and no, i won't learn the fscking legacy
codebase to help with that.)
there is not much to do except create a tarball of 1.2.5-dev and test it
as good as possible and if people agree of the quality, then release this
tarball.
Cheers
Michi
after that, we need to push 1.4.0 out. let's identify the last
remaining showstoppers and release. it's going to be a dot-zero
release, so people will be warned :) it'll probably take me a week or
so to dig through all the recent patches, and then i can help out again.
then, we need something to revive the community, and with the burden
of releases gone, we can talk about the future of lenya, cool features
and clean, shiny data structures. to that end, i propose to have a
hackathon, as soon as possible. i'm starting another thread for this.
regards,
jörn
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
+41 44 272 91 61
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
