<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 5, 2016 at 4:10 PM, Stefan Negrea <span dir="ltr"><<a href="mailto:snegrea@redhat.com" target="_blank">snegrea@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><span class="">On Tue, Jul 5, 2016 at 3:19 AM, Thomas Heute <span dir="ltr"><<a href="mailto:theute@redhat.com" target="_blank">theute@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Thu, Jun 16, 2016 at 6:11 PM, Stefan Negrea <span dir="ltr"><<a href="mailto:snegrea@redhat.com" target="_blank">snegrea@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">I really like this last revision because the content is sectioned along the way we deliver to users. So when a user navigates the website, the content is always related to what they can directly download and use and not mixed together.<div><br></div><div>I have 3 small proposals:<div>1) Hawkular and Overview can be combined into one Hawkular Overview or Hawkular (which has the overview of the projects).</div></div></div></blockquote><div><br></div></span><div>This is more an issue with the representation in the mindmap I think.</div><div>Hawkular is really the homepage: <a href="http://www.hawkular.org/index.html" target="_blank">http://www.hawkular.org/index.html</a> and I think we can remove the link since the link on the logo does the same thing and it's quite a UXD standard.</div><div>Overview is a more detailed page: <a href="http://www.hawkular.org/docs/overview.html" target="_blank">http://www.hawkular.org/docs/overview.html</a> a user should find it's way among the various projects.</div><span><div></div></span></div></div></div></blockquote><div><br></div></span><div>As long as we do not have two top menu entries, one for Hawkular and one for Overview, then the proposal makes sense. <br></div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>2) The Grafana plugin should be moved under Metrics because is for Metrics and only Metrics.</div></div></div></blockquote><div><br></div></span><div>The Grafana plugins works with Metrics and Services</div></div></div></div></blockquote><div><br></div></span><div>But it is a Metrics specific integration, no other services will ever integrate with Grafana.<br></div></div></div></div></blockquote><div><br></div><div>It is not Hawkular Metrics specific if it works for Hawkular Services.</div><div><br></div><div>Thomas</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>3) Hawkular Server should be renamed Hawkular Services because that the official project name.</div></div></div></blockquote><div><br></div></span><div>OTOH I would not want a totally separate structure for Hawkular Services *and* Hawkular Community, as they are very much the same except for some installation process (have to install C* separately or not) and maybe for additional parts in Community. The idea was to combined both into a single concept of server.</div></div></div></div></blockquote><div><br></div></span><div>Agree here, what I suggested is that Hawkular Community is just a subsection in the Hawkular Services; and not two different sections. That will give more visibility to the concept of Hawkular Services rather than promote the unused name of Hawkular Server .<br></div><div><div class="h5"><div> <br><br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><font color="#888888"><div><br></div><div>Thomas</div></font></span><div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br></div></div></div><div class="gmail_extra"><br clear="all"><div><div data-smartmail="gmail_signature"><div dir="ltr">Thank you,<br>Stefan Negrea<br><br>Software Engineer<br></div></div></div><div><div>
<br><div class="gmail_quote">On Wed, Jun 15, 2016 at 1:18 PM, Thomas Heute <span dir="ltr"><<a href="mailto:theute@redhat.com" target="_blank">theute@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">Sorry, I meant to sent the PNG file... here it is</div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 15, 2016 at 8:08 PM, Thomas Heute <span dir="ltr"><<a href="mailto:theute@redhat.com" target="_blank">theute@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">Based on that suggestion, here is another proposal. <div><br></div><div>Rectangle means a page</div><div>Underline is more likely a section on a page</div><div>Green arrows mean links (To Travis, to gitbook.io...) </div><div><br></div><div>Let me know what you think of that updated section</div><span><font color="#888888"><div><br></div><div>Thomas</div></font></span></div><div class="gmail_extra"><br><div class="gmail_quote"><span>On Tue, Jun 14, 2016 at 10:32 PM, Stefan Negrea <span dir="ltr"><<a href="mailto:snegrea@redhat.com" target="_blank">snegrea@redhat.com</a>></span> wrote:<br></span><div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">I do not see the idea proposed yet, but why not structure the website around major projects? We have Hawkular community, Hawkular Services, Hawkular Metrics, and APM. Projects like Inventory or the clients would fall under Hawkular Services umbrella. So rather than designing a generic structure with everything make individual sub-sites and then apply the structure you proposed.<div><br></div><div>The current website was designed when the direction of the community was different so a re-org along the previous structure is not sufficient.</div><div class="gmail_extra"><br clear="all"><div><div data-smartmail="gmail_signature"><div dir="ltr">Thank you,<br>Stefan Negrea<br></div><div dir="ltr"><br></div></div></div><div><div><div class="gmail_quote">On Tue, Jun 14, 2016 at 12:08 PM, Michael Burman <span dir="ltr"><<a href="mailto:miburman@redhat.com" target="_blank">miburman@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Currently Heapster stores in internal memory few minutes of data and allows queries that request this data (through its REST-interface). The consume part will just request the data from the HWKMETRICS instead.<br>
<span><br>
- Micke<br>
<br>
----- Original Message -----<br>
</span><span>From: "Thomas Heute" <<a href="mailto:theute@redhat.com" target="_blank">theute@redhat.com</a>><br>
To: "Discussions around Hawkular development" <<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a>><br>
</span><span>Sent: Tuesday, June 14, 2016 4:09:40 PM<br>
Subject: Re: [Hawkular-dev] Hawkular.org<br>
<br>
<br>
<br>
</span><span>On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman < <a href="mailto:miburman@redhat.com" target="_blank">miburman@redhat.com</a> > wrote:<br>
<br>
<br>
Consumers is terrible word for any client, as they both consume as well as produce the data.<br>
<br>
Well that was actually reflecting the current state, we have "things" that feed data to the server and "things" that consume data from the server. The client libraries provide an API to feed and consume.<br>
<br>
<br>
For example for Heapster, we currently produce the data, however at the moment I'm creating a change that will consume the data from HWKMETRICS.<br>
<br>
Why does it consume data now ?<br>
<br>
Thomas<br>
<br>
<br>
<br>
<br>
Integration / clients is far more used and known word, while consumer/producer is something more specific and implies a design pattern.<br>
<br>
- Micke<br>
<br>
</span><div><div>_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
</div></div></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br></blockquote></div></div></div><br></div>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br></blockquote></div><br></div></div>