Thanks for the comments, I'm really looking more for feedback on the organization of the content, all the content is taken from the existing.For the 3rd point, the current website has 2 very similar pages (I only conserved one here as it was a quick shot, but the 2 needs to be merged)On Thu, Jul 7, 2016 at 11:37 AM, Alissa Bonas <abonas@redhat.com> wrote:3. Community-Connect leads to page named "Join". Perhaps it would more clear to make the link and the page name the same (and I would call it "Get involved" anyway)2. Top level menu font color is a really pale grey so everything looks disabled.Couple of suggestions:1. In the "Hawkular features" section in homepage make the icons clickable. right now the only way to get more info is to click the "more" part.On Thu, Jul 7, 2016 at 11:58 AM, Thomas Heute <theute@redhat.com> wrote:So here is a very rough idea of how it would look like:Content need to be adapted, new pages to be created, but hopefully you get the ideaOn Tue, Jul 5, 2016 at 8:27 PM, John Sanda <jsanda@redhat.com> wrote:_______________________________________________I think a top-level project makes the most sense.On Jul 5, 2016, at 10:21 AM, Thomas Segismont <tsegismo@redhat.com> wrote:
Le 05/07/2016 à 16:05, Stefan Negrea a écrit :On Tue, Jul 5, 2016 at 8:03 AM, Thomas Segismont <tsegismo@redhat.com
<mailto:tsegismo@redhat.com>> wrote:
Le 05/07/2016 à 14:59, Heiko W.Rupp a écrit :2) The Grafana plugin should be moved under Metrics because is for MetricsIf this is true - can we make it work with H-services as well?and only Metrics.
The Grafana plugin works with all active flavors of Metrics: standalone,
Openshift-Metrics and Hawkular-Services.
I'm not sure what Stefan meant.
The Grafana plugins works with Metrics deployed on all distributions
however, the plugin itself can only be used with the Metrics project,
there are no projects (such as Alerts, or Inventory) that will ever
integrate with it. That is why I think it should be under the Metrics
project and not in another place. The integration itself is very
specific to just Metrics, not the entire Hawkular Services.
I see what you meant now. But we can't presume anything about other
services roadmaps. For example, the datasource plugin annotation feature
could be implemented with requests to an event service.
Anyway, since it should be able to connect to Metrics in different
environments (H-Services, OS-Metrics and standalone), I err on the side
of promoting it as a top level project.
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev