On Fri, 4 Jan 2002 23:23, Ceki Gülcü wrote: > The threat is to Jakarta's *nature* and it comes from our indecisiveness. > > Real problems I see is > > 1) lack of focus,
Dont see this as a problem. Each project is usually focused on its dowmain and the overall project has a sort of scope. Personally I would have no problem widening scope of jakarta to include virtually any java project, serverside, clientside, frameworks, products, etc but not everyone thinks this is a great idea ;) > 2) duplication between projects, diversity aids evolution though preferably it would be intra rather than inter project duplicity. However the PMC has historically not seen that as desirable due to advertising. > 3) lack of common procedures for doing things. This is the one possible issue I see. However I only see it as a problem for the "external" interface between projects. Mainly this involves things like release naming cconventions, targets in ant files, location of intermediate and destination files in a build. It really is irrelevent to outsiders what indent style is used, whether anakia or stylebook is used yadda yadda. So I +1 on suggesting standards for external parts of project, -1 for forcing it -- Cheers, Pete ------------------------------------------ I just hate 'yes' men, don't you Smithers? ------------------------------------------ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
