Thanks Oli for making me laugh :) Partially I'm still coming to learn the in and outs of the development process. As an infrequent consumer of the dev list before becoming a committer the reason why things happen seem obscure sometimes or just plain out of the blue.
One of those obscure reasons is why some things get worked on and other don't. There's bundles that seem to invoke a lot of user noise that don't seem to get attention. An example of that is the Sling Rewriter and it's lack of OSGi configuration support. Which throws just about everyone the first time they use it. Additionally I've got ideas for improvements for bundles, like the Rewriter, and the Post Processor but I'm not sure the effective way to communicate them which Bertrands response helped a lot with. And yes a vision or a plan would be nice. We do snapshot style releases, will we ever do supported releases? We just released Sling 10, but tomorrow if we release an incremental version of pipes or sling models, why aren't we doing a release of 10.1? Also there seems to be a slow movement away from Slings original purpose of being that which wraps the JCR to a Resource Provider agnostic framework, am I seeing things, or is there a a plan? Things like that go through my mind. - Jason On Thu, Feb 15, 2018, at 8:15 AM, Robert Munteanu wrote: > Hi Jason, > > On Wed, 2018-02-14 at 16:05 -0500, Jason E Bailey wrote: > > Couple of questions. > > > > 1. Do specific committers 'own' certain modules/projects > > 2. Does anyone maintain a grand vision? > > I won't add on to Oli's and Bertrand's excellent questions. However I'm > curious as to why you asked these questions :-) > > Do you feel a need for more/less ownership or that we should have a > grand(er) vision than what is here right now? > > Thanks, > > Robert
