Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Start Contributing to Perl, It's Easy!
Search
Augustina Ragwitz
July 24, 2013
How-to & DIY
0
900
Start Contributing to Perl, It's Easy!
OSCON slide deck
Augustina Ragwitz
July 24, 2013
Tweet
Share
More Decks by Augustina Ragwitz
See All by Augustina Ragwitz
Start Contributing to Perl, It's Easy!
missaugustina
3
230
Other Decks in How-to & DIY
See All in How-to & DIY
IoTカーテンオープナー
keicafeblack
0
150
TOMARIGI
bigtree
1
2.5k
JAWS-UG勉強会オンライン配信事情
awsjcpm
1
130
ITエンジニアにおすすめのゲームFactorio御紹介
zembutsu
PRO
1
590
元SREのCREが伝えたい、Mackerelをもっと活用するための実践Tips集 / Mackerel Drink Up #11 do-su-0805
dosu0805
0
120
Zeitplanung und Selbstmanagement
ddeimeke
0
340
The story of repairing my junk keyboard with The kinT keyboard controller
kurotaky
0
1.2k
一番やさしいDJ入門 2024
stefafafan
6
1.4k
スターバックスの黒板アートを生成AIで描かせてみたら...
scbc1167
0
220
即納モデルとの戦い
ragemax
0
270
まだまだダンボールスタックチャンv2
syumme01
0
1.7k
面接で伸びしろを感じさせる方法 / How to make the interviewer feel like you have potential
uenitty
1
370
Featured
See All Featured
Fashionably flexible responsive web design (full day workshop)
malarkey
398
65k
How to train your dragon (web standard)
notwaldorf
73
5.2k
Unsuck your backbone
ammeep
663
57k
A Philosophy of Restraint
colly
197
16k
The Cult of Friendly URLs
andyhume
74
5.7k
We Have a Design System, Now What?
morganepeng
43
6.7k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
187
16k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
116
18k
A designer walks into a library…
pauljervisheath
200
23k
Become a Pro
speakerdeck
PRO
11
4.5k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
19
1.7k
Reflections from 52 weeks, 52 projects
jeffersonlam
345
19k
Transcript
Start Contributing to Perl, It's Easy!
Augustina Ragwitz
[email protected]
irc.perl.org: auggy freenode irc: mmmpork twitter: @mmmpork
Perl Wants You!
Open Source Software is “Free!”
Open Source is like Public Radio (well... more like Public
Access TV)
Want to pay your dues? Contribute!
Start Small
Small Code Patches
Documentation
Unit Tests
Learn the Process
New Code means New Context
Don't be intimidated no one is judging you
PEOPLE make up communities
Talk to the community
irc.perl.org #p5p #perl-help
Why do we need this talk?
Tribal Knowledge
Where can I contribute to Perl?
Perl Core a.k.a. Perl 5 Porters
dev.perl.org #p5p on irc.perl.org
[email protected]
Pumpkings
AKA Sucker of the Moment “I was told there would
be pumpkin pie!”
Submit a patch, become immortal!
Perl Core != C programming
Documentation
Patch supporting scripts
Improve unit test coverage
Check RT for bugs http://rt.perl.org
Whoa! A To-Do List! Porting/todo.pod
How to submit a patch: http://perldoc.perl.org/perlhack.html
Perlbug utility + helpful tips http://perldoc.perl.org/perlbug.html
The CPAN Comprehensive Perl Archive Network
AKA The Place Where Modules Live
MetaCPAN http://www.metacpan.org
PAUSE Perl Authors Upload Server http://pause.perl.org
CPAN Testers Test all the Modules on all the Perls
http://www.cpantesters.org
Cool Stats! http://stats.cpantesters.org
How can I contribute to CPAN?
File a bug
Struggled to use a module? Improve documentation!
Especially if the author helped you!
Did you change anything to make it work? Submit the
patch!
How to submit a patch to CPAN
Disclaimer: TIMTOWTDI
Step One: Get the source code
Check Metacpan Repository Information
Check the Module documentation
Last Resort: Download the tarball
Git::CPAN::Patch
Step Two: Hack, Hack, Hack
Step Three: Submit the patch
Has the author specified a bugtracker?
Examples: Github Bitbucket Sourceforge
GitHub http://www.github.com Make a “Pull Request”
If not, use RT http://rt.cpan.org
Send an email to RT and attach your patch
[email protected]
Use RT if: Author says to or No bugtracker information
How do I know my patch was submitted?
RT responds with an email
GitHub shows your pull request
What happens when I submit a patch?
Scenario One: Merged and Released!
Scenario Two: Author responds to bugtracker ticket
What if my patch is rejected? :(
Don't give up!!!
Use the author's feedback to fix your patch
What if the author doesn't respond... AT ALL!?
[email protected]
FORK!
How do I write a patch that's likely to get
merged?
Don't submit a large, complex patch Each issue gets its
own commit
Write clear commit messages
Be consistent with the author's style
Update documentation
Write tests
Include a changelog entry
Collaboration is FUN!
Q&A