On 7/8/10 10:58 AM, Carsten Ziegeler wrote: > Justin Edelson wrote >> On 7/7/10 11:55 AM, Ian Boston wrote: >>> >>> On 7 Jul 2010, at 16:26, Justin Edelson wrote: >>> >>>> I'd like to release the contrib/gwt/servlet module, but have some >>>> misgivings about the versioning scheme used there. >> >> One more thing I'd like to do before this release is more >> contrib/gwt/servlet to bundles/extensions/gwt and contrib/gwt/samples to >> samples/gwt. >> >> I'm not sure what, if any, policy exists for moving things from contrib >> (or even how something ends up in contrib in the first place), but if a >> PMC member could give me the OK (or not), I'd appreciate it. >> > The original idea was that all new modules start in contrib - however we > failed to follow this sometimes, so some modules show directly up in the > main area. > Modules from contrib can be moved to the main area if there is the > fealing that this is an important part of sling and/or this is backed up > by several developers. > Now, here again, the idea is to not polute the main area with hundreds > of bundles which are not maintained anymore. > > Or in other words, from a users perspective: if something is in the main > area, users can be sure that they are helped if they have problems etc. > whereas if something is in contrib it might be that there is no activate > developer (anymore) > > Ok that's a long anwswer :) Thanks for the long answer :). This makes a lot of sense.
> > Now for the gwt stuff I'm not sure - I'm not against moving it, however > I have the feeling that atm there is no general interest in it. So count > this as a 0 :) Well, my intent in moving it to bundles/extensions was to say that I was going to actively upgrade it going forward. But if I'm the only one willing to do so, I'll leave it in contrib. If it attracts significant usage (or any usage other than me), we can move it later. Thanks, Justin > > Regards > Carsten
