php/archived-presentations
1
0
Fork 0
mirror of https://github.com/php/presentations.git synced 2026-03-23 23:22:22 +01:00
Code Issues Packages Projects Releases Wiki Activity

slides from the PEAR talk at ossbarcamp in Dublin, Ireland on Sat 19th this month

Browse Source
This commit is contained in:
Ken Guest
2009-09-22 23:10:12 +00:00
parent a7c342d140
commit b62bc281d2
13 changed files with 181 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
ossbarcamp2009.xml Normal file
View File

@@ -0,0 +1,29 @@
<presentation
jskeyboard="1"
template="php"
logo1="/images/pear.png"
logoimage1url="http://pear.php.net/"
navbarbackground="#339900"
backgroundcol="#f0f0f0"
navsize="1.4em">
<topic>PEAR</topic>
<title>PEAR</title>
<event>OSSBarCamp</event>
<location>Dublin</location>
<date>September 19, 2009</date>
<speaker>Ken Guest</speaker>
<email>kguest@php.net</email>
<url>http://pear.php.net/</url>
<slide>slides/ossbarcamp2009/titlepage.xml</slide>
<slide>slides/ossbarcamp2009/intro.xml</slide>
<slide>slides/ossbarcamp2009/consumers.xml</slide>
<slide>slides/ossbarcamp2009/packages.xml</slide>
<slide>slides/ossbarcamp2009/tools.xml</slide>
<slide>slides/ossbarcamp2009/installer.xml</slide>
<slide>slides/ossbarcamp2009/qualityassurance.xml</slide>
<slide>slides/ossbarcamp2009/whyusepear.xml</slide>
<slide>slides/ossbarcamp2009/contributing.xml</slide>
<slide>slides/ossbarcamp2009/support.xml</slide>
<slide>slides/ossbarcamp2009/resources.xml</slide>
<slide>slides/ossbarcamp2009/contact.xml</slide>
</presentation>

15
slides/ossbarcamp2009/consumers.xml Normal file
View File

@@ -0,0 +1,15 @@
<slide title="are you a PEAR consumer?">
<blurb>
A lot of solutions written in php use pear components - so you might be using
PEAR as a consumer already.
</blurb>
<list>
<li>phpmyadmin: Spreadsheet_Excel_Writer and PEAR_SOAP</li>
<li>mediawiki: Text_Diff</li>
<li>egroupware: HTTP_WebDAV, Net_IMAP</li>
<li>gallery2: HTML_Safe, Mail_Mime</li>
<li>magento uses pear to update the system and manage plugins</li>
<li>symfony does similar</li>
<li>horde</li>
</list>
</slide>

8
slides/ossbarcamp2009/contact.xml Normal file
View File

@@ -0,0 +1,8 @@
<slide title="Contacting me">
<list fontsize="5em" effect="slide">
<bullet>blog: http://blogs.linux.ie/kenguest</bullet>
<bullet>twitter: @kenguest</bullet>
<bullet>facebook: /kenguest</bullet>
<bullet>email: kguest@php.net</bullet>
</list>
</slide>

11
slides/ossbarcamp2009/contributing.xml Normal file
View File

@@ -0,0 +1,11 @@
<slide title="Contributing">
<list>
<bullet>log a bug report</bullet>
<bullet>submit patches (even better - include unit tests!)</bullet>
<bullet>writing docs </bullet>
<bullet>writing new packages (formal process; proposal, review etc)</bullet>
<bullet>peer review during the entire process</bullet>
<bullet>translate documentation</bullet>
<bullet>show appreciation: buy items off developers wishlists!</bullet>
</list>
</slide>

28
slides/ossbarcamp2009/installer.xml Normal file
View File

@@ -0,0 +1,28 @@
<slide title="The Installer">
<blurb>
why deploy code via a pear installer?
</blurb>
<list>
<bullet>
imagine a new release of a package you've bundled comes out fixing a critical
security issue.</bullet><bullet> Do you tell your users/customers to copy files on top of others
and risk things being done incorrectly...
</bullet><bullet>...or just do $pear upgrade package-1.01 ?
</bullet>
<bullet>
you can use the pear installer for deploying your own applications and
packages.
</bullet>
</list>
<blurb>
why not rpm or deb or....just include everything in one big archive
</blurb>
<list>
<bullet>pear packages are operating system agnostic</bullet>
<bullet>have a 'state' indicating maturity (devel/alpha/beta/stable)</bullet>
<bullet>have release version numbers </bullet>
<bullet>contain examples, unit tests, documentation</bullet>
<bullet>the installer handles interdependencies</bullet>
</list>
</slide>

