perigrin

CmdUtils.CreateCommand({
  name: "delicious",
  description: "It is equivalent to the Delicious.com bookmarklet.",
  icon: "http://delicious.com/favicon.ico",
  homepage: "http://www.makadia.com",
  author: { name: "Svapan Makadia", email: "codewzrd@hotmail.com"},
  help: "If you select some text, it will be placed in the notes field.",
  
  preview: "Bookmark the current page to Delicious.com",

perigrin

# $ tweet Hi mom!
#
# Put this in ~/.bashrc or wherever.
# If it doesn't work, make sure your ~/.netrc is right
#
# (Thanks to @anildigital and @grundprinzip for curl-fu)

function tweet {
  curl -n -d status="$*" https://twitter.com/statuses/update.xml --insecure &> /dev/null
  echo "tweet'd"

perigrin

=pod

=head1 NAME

Moose::Manual::Contributing - How to get involved in Moose

=head1 GETTING INVOLVED

Moose is a pretty open project and we are always willing to accept bug fixes,
more tests and documentation patches. Commit bits are given out freely, and

perigrin

New branching layout for Moose/Class-MOP

main branches:

master
stable
branches
topics

people:

perigrin

import os

PATCHIDCACHE={}
def getpatchid(commit):
    if commit in PATCHIDCACHE:
        return PATCHIDCACHE[commit]
    r = os.popen("git-diff-tree -p %s | git-patch-id" % commit).read().strip().split()
    if r:
        PATCHIDCACHE[commit] = r
    return r

perigrin

#!/usr/bin/env python

REPOPATH="/home/andersg/xmms2-mergetest"
OUTPUTFILE="/var/www/git.xmms.se/merge/index.html"
#OUTPUTFILE="/tmp/merge.html"
BASEREMOTE="origin"

BASEBRANCH=BASEREMOTE + "/master"

import os

perigrin

Ach Quiorvoo 1
Aegloegga 8
Aes Kniondoo Eamb 4
Aes Kniondoo Eamb 8
Aesphizz 5
An Knessee Iopr 2
Blagl 1
Blou Omeu 6
Blou Omeu 7
Clui Oapa 6

perigrin

#!/usr/bin/perl
use strict;
use warnings FATAL => qw( all );

use Net::Twitter::Lite;
use Lingua::EN::Inflect qw(NO NUMWORDS);
use HTML::Entities qw(encode_entities_numeric);

use lib '../files/perl/lib';
use Base::Roots qw(get_data data_directory);

perigrin

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 YAPC::NA itself. Most of these concerns stem from a lack of supervision of the various organizing groups, and a lack of overall direction and "steering". Policy decisions (such as Codes of Conduct) are left to the individual organizers, who already have an entire conference let alone having to wade into gender politics in the modern American IT industry. Additionally I've personally witnessed the, inefficient, transfer of institutional knowledge when organizing YAPC::NA 2011.

perigrin

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 Codes Of Conduct) are left to the individual organizers or organizing groups, who are already overwhelming with organizing a 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.