Re: [Hawkular-dev] hawkular.org - Redux Initiative

The aim is to add a "Tracing" entry as a "stage 2", but wasn't sure whether this meant releasing a version of the website without it first, and then introduce it as a separate step?

A general comment - perhaps we should drop the "Hawkular" part from each component - so then we simply have "Metrics", "Alerts" and "Tracing"?

On Tue, Jul 4, 2017 at 8:22 AM, Heiko Rupp <hrupp(a)redhat.com&gt; wrote: > Hey, > > On 3 Jul 2017, at 23:42, Stefan Negrea wrote: > > > I waited about 2 weeks to allow enough time for feedback. There was a > > good amount of initial discussion on the document mostly in the form > > of proposals to enhance the initial plan. There were zero negative > > comments and nobody opposed the plan. > > I know I did not chime in on the document, so have no right > to complain now :-) > > I think though that the removal of Hawkular Services is wrong. > It may indeed at the moment only exist for that one consumer, > which is ManageIQ, but not listing it is in my opinion also > confusing. Instead of removing it, we should perhaps better > educate visitors of the web site (in a graphical way?) how this > relates to the other projects. > Similar to Tracing. This is no longer Hawkular APM, so it is right > not to list Hawkular APM, but so far Tracing folks are still under the > Hawkular umbrella and the blog contains a lot of content about it. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev