I'm with Matt on this. Since it is not perfect to everybody's satisfaction, let us move it to the /plugins tree (at least for now). Sandbox is definitely not the place for it.
Erik, contrary to your belief, the /plugins tree does not contain only those plugins that work independent of G. It *mostly* contains plugins that integrate independent projects (like Liferay, ApacheDS, roller etc) with G. Now the monitoring plugin does not actually fit that bill. Neverthless, that is still a step above sandbox, and still on the road to trunk/plugins. It can still be released with 2.1 and still available in the plugins catalog for possible installation. Cheers Prasad On Dec 8, 2007 12:00 AM, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > > On Dec 7, 2007, at 9:11 AM, Anita Kulshreshtha wrote: > > >> 2. If yes, then where should we move it to? Should it be in server/ > >> trunk/plugins or should the monitoring plugin be a subproject. > > > > I was thinking of plugins.. > > I'm not sure it really matters where the code goes in the interim. > Plugins makes sense but I would move it to trunk first. Trunk is > certainly viable and would likely get more people to look at the code, > report issues, and most likely ooh and awe about cool looking graphs > and statistics. > > If it turns out that the monitoring bloats the server in an > unacceptable way, has incorrect statistics or consumes too many > resources then I would think that moving it to plugins would be a > reasonable approach. > > >
