<div dir="ltr">Personally I would vote for:<div> - Renaming the existing "Hawkular Agent" to "Hawkular WildFly Agent" and reduce its scope to the embedded WF scenario (+ remote for domains). Small in scope == easier to maintain, document, understand...</div><div> - Name this one "Hawkular Kubernetes Agent", or "Hawkular OpenShift Agent" if it really depends on OpenShift (but I'm not sure why), because the discovery is a key feature and I guess (will) use Kubernetes API.</div><div><br></div><div>I can understand this could be extended to other usecases that don't involve WildFly or Kubernetes, but I'm afraid that we just make things more complex/harder to understand while those 2 targets are key.</div><div><br></div><div>PS: I don't think we need yet another cryptic name as GoHawk / Hawkulark (and in theory requires legal implication)</div><div><br></div><div>Thomas</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 18, 2016 at 7:08 PM, John Mazzitelli <span dir="ltr"><<a href="mailto:mazz@redhat.com" target="_blank">mazz@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">OK, folks, as much as I hate these "what should we name this thing?" threads, I have to do it.<br>
<br>
We are at the point where we are going to start going full-throttle on building out an agent that can monitor things on Open Shift (and Heiko wants to be able to monitor things outside of Open Shift - I'll let him chime in on what his use cases are to get a better feel for what he's thinking)<br>
<br>
We need a name ASAP so we can create a repository under the Hawkular github namespace and put the code up there so people can start working on it. I would like to do this sooner rather than later - say, by Thursday???<br>
<br>
Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because "k" == kubernetes.<br>
<br>
I was thinking "GoHawk" (rhymes with "mohawk") because it is implemented in "Go"<br>
<br>
I wasn't keen on relying on "kubernetes" as part of the name since its really targeting Open Shift and even then doesn't have to run in Open Shift (back to the ideas Heiko has for this thing).<br>
<br>
"GoHawk" doesn't seem to be a winner simply because what happens if we implement other hawkular feeds in Golang?<br>
<br>
I'm assuming we'll come up with a name and agree to it collectively as a group - but I nominate Thomas H, Heiko R, and John D. as the committee to give the final approval/tie-breaking authority :) It won't be me. I suck at coming up with names.<br>
<br>
--John Mazz<br>
<br>
P.S. Who knows how to setup one of those online polls/surveys where you can enter your submissions and vote for other submissions?<br>
______________________________<wbr>_________________<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/<wbr>mailman/listinfo/hawkular-dev</a><br>
<br>
<br>
</blockquote></div><br></div>