Whether you want them to or not, David, most of the people in the community assume that when you say to ignore or not worry about someone's comment that you're speaking from experience and are in the know on the best practice.
That kind of kills discussion. I'm of the opinion that this community should have the mentality that if a decision has to be made, that it be made in local, custom code. The only decisions that should be put into SVN are the _best_ decisions, not just _a_ decision. The only way to come to a _best_ decision is to point out specifically, the strengths and weaknesses in the options presented. --- "David E. Jones" <[EMAIL PROTECTED]> wrote: > > Discussion is just one part of decision making. > Eventually a decision has to be made. My involvement > in that issue was nothing more than it is in most > cases: reviewing the decision and commenting on it. > > -David > > > Chris Howe wrote: > > That's very interesting, David. Considering that > > questioning of patterns is exactly what was being > done > > in OFBIZ-81 and you of all people prompted others > to > > dismiss the idea, even when the problem was > > articulated. > > > > --- "David E. Jones" > <[EMAIL PROTECTED]> > > wrote: > > > >> The best info to date on these things would be > the > >> Framework Introduction videos and the Best > Practices > >> Guide. > >> > >> Of course, anyone who has spent enough time with > >> OFBiz to have commit access in a certain area > should > >> be familiar enough with the artifacts in that > area > >> to recognize the established patterns. > >> > >> It's just like any effort to maintain > consistency: > >> precedence is the key. Of course, precedence > should > >> be questioned and reconsidered regularly and > >> sometimes even changed. > >> > >> If this is a problem, it is the duty of the > >> community (including me and all of us on this > >> mailing list) to fix it, especially those who > >> consider it a problem. > >> > >> -David > >> > >> > >> Adam Heath wrote: > >>> David E. Jones wrote: > >>>> In general please don't be too quick to change > >> things, especially that > >>>> are related to established patterns. Many of > >> these were established > >>>> after years of feedback and trying different > >> things and there are > >>>> always trade-offs with such things that one > must > >> watch out for. > >>> Ok, so what are the established patterns? Are > >> they documented anywhere? > >>> If no one knows them, then expect to have more > of > >> this in the future. > >> > > >
