Thank you, Markus, this is really the core of it all.
On 13.10.2005, at 17:34, Markus Strickler wrote:
...
Both steps mean major efforts, binding lots of developer resources,
probably cause a lot of instability for the next releases (both API
wise and in terms of runtime stability, as mature, well tested code
gets replaced by new code). On the other hand, Magnolia still lacks in
important features. The publishing mechanism still needs transaction
capabilities,
Alex is tackling it
there is no content locking, no versioning,
Yes
no link management,
bigger effort needed
etc. All important features of a content management system, and in my
experience the main reasons why people opt against using Magnolia.
I would love to hear from everyone what they thing should be done most.
We have 143 outstanding issues in jira.magnolia.info - and you can vote
for any of them as well as add what you think should be there. We need
your feedback. Besides, if everyone on this list fixes one issue we
will have 60 people that get nothing to do :-)
All in all what would be interesting to hear are the experiences with
creating the currently existing modules. The DMS was supposed to be
using JSF, for example.
We did not use JSF in the end.
The refactoring to support workflow will probably help as well.
definitely
Once all cms functionality is clearly factored out, you should be able
to change the frontend to whatever suits your needs.
What I would definitely like so see is more discussion on how to add
your own modules to Magnolia. Again documentation on the module API
would be a step in that direction.
Yes yes yes yes.
We will have to finish 2.2 for various reasons, and it will have two
major issues solved - JAAS and the (optional) usage of workspaces
instead of repositories. Once that is out, I think that documentation
and examples as well as describing the modules we would love to have in
detail is what we will do next, before adding a single new feature.
(that is unless workflow integration will have to be done first) But
the point is made and heard - and I ask everyone to participate in
updating the documentation - if it is patches to the java doc, its
better than complaining. Examples to the tag usage. Sample sites or
paragraphs. Cleaning up the wiki and putting the best of it into SVN.
There is really quite a bit everyone up us can do, and we have 200 devs
on this list. One hour each week from each of you will make such a big
difference you will not believe it.
Both JSF and Spring are great frameworks. But don't forget that
Magnolia is first of all a Content Management system for people to use
and not a showroom for the latest and greatest in Java Enterprise
technology.
Exactly. Thank you.
- Boris
http://betterfasterbigger.blogspot.com/
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
