+1 Even a bit of documentation (which seems scattered about... in the specification, on VMW sites/properties, etc) would go a long way in helping users realize the benefit of the tool and provide feedback, maybe even contribute some PRs. Having metrics on GemFire in realtime is hugely invaluable (even just explaining all the metrics and what they mean, how they are visualized should be sufficient).
On Fri, Sep 23, 2016 at 9:32 AM, Dave Barnes <dbar...@pivotal.io> wrote: > Here's a proposal based on what I've seen in this thread: > 1. We remove JVSD documentation from the user manual. > 2. We save what's been written so far (mostly just build instructions) as a > README on the feature branch. > > On Thu, Sep 22, 2016 at 7:40 PM, Anthony Baker <aba...@pivotal.io> wrote: > > > Corporate org structures don’t get a voice on ASF mailing lists, only > > community participants :-) > > > > Anthony > > > > > > Begin forwarded message: > > > > *From: *Dave Barnes <dbar...@pivotal.io> > > *Subject: **Re: jvsd* > > *Date: *September 22, 2016 at 4:37:19 PM PDT > > *To: *dev@geode.incubator.apache.org > > *Reply-To: *dev@geode.incubator.apache.org > > > > Silence = "Docs group gets to pick" > > > > > > > -- -John 503-504-8657 john.blum10101 (skype)
