I'm with Jim in that it takes more than a name, but a name does go a long way in terms of product perception. We all know what the QAH is and its importance. Potential sponsors probably don't. Names like "Perl Critical Infrastructure Summit" are pretty much self-explanatory, while "Perl Quality Assurance Hackathon" or "Perl QA Hackathon" are definitely confusing from the outside.
Is the effort of elucidating others really worth it? If there are no particular attachments to the name, I'm all for changing it and seeing if it makes a difference. Maybe I'm missing a point here, but it doesn't look like a big deal to me. It's a label on a website and maybe a flyer. QAH might be a well-known brand *inside* the Perl community and that's pretty much it. I don't expect a lot of raised eyebrows over this, at least not from people outside this mailing list. If it makes no difference and we miss the old name, we can always change it back too - again, no big deal. As for the new name, I like all ideas so far, but I'd put the "Annual" in the explanation instead on in the label - maybe replaced by "yearly" - so we are free to move the frequency around without worrying about new acronyms :) "Perl Critical Infrastructure Summit" gets my vote, even though "PCI Summit" makes me think of other things entirely. Cheers! On Sat, Apr 9, 2016 at 2:32 PM Kent Fredric <kentfred...@gmail.com> wrote: > On 10 April 2016 at 04:49, Sawyer X <xsawy...@gmail.com> wrote: > > Perl Annual Critical Infrastructure Summit. > > > Perl Infrastructural Engineering Summit. > > PIES. :D > > > Summit of Perl Infrastructural Critical Engineering. > > SPICE. > > Hth. > > -- > Kent > > KENTNL - https://metacpan.org/author/KENTNL >
