Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up for free
Start Contributing to Perl, It's Easy!
Augustina Ragwitz
July 24, 2013
How-to & DIY
0
890
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
micro:bitでオタマトーン
keicafeblack
0
480
2022.10.23 メタル #スタックチャン を作ってみた。
mongonta0716
0
490
iPaaSでコードを書かずに"ちゃんとLINE Bot"を作る #linedc
n0bisuke2
1
980
Consommation électrique du foyer
melix
0
120
JWCについてのご意見
bigtree
0
210
ITエンジニアのための正しい手斧の投げかた
dominion525
2
300
イベント参加者向けVRChatガチ初心者ガイド / VRChat for ultra beginner
chitose_snn
2
590
意思決定と多様性から紐解く古典的ファシリテーションと心理的安全性
sobarecord
0
190
Selbstverwaltung und Zeitplanung
ddeimeke
0
3.8k
一人ひとりがオーナーシップを持って開発できるチームを目指して
kuroppe1819
5
32k
コーチズクリニック活用のススメ / スクフェス札幌 2021 / coaches clinic
spring_aki
PRO
2
1.8k
ヤフオクで原付買った話
arkw
0
110
Featured
See All Featured
No one is an island. Learnings from fostering a developers community.
thoeni
12
1.5k
Code Reviewing Like a Champion
maltzj
508
38k
Documentation Writing (for coders)
carmenintech
51
2.9k
Rails Girls Zürich Keynote
gr2m
87
12k
Adopting Sorbet at Scale
ufuk
65
7.8k
5 minutes of I Can Smell Your CMS
philhawksworth
198
18k
Building Applications with DynamoDB
mza
85
5k
Debugging Ruby Performance
tmm1
67
11k
Put a Button on it: Removing Barriers to Going Fast.
kastner
56
2.5k
Clear Off the Table
cherdarchuk
79
290k
JazzCon 2018 Closing Keynote - Leadership for the Reluctant Leader
reverentgeek
175
9.1k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
318
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