[Hawkular-dev] open shift agent - what to call it?

[Thomas Heute]

I would really hate to have:
  - Hawkular Agent (is our current name for the Wildfly agent)
  - Hawkulark or hawkster or hawkshift... for this Kuber/Openshift one
  - hawkraf or karhawk if we ever build an embedded karaf agent
  - hawkdroid andrhawk when someone contributes an Android monitoring agent
  - ...




On Wed, Oct 19, 2016 at 9:20 AM, Thomas Heute <theute at redhat.com> wrote:

> Personally I would vote for:
>    - 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...
>    - 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.
>
> 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.
>
> PS: I don't think we need yet another cryptic name as GoHawk / Hawkulark
> (and in theory requires legal implication)
>
> Thomas
>
> On Tue, Oct 18, 2016 at 7:08 PM, John Mazzitelli <mazz at redhat.com> wrote:
>
>> OK, folks, as much as I hate these "what should we name this thing?"
>> threads, I have to do it.
>>
>> 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)
>>
>> 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???
>>
>> Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because "k" ==
>> kubernetes.
>>
>> I was thinking "GoHawk" (rhymes with "mohawk") because it is implemented
>> in "Go"
>>
>> 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).
>>
>> "GoHawk" doesn't seem to be a winner simply because what happens if we
>> implement other hawkular feeds in Golang?
>>
>> 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.
>>
>> --John Mazz
>>
>> P.S. Who knows how to setup one of those online polls/surveys where you
>> can enter your submissions and vote for other submissions?
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161019/ce8d7481/attachment-0001.html