Hi Mike, Mike Müller schrieb: > Hi all, > > First of all, I would like to thank all of you for the big efforts to enhance > and refine sling step by step. I'm watching the project since a few months > for now and tested sling in a few simple projects - and it really is very > easy to use it right from scratch.
Thanks to you ;-) > > But to be honest, it's rather hard to really get into the code of sling if > you try to build a complex app, not only based on scripting. The big problem > by now for a non-sling-insider is the documentation. The website mostly is > outdated. Dont' get me wrong, I know sling is open source and all free, so > nobody has to bother about missing things. And yes, if you try hard enough, > you also get into the details of sling. But that's the problem of the > project: I think sling is such a good project it should get out of the > incubator. The project is mature, it is tested in real projects (as Day's > CQ5) and it evolves further. It seems that the only thing which holds sling > off to get out the incubator is the list of active committers outside Day. My > company would like to move our products on a sling based core and we also are > interested to develop sling and help to enhance it. To make it easier for > others to use and also contribute to sling, I think the following things > would be as impo rtant as the source code itself: First of all: We are perfectly aware of this situation, but fail to be able to really cope with it in the sense of updating all docs, due to overfilled time tables (you know the problem ;-) ). One thing you could do, except of contributing code of course, is to contribute documentation ;-) > > 1) an up-to-date website with documentation about the core part of sling > (like architecture, request processing, which services/interfaces are exposed > by the core of sling and which are additional services/interfaces?, how and > where can you enhance sling -> servlets, scripting, components) > > 2) a short getting started guide for developers e.g. how do I develop for > sling with eclipse without getting long roundtrips (or other IDEs, what's > about the eclipse plugin for jcr/sling?) > > 3) a short how-to guide for a real productive installation (like apache as > front server with mod_proxy or similar) +1 for 1-3 Sounds good and this is also what is spinning around in our heads .. but it never finds time to spin down into the fingers and over the wires. > > 4) a separation of the core code and the additional bundles (as it is already > planed for the new release) -> maybe almost done? Carsten has already done that. We now have the "main folders" (parent, api, bundles and launchpad) which constitute what's going into the next big release. And we have the contrib folder (with the same structure as the bundles folder), which are additional bundles, we will be releasing separately later, based on community requirements. > > It's great to hear that there will be soon a new release of sling. IMHO the > new release should be really used to get more people using sling and also to > get more people be involved in sling development. Maybe in favour of a > consistent documentation the release should be delayed. We have discussed delaying the release for documentation before the first release (which dates back almost a year now!). And we decided to cut the release and then update the docs. My position is to do the same this time... The release is overdue as is the docs. But I think first things first and the docs will surely follow. Promised. Finally: As I said, contribution is also possible in the form of documentation and we very much welcome documentation contribution. Hope this helps to understand the situation as it is. Regards Felix > > WDYT? > > regards > Mike >
