I agree with Ruth. This sounds like a user requirement. And the community should decide on this.
Furthermore, the remark 'users might like a new feature, but that doesn't mean the dev community wants it in the project' smells like measuring with double standards; as if the meritocratic principle doesn't apply when the committers don't want it in. Or as if changes always get in, when only the committers want it. 2012/7/15 Adrian Crum <[email protected]> > Ruth, > > I understand your viewpoint. Personally, I prefer to present my ideas to > the dev list to see if it is something the dev community wants included in > the project. Users might like a new feature, but that doesn't mean the dev > community wants it in the project. If there was no interest from the dev > community, then I would offer it as an add-on product and announce it on > the user list. > > I am also a user, and the design was based on the requirement to monitor > and control server performance. I suppose I could go to the user list for > more ideas, but the code I'm planning to commit is pretty basic, and users > will be free to enhance it in whatever way they please. > > -Adrian > > > On 7/15/2012 12:13 PM, Ruth Hoffman wrote: > >> Hi Adrian: >> Shouldn't this be discussed on the "user" list? IMHO Words like >> "applications" and "stats about services and entities"...those are all >> indicative of user requirements, not developer requirements. >> >> Users should be driving requirements gathering and analysis for OFBiz and >> not developers. >> Just my 2 cents. >> Regards, >> Ruth >> >
