<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Sébastien,<div class=""><br class=""></div><div class="">I respond to you in private... for i was already working on a 'project' that might help us indeed... but rather not have it disclosed now, since i need to have the whole marketing thing in place first.</div><div class=""><br class=""></div><div class="">I've registered <a href="http://www.perl.evetns" class="">http://www.perl.evetns</a> and was ... in conjunction with the Act-Voyager REST api going to build a new global frontend the new front end could be hosted by a single instance, as long as people adhere to the REST api, but <a href="http://www.perl.events" class="">http://www.perl.events</a> would just be a easy way to see what is going on world wide and have a website directly available, without munging on templates.</div><div class=""><br class=""></div><div class="">so we could still host the old ACT as is and start with a (uniform) new front end, and yes, my.perl.events would be the private pages for personal admin stuff.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">So, that also explains my renewed interest in having acces to the Act server, to continue with the REST api, and implement bit by bit</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Concerning YAPC::Amsterdam, until mid december, it seems we will work with <a href="http://yapc.amsterdam" class="">http://YAPC.Amsterdam</a></div><div class="">After that, we might move to TPC.Amsterdam</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 25, 2016, at 9:21 PM, Sébastien Aperghis-Tramoni <<a href="mailto:sebastien@aperghis.net" class="">sebastien@aperghis.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello,<br class=""><br class="">Theo van Hoesel wrote:<br class=""><br class=""><blockquote type="cite" class="">YAPC::Amsterdam a.k.a "The Perl Conference in Amsterdam"<br class=""><br class="">please setup the servers so we can start publishing the website for<br class="">YAPC next year.<br class=""><br class="">it has been discussed with people from TPF and from now on, we'd like<br class="">to use a new 'top-level directory name: /tpc<br class="">sub path: /tpc/amsterdam-2017<br class=""><br class="">suggested Act-Conference repo:<br class=""><a href="https://github.com/Act-Conferences/tpc-2017-amsterdam" class="">https://github.com/Act-Conferences/tpc-2017-amsterdam</a><br class=""></blockquote><br class="">Laurent just created it.<br class=""></div></div></blockquote><div><br class=""></div><div>I got the message from GitHub, indeed</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class="">other conferences will follow that pattern. No longer will "The Perl<br class="">Conference" be divided in regions, they will be named with the city<br class="">where it's being held. Much like OSCON. TPF does prefer global<br class="">branding, As does the majority of the Amsterdam organisers.<br class=""><br class="">If, for example the next YAPC::NA would be held in Detroit... it will<br class="">be: "The Perl Conference in Detroit" ... /tpc/detroit-2017<br class=""></blockquote><br class="">"The Perl Conference" sure will be easier to market than "YAPC."</div></div></blockquote><div><br class=""></div><div>i love YAPC.Amsterdam,. The Perl Conference</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">However, a piece of information missing in your email is the domain<br class="">which should support the conference(s). Also, out of the box, I'd<br class="">say we can't insert a "/tpc/" in the middle of URLs like this.<br class=""></div></div></blockquote><div><br class=""></div>that was a mistake from my side:</div><div><br class=""></div><div>/tpc-2017-amsterdam</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="">We can probably somehow cheat with some ProxyPass or RewriteRule<br class="">trickery, but it's not really elegant.<br class=""><br class="">If the aim is to make things simpler & easier to find, a single<br class="">domain like <a href="http://perlconference.org" class="">perlconference.org</a> to host all these newly branded<br class="">conferences seems the most obvious way to go.<br class=""><br class="">Act being Act, we need a dedicated subdomain. For example:<br class="">- <a href="http://act.perlconference.org" class="">act.perlconference.org</a><br class="">- <a href="http://the.perlconference.org" class="">the.perlconference.org</a><br class="">- <a href="http://my.perlconference.org" class="">my.perlconference.org</a><br class=""><br class="">Then next year's editions would have the following URLs:<br class="">  <a href="http://the.perlconference.org/tpc-2017-amsterdam/" class="">http://the.perlconference.org/tpc-2017-amsterdam/</a><br class="">  <a href="http://the.perlconference.org/tpc-2017-detroit/" class="">http://the.perlconference.org/tpc-2017-detroit/</a><br class=""><br class="">What do you think?<br class=""></div></div></blockquote><div><br class=""></div><div>that does look nice</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">-- <br class="">Sébastien Aperghis-Tramoni<br class=""></div></div></blockquote><div><br class=""></div><div><br class=""></div>Thanks for responding so fast this time!!!!</div><div><br class=""></div><div>Theo</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">Close the world, txEn eht nepO.<br class="">_______________________________________________<br class="">Act mailing list<br class=""><a href="mailto:Act@mongueurs.net" class="">Act@mongueurs.net</a><br class="">http://listes.mongueurs.net/mailman/listinfo/act<br class=""></div></div></blockquote></div><br class=""></div></body></html>