Hi, On Wed, Jan 1, 2014 at 11:27 PM, Dominik Süß <[email protected]> wrote: > First of all - Happy new year to all of you from my side :)
Thanks, happy 2014 to all Sling community members! A few comments on your wishlist, in general I agree that those are nice goals to have. > ...DevOps optimization: this includes setup, patching, monitoring and > scalling of installations... I also think this is the next big topic to tackle for Sling. I have a number of (somewhat wild) ideas about this, hoping to get some interns to work on experiments in that area in 2014. I'm in favor of not going too far inside Sling with this, and taking a systems approach to configuration and upgrades management to separate concerns and keep Sling lean and mean. > ...Subtopic Deployments: It is still not clear how to package deployments > the right way, although various mechanisms are available it seems like > there still is room for optimization... Not sure what you mean by this but the devops work can also help here - I'm thinking in particular of letting Git or other repositories drive the configuration of Sling instances, as recently discussed. > ...POST Servlet: this is an area that I have on my list since last year and > where I started to work on a proposal for a new version that hopefully can > be a base for something that replaces the old POST Servlet and reduces the > need for implementing custom Servlets as much as possible... I like this, the challenge here IMO is keeping things backwards compatible, so the starting point is to make sure the current code has full test coverage. > ...Feature Flags: although the "Feature of Features" seams close to be ready > as first draft there is a lot of work left... Agreed, at this point we need small reversible steps in this direction, to help converge on the use cases and how we implement them as this is very new territory for most of us. The devops systems approach can also play a role here, as turning a feature on or off can in some cases be implemented by routing incoming requests to different Sling instances. > ...Documentation... I already replied to that one in this thread, I'm still a big fan of readable tests as the ultimate reference documentation, and keeping written documentation at the overview level to make it sustainable and accurate. Yet, we have a long way to go here. As a simple thing were any community member can help, we still have too many old pages under http://svn.apache.org/repos/asf/sling/site/trunk/content/site/ that need to be cleaned up as per my comment 04/Apr/13 12:28 in SLING-2002. Apart from all that my wish for 2014 is that we can get more people involved in Sling who are not using CQ, to keep the diversity. Not only in terms of company influences (I think we're doing ok despite a majority of Adobe/CQ related community members) but above all in terms of a diverse set of use cases that help make Sling better by bringing in different views. -Bertrand
