In short: Make an account, email admins and cc author, then shotgun every place the author's likely to see your intent, then wait a few weeks, and if your efforts have been clear, and the author unresponsive, admins will transfer rights to you.
Typically following this procedure results in the original author reacting, and if they don't, then there's nothing wrong or nerve-wracking about a transfer. CPAN has a big body of history pointing to this working just fine.
Besides, if i interpret this right that the number of rubygem admins is low enough that simply handling such a simple matter would be a problem, then you have bigger fish to fry.
----
Edit: Then again, Benjamin admits that his post doesn't solve:
> deal with gems whose owners are AWOL
Which is the real problem, and the solution to which solves pretty much all other cases too.
http://www.cpan.org/misc/cpan-faq.html#How_adopt_module
In short: Make an account, email admins and cc author, then shotgun every place the author's likely to see your intent, then wait a few weeks, and if your efforts have been clear, and the author unresponsive, admins will transfer rights to you.
Typically following this procedure results in the original author reacting, and if they don't, then there's nothing wrong or nerve-wracking about a transfer. CPAN has a big body of history pointing to this working just fine.
Besides, if i interpret this right that the number of rubygem admins is low enough that simply handling such a simple matter would be a problem, then you have bigger fish to fry.
----
Edit: Then again, Benjamin admits that his post doesn't solve:
Which is the real problem, and the solution to which solves pretty much all other cases too.