The world of Ruby has little tradition of preserving backward compatibility. Public APIs change frequently, existing code often breaks after an upgrade.
By backporting a gem you can use modern libraries without having to upgrade your Rails or Ruby. Or you might want to port a security patch to a version branch that is no longer maintained by the community.
We're the people behind Rails LTS, so we know about issues of backward compatibility and the idiosyncrasies of old versions of Rails and Ruby. Imagine an office with 12 people spending their day working on apps ranging from Ruby on Rails 2.3 to 4.1, from Ruby 1.8.7 to 2.1: That's us. We've been doing this since 2007 (circa Rails 1.2). We have the longest beard you can grow for this.
We will port almost everything. There are some cases when we will question if a gem is a good candidate for efficient backporting. For example:
Once you commission us, we will backport the gem in its current state. We will not maintain it afterwards, or fix bugs other than bugs introduced by the porting process. However, you can always commission us to port upstream changes later on.
If the gem has tests, we will usually backport them. If the gem has no tests, we might add some if we feel it aids the porting process.
Tell us the gem you'd like us to port and we will send you an offer. Here is what you can expect in terms of cost:
We offer some discounts as well:
We can either e-mail you the files or give you access to a Git remote.
It usually takes us a couple of days or weeks. The exact time depends on the size of the task and our current project load. When you contact us for a quote, we will include information about delivery time.
Please send a message to email@example.com with the following information:
We will reply with additional questions or a quote.