Re: Last contribution (was : Re: [VOTE] Move Lenya to Attic)

Andreas Hartmann <[email protected]> Tue, 17 Feb 2015 15:45:10 +0100
Newsgroups gmane.comp.cms.lenya.devel
Message-ID <[email protected]>
Hi Florent,

Am 16.02.15 um 12:22 schrieb florent andré:
> This is with a big melancholy that I send my +1 to this vote...
> But the facts are where and we have to move to attic.
>
> As a last contribution to this project I would love that anyone who
> participate to this great CMS and community put a word on what was the
> goods and the bads on :

just some quick points:

> * main design principles

Major goals, derived from our positioning diagram [1]:

* Standards compliance
* Industrial strength (robustness, scalability etc.)
* Flexibility
* Extensibility

Some design principles derived from these goals:

* Design everything thoroughly (orthogonal API etc.)
* Framework approach: Make everything generic and reusable
* Do everything in XML (can be easily validated and processed)
* Ensure data integrity at all times
* Let the framework validate everything (content, links)
* Easy & robust deployment, automatic URL rewriting

 From my point of view, these principles are what makes Lenya stand out 
of the crowd. I have worked with quite a few Lenya installations; in all 
of them the content (which is the main asset of a CMS installation) was 
in very good shape (easy to automatically migrate or process/transform).

> * technological choices

Some things we should have done differently (from my POV):

* Database or JCR for content storage (transactional, indexed)
* Don't use the sitetree XML file (doesn't scale well)
* Index all links for fast link checking
* Access control on the content level (as opposed to URL-based)

> * community and his management

The community was small, but very committed and constructive. I think we 
didn't do a bad job managing the community. Maybe we could have tried 
harder to build a larger community, but this would have required 
lowering the entry barrier, which is not easy without investing quite a 
lot of work and without risking to compromise some of the main 
principles (see above).

> * ...

> Introduced by a paragraph on the history of Lenya genesis.

A bit of info is on the website [2].

> A kind of collaborative epitaph that give some clues, good and bad ideas
> for open-source CMS software developers.
>
> Concretely we can initiate a .md file in the svn repository, on send
> your words on this thread - I can take care of putting them all together.

Sounds good. We could also consider copying the repo to github, WDYT?


[1] http://lenya.apache.org/index/roadmap.html
[2] http://lenya.apache.org/index/history.html

-- Andreas



> On 13/02/2015 16:36, Richard Frovarp wrote:
>> This is a vote that is open for one week on proposing the following
>> resolution to the board to move Lenya to the Attic. The resolution text
>> was taken from: http://attic.apache.org/resolution.html. This direction
>> was discussed previously on the dev list from Jan 27th to Feb 6th with 4
>> responses.
>>
>> Terminate the Apache Lenya Project
>>
>>         WHEREAS, the Board of Directors deems it no longer in the best
>>         interest of the Foundation to continue the Apache Lenya project
>>         due to inactivity
>>
>>         NOW, THEREFORE, BE IT RESOLVED, that the Apache Lenya
>>         project is hereby terminated; and be it further
>>
>>         RESOLVED, that the Attic PMC be and hereby is tasked with
>>         oversight over the software developed by the Apache Lenya
>>         Project; and be it further
>>
>>         RESOLVED, that the office of "Vice President, Apache Lenya" is
>>         hereby terminated; and be it further
>>
>>         RESOLVED, that the Apache Lenya PMC is hereby terminated.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>