Slides from our Newer Yankee Workshop "Build-a-Gem" session.

1. Newer Yankee Workshop Build-a-Gem

3. Packaged Following a Convention

4. Python Eggs, Perl CPAN Modules, PHP PEAR Packages

6. DRY

7. Version control across different project

9. Always have test coverage

10. Write your README (README.rdoc)

11. Expose commit history (github is most common)

12. Good documentation – RDOC

13. Versions 0.0.0 (major, minor, patch)

14. Use pre for Prereleases ( 0.1.0pre1 )

16. But... we'll be using Jeweler http://github.com/technicalpickles/jeweler

18. github also used to host gems (more confused?)

20. Cache / distribute .gem files – building sometimes makes “binaries” which are system-specific.

22. $LOAD_PATH then require gem

23. require 'rubygems'

24. gem bundler (bundler) - bundler under rapid development!

25. Hello World (simple example followed by nextbus example followed by everyone pairing and gem building)