Random holiday fun: Vote for buildbot naming conventions!

[Austin Seipp]

Hi *,

Everyone has been working hard getting things ready for the branch/RC
later this week - and that's really appreciated! As always, GHC
wouldn't be what it is without you.

But it's the holidays - that's stressful for some, and real time
consuming for others. So to keep things light and a little
interesting, and if you have a minute as an experiment, I'd like to
ask you all something:

What naming conventions should we use for GHC buildbots? We've been
adding more bots recently, and we've just gotten hold of some new
hardware this week.

Currently, GHC buildbots don't have any reserved name or identifier,
or DNS entries. I'd like to change that - we mostly refer to them by
IP, but this is annoying A) to remember and B) to tell other people.
We'll likely begin to lease out these machines to developers so they
can test and debug - meaning they'll be mentioned more.

I'd like to propose a theme for naming buildbots - this theme would be
used to populate DNS entries under the *.ghc.haskell.org domain.

The question is: what naming convention do we use?

So I created a poll for this. You can see that poll and vote for your
favorite options on Phabricator:

  - https://phabricator.haskell.org/V3

It's an approval vote rather than a plurality; so feel free to select
multiple choices. The winner with the most votes will get selected.

Note: the selection of options is relatively random and pre-selected;
there is an upper limit on the number of choices - 10 max - so I
merely picked some categories I thought would work and be generic
enough.

I imagine this vote will be open for about a week or so. I'd like it
if developers could vote on their favorites, or simply leave comments
on the vote for further suggestion - we could institute a vote with
better names.

Thanks all - and be sure to have happy holidays.

P.S I did not know RFC 1178 existed before today. Seems like there's
one for everything...

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/