genehack

# The Standards of Conduct for YAPC::NA 2014

It appears the most common complaint about the Code of Conduct and the 
ensuing events at YAPC::NA 2013 was about the meta-conversation about 
the Code of Conduct at YAPC::NA 2013. As the lead organizer for 2014, 
I would like to make some comments early so as to (hopefully) quell 
this meta-conversation long before anyone has to make a decision to
attend the conference.

1) There will be a Standards of Conduct for 2014. 

genehack

use Filesys::Notify::Simple;
use App::Prove;

use lib qw(lib);

my $watcher = Filesys::Notify::Simple->new([ './lib', './t/lib' ]);
my $prove   = App::Prove->new;

while ( 1 ) {
  $watcher->wait(sub {

genehack

Some concerns about the future of YAPC::NA were recently brought to my attention on IRC. The ensuing discussion revealed some people had valid concerns about the future of Perl conferences and particularly concerning to me, YAPC::NA.

Most of these concerns stem from a lack of supervision of the various organizing groups, and a lack of overall policy direction from the TPF level. Policy decisions (such as, for example, Codes Of Conduct) are left to the individual organizers or organizing groups, who are already overwhelmed with organizing their conference, let alone dealing with all aspects of gender politics in the modern American IT industry. Additionally, I've personally witnessed the inefficient transfer of institutional knowledge when organizing YAPC::NA 2011. I think that with an improved retention of knowledge from one year to another, YAPC::NA conferences could be organized much more effectively.

genehack

[%~
# Some illustrious documentation to get you started:
#
# The macros defined are to generate markup to save people from copy and pasting
# markup. They copy and paste hashes instead, which should be safer (in theory)
#
# The macros for forms are:
#  * text_field - A text field
#  * textarea_field - A textarea field
#  * password_field - A password field, text_field({ type => 'password', ... })