A Fresh Cup is Mike Gunderloy's software development weblog, covering Ruby on Rails and whatever else I find interesting in the universe of software. I'm a full-time Rails developer and contributor, available for long- or short-term consulting, with solid experience in working as part of a distributed team. If you'd like to hire me, drop me a line. I'm also the author of Rails Rescue Handbook and Rails Freelancing Handbook.

Navigation
« Double Shot #829 | Main | Double Shot #828 »
Wednesday
Feb292012

Open Source Report #6

So…I have in fact been sticking to my "do something for open source every day" resolution. What I haven't managed to do is keep up these blog entries about it! Well, time for a reset. Here's a fast list of what I've done the past few weeks, and perhaps I can get back to more regular posting next week.

  • More cleanup work on the RubyGems Guides.
  • Got my Shoehorn gem for Shoeboxed integration building on my continuous integration server.
  • Contributed a tiny bit of code and some troubleshooting to axlsx.
  • Fixed a typo in the authlogic documentation.
  • Kept up with the weekly edge Rails postings (and I'm pursuing another opportunity in connection with this; stay tuned).
  • Decided I was barking up the wrong tree entirely with larkistrano, and killed off the project. Going to rethink this and maybe try again.
  • Documented the :inverse_of option for associations for the Rails Guides.
  • Did an editing pass over the Updating Rails guide.
  • Posted details on using Mercury editor, Carrierwave, and Amazon S3 together.
  • Fixed a path issue in sublime_guard.
  • Forked the feed-normalizer gem to make it a bit more resilient in the face of unparseable HTML.
  • Fixed a parsing issue in the Command Reference in RubyGems Guides.

If you're trying to figure out how to contribute to open source yourself, you could always start with a search on GitHub. Or try OpenHatch.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>