I don't have a strong preference but "infrastructrure" reminds me of "infrastructure as a code" or something similar, which I suppose doesn't match with what we actuallly have. I'd +1 for something that keeps "QA" or "toolchain" or whatever that reminds us of CPAN or the tools to install (or analyze or whatever we need to do before installing).
2016-04-10 1:49 GMT+09:00 Sawyer X <xsawy...@gmail.com>: > Merging the suggestions I saw so far: > > Perl Annual Critical Infrastructure Summit. > > A mouthful, and not a fun acronym. > > On Sat, Apr 9, 2016 at 6:16 PM, Karen Etheridge <p...@froods.org> wrote: >> When I saw this thread title I thought it was going to be discussing the >> "QA" part of it, and I thought "yeah, right on!".. I totally agree with >> Neil's points about what we do not being a "hackathon" though. >> >> ..And I also like the idea of changing the QA bit to Infrastructure. >> >> Perl Infrastructure <something> gets a vote from me. >> >> >> On Sat, Apr 9, 2016 at 8:50 AM, Kent Fredric <kentfred...@gmail.com> wrote: >>> >>> On 10 April 2016 at 03:45, David Golden <da...@autopragmatic.com> wrote: >>> > Perl Toolchain Summit >>> >>> >>> Because "Toolchain" is not really a word that necessarily makes sense >>> outside Perl, you can use "Infrastructure" or even "Critical >>> Infrastructure" in its stead. ( I personally like Critical, its a >>> very spicy word, and accurately reflects the propensity of this sphere >>> of things to either go pear shaped or steal your SAN Cookies ) >>> >>> Also, depending on how many words you want to spend, throwing "Annual" >>> in there might help give some context to how frequently these things >>> happen. >>> >>> The narrative you want to be carrying in your words is: >>> >>> "Every year, we get all our brightest in one place and discuss and >>> work on the most pressing and important problems that affect the the >>> broadest number of concerns in the Perl+CPAN ecosystem" >>> >>> -- >>> Kent >>> >>> KENTNL - https://metacpan.org/author/KENTNL >> >>
