[yapc] YAPC::NA::2006 wiki down?
cbrandt at buffalo.edu
Mon May 21 09:54:59 PDT 2007
I'm going to encourage future YAPC's to take advantage of the generosity
of the Act! developers and use their hosting. The system is improving
all the time and it is convenient for people who attend multiple YAPCs
since their login will be used across the systems.
WRT the URLs and DNS issues, there were some good ideas posted. I'd like
to invite folks to the YAPC BOF and we'll try to come up with a sensible
plan to get this squared away:
I agree that it would be nice to offer names off yapc.org rather than
having groups go get custom URLs for each conference.
WRT older conference content, my goal with old content has been to shut
down sites some time after the conference (specifically wikis) and
archive the content on yapc.org. Old YAPC::NA sites are available via
links on each subsequent year's site. Chicago was hosted a bit
different, so I'm still getting the archived content put up on yapc.org.
However, when this is complete the wiki won't be live for Chicago.
For Act-hosted conferences, I believe the content will continue to be
available after the conference.
Back to the original question, what do you need off the YAPC Chicago wiki?
Tatsuhiko Miyagawa wrote:
> On 5/18/07, Uri Guttman <uri at stemsystems.com> wrote:
>> variations we want. then finding the yapc wiki from any year/place will
>> be easier. even if the actual hosting is different we should have a
>> standard way to make a url for any yapc and link to its main page, wiki,
> I'm more interested in the actual hosting bit. To me it appears that
> this year Vienna and Houston share the Act database and allows users a
> single-sign on. (correct?)
> In 2006 we thought about how to build our site for YAPC::Asia and
> chose Movable Type as its backend, since at that time Act was not
> really open-source, and the website designer in our team and I both
> work for the comapny behind MT (Six Apart).
> But sharing Act instance in all of YAPCs would give lots of benefits
> to organizers and attendees. No reinvenrtion of wheel (like I created
> timetable HTML generator and iCal feed using MT plugin) and no
> duplicated authentication. If I'm going to host YAPC::Asia for 2008
> (which at this point I can't say anything about) I'd definitely look
> into using Act, either running it on our own server or sharing the
> Even if we host Act on our own, sharing user auth using external API
> like TypeKey or BitCard protocol would be quite nice.
The Perl Foundation
email: cbrandt at perlfoundation.org
IM: cbrandtbuffalo at mac.com
More information about the yapc