9
slides/ossbarcamp2009/intro.xml Normal file
View File

@@ -0,0 +1,9 @@
<slide title="What is PEAR?">
<list fontsize="5em" effect="hide">
<bullet>PHP Extension Application Repository</bullet>
<bullet>a collection of PEAR 'packages' (over 500 packages from the main channel) </bullet>
<bullet>a package installer</bullet>
<bullet>a coding standard</bullet>
<bullet>a community</bullet>
</list>
</slide>

15
slides/ossbarcamp2009/packages.xml Normal file
View File

@@ -0,0 +1,15 @@
<slide title="Packages">
<blurb>there are other well used packages...</blurb>
<list>
<li>HTTP_OAUTH</li>
<li>services_digg</li>
<li>services_twitter</li>
<li>mail_queue</li>
<li>validate</li>
</list>
<blurb>
have a look at pear.php.net
</blurb>
</slide>

11
slides/ossbarcamp2009/qualityassurance.xml Normal file
View File

@@ -0,0 +1,11 @@
<slide title="Quality Assurance">
<blurb>
there's a PEAR quality assurance team
</blurb>
<list>
<bullet>can pull 'dodgy' releases</bullet>
<bullet>can force releases left abandoned by their authors</bullet>
<bullet>advise developers re APIs, architecture etc</bullet>
<bullet>code has to conform to PEAR coding standards</bullet>
</list>
</slide>

11
slides/ossbarcamp2009/resources.xml Normal file
View File

@@ -0,0 +1,11 @@
<slide title="Resources">
<list fontsize="5em" effect="slide">
<bullet>http://go-pear.org/</bullet>
<bullet>http://pear.php.net/support/</bullet>
<bullet>PEAR Installer Manifesto by Greg Beaver</bullet>
<bullet>http://www.packtpub.com/PEAR-Installer/book</bullet>
<bullet>http://pear.php.net/manual/</bullet>
<bullet>http://pear.php.net/manual/en/installation.shared.php</bullet>
<bullet>http://pear.php.net/manual/en/installation.cli.php</bullet>
</list>
</slide>

10
slides/ossbarcamp2009/support.xml Normal file
View File

@@ -0,0 +1,10 @@
<slide title="Support and Community">
<list fontsize="5em" effect="slide">
<bullet>irc: #pear on efnet</bullet>
<bullet>pear.php.net</bullet>
<bullet>mailing lists</bullet>
<bullet>http://pear.php.net/support/</bullet>
<bullet>twitter: @pear (not a support channel!)</bullet>
<bullet>facebook: pear</bullet>
</list>
</slide>

3
slides/ossbarcamp2009/titlepage.xml Normal file
View File

@@ -0,0 +1,3 @@
<slide template="titlepage" fontsize="6em">
<title>Welcome!</title>
</slide>

19
slides/ossbarcamp2009/tools.xml Normal file
View File

@@ -0,0 +1,19 @@
<slide title="Tools for the PHP Developer">
<blurb>a number of tools for the php developer are available through
PEAR:</blurb>
<list>
<bullet>php_codesniffer (conformance to Coding Standards)</bullet>
<bullet>PhpDocumentor (generate documentation)</bullet>
<bullet>php_uml (analyse code, generate UML)</bullet>
</list>
<blurb>
and on other pear channels:
</blurb>
<list>
<bullet>phpunit.de/phpunit (unit testing)</bullet>
<bullet>phpunit.de/phpcpd (tool for spotting when to refactor)</bullet>
<bullet>phpunit.de/phploc (stats)</bullet>
<bullet>pear.pdepend.org/PHP_Depend (metric tool)</bullet>
</list>
</slide>

12
slides/ossbarcamp2009/whyusepear.xml Normal file
View File

@@ -0,0 +1,12 @@
<slide title="Why Use PEAR Packages?">
<list>
<bullet>'framework agnostic' - you can use it anywhere. Why reinvent the wheel?</bullet>
<bullet>use a package that does exactly what you want</bullet>
<bullet>find one that almost suits and add the missing functionality</bullet>
<li>You don't have to write the code yourself</li>
<li>Commercial friendly OSS licenses</li>
<li>A community of developers to rely on, instead of a single person</li>
<li>Classes for common tasks that can be used without pulling in an entire
framework</li>
</list>
</slide>