[yapc] YAPC::NA SOLD OUT!!!

JT Smith admin at yapcna.org
Mon Apr 30 11:36:35 PDT 2012

> This, and your other comments, should have been in the blog post.
> That's what I was originally asking for - clarification. The fact that we
> hard to work hard to get your rationale out of you was the thing that bothered
> me.


> But genuine communication about decisions being taken and the reasons
> why hasn't been as prevalent.

My guess is that very few care about why, and I'm happy to answer if they do care. I haven't been shy at all about responding to anyone that asks anything. But I will try to do better for getting out "why" as we move forward.

> Had your blog post said "we're calling it for the moment because we want to
> ensure attendee experience - while we may be able to get a larger room for
> some things or a second room, the dinner simply can't be scaled any further
> and that's true of many other activities. But please watch this space for
> further news, we're working on something that will be of great interest to
> those of you who've missed out but we aren't quite ready to announce it"
> I'd've been applauding you.

Ok. I'll make a mental note about that for other announcements. 

> If you go back and update it, I'll be applauding you.

I've updated the original blog post, but that won't update all the various places it's syndicated to.

> "Sold out" at 411 attendees in a location big enough overall (I know that
> you only have a small subset of it) that I'm getting comments along the
> lines of "I'm mystified as to how one sells out a vanue that size without
> bringing in 10k people or so" needed an explanation.
>> Change is tough. I don't think the changes are we've made are so sweeping that it will be a bad conference, but I am willing to risk it because I think its time for YAPC to evolve.  Perl has evolved dramatically in the past few years, but YAPC has largely remained the same. I'm happy to take full responsibility for it. =)
> I respect that. I'm saying that the brevity of the post doesn't strike me
> as good promotion, and that while you're convinced that the things you're
> doing are the right thing to do, you don't seem to be being very successful
> at promoting those changes to the core community, and given you seem to be
> doing so well at promoting the conference overall that seems like it must be
> an omission rather than a capability problem - so speaking up so the omission
> can be fixed seemed like a good idea.

Fair enough.

>> If you really don't want to come to YAPC because you think we're doing a bad job, I'm sorry to hear that. I'm certainly willing to take you off the speaking schedule if you decide you don't want to come because you don't think it's going to be fun. I certainly wouldn't want you to feel obligated to come.
> If I'd decided I didn't want to come, I would have said that.


> -- 
> Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue
> http://shadowcat.co.uk/blog/matt-s-trout/   http://twitter.com/shadowcat_mst/
> Email me now on mst (at) shadowcat.co.uk and let's chat about how our Catalyst
> commercial support, training and consultancy packages could help your team.

More information about the yapc mailing list