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
980
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
250
Other Decks in How-to & DIY
See All in How-to & DIY
How to Hire a Driver for Long Distance Travel?
greaterservice
0
170
GreenPAK 初心者向けハンズオン資料
aoisaya
2
460
音に負けない!子どもが騒いでいる脇でも快適オンラインMTGの秘伝
kaitou
0
410
HCIのデモに役立つ映像活用アイデア集 #WISS2024 ナイトセッション #HCIVideoCulture
bonsaistudiojp
2
910
3ヶ月でできる! 探査機自作ゼミ教材自作入門
sksat
6
2.6k
GPT-4oに遅刻理由を考えてもらうボタン #gpt_4o #iotlt #chatgpt
n0bisuke2
0
380
ModuleLLM、最前線!
anoken
0
190
ラズパイカメラ向け ケーブル延長基板・ハウジングの開発
koheimasaki
PRO
1
290
Raspberry Pi Connectを使って #Manus => Node-RED操作チャレンジ #iotlt vol121
n0bisuke2
0
130
苦手の克服方法 / How to overcome weaknesses
toma_sm
0
270
在宅フルリモートワークを可能にするスキルと知識n連発! / how to more effective remoteworking
masaru_b_cl
3
1.1k
ブロックテーマをゴリゴリに使い倒してサイトを作った話 / Kansai WordPress Meetup 2025 01 25
tbshiki
1
560
Featured
See All Featured
Gamification - CAS2011
davidbonilla
81
5.4k
The Language of Interfaces
destraynor
158
25k
It's Worth the Effort
3n
185
28k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
126
53k
Rails Girls Zürich Keynote
gr2m
95
14k
Code Review Best Practice
trishagee
69
19k
The Pragmatic Product Professional
lauravandoore
35
6.7k
Raft: Consensus for Rubyists
vanstee
140
7k
jQuery: Nuts, Bolts and Bling
dougneiner
63
7.8k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
181
54k
Building Better People: How to give real-time feedback that sticks.
wjessup
367
19k
How STYLIGHT went responsive
nonsquared
100
5.6k
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