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
JAWS-UGについて JAWS-UG TOHOKU [青森] 弘前開催
awsjcpm
0
230
JAWS-UG会津 & JP Stripes会津 合同勉強会 JAWS-UGとAWSコミュニティプログラムアップデート
awsjcpm
0
120
JAWS-UG Fukuoka - AWS re:Invent 2024 re:Cap AWS Community Perspective
awsjcpm
2
170
さらなるアウトプットに、Let's ライトニングトーク! ― LTのやり方
ma2shita
2
1.4k
チームビルディングを受けてみた
harukahosokawa
3
180
DroidKaigi 2024 - 海外就職というキャリアの選択肢
iyotetsuya
1
1k
「無理」を「コントロール」するスキル / Skills to Control "Muri"
hageyahhoo
6
2.9k
骨折と入院とIoT #iotlt
n0bisuke2
1
350
Within the team, I grow as a tester and continuously pursue product quality
camel_404
7
2.6k
QFHアンテナを作ってみた、 それとパッチアンテナ
takurx
1
180
JAWS-UG/AWSコミュニティプログラムのご紹介 - JAWS-UG 佐賀
awsjcpm
2
160
バッドプラクティスから学ぶハワイアン航空で行く re:Invent
kentosuzuki
0
360
Featured
See All Featured
Documentation Writing (for coders)
carmenintech
73
5k
Why Our Code Smells
bkeepers
PRO
339
57k
Automating Front-end Workflow
addyosmani
1370
200k
Speed Design
sergeychernyshev
32
1.1k
Code Reviewing Like a Champion
maltzj
525
40k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
27k
The Pragmatic Product Professional
lauravandoore
36
6.8k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
13k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
29
1.9k
How GitHub (no longer) Works
holman
315
140k
The Invisible Side of Design
smashingmag
301
51k
The Illustrated Children's Guide to Kubernetes
chrisshort
48
50k
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