From th.j.v.hoesel at gmail.com Sun Oct 23 14:07:22 2016 From: th.j.v.hoesel at gmail.com (Theo van Hoesel) Date: Sun, 23 Oct 2016 13:07:22 +0100 Subject: [Act] YAPC::Amsterdam Message-ID: <761B2B22-25DB-4120-BB12-7CF52C6D9E7C@gmail.com> a.k.a "The Perl Conference in Amsterdam" please setup the servers so we can start publishing the website for YAPC next year. it has been discussed with people from TPF and from now on, we'd like to use a new 'top-level directory name: /tpc sub path: /tpc/amsterdam-2017 suggested Act-Conference repo: https://github.com/Act-Conferences/tpc-2017-amsterdam other conferences will follow that pattern. No longer will "The Perl Conference" be divided in regions, they will be named with the city where it's being held. Much like OSCON. TPF does prefer global branding, As does the majority of the Amsterdam organisers. If, for example the next YAPC::NA would be held in Detroit... it will be: "The Perl Conference in Detroit" ... /tpc/detroit-2017 please, lets start moving... Theo P.S. will you add co-contributer: Detlev Hauschildt (https://github.com/detlevh ) -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien at aperghis.net Tue Oct 25 22:21:53 2016 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Tue, 25 Oct 2016 22:21:53 +0200 (CEST) Subject: [Act] YAPC::Amsterdam In-Reply-To: <761B2B22-25DB-4120-BB12-7CF52C6D9E7C@gmail.com> Message-ID: <706768345.186042091.1477426913431.JavaMail.root@spooler3-g27.priv.proxad.net> Hello, Theo van Hoesel wrote: > YAPC::Amsterdam a.k.a "The Perl Conference in Amsterdam" > > please setup the servers so we can start publishing the website for > YAPC next year. > > it has been discussed with people from TPF and from now on, we'd like > to use a new 'top-level directory name: /tpc > sub path: /tpc/amsterdam-2017 > > suggested Act-Conference repo: > https://github.com/Act-Conferences/tpc-2017-amsterdam Laurent just created it. > other conferences will follow that pattern. No longer will "The Perl > Conference" be divided in regions, they will be named with the city > where it's being held. Much like OSCON. TPF does prefer global > branding, As does the majority of the Amsterdam organisers. > > If, for example the next YAPC::NA would be held in Detroit... it will > be: "The Perl Conference in Detroit" ... /tpc/detroit-2017 "The Perl Conference" sure will be easier to market than "YAPC." However, a piece of information missing in your email is the domain which should support the conference(s). Also, out of the box, I'd say we can't insert a "/tpc/" in the middle of URLs like this. We can probably somehow cheat with some ProxyPass or RewriteRule trickery, but it's not really elegant. If the aim is to make things simpler & easier to find, a single domain like perlconference.org to host all these newly branded conferences seems the most obvious way to go. Act being Act, we need a dedicated subdomain. For example: - act.perlconference.org - the.perlconference.org - my.perlconference.org Then next year's editions would have the following URLs: http://the.perlconference.org/tpc-2017-amsterdam/ http://the.perlconference.org/tpc-2017-detroit/ What do you think? -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. From th.j.v.hoesel at gmail.com Tue Oct 25 22:50:42 2016 From: th.j.v.hoesel at gmail.com (Theo van Hoesel) Date: Tue, 25 Oct 2016 21:50:42 +0100 Subject: [Act] YAPC::Amsterdam In-Reply-To: <706768345.186042091.1477426913431.JavaMail.root@spooler3-g27.priv.proxad.net> References: <706768345.186042091.1477426913431.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: <630B90F0-6BA7-4846-AFC4-25B157EED40F@gmail.com> Hi S?bastien, 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. I've registered http://www.perl.evetns 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 http://www.perl.events would just be a easy way to see what is going on world wide and have a website directly available, without munging on templates. 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. 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 Concerning YAPC::Amsterdam, until mid december, it seems we will work with http://YAPC.Amsterdam After that, we might move to TPC.Amsterdam > On Oct 25, 2016, at 9:21 PM, S?bastien Aperghis-Tramoni wrote: > > Hello, > > Theo van Hoesel wrote: > >> YAPC::Amsterdam a.k.a "The Perl Conference in Amsterdam" >> >> please setup the servers so we can start publishing the website for >> YAPC next year. >> >> it has been discussed with people from TPF and from now on, we'd like >> to use a new 'top-level directory name: /tpc >> sub path: /tpc/amsterdam-2017 >> >> suggested Act-Conference repo: >> https://github.com/Act-Conferences/tpc-2017-amsterdam > > Laurent just created it. I got the message from GitHub, indeed >> other conferences will follow that pattern. No longer will "The Perl >> Conference" be divided in regions, they will be named with the city >> where it's being held. Much like OSCON. TPF does prefer global >> branding, As does the majority of the Amsterdam organisers. >> >> If, for example the next YAPC::NA would be held in Detroit... it will >> be: "The Perl Conference in Detroit" ... /tpc/detroit-2017 > > "The Perl Conference" sure will be easier to market than "YAPC." i love YAPC.Amsterdam,. The Perl Conference > However, a piece of information missing in your email is the domain > which should support the conference(s). Also, out of the box, I'd > say we can't insert a "/tpc/" in the middle of URLs like this. that was a mistake from my side: /tpc-2017-amsterdam > We can probably somehow cheat with some ProxyPass or RewriteRule > trickery, but it's not really elegant. > > If the aim is to make things simpler & easier to find, a single > domain like perlconference.org to host all these newly branded > conferences seems the most obvious way to go. > > Act being Act, we need a dedicated subdomain. For example: > - act.perlconference.org > - the.perlconference.org > - my.perlconference.org > > Then next year's editions would have the following URLs: > http://the.perlconference.org/tpc-2017-amsterdam/ > http://the.perlconference.org/tpc-2017-detroit/ > > What do you think? that does look nice > > -- > S?bastien Aperghis-Tramoni Thanks for responding so fast this time!!!! Theo > > Close the world, txEn eht nepO. > _______________________________________________ > Act mailing list > Act at mongueurs.net > http://listes.mongueurs.net/mailman/listinfo/act -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan at dwright.org Wed Oct 26 00:50:44 2016 From: dan at dwright.org (Daniel Wright) Date: Tue, 25 Oct 2016 18:50:44 -0400 Subject: [Act] YAPC::Amsterdam In-Reply-To: <706768345.186042091.1477426913431.JavaMail.root@spooler3-g27.priv.proxad.net> References: <706768345.186042091.1477426913431.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: <23883CF5-6DA1-4740-93D1-BB2F9ADCEE18@dwright.org> > On Oct 25, 2016, at 4:21 PM, S?bastien Aperghis-Tramoni wrote: > > If the aim is to make things simpler & easier to find, a single > domain like perlconference.org to host all these newly branded > conferences seems the most obvious way to go. > > Act being Act, we need a dedicated subdomain. For example: > - act.perlconference.org TPF currently owns perlconference.{com|net|org|us} If you?d like, I can delegate act.perlconference.org to your nameservers, or you can provide the IP address and I can point it your way. -Dan -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From sebastien at aperghis.net Mon Oct 31 21:20:29 2016 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Mon, 31 Oct 2016 21:20:29 +0100 (CET) Subject: [Act] YAPC::Amsterdam In-Reply-To: <23883CF5-6DA1-4740-93D1-BB2F9ADCEE18@dwright.org> Message-ID: <1042457097.228996766.1477945229744.JavaMail.root@spooler3-g27.priv.proxad.net> Daniel Wright wrote: > S?bastien Aperghis-Tramoni wrote: > > > If the aim is to make things simpler & easier to find, a single > > domain like perlconference.org to host all these newly branded > > conferences seems the most obvious way to go. > > > > Act being Act, we need a dedicated subdomain. For example: > > - act.perlconference.org > > > > TPF currently owns perlconference.{com|net|org|us} > > > If you?d like, I can delegate act.perlconference.org to your > nameservers, or you can provide the IP address and I can point it > your way. If I understand Theo's plan correctly, yes, please setup act.perlconference.org as a CNAME to conferences.mongueurs.net. This record is itself a CNAME to the current server, spectre, but we will Very Soon migrate Act to the new server, phantom. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. From sebastien at aperghis.net Mon Oct 31 23:34:02 2016 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Mon, 31 Oct 2016 23:34:02 +0100 (CET) Subject: [Act] YAPC::Amsterdam In-Reply-To: <1042457097.228996766.1477945229744.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: <1138398773.229681226.1477953242455.JavaMail.root@spooler3-g27.priv.proxad.net> The repository for The Perl Conference 2017 in Amsterdam is available: ? https://github.com/Act-Conferences/tpc-2017-amsterdam The test site is online: ? http://test.mongueurs.net/tpc-2017-amsterdam/ -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO.