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
3ヶ月でできる! 探査機自作ゼミ教材自作入門
sksat
6
2.6k
Terra Charge|普通充電器ご利用ガイドブック / Terra Charge Ordinary Charger Guidebook
contents
1
310
GPT-4oに遅刻理由を考えてもらうボタン #gpt_4o #iotlt #chatgpt
n0bisuke2
0
390
AIをフル活用! 猫版MBTI「CATS診断」 爆速開発の裏側【個人開発のAIツール活用 LT Night 登壇用スライド】
omori0219
0
950
GreenPAK 初心者向けハンズオン資料
aoisaya
2
460
中指立てたか判定IoT #iotlt #p5js
n0bisuke2
0
300
LT(Lightning Talk)のドキドキ感を共有する IoT ぼっとキーホルダ!
scbc1167
0
370
How to get hundreds of organic backlinks through statistics link building
ronishehu
1
270
JAWS-UG山梨第0回 AWSのユーザーコミュニティ支援
awsjcpm
0
170
骨折と入院とIoT #iotlt
n0bisuke2
1
330
静岡県のお相撲さん20240509/sumo_wrestler_from_shizuoka_prefecture_20240509
nicepapa_hirano
0
280
DroidKaigi 2024 - 海外就職というキャリアの選択肢
iyotetsuya
1
950
Featured
See All Featured
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
53
2.9k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
50
5.5k
Mobile First: as difficult as doing things right
swwweet
223
9.7k
Building Flexible Design Systems
yeseniaperezcruz
328
39k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
15
1.6k
Reflections from 52 weeks, 52 projects
jeffersonlam
351
21k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
126
53k
Agile that works and the tools we love
rasmusluckow
329
21k
Visualization
eitanlees
146
16k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
138
34k
Documentation Writing (for coders)
carmenintech
72
4.9k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
229
22k
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