• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Managing Modules Without Going Crazy (NPW 2007)
 

Managing Modules Without Going Crazy (NPW 2007)

on

  • 4,743 views

How to be the maintainer of many modules without killing yourself, being divorced, or eaten by starved house cats

How to be the maintainer of many modules without killing yourself, being divorced, or eaten by starved house cats

Statistics

Views

Total Views
4,743
Views on SlideShare
4,742
Embed Views
1

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Managing Modules Without Going Crazy (NPW 2007) Managing Modules Without Going Crazy (NPW 2007) Presentation Transcript

    • Managing Modules Without Going Crazy brian d foy Nordic Perl Workshop 2007
    • Just Get Work Done
    • Less time maintaining modules Fewer complaints More time doing anything else Learn to live with “Good Enough” Have a life
    • ß
    • Just be yourself Don’t follow the leader (not even me) Finished work is the priority Playing with new tools is not the goal
    • Maintain modules Don’t spend time maintaining maintenance Avoid sysadmin monkey work Make reports, do meta-checks Script releases Use developer releases
    • Use old tools New OS’s / distros are nice, but generally a waste of time Same with new tools Don’t upgrade until you need to Don’t get rid of something that works
    • Avoid non-module work Don’t spend your time being a sysadmin Schemas come later Tolerate shaggy yaks Feeling good vs. useful work
    • Don’t let others host it Individuals, that is Avoid single points of failure Use Sourceforge, Google Project Hosting, et alia
    • Makemaker Module::Build has some problems Module::Build is not core Most people don’t need anything fancy Who cares what Schwern says? :) Unfortunately, Makemaker breaks a lot now
    • Avoid dependencies Code re-use is good You can go to far, e.g. Class:: If When dependencies break, so do your modules
    • Delete old versions Keep old versions out of user’s reach http://pause.perl.org Everything kept on BackPAN (backpan.cpan.org)
    • Scripted checks Automatically monitor module health Periodic smoke tests Nightly reports
    • Scripted releases Do everything the same way Check for common problems Have a consistent process
    • Module::Release • Won’t release anything until all checks pass • Checks... • test, disttest • kwalitee • VCS status • anything else you like • Uploads to right places
    • Developer releases $VERSION ends in /_d+z/ PAUSE won’t index CPAN tools won’t install Still in CPAN Search (http://search.cpan.org)
    • Changes files Avoid questions from users New features Fixes to bugs Should I upgrade?
    • CPAN Testers http://testers.cpan.org Almost every platform / Perl version Sometimes broken, but don’t sweat it
    • RT rt.cpan.org A pain, but adequate Collect all comments in one place Mention ticket numbers in Changes
    • The